|
|
Post by Deleted on Jan 23, 2018 18:16:20 GMT -5
Idk why this began happening to me recently, but if you place a start pos that is exactly on the same x-position of a move trigger the trigger will bug out (basically the move bug in 2.0, but thank god it isn't permanent). It's really annoying when you are practicing a level with lots of move triggers.
I've never noticed this until like a week ago, so it might just be my phone being weird. But test it out yourself xd
|
|
1,534 posts
Favorite Level: Laughter by chamoylol and Pinkiemania by ChuchitoDomin
|
Post by Pinkie Pie on Jan 23, 2018 23:32:49 GMT -5
yea it happened to me when practicing fusion flare (im on pc)
i think the best fix is to just place the start pos somewhere else (maybe with no move triggers)
|
|
|
|
Post by flash on Jan 24, 2018 18:58:42 GMT -5
basically if the startpos is on the same column as a move trigger it'll perform the move trigger once when the level loads, then once again when you actually start moving, so it does it twice.
|
|
|
|
Post by Deleted on Jan 25, 2018 20:35:04 GMT -5
basically if the startpos is on the same column as a move trigger it'll perform the move trigger once when the level loads, then once again when you actually start moving, so it does it twice. Yup this is exactly what happens. I managed to evade it by just moving the start pos one step backward, but this is still a bug that should be fixed  |
|
