SolarStrike Software

Hey all.

Those crashes I'm getting ingame seems to be when Im playing for more than 4-5 hours. Then the games crashes and I need to restart it. Same issue is when Im botting mobs, the game crashes and it kills my character if I dont press, "Send or Cancel" which I dont because I'm AFK under the botting period. So I'm wondering if there is a script or code that can catch this crash report and automatically press "Cancel" when it occurs so it dont kill my character?

Thanks! / Hx

I wish this too. I think htere was a bit of a discussion about this but nothing became of it. I think the administrator said something along the lines of 'she couldn't identify the application that caused the error box'.

Maybe we can revisit this Administrator?

Actually I think we were able to kill off the game if it had an error, but the problem was having it automatically restart the client and login. I should still have the code around here to restart the client, but, having it login and select character are still a problem.

But the first propblem is when it crashes, if the game doesn't close, then the server thinks your still online and your character dies. So first priority is to kill the client process as soon as a crash occurs.

A solution to auto logging in would be great but it's another issue entirely.

So can you implement auto terminating of the process when it crashes?

rock5 wrote:But the first propblem is when it crashes, if the game doesn't close, then the server thinks your still online and your character dies. So first priority is to kill the client process as soon as a crash occurs.

A solution to auto logging in would be great but it's another issue entirely.

So can you implement auto terminating of the process when it crashes?

Perhaps I can look into it if I get a chance.

BTW. What's the purpose of this folder "ROM general" as apposed to the regular "Runes of Magic" folder?

Nearly everything in the RoM forum is specific to botting. This is for pretty much anything to do with the game, including information on quests, dungeons, general information, whatever.

So topics related to rom but not Botting? Maybe a more descriptive name? Like "RoM - Non botting related topics"?

rock5 wrote:So topics related to rom but not Botting? Maybe a more descriptive name? Like "RoM - Non botting related topics"?

The subtitle says:

Talk about anything in Runes of Magic. This does not need to pertain to botting.

Does this show under whichever theme you have selected?

Ah.. Didn't notice that.

rock5 wrote:Ah.. Didn't notice that.

Don't feel too bad. I have a feeling that 99% of the other visitors to this site don't, either.

I'm glad that I'm not alone about this. Well I hope we/you can find a solution.
Last night I tested to change the graphics and audio etc to the minimal resoultion. I also pressed Ctrl + Z to hide the actionbar etc for less lagg. Didnt have a crash under those 7 hours of mob farming. Will do some more tests when I get home.

If we can get the client to close while the Crash occur its pretty enough for me, I dont need the autologging and restarting client. But it would be a bonus if you can make that work

If admin can find the start client code mentioned I should be able to come up with something.
Have a few ideas already forming =)

lisa wrote:If admin can find the start client code mentioned I should be able to come up with something.
Have a few ideas already forming =)

Thats great =)

You know, this is actually possibly easier than we might have thought. All you need to do is detect the crash window (findWindow("Crash Report"), getWindowClassName("#32770")) and then just kill the task (classes/player.lua:2843).

Seems to work.

Thats great, will you publish the code in short or do you have some testings left? =)
And could you learn me where I need to put this code or it comes in a separate file that need to go under a specific folder?

/ Hx

Administrator wrote:You know, this is actually possibly easier than we might have thought. All you need to do is detect the crash window (findWindow("Crash Report"), getWindowClassName("#32770")) and then just kill the task (classes/player.lua:2843).

Seems to work.

If you multiclient though how would you know which client crashed?

You kill the crash report process, which would take the client with it.

I guess what I meant to ask was

If you multi client and multibot.
If 1 of the clients crashed all of the bots would detect the window pop up, so need to decide which bot is still running fine with a client and which actually crashed and only the one that crashed kill the crash report.

I guess easiest way would be to add any code into the
function error

I can't seem to find it though, is it part of micromacro.exe ?

If you kill the Crash Report window, it closes the paired game client automatically. There is no need to figure out which client it came from.

error() is a Lua function. But, there is a callback. I think in functions.lua, there's something like function onErrorCallback().