Recently i released a little project based on Maxi031 one to allow anyone to include quests in their maps, MlSideQuests. Initially only a TM² thing, i was able to make it work in SM with close to no change.
SBVille was doing a special map in SM Obstacle and wanted to include a little quest in there (with MT clips). I thought the project i released could help him too so we integrated it.
After everything was set up yesterday, we did a test and something was very wrong. I found out, cf. title, the issue: Everytime a MT clip is triggered, the previous MT clip the player triggered is also triggered, again. I found this because after analysing values returned to the server, they were not where they should be, it was like exchanged. And seeing the times at which each request was made, i understood what exactly was the issue. You could see stuff like that:
Code: Select all
... [02/Dec/2019:00:08:21 +0100] "GET /...&Token=43 HTTP/1.1" 200 5043 "-" "ManiaPlanet ... (previous trigger)
... [02/Dec/2019:00:08:21 +0100] "GET /...&Token=44 HTTP/1.1" 200 5042 "-" "ManiaPlanet ... (actual trigger)
... [02/Dec/2019:00:08:57 +0100] "GET /...&Token=44 HTTP/1.1" 200 5042 "-" "ManiaPlanet ... (previous trigger)
... [02/Dec/2019:00:08:57 +0100] "GET /...&Token=41 HTTP/1.1" 200 5042 "-" "ManiaPlanet ... (actual trigger)
... [02/Dec/2019:00:17:22 +0100] "GET /...&Token=37 HTTP/1.1" 200 5042 "-" "ManiaPlanet ... (previous trigger)
... [02/Dec/2019:00:17:22 +0100] "GET /...&Token=60 HTTP/1.1" 200 5042 "-" "ManiaPlanet ... (actual trigger)On my side i did what i needed to bypass that bug, by preventing any overwrite of values already set before during the quest.
Update: Seems like its even more broken than i thought. The map was made available on a server and any action (for instance: cp jump, spec a player, switching to another player to spec) triggers the previous MT clip triggered if it exists. Cf. below, seems that when spectating, it's the previous MT trigger that player triggered that you'll see (if there's something to see).
Some Twitch clips displaying the issue from this update ^ (which seems a bit different (and not a 100% thing, or 100% but entirely different when spectating and it's just the last MT clip triggered by the player you're spectating that'll also get to trigger) than the original reported bug):
This one below is a bit different, it's not the per-se "previous" triggered MT clip since there's one at the very beginning of the map, so no idea why it's triggering this one specifically (which is the one from the crystal at the start to start the quest). Or it's actually not different at all and it's as i thought afterwards: "entirely different when spectating and it's just the last MT clip triggered by the player you're spectating that'll also get to trigger":