Automapping stops working when a project's rules.txt is modified during runtime. #3907

Does this only happen when you set the Automapping rules file via the Project properties? Does it ever happen when using rules.txt within the working map's directory instead?

And just to eliminate a different issue: Does your working map have a (possibly non-working or undesired) rules.txt in its directory? This should normally take precedence over the rules file set in the Project Properties. If this is what's getting in the way of your automapping working, then your "fix" actually reveals a potential bug in Tiled where the priority of the two files is incorrect.

Does this only happen when you set the Automapping rules file via the Project properties? Does it ever happen when using rules.txt within the working map's directory instead?

To date, I have only ever used Automapping by setting the rules in this window, and not by having the rules.txt file share a folder with their respective maps.

And just to eliminate a different issue: Does your working map have a (possibly non-working or undesired) rules.txt in its directory? This should normally take precedence over the rules file set in the Project Properties.

In my entire project I only have the one rules.txt file, and it lives in its own folder, with the rules maps it points to being in another folder, i.e.

./data/rules.txt

then in the file itself, rulemaps/rules-wall.tmx rulemaps/rules-roof.tmx

Update: I thought I figured it out, but I can't seem to get this to reproduce reliably. It looked like whenever I made a change to rules.txt by adding a new .tmx map to it, the rules.txt needed to be re-set within the Project Settings, but I'm not certain.