Removing extra tile defaults to hexarealm tile

[hackedpassword]

Not-quite-a-bug. More of an artifact.

When removing Z2 desert3.png, which was just a duplicate of Z2 desert.png, any use of ruleset Z2 including built in Zelda 2 map, 1 out of 3 desert tiles are using hexarealm desert.

This was not correctable by:

• selecting Desert terrain and replacing the wrong sprite tiles
• selecting different terrain, replacing, re-replacing with Desert
• wiping out all occurrences of Desert, save the map, reload Unciv
• deleting the built-in map Zelda 2, and moving Unciv64/maps/ elsewhere, reloading with no Z2 map files present
• faking a tileset layer via jsons/TileSets/HexaRealm.json ("Desert3": ["Desert2"],)
• specifying a blank fallback tileset instead of commenting the fallback line
• creating a new map with no Z2 map presence
• starting with vanilla unciv as a different ruleset, swapping to Z2
• swapping rulesets and/or mods

No iteration of Desert3 in any json sans the fallback test.

Temporary solution - re-add Desert3.png to the Tileset.

Question is how in funk is Unciv retaining any reference to Desert3, unless, and most probable, the existence of core HexaRealm Desert3.png is implicit until superseded by the mod Tileset.

unciv: android/Images.Tilesets/TileSets/HexaRealm/Tiles/Desert3.png

So, if that's true, is there an exclusion attribute for sprites we're not trying to use? Thought maybe the fallback hack above might do the trick if that was possible.

[hackedpassword]

The square highlight above tagged by a ? was solved by removing fallback="" from the hexarealm json, simply commenting the line out.

I thought up a potential solution, kinda brute force. Create another desert tile, maybe called 'Sands', dupe desert attributes, paint the desert.

Maybe there's an exclusion method to ignore certain images, for other situations like this one.