This is flagrant with GetMousePosition, which is supposed to add 4 values at the end of the output list:
- Value 1: Value set for the GetMousePosition command
- Value 2: X coordinate of the mouse
- Value 3: Y coordinate of the mouse
- Value 4: Mouse button
If you are not using a button of the mouse, then value 4 will be equal to 0. If after having the 3 values defined by using Control Variables: MIDI Ticks commands, you hypothetically only have the value 4 left in the output list, and use another GetMousePosition at this moment, the Player will consider the 5 remaining values in the output list to be firstly the four values from the new GetMousePosition command, and then finally the first value 4 that was equal to a 0.
This case is not encountered in the demo, as they do track the mouse key used and thus do not trigger this exact problem, but it could happen in some Ineluki games depending on how they are coded.
This is flagrant with GetMousePosition, which is supposed to add 4 values at the end of the output list:
If you are not using a button of the mouse, then value 4 will be equal to 0. If after having the 3 values defined by using Control Variables: MIDI Ticks commands, you hypothetically only have the value 4 left in the output list, and use another GetMousePosition at this moment, the Player will consider the 5 remaining values in the output list to be firstly the four values from the new GetMousePosition command, and then finally the first value 4 that was equal to a 0.
This case is not encountered in the demo, as they do track the mouse key used and thus do not trigger this exact problem, but it could happen in some Ineluki games depending on how they are coded.
