There are two types of colliders; Box Colliders and Circle Colliders. You can config the colliders width, height and offsets. For Circle Colliders you won't set a radius, instead you configure it if you are making a box and circle will be created inside the box.

Collider Examples:

Setting up Colliders

Colliders are created inside the Players notebox or as a comment inside an Events page. Events colliders depends it's page, so you may need to make the collider on all pages.

Collider (Note Tag)
[code]<collider:type,width,height,ox,oy>[/code]

Type: Set to box or circle.
Width: Set to the width of the box / X Diameter of the circle.
Height: Set to the height of the box / Y Diameter of the circle.
OX: Set to the x offset of the collider relative to it's px value.
OY: Set to the y offset of the collider relative to it's py value.

Collider Definitions:

You can also set up a different collider depending on the direction the character is facing.
[code]<collider>
5: type, width, height, ox, oy
X: type, width, height, ox, oy
</collider>[/code] Where 5 is the default box if a box isn't set for a direction.
And X is the box for that direction.
Direction can be 2, 4, 6 or 8.

Changing Colliders

You can change colliders with event by using a script call or plugin command.
Script Call [code]$gamePlayer.changeCollider(type, width, height, ox, oy);[/code] For Events: [code]$gameMap.event(eventId).changeCollider(type, width, height, ox, oy);[/code]

eventId: The ID of the event.
type: "box" or "circle" **with the Quotes!!**
width: The width of the collider, no quotes
height: The height of the collider, no quotes
ox: The X Offset of the collider, no quotes
oy: The Y Offset of the collider, no quotes

Plugin Call [code]quasi collider id type width height ox oy[/code]

id: Set to 0 for the player or set to the ID of the event.
type: box or circle, no quotes
width: The width of the collider, no quotes
height: The height of the collider, no quotes
ox: The X Offset of the collider, no quotes
oy: The Y Offset of the collider, no quotes

Example 1 Lets give the player a circle collider that's 48x48 [spoiler] [/spoiler] Example 2 Lets give an Event a box collider that's 48x48 [spoiler] [/spoiler] Example 3 Now lets change a players collider using an Event [spoiler] [/spoiler]

Tile boxes are automatically created. Their sizes will also adjust depending on your Tile Size settings. Tile boxes merge will all the tile layers. So if the bottom layer is impassable but the top layer is passable, the whole tile will be impassable. To get around this we can use Region Boxes. Region Boxes take priority over Tile Boxes, therefore we can create a passable region box and place it over an impassable tile to make it passable.

In order to be able to use Region Boxes, you will need to enable the Use Region Boxes setting. Once it's enabled you will need to create a json file called "RegionBoxes.json" inside the JSON Folder you set in the settings.

JSON template (JSON) [code]{ "REGION ID 1": [ {"width": w, "height": h, "ox": ox value, "oy": oy value, "tag": "value"} ], "REGION ID 2": [ {"width": w, "height": h, "ox": value, "oy": value}, {"width": w, "height": h, "ox": value, "oy": value} ] }[/code]

Region ID: The region that will use this box.
Be careful with the commas ( , ) place them after } or ] only if it's not the last one in the list!
The tag field will act like notetags for regions. This will allow me to treat regions differently depending on the tag if needed.

Few tags [code]<counter> <bush> <ladder> <damage>[/code]

* You can use more then one tag, just keep it inside the "" quotes!

Ex: "<bush><damage>"

Example JSON File.
https://gist.github.com/quasixi/ff149320fd6885191d87

If you don't want your tile collisions to be all boxes and have unique shapes, you can use Collision Maps. Collision Maps will overlay Tile Boxes, so if you don't want conflicting Tile Boxes, make the whole map passable by either editing the tiles passability in the Tileset Editor, or use a passable Region. Region Maps are an extra tool for developers and for Region Maps may be used in addons.

Yay Circle collisions complete! #RPGMakerMV pic.twitter.com/KxX4wbAnAO

— Quasi (@QuasiXi) November 5, 2015

Creating Collision Maps / Region Maps

You can create the maps in any image editor you want. For Collisions Maps use the color you set for Collisions in the settings to indicate collisions. You can use any color you want in Region Maps. Place these images in the folder you set in the settings for Collision Map Folder and Region Map Folder

Enabling Collision Maps (Notetag) [code]<cm=filename>[/code] Enabling Region Maps (Notetag) [code]<rm=filename>[/code]

filename: Set this to the name of the image you want to load.
* These notes should be placed inside the Maps Notes found in the Map Properties.

Changing Collision Maps / Region Maps

Change Collision Maps (Script Call) [code]$gameMap.loadCollisionmap("filename");[/code] Change Region Maps (Script Call) [code]$gameMap.loadRegionmap("filename");[/code]

filename: Set this to the name of the image you want to load.
* filename should be wrapped with quotes. * This will replace the current one. * If filename is left empty, collision map will be disabled.

- To Do

Example 1 Set up a map with a collision map with a file name "!CollisionMap" and a region map named "!RegionMap" [spoiler] [/spoiler] Example 2 Lets change the collision map with a script call. [spoiler] First lets have an event that changes the collision map to a collision map named "!CollisionMap2" Now lets change the event so it removes the collision map by not setting a filename. [/spoiler] Example 3 Lets set up a tile collision map [spoiler] First we need a tile collision image inside the tilesets folder. This image needs to be 16x16. So if our tile size is 48x48 then our image needs to be 768x768. Here's my test image I used: I was a bit lazy to do all the tiles, so I only did a few of them for testing. This is a collision map for the Outside_B tiles. Now lets open the Database, open the Tilesets tab, and go to the outside tileset and lets add the collision map. Since this is for a B tile we will use the <cmb:filename> tag. Your result should look like: And that's all! Now go draw some tiles from those b tile location to test! [/spoiler]

Passability levels are a new feature which sets wither a character can walk over water or deep water tiles.

Levels:

• 0 - Default, Can only move on passable tiles
• 1 - Boat, Can only move on water 1 tiles
• 2 - Ship, Can only move on water 1 and water 2 tiles
• 3 - NEW, Can move on passable tiles and water 1 tiles
• 4 - NEW, Can move on passable tiles, water 1 and water 2 tiles

Set default Passability Level for Event(Comment)
[code]<pl:LEVEL>[/code]

LEVEL: Change LEVEL to the passability level you want to set it to.
* Resets on page change.

Changing a Characters Passability Level (Script Call)
[code]$gamePlayer.setPassability(LEVEL);[/code] For Events: [code]$gameMap.event(ID).setPassability(LEVEL);[/code]

ID: The ID of the event.
X: Change LEVEL to the passability level you want to set it to.

Changing a Characters Passability Level (Plugin Command)
[code]quasi setPassability ID LEVEL[/code]

ID: The ID of the event or set to 0 for the player.
LEVEL: Change LEVEL to the passability level you want to set it to.

Check a Characters Passability Level (Script Call)
[code]$gamePlayer.passabilityLevel();[/code] For Events: [code]$gameMap.event(ID).passabilityLevel();[/code]

ID: The ID of the event.
These calls will return the value of their passability level.

Example 1 Lets test out all the different passability levels. [spoiler] First lets create a map with some water and deep water tiles. Should look something like: Now lets create 4 events on the left side of the water and give them passability levels from 1-4. This is how my 1st event looks: I put a move route to have it keep moving right, so we can have it try to walk over the water tiles, and put the frequency at 5 for quicker testing. Our map should now look something like: Add your player starting location to that map, and hit play test! You should only see 2 of the 4 events move. The ones with a passability level of 1 and 2 should be stuck since they can only move on water tiles! Once all the events are done moving, you should see something like: Now lets move the events position so they start on the water. Now play test this and all 4 should now move! Once they stop moving you should see something like: And that's all there is to it! This should help you understand what passability levels are and do. [/spoiler]

Moving characters can be pretty tidious when using pixel movement. So there are a few new functions to make it easier.

* Example of an Event moving 3 tiles left then 3 tiles right.

Script calls for Move Routes

The following should be placed inside the "script..." command in Move Routes.
QMove (Quasi Move) Moves the character X amount of distance, ignores Off Grid setting [code]qmove(direction, amount, multiplicity)[/code]

direction: Which direction the movement should be.
amount: How many times should the player move.
multiplicity: Multiplies amount by this value for easier calculations.

MMove (Multiple Move)
Moves the character X amount of distance, stays on Grid. [code]mmove(direction, amount, multiplicity)[/code]

direction: Which direction the movement should be.
amount: How many times should the player move.
multiplicity: Multiplies amount for easier calculations.
* Directions are 2 (down), 4(left), 6(right), 8(up), 5(forward), 0(backward)

Arcing [code]arc(pivotX, pivotY, deltaRadian, counterClockwise, frames)[/code] or [code]arcTo(charaId, deltaRadian, counterClockwise, frames)[/code]

pivotX: The pixel X location to rotate around.
pivotY: The pixel Y location to rotate around.
charaId: The character Id to rotate around, if Id is 0 it will rotate around the player.
deltaRadian: The distance to travel in the arc in radians ( Default 2 PI ), leave blank, null or false to use default.
counterClockwise: Set to true or false. Default: false
frames: How long should it take to complete the arc.

Initializing Events OX and OY

You can fine tune your events starting location, so they will stand at the pixels you want them to.
Setting initial Offsets (Comments) [code]<ox=X>[/code]

X: Change X to the inital X offset.

[code]<oy=Y>[/code]

Y: Change Y to the inital Y offset.

* Offsets resets on page change.

Jumping

There are two new functions for jumping. A Pixel based jump and a jump forward.

Pixel Jump (Script Call) [code]$gamePlayer.pixelJump(distanceX, distanceY)[/code] For Events: [code]$gameMap.event(ID).pixelJump(distanceX, distanceY)[/code]

ID: The ID of the event.

Jump Foward (Script Call) [code]$gamePlayer.jumpForward(direction)[/code] For Events: [code]$gameMap.event(ID).jumpForward(direction)[/code]

ID: The ID of the event.
direction (Optional): Direction can be 2, 4, 6 or 8.

Example 1 [spoiler] [/spoiler]

Get tile flags [code]$gameMap.flagsAt(x, y);[/code]

x and y default to players x and y

Works best when grid is equal to tile size. The results are logged in the console.

Get color from region map [code]$gameMap.getPixelRegion(x, y);[/code]

x and y default to players center location.

return value is a string of the hex color.

Create a collider [code]var myBoxCollider = new QuasiMovement.Box_Collider(w, h, ox, oy, shiftY);[/code] For circle: [code]var myCircleCollider = new QuasiMovement.Circle_Collider(w, h, ox, oy, shiftY);[/code]

x and y default to players center location.

return value is a string of the hex color.

Moving Colliders [code]myCollider.moveto(x, y);[/code]

Set X and Y in pixel terms.

Also use the variable that you used to make the collider.

Showing Custom collider on map [code]SceneManager._scene.addTempCollider(collider, duration);[/code]

collider: the collider object
duration: the duration it will display

(Only works if you're in Scene_Map!)

Get characters that overlap with a collider [code]$gameMap.getCharactersAt(collider, ignore);[/code]

collider: the collider object
Ignore: a function that returns return to ignore

Returns an Array of characters it overlays.
(Search this plugin for an example usage if needed)

Get map tiles that overlap with collider [code]$gameMap.getTileBoxesAt(collider);[/code]

collider: the collider object

Returns an Array of tilesboxes it overlays.
You will need to manually filter this array because there is no ignore parameter, so it returns all tiles.
(Search this plugin for an example usage if needed)