Lately I've experienced something very frustrating: some RMXP project of mine would crash, leaving no error message, which leaves me unable to locate the problem. What's even more strange about it is that it occurs when running scripts known to work properly otherwise - the only difference is that I'm trying to read them from .RB files rather than put them directly in the script efitor.

Evertyhing works fine with this system otherwise, although some problems while loading .RB files are not reported and thus cause them not to be loaded entirely, but I think i'm through with this kind of bugs now, especially since they produced normal errors I was able to extrapolate from. The .RB files are perfect copies of their script editor entries counterpart, I double-checked that several times.

So, I was wondering if anyone had also experienced such inconvenience, and/or had any clue about what would cause it and what could be done about it.

In case this provides any relevant information, I've experienced this on two occasions so far: while using my Animated Custom Menu System, when pressing C to select an item/skill and switch to the target selection in the item/skill scene, and when entering my improved load/save menu. Everything works fine when removing the Window_Target script (which replaces the default target window with rotating widgets) in the former case, and the Scene_File script (which overrides Scene_Save and Scene_Load with as single scene which serves for both) in the latter.

I dont understand what RP files are but have you tried to put the scripts in the script editor? I THINK they all need to be in there, otherwhise RMXP won't know where to load the scripts for different modules from. I don't know, but it may help to put the scripts in the script editor!

you can try to enclose the main script inside a

then print the last error on the ensure or something

There's a reason why I'm trying to load those scripts from outside the script editor. It is the point to leave them out.


I didn't know about the ensure statement, thank you. It works, i.e. the block given after ensure does execute, but sadly I have no idea what I could do with it, since it does not seem to capture any exceptions, so there's nothing to print... Besides I'm already using a rescue statement to catch any "normal" exceptions.

Boy do I feel your pain. I'm been having to deal with no-message crashes with another script I've been using. The only thing I can think of--and this is very tedious--is to try catching exceptions or just commenting out chunks of the code at a time, and maybe the problem area can be found through trial and (no) error.

RM crashing without an error message should be like against the law or something. It makes the debugging process insanely difficult!

Use the $! and $@ variables. They are the instance of the last exception and the stacktrace.

begin
# Do stuff
ensure
p $!, $@
end

That's good to know!

I think I found the problem line. Ironically, it was a "raise" call that was causing it.