This should not be case unless you approach it incorrectly. If you look at my example, each spawned actor has a unique coord ID, even though it’s an instance of the same tile actor.
Inheritance (Parent ↔ Childlren) would work for this, especially if the tiles will have some shared functionality:
- parents have a
tiletag and int ID - child sand tile has an additional ‘sand’ tag
- child stone tile has an additional 'stone ‘tag’
When you query a tile, you can assemble those tags into an unique ID used to query a database. TileSand5 for example.
But, I still feel you’re massively overcomplicating this. I do not know what your Treasure is - so it’s hard to advise with something tangible.
As you spawn tiles and know they will have a treasure, give the tile an ID (name / int) that identifies the treasure. No need to involve coordinates, not for this at least. As tiles go away, feed their IDs to a Data Table / Map Dictionary (no clue how your backend looks like).