MV3D Layered Tile Configurations

Important:

MV3d and MZ3D had a recent update, at the time of writing to version 7.2
This extension was not tested on those yet.
Also keep in mind, from 7.0 onwards they have a native way to set region configurations per layer...
But not tile configurations, like this one does. And if it still works the same, layered tile configurations overcome the original region ones, meaning you would still need this plugin's region configurations for overcoming those.

Cutievirus' MV3D for RPG Maker MV, and on the same way MZ3D for MZ, is in my opinion a great addition for RPG Maker. Despite still being in development, it allows you to, withing certain limitations of the engine, turn your games into 3d ones.

RPG Maker MZ re-introduced layers (technically they were already in MV, but not controllable to the level MZ allows), thus this extension was tested mostly on MZ.

Layers in MV3D/MZ3D usually only affects one thing: regions only affect tiles on layer 1.

This small extension I made is supposed to change this.

• With the proper notetag, set on the tileset or even on the map, the tile can be rendered on the map differently depending on the layer it is added on.
• You can also make  regions affect other layers too, not just layer 1.
• With how it is coded, tiles set with a different configuration on layer 1 can bypass the changes of the region.  Take advantage of this, or set the regionto affect layer 1 and overwrite even them.

The idea that gave birth to this was so that a wall tile put on layer 2 would be able to be set as with fringe, basically having a set of wall floating above the ground and turning a passage into a doorway.
This is just one idea, but many more can be had.

How to use:

Add the extension plugin on the plugin manager, bellow the actual mv3d or mz3d.

Setting specific tiles:

You can set this for the tiles themselves on either the Tilesets tab on the database, or on the settings of the map itself.

The main difference is that doing so in the Tileset will affect everywhere the tileset is used on, while on the map it will only affect that specific map.

On the other hand, anything the map setting says that is different from the tileset's, the map's will  be the one used. But if something is set on the tileset settings but not on the map's, it will stay for the map's. For example, you can add height or fringe on the map settings, but set the texture only on the tileset settings.

Good for having a tile with the same settings in most places save for a few maps where they work different.

For Tileset, put on the comment box the note block

<mv3d-layer#>
  (content)
</mv3d-layer#>

substituing the # for the number of the layer you want those settings to affect.

Work inside the note block just like you would set the tiles on the usual mv/z3d: set the specific tile as tileset image, x of the tile on the map editor, y of the tile, colon, then the setting. One of them per line.

For example, A5,4,3:(settings)

For map settings it is the same thing, but instead of <mv3d-layer#> you use <mv3d-layer#-tiles>.

Example:

<mz3d-layer4-tiles>
  A5,4,3:fringe(2)
</mz3d-layer1-tiles>

Setting regions:

Separate layer settings per region can only be set on the map.

It is set similar to how you can set specific regions on the map settings, region colon settings ( 15:(settings) for example), but you use a note block similar to the one used for layer tile settings, but using <mv3d-layer#-regions>.

Example:

<mz3d-layer3-regions>
15:height(3)
</mz3d-layer3-regions>

The usage of (and need for) Region Layer 1:

Usually Regions only affect Layer 1. That would make most think that Layer 1 for regions would be useless.

But as mentioned before, map settings take preference over tileset settings. Just the same way, this plugin's layered tile and region settings take precedence over  the default region ones.

Meaning any setting for a tile on layer 1 would take over the default region settings...

But not region layer 1 settings.

While not usually that important, it is important to keep this in mind on the instances where it would be.

Layers on MV instead of MZ:

Layers are also on RPG Maker MV, but not as easy to set as on MZ. When you set MZ's map layering to Auto,  it is working just like it does on MV. 

Most A1 tiles are set for Layer 1.

Layer 2 are the exception, and are limited to: the right half of A2, and the three animated "water decoration" tiles of A1.
An important point, those "water decoration" tiles are named so because when put the first tile of A1, usually a water tile, is set on A1 together with them.

B, C, D and E, also known as B-E, use layers 3 and 4.
Specifically, the first time you set one of their tiles it is on layer 4, and if you set another on the same tile the old one will be moved to layer 3. A tile on layer 3  is removed completely if overwritten.
The exception for this is the very first tile of B, usually (and preferably) a completely empty tile. Using it will remove the original tiles from both layers 3 and 4.

So, with proper practice, you should still be able to use this extension for MV3D, just like it is useable on MZ3D. But would require some extra work.

As a side-mention, you can open an MV map on MZ and use its layers, and as long as you do not change the tiles afterwards it will stay in the layers you set.