02-24-2020, 05:47 AM
The default wait routine in Scene Map part of the $game_system.map_interpreter.update command in the update method's main loop and runs before the default message update. So it should have worked by default. My inquiry is to know if any changes were made to Scene_Map. That would be key.
Likely example.
So yeah, look at the script and see if there's any Scene_Map code. If so, we can always add a custom WAIT command before the message system's custom update just for you.
(02-24-2020, 02:05 AM)Whisper Wrote: Animation and message still appears simultaneously. Waiting applies AFTER message (Player can't move for x time). But at least there is no graphic freeze.According to this, the message and animation show simultaneously... then waits. If the custom message system is added to the start of Scene_Map's update method, this would be the result.
Likely example.
Code:
def update
yadda - yadda - yadda
new message system <-- Executes Message Immediately
yadda - yadda - yadda
beginning of original code
default screen graphics <-- Executes Animation Immediately
default wait code <-- NOW WAIT
default (and unused message)
yadda - yadda - yadda
end
So yeah, look at the script and see if there's any Scene_Map code. If so, we can always add a custom WAIT command before the message system's custom update just for you.