Hey folks, I get this message since I updated my map a bit. Didn’t do anything out of the ordinary as far as I can recall, but then it all went wrong in Unity.
SuperTiled2Unity version: unknown, Unity version: 2022.3.44f1
Errors Detected. Your Tiled asset may not function correctly. Please follow directions to fix.
Missing Dependencies - Files Are Missing Or Misplaced
The following assets are needed by Super Tiled2Unity.
This asset is dependent on other files that either cannot be found or they failed to be imported.
They may be missing entirely or they may be in the wrong folder.
Note that all Tiled assets must be imported to Unity in folder locations that keep their relative paths intact.
qrc:/automap-tiles.svg
But since this is an internal file from Tiled I have no way of replacing this. But maybe there’s an entire different reason this error is popping up?
Hope to get some help!
Greets
You should not be importing your Automapping rules maps into your Unity Project, as they only make sense in the context of Tiled. ST2U has no special handling for this tileset, and the way to avoid this error is to make sure Unity doesn’t try to import those maps.
Unity ignores files and directories that start with . or end with ~, so the simplest way to get your Automapping stuff out of the way is to put it in a directory whose name meets one of those criteria (you’ll need to adjust your rules.txt though - the easiest way is usually to move the rules.txt into that hidden directory too so it doesn’t need changing, and then set Tiled to use it in your Project settings.)
Yes and actually, I never did try to import my automapping rules into Unity.
This was just an error that popped up suddenly, making me think that maybe I left one of the tiles from the automapping-rules somewhere in a layer that I shouldn’t have. But so far I’ve scanned everything and I don’t see it anywhere…
Is one of your Automapping rules maps perhaps for some reason in a directory that Unity looks at? Another possibility is that you added the tileset to a map unintentionally, but didn’t use any of the tiles - I think ST2U will still try to load the tileset in that case.
Try opening the map that causes the error in a text editor and searching for automap-tiles.tsx.
I think I may have a culprit in my map
<tileset firstgid="1153" source=":/automap-tiles.tsx"/>
Open the map in Tiled, navigate to that tileset in the Tilesets view, and click the Remove Tileset button. That’ll give you the option to remove any tiles that may be used in it, if there are any.
But that’s the internal ruleset that I cant delete (the bin icon is greyed out?)
Odd. Make sure there isn’t another copy of the AutoMap Rules tileset elsewhere in the tileset list. I don’t think there should be since I think the list is alphabetical, but just in case.
And make sure you’re looking at that exact map file, and not a copy of it.
If you’re looking at the right map and the tileset is really not there, then you should be able to safely remove the <tileset firstgid="1153" source=":/automap-tiles.tsx"/> line via a text editor.
If the tileset is listed in the file but isn’t shown as part of the map in Tiled, that may be a bug…
Tiurns out I was looking at the wrong version of that map. To clarify: Yesterday I installed the latest version of Tiled and after that corrupted map was still corrupted, but a new one was added next to it. That one worked (even though it also had the same errors). But the texteditor for that map showed me all this code. I deleted everything and now it works fine again. 
Thank you very much for your quick help!
<tileset firstgid="1153" name="AutoMap Rules" tilewidth="32" tileheight="32" tilecount="5" columns="5" tilerendersize="grid" fillmode="preserve-aspect-fit">
<image source="qrc:/automap-tiles.svg" width="160" height="32"/>
<tile id="3">
<properties>
<property name="MatchType" value="Empty"/>
</properties>
</tile>
<tile id="1">
<properties>
<property name="MatchType" value="Ignore"/>
</properties>
</tile>
<tile id="2">
<properties>
<property name="MatchType" value="NonEmpty"/>
</properties>
</tile>
<tile id="4">
<properties>
<property name="MatchType" value="Other"/>
</properties>
</tile>
<tile id="0">
<properties>
<property name="MatchType" value="Negate"/>
</properties>
</tile>
</tileset>
It looks like you embedded the Automapping tileset into the map. There’s no reason to ever do that, but since Tiled sees that tileset as just a regular tileset, it doesn’t prevent it.
@bjorn Perhaps it might be good to show a warning when a user attempts to embed the Automapping tileset like this, explaining that there should be no reason to do this, and that the tileset will still refer to other files that don’t exist outside of Tiled (namely, the tileset image)? Of course, that won’t help with the embed tilesets export option…
