I think this is more an opinion-based question but here are my thought (I'm not a C++ expert):
Create a base class Tile that will handle generic stuff like rendering, animations if any, behavior of the tile...
For each of your special tiles, create a new class that inherits from your base class Tile and override the behavior if your new tile has a custom ...
I'd probably use those three variables:
Previous and next tile are pretty self explainatory. If player wants to move, nextTile is set to his target coordinates (eg. [2, 1]). Player is in "moving" state if previous and nextTile are different. The "transition" field is used to tell where the player is ...
It appears like you are looking at the inspector of one of several subsprites of an image asset you imported with the "Sprite Mode: Multiple" setting and then sliced with the sprite editor.
The second screenshot, however, appears to have marked several actual tile images, not the subsprites created from them. It appears like they are using a separate image ...
It is an old question - There doesn't still seem to be easy way to show clearly the origin and the bounds of a Tilemap, but it can be solved with a script that runs in the Editor like Philipp said.
I created this script. Red border shows the Tilemap current bounds, green cross shows the 0,0,0 position of Tilemap. Script does take into account position of ...
public class GetTilemapCoordinate : MonoBehaviour
public Grid grid;
SceneView.duringSceneGui += GetMousePosition;
public void GetMousePosition(SceneView scene)
Event e = Event.current;
if (e != null)