Udefined method when editing a gameover script.

[AceOfAces_Mod]

Consider the following scenario:


You installed DoctorTodd's GameOver +.


You modify part of the script like this:


class Scene_Gameover < Scene_Base
#--------------------------------------------------------------------------
# * Start Processing
#--------------------------------------------------------------------------
def start
super
play_gameover_music
tone = Tone.new(80,0,0,200)
$game_map.screen.start_tone_change(tone, 120)
SceneManager.scene.wait(180)
fadeout_frozen_graphics
tone = Tone.new(0,0,0,255)
$game_map.screen.start_tone_change(tone, 1)
SceneManager.scene.wait(1)
create_background
create_command_window
end


In this scenario, the game crashes with this message:

NOTE: It could also happen on the vanilla Scene_GameOver Script.

 

[Andar]

simple as the error message tells: wait is not defined for any scene.


wait is a function of the game interpreter to be used in the game loop for events, and it is a subfunction of special parts where timing counts (like in messages or battles), but scenes are timeless and have no wait, so you can't use wait as a method of a scene.


EDIT: You'll need an entirely different structure here, but I can't tell you how.

 

[Sixth]

Ohh, you can use 'wait(frames)' if you define it. //rmwforums.s3.amazonaws.com/emoticons/default_tongue.gif


Scene_Battle actually got that method defined. Not that it is usable on the game over screen, but it is a scene with a wait method, right? 


Anyway, if you just want to force a few frame wait time, you can use this:


Graphics.wait(frames)


This will wait the amount of frames you enter while still updating the screen.


Note that this will NOT run any other stuffs while waiting, only the screen redraw. If you need to update something else too while waiting (like some sprites, windows, or the input module), you will need to create your own wait method where you update all what you need, and just loop that for the amount of frames you want.


For example, you want to update the "screen" game map is using, otherwise it will never change the tone no matter how long you wait.


Remove those wait lines you added, and do the following:


120.times do
Graphics.update
$game_map.screen.update
end
Graphics.wait(60)


Insert this just below the first tone change you do in your script. This will finish the tone change for the screen and after that, it will wait an extra 60 frames before continuing.


Because the second tone change should only last 1 frame (very quick), you don't really need to wait here. 


Instead, you can forcibly call the update method of $game_map.screen to instantly change the tone.


So, after the second tone change, just enter this:


$game_map.screen.update




Of course, I didn't test this, because I can't seem to trigger the game over screen, not even if I want to, I just can't lose in games. //rmwforums.s3.amazonaws.com/emoticons/default_biggrin.gif


Okay, jokes aside, I really didn't test this, but in theory, it should work. 

 

[AceOfAces_Mod]

It works, but for some reason, it doesn't tint the screen. Am I doing something wrong?

 

[Sixth]

I just noticed that you try to do this in the start method.


That won't work like that, because during scene changes, the graphic changes are frozen until the transition effect is called, and on that scene, that method is called in the 'fadout_frozen_graphics', which will also get rid of the background picture for the map too at the same time, so there is not much you can do to actually show that tint effect in that method without rewriting the whole start method.


Instead, you should perform the tinting before you actually call the game over scene, so that you are still on the map, and can tint that map screen freely. When you are done with the tinting stuffs and all, you can call the game over screen.


This might even look better, considering that the map itself can still be updated, so there can be moving events and stuffs around while the screen is being tinted.


You can modify this method in Game_Interpreter to do your stuffs before getting on the game over screen:


def command_353
SceneManager.goto(Scene_Gameover)
Fiber.yield
end


So, put your tint stuffs before the actual game over call.

 

[AceOfAces_Mod]

Well, tried and instead of tinting, I get frozen graphics until the game over scene starts up. Maybe it's an issue caused by the Crossfader script I use?