Missing } Counter - Something to force the game to give report if a } is missing

[LiamRiordan]

When I code and rush sometimes to test something, I can forget to put a } at the end of an event. I only find this out when I know to look there, but when the game attempts to load the game, it doesn't produce a crash report, it only keeps trying to load then locks. You cannot ALT-TAB, but you can force the task manager to pop up and close the game that way.

Can there be a way that if the game is stuck on a certain file on scenario load, that it will stop loading that file, and produce a crash report to notify the user? Since if you implant a large number of files at once, it can be a royal pain to know which one it is that's causing the problem.

Can it be like "Unable to load "xxx.txt"" Then Abort, Retry, Ignore.

Possible?

 

[Arturius]

Does retry-button work for you?

 

[novapaddy]

I find the error reporting excellent and much better than it has ever been before now.

Go into settings.cfg and change the 0 to 1:

0 # Extra debug logs (savedebug.txt): 0 = disabled, 1 = enabled, 2 = enabled + extra map statistics

Set at 2 you'll get way too much info, unless you are working on a map?

But set at 1, you'll get every single error listed, and this is usually enough to find the error you require?

 

[LiamRiordan]

The problem is the crash window doesn't even appear even with the extra bug reports, the game just keeps getting stuck on the file with the missing } so it doesn't force crash itself.

 

[novapaddy]

I've had error reports where an extra "}" was indicated, but unfortunately not a missing "}" yet. I think the code just tries to make sense of it all, but usually the next item will show an error as it is being read incorrectly.. so go back one item and you should be able to see the error?

 

[MartinBG]

The problem is the crash window doesn't even appear even with the extra bug reports, the game just keeps getting stuck on the file with the missing } so it doesn't force crash itself.

If that happen you still can terminate the game and then go and check savedebug.txt. With extra debug logs enabled (setteings.cfg) not just errors are logged so you should be able to find where the problem is by looking at the last lines in the log.

 

[Lyrecryer]

You should also try to play this game in window mode as well. Makes things a lot easier.

 

[Arturius]

Does retry-button work for you?

What I wanted to state with this comment that I would like to see a working retry button, so that I can fix a file on the fly, push the retry button and the loading progress is going on.

 

[LiamRiordan]

You should also try to play this game in window mode as well. Makes things a lot easier.

I do when I bother in a long coding session, most of the other times though I don't do that since I hate seeing my screen in 16-bit.