Altimit Pixel Movement [0.50β]

xilefian · 2017-10-09T07:24:25+0900

Altimit Movement 0.50 beta This is an open-source project, feel free to clone the repository and make pull requests. About This Plugin replaces the default movement and collision system with vector-based movement and polygon-based collision. I've tried many different pixel-movement Plugin in the past, but have found that each one has a set of corner-cases that causes it to fail or break. As a result, I decided to create my own one with the goal of it being as water-tight as possible. Altimit Movement is designed to be a drop-in replacement for the default movement system. The primary goal of it is to not be "unexpected"; once Altimit Movement is in your project, it should feel like RPG Maker MV has always featured pixel-movement. The goal is for Altimit Movement to be the ultimate pixel-movement Plugin. Web Demo altimit.systems/projects/vectormovement Download Latest Version Download Plugin (Right-click, save-as) View on GitHub Video Features 8 direction movement Custom character hit-boxes Beta Release The beta release is about developing the API, including Plugin parameters and commands. The goal is to bring it up to par with other existing movement Plugins and provide everything needed for developers to create a game using all the features available with the Plugin. Known Issues The latest issues are listed on the project page at the following URL: github.com/AltimitSystems/mv-plugins/issues Feel free to report issues in this thread or create a new issue on the project tracker (label as Altimit Movement). Altimit Movement Debug Altimit Movement has a companion Plugin that can display debug information (shown in the video above). It is available at the following URL: https://github.com/AltimitSystems/mv-plugins/tree/master/movement-debug Like Altimit Movement, this is an alpha release and has its own issue tags and road-map (such as displaying debug collision information for vanilla MV without Altimit Movement).

● ARCHIVED · READ-ONLY

Started by xilefian Oct 8, 2017, 10:24 PM 545 posts Page 16 of 28 View original ↗

Restart

#301 Jan 28, 2020, 04:32 AM Source

That's not the default collider, right? Check to see where the player's .x and .y point is relative to your collider. IIRC it isn't in the exact center by default, which can be confusing.
Skurge

#302 Jan 28, 2020, 06:12 AM Source

I kind of like "followers struggling to follow party leader" in the video, it gives me those nostalgic feels of old games where the A.I would get stuck behind walls and things.
Sir levée

#303 Feb 2, 2020, 05:57 AM Source

Is this plugin still being updated? I've found a few issues. So anyway, The game when using the plugin doesn't read player X, Y position on a map properly and I'll have to pass the center of a tile rather than be occupying the majority grid space of it. The second issue is that when using mouse mode and being transferred to another map the position you pressed last will be passed onto the next area forcing you into moving to the X Y of the last click unless you click somewhere else again.Thirdly, I thought disabling mouse mode after transferring would reset/Remove the last click and be a workaround but was surprised to see it doesn't, and that could become a problem during scenes triggered by touch or coordinates where you keep moving instead of pausing
(EDIT) So first issue still stands but something weirder, The detection grid is off for player X, Y once the plugin is in

An example is that the starting point in the image below is X 21 Y 14 but you are not in those coordinates unless you are actually in the red box
Restart

#304 Feb 3, 2020, 07:38 AM Source
Sir levée said:
Is this plugin still being updated? I've found a few issues. So anyway, The game when using the plugin doesn't read player X, Y position on a map properly and I'll have to pass the center of a tile rather than be occupying the majority grid space of it. The second issue is that when using mouse mode and being transferred to another map the position you pressed last will be passed onto the next area forcing you into moving to the X Y of the last click unless you click somewhere else again.Thirdly, I thought disabling mouse mode after transferring would reset/Remove the last click and be a workaround but was surprised to see it doesn't, and that could become a problem during scenes triggered by touch or coordinates where you keep moving instead of pausing
(EDIT) So first issue still stands but something weirder, The detection grid is off for player X, Y once the plugin is in

An example is that the starting point in the image below is X 21 Y 14 but you are not in those coordinates unless you are actually in the red box

For #1, with Altimit, events triggers work a bit differently.

Player Touch: the player must be fully inside the event before it to be triggered (or the event fully inside the player, if the event collider is smaller than the player's). Think of it as 'overlaps'

Event touch: the event will fire the moment the colliders even slightly touch. Think of it as 'touches'.

I have a fix for #2, or rather, MechPen does
MechPen said:
Changing
Code:
var Game_Player_clearTransferInfo = Game_Player.prototype.clearTransferInfo; Game_Player.prototype.clearTransferInfo = function() { Game_Player_clearTransferInfo.call( this ); this._moveTarget = false; this._moveTargetSkippable = false; };

to
Code:
var Game_Player_clearTransferInfo = Game_Player.prototype.clearTransferInfo; Game_Player.prototype.clearTransferInfo = function() { Game_Player_clearTransferInfo.call( this ); this._moveTarget = false; this._moveTargetSkippable = false; this._touchTarget = null; };

fixes this for any sort of map transition.
You'll probably also want this fix
Restart said:
One problem using mouse movement is that if you define colliders using events, players clicking on that collider will have their destination set to the x,y coordinate of the event's base position, which isn't great.

This tweak to Game_Player.prototype.moveByInput will ignore any characters with no image when deciding on whether to track an event or not, so invisible colliders (and other invisible accessory events) will remain unnoticed by the mouseclick.

Code:
if ( touchedCharacters.length ) { if(!(touchedCharacters[0]._characterName=="")) //ignore characters with no image { // Move toward character characterTarget = touchedCharacters[0]; } }
Sir levée

#305 Feb 3, 2020, 08:38 AM Source

Whoah, Thanks for these gifts, Oh and for issue #1 I'm not using triggers, I'm using a common event that stores X Y in variables then transfers you using a conditional branch by those variables when you've reached the determined edges of the map, so using that I found the grid was off as I would get transfered after having to go too far into a tile when going down and left, and then too soon when going up or right

So all maps are 34x34 with black borders. When Variable "PlayerX" reaches X: 33 it transports the player to the adjacent map but as you can see in the images X doesn't update from X: 32 even though I'm definitely in X: 33, and then it does the same with down, And then I don't have to touch borders on the top or left sides to transfer

The whole Player X,Y detection grid is like its set to 1.5-1.5

Here's another example on a fresh project, Because its shifted Down-right I can enter negative coordinates
Restart

#306 Feb 3, 2020, 04:00 PM Source

Oh yeah RPGM by default doesn't put a character's .x and .y property at the center of a tile even without altimit - IIRC it's based on the top-left. In the base game, if you have Harold standing in the top-left tile he's gonna be recorded at (0,0) and not (0.5,0.5). Altimit doesn't fiddle with that.

You can change the PC's collider and sprite locations so that the (x,y) coordinate for the player is embedded somewhere inside him if you want, but if you're using the same common event it's probably easiest to just experiment with the exact border until the map change looks good.
Sir levée

#307 Feb 3, 2020, 04:53 PM Source

Interesting, Never knew it was like that by default. Thanks for reply and bit of info, I Never would have realized it was like that with only being confined to grid movement. But I'll work with it as is now and see what I can do
MangoFlavour

#308 Feb 13, 2020, 10:30 AM Source

Possibly a dumb question, but what determines whether an Event on the "Same as Player" layer will appear above or below the player? I was thinking redefining the collision box using comments would influence this but I can't get anything to change.

If that's not super clear, I mean when you walk above (north of) an event, the player appears behind/underneath it. And when you're below (south of) an event, you appear in front/above of the event. Do custom collision boxes in this plugin not affect that at all?
Restart

#309 Feb 16, 2020, 05:00 AM Source

MangoFlavour said:
Possibly a dumb question, but what determines whether an Event on the "Same as Player" layer will appear above or below the player? I was thinking redefining the collision box using comments would influence this but I can't get anything to change.

If that's not super clear, I mean when you walk above (north of) an event, the player appears behind/underneath it. And when you're below (south of) an event, you appear in front/above of the event. Do custom collision boxes in this plugin not affect that at all?
I believe the collision doesn't effect it, but it should be easy to test
Crashykk

#310 Feb 21, 2020, 09:09 PM Source

Restart said:
IIRC it's based on the top-left.
Is there a way to change it to middle of a collider somehow?
Restart

#311 Feb 24, 2020, 10:37 PM Source

CrasheR said:
Is there a way to change it to middle of a collider somehow?
Easiest way is to just move the default collider, which you can do in the plugin settings.
Crashykk

#312 Feb 26, 2020, 07:46 AM Source

Restart said:
Easiest way is to just move the default collider, which you can do in the plugin settings.
Tried it. It doesnt work very well if you have ABS in your game. Enemies do some wierd stuff when i recrate colider to the middle of the character sprite and some clisions look very awkward, cuz sprite gets in half in to the objects. :/

Restart

#313 Feb 26, 2020, 03:38 PM Source

yeah you have to move your sprites as well,

Easy way is to use yanfly's event sprite offset, or mog's char poses, or one of the many other plugins for doing it

If you want to roll your own, here's the base code from rpg_objects

Code:

Game_CharacterBase.prototype.screenX = function() {
    var tw = $gameMap.tileWidth();
    return Math.round(this.scrolledX() * tw + tw / 2);
};

Game_CharacterBase.prototype.screenY = function() {
    var th = $gameMap.tileHeight();
    return Math.round(this.scrolledY() * th + th -
                      this.shiftY() - this.jumpHeight());
};

here's the code from altimit that modifies it (and I think this might be the source of the yanfly jitter but heck if I'm diving into that nightmare again once I have a fix that works for me)

Code:

var Game_CharacterBase_screenX = Game_CharacterBase.prototype.screenX;
      Game_CharacterBase.prototype.screenX = function() {
        var round = Math.round;
        Math.round = Math.floor;
        var val = Game_CharacterBase_screenX.call( this );
        Math.round = round;
        return val;
      };

      var Game_CharacterBase_screenY = Game_CharacterBase.prototype.screenY;
      Game_CharacterBase.prototype.screenY = function() {
        var round = Math.round;
        Math.round = Math.floor;
        var val = Game_CharacterBase_screenY.call( this );
        Math.round = round;
        return val;
      };

I think if you replaced the altimit code with something like this

Code:

var Game_CharacterBase_screenX = Game_CharacterBase.prototype.screenX;
      Game_CharacterBase.prototype.screenX = function() {
        var round = Math.round;
        Math.round = Math.floor;
        var val = Game_CharacterBase_screenX.call( this ) - Math.round($gameMap.tileWidth()/2);
        Math.round = round;
        return val;
      };

      var Game_CharacterBase_screenY = Game_CharacterBase.prototype.screenY;
      Game_CharacterBase.prototype.screenY = function() {
        var round = Math.round;
        Math.round = Math.floor;
        var val = Game_CharacterBase_screenY.call( this ) - $gameMap.tileHeight();
        Math.round = round;
        return val;
      };

you'd end up changing the base of the sprite (that is, the middle of the bottom edge) to the exact .x and .y coordinate. Haven't tested it, though.

Honestly I haven't had any issues dealing with the default tile offset, since all the relative math between events is identical.

Crashykk

#314 Feb 26, 2020, 10:21 PM Source

When I touch tile (that has other region) with left side of players collider (doesn't matter where i place it) its automatically thinks i'm at that region number. Even if that tile is not accessible. Thats why i was asking if you can move it from left corner of collider to middle of collider. Im complete noob if we talking about javascript. :(
Ace of Spades

#315 Feb 27, 2020, 02:25 AM Source

CrasheR said:
When I touch tile (that has other region) with left side of players collider (doesn't matter where i place it) its automatically thinks i'm at that region number. Even if that tile is not accessible. Thats why i was asking if you can move it from left corner of collider to middle of collider. Im complete noob if we talking about javascript. :(

I think you're over-complicating things. Instead of moving the colliders, sprites, etc.... just change the value of the X Y coordinates you're getting from the player. Are you currently using Game Variables to determine the X Y coordinate, or are you using scripting? I'm assuming you're using Game Variables if you aren't familiar with js.

Under Control Variable command, you can set two variables: one for PlayerX one for PlayerY.

Control Variable, then select set to Script. Under the scripts fields, use ($gamePlayer.x + 0.5) and ($gamePlayer.y + 0.5) for each variable respectively.

Now those variables will be checking the center of the Collider box, instead of the upper left corner.
So if you want to use another Variable for Player Region, you can set it to Obtain the region ID of the X,Y values we set above.

Hope that made sense, let me know if you have questions.
Restart

#316 Feb 27, 2020, 01:31 PM Source

Why are you using regions with altimit instead of just defining a collider?
Ace of Spades

#317 Feb 27, 2020, 01:49 PM Source

Restart said:
Why are you using regions with altimit instead of just defining a collider?
It looks like he's just using the region ID to determine which tile the player is standing on, not for collision. Almost like a pseudo-elevation system, the player region ID would tell which elevation level the player is standing on. At least that's what it appears as me, I don't want to assume anything. I'm doing something similar with my game, albeit it's a bit more complicated.
Crashykk

#318 Feb 27, 2020, 07:50 PM Source
Ace of Spades said:
Are you currently using Game Variables to determine the X Y coordinate, or are you using scripting? I'm assuming you're using Game Variables if you aren't familiar with js.

Full script calls, 0 variables.

Ace of Spades said:
pseudo-elevation system
Correct.
Code:
$gameMap.regionId($gameMap._events[this._eventId].x, $gameMap._events[this._eventId].y) === $gameMap.regionId($gamePlayer.x, $gamePlayer.y)
For region check.

ABS is based on Script Calls as well. I dont know javascript, but Calls are similar to those from previous makers.
Code:
Math.abs($gamePlayer._y - $gameMap._events[this._eventId]._y) >= 0 && Math.abs($gamePlayer._y - $gameMap._events[this._eventId]._y) <= 1 Math.abs($gamePlayer._x - $gameMap._events[this._eventId]._x) <= 1 && Math.abs($gamePlayer._x - $gameMap._events[this._eventId]._x) >= 0
Fragment of code.

All i want works perfect. Elevation level are determined correctly. The only problem is with that left side of collider. :/
I tried
Code:
$gameMap.regionId($gameMap._events[this._eventId].x, $gameMap._events[this._eventId].y) === $gameMap.regionId($gamePlayer.x - 0.5, $gamePlayer.y)
As well, but game does some wierd stuff.
Ace of Spades

#319 Feb 27, 2020, 08:36 PM Source
CrasheR said:
All i want works perfect. Elevation level are determined correctly. The only problem is with that left side of collider. :/
I tried

Code:
$gameMap.regionId($gameMap._events[this._eventId].x, $gameMap._events[this._eventId].y) === $gameMap.regionId($gamePlayer.x - 0.5, $gamePlayer.y)
As well, but game does some wierd stuff.
View attachment 135405
For your last line of code you posted, you should be adding 0.5 to the player X, instead of subtracting. You'd be doing to same for the event as well (because currently it's checking the upper left most edge of the event instead of the center) You may also need to add 0.5 to the y value, as I suggested.
Code:
$gameMap.regionId($gameMap._events[this._eventId].x + 0.5, $gameMap._events[this._eventId].y + 0.5) === $gameMap.regionId($gamePlayer.x + 0.5, $gamePlayer.y+0.5)
This will check the region ID of the center of the default collier box. Same would apply for events as well. Hope this helps.
Crashykk

#320 Feb 27, 2020, 09:23 PM Source

Ace of Spades said:
This will check the region ID of the center of the default collier box. Same would apply for events as well. Hope this helps.
Works perfect. Thank you very much!