[Solved] Player start locations ALWAYS fixed + hero skins not working

[Nicks]

So basically I have this map where I have a bunch of triggers that do all sorts of things (create a dialog, set a timer, set a random effect every 30 seconds, set hero limit, etc.). I do NOT have any player forces enabled or fixed player start locations enabled. Fixed random seed is also OFF. In all the times I kept testing the map, player start locations were randomized as expected and hero skins from the skin menu were working too... Until I added a trigger to add a new timer for another feature and then all of a sudden player start locations are constantly fixed based on their color and the hero skins stopped working. I rollback and deleted that trigger that supposedly I thought caused this but even then these things were still not working. Any general idea of what can cause this to happen?

 

[Uncle]

99% of the time things are working as intended. It's very unlikely that you're experiencing a malfunction that nobody else has experienced before.

So it's safe to assume that it has nothing to do with that trigger and that...

1) You've created another trigger that interferes (maybe a 3rd party system that you imported recently).
2) You've changed the seed/start location settings again without realizing it.
3) You're playing the wrong version of the map (it happens).

Good luck!

Edit:
Oh and there is one very rare bug that can go undetected. Sometimes your Variable Types can become "blank". The only way to determine this is to scroll through your Variables in the Trigger Editor (left side) and click each one to check to see if it's Type is empty or not. A "blank" variable will NOT disable any triggers or break any references in Events/Conditions/Actions - which is why it's so difficult to detect. So it will appear as though it's working correctly but will fail to function properly once in-game. You should backup your map before checking for this because you can actually break references while selecting them. Bugs like this are why it's much safer to work with variables inside of the actual Variable Editor menu instead of outside of it.

 

[Chaosium]

Make sure that this option is turned off just in case

 

[Nicks]

Make sure that this option is turned off just in case

View attachment 518669

I did turn it off, if you read the full post

99% of the time things are working as intended. It's very unlikely that you're experiencing a malfunction that nobody else has experienced before.

So it's safe to assume that it has nothing to do with that trigger and that...

1) You've created another trigger that interferes (maybe a 3rd party system that you imported recently).
2) You've changed the seed/start location settings again without realizing it.
3) You're playing the wrong version of the map (it happens).

Good luck!

Edit:
Oh and there is one very rare bug that can go undetected. Sometimes your Variable Types can become "blank". The only way to determine this is to scroll through your Variables in the Trigger Editor (left side) and click each one to check to see if it's Type is empty or not. A "blank" variable will NOT disable any triggers or break any references in Events/Conditions/Actions - which is why it's so difficult to detect. So it will appear as though it's working correctly but will fail to function properly once in-game. You should backup your map before checking for this because you can actually break references while selecting them. Bugs like this are why it's much safer to work with variables inside of the actual Variable Editor menu instead of outside of it.

Well, turns out every player "Controller" in "Player Properties" has to be set to "User" rather than "Computer". I would understand this making starting locations fixed but I don't understand it making skins not working. Regardless, after changing them to User now both things work properly. Thanks for the help lol