When working with other modules, particularly Token Attacher, sometimes things get into an incompatible state. I have posted an issue on TA's github detailing the specifics of an issue I was having when using cloning regions.
My best guess is that there are clones somewhere in the Foundry data structure that TA is tripping over. I've looked into it a bit and have some idea of how Foundry's flags work. One thing that I've noticed is that flags persist even after the relevant module is disabled. What I would like to see from your side is an aggressive, scorched earth nuclear option to deal with cloned region tokens. Preferably, it would take the form of a macro that functions when MLT is disabled that cycles through all the scenes and blows away any and all token-related data without affecting the region definitions themselves.
When working with other modules, particularly Token Attacher, sometimes things get into an incompatible state. I have posted an issue on TA's github detailing the specifics of an issue I was having when using cloning regions.
My best guess is that there are clones somewhere in the Foundry data structure that TA is tripping over. I've looked into it a bit and have some idea of how Foundry's flags work. One thing that I've noticed is that flags persist even after the relevant module is disabled. What I would like to see from your side is an aggressive, scorched earth nuclear option to deal with cloned region tokens. Preferably, it would take the form of a macro that functions when MLT is disabled that cycles through all the scenes and blows away any and all token-related data without affecting the region definitions themselves.