GridMap enhancement - A signal or callback for on_cell_changed()

[Scott3730]

The GridMap node would be an order of magnitude more powerful if I could have an editor script be able to detect whenever a cell has changed.

This could be achieved by any of a number of options. I'm not sure which would be the most appropriate method:

• A notification that i could check for in _notification()
• A signal (not sure if having signals that fire in editor/tool mode would be appropriate?)
• A method that could be overridden in a tool mode script that extends GridMap, maybe _on_cell_changed(cell_pos)

With this simple addition, I could write an auto-tile editor script in GDScript that I could share with everyone. You could have variation in tiles occur automatically; ie, place a tree tile and have a random one of six tree models spawn. You could have tiles automatically rotate in specific ways.

There would be lots of possibilities opened up by this.

[Zylann]

Keep in mind that if you do auto-tiling, it implies changing neighbor tiles to connect, and that will trigger on_cell_changed too, because that signal fires anyways without knowing what happens.
For tile variations, it also means that if you set the tile, it will trigger the signal again and you'll get an infinite loop unless you work around with some boolean, assuming your tool is the only one thing listening to that signal... IMO, in the context of auto-tiling and variations, such a signal doesn't sound like a clean idea.

[Scott3730]

what about _on_cell_change(Vector3 cell_pos, int new_id) ? or old_id, or both. I'm not sure which would be more useful. But there has to be a solution here somewhere. Or possibly if the engine detected when the new id was different from the old one, and only fired if true, that would stop any infinite loops, and if you're autotiling, only the cells one space away from the edge being tiled would receive the signal, because further back, the values wouldn't change.

[Zylann]

Still in the use case of auto-tiling, I was more thinking about a different path to set tiles in an auto-tiling way, something more specialized than a generic "a tile changed". I remember there was an existing issue where people were discussing this?
As soon as you think about auto-tiling, there is a distinction to be made between "master tiles" and "final tiles". For example, you may place grass, or road (master tile), but it can place one in many grass tiles, or modify neigbors to connect roads in various ways (final tiles). A "final" tile can be considered a "master" tile though, as long as there is only one of a given kind. The thing is, the master tile you place might not be the one you get because of auto-tiling.

Note: I read this is for GridMap, but what I mean is also valid for TileMap ;)

[Scott3730]

Yes! Actually, when making an autotile system, i reserve the first handful of tiles in a set for "air, material 1, material 2, etc", rather than the 32 different tiles / orientations that could represent them. So you paint in materials, and let the auto tile script define the actual tiles. I believe this is exactly what you're also describing. 😄

It would obviously be ideal to have this entire concept baked right into the engine implementation of GridMap (but that is a lot of work, that's why i'm not asking for it). But with a simple notification of some sort that i can respond to in script, i can hack together something that works.

As long as it is either only called when a cell's index actually changes, or is called with the old/new state passed as a parameter.

[Zylann]

Yeah that's my point: on_cell_changed doesn't know if the change is the one you want to place or the one done by auto-tiling, because it's too generic. It may help hack something indeed, but you'll have to deal with the limitation unless Godot gets aware of auto-tiling ;)