Tiles, and Events and the Map itself can be configured with various properties to change how they look and behave.
Configurations can be entered into note boxes or event page comments. Tileset and map configurations need to be wrapped in a <mv3d> </mv3d> block (<mz3d> </mz3d> block in Rpg Maker MZ),
<mv3d> configuration configuration </mv3d> <mz3d> configuration configuration </mz3d>
while event configurations need to be inside a <mv3d: > tag (again, <mz3d: > in MZ), be them in the notebox or inside a comment.
<mv3d: configuration, configuration> <mz3d: configuration, configuration>
Configurations are written using “configuration functions”.
A configuration function consists of a name followed by a list of parameters enclosed in parenthesis. The following is an example of a basic configuration function.
Some configuration functions have named parameters which can be used, and some might have parameters separated into groups, separated when setting them up by a | vertical bar. The following are examples of more advanced configuration functions.
MV3D has a Plugin Parameter named “Map Defaults”, set as part of “Map Settings”.
These settings are applied automatically to all maps… unless the map itself has different settings inside a <mv3d> </mv3d> block.
As A3 and A4 tiles are set in pairs vertically, the upper one being the “roof” and the lower one the “wall” itself, the two members of the pair behave differently.
What would in a 2d game be the “roof” tile is set so the top of the wall's block is the original tile, while the sides are its respective wall.
The “wall” tile is by default the same tile on all sides.