Possible to debug and trace Evebot scripts?

[kidvid]

I've submitted a couple of bug reports for the Evebot, and having some extra time this past weekend, I tried to see if I could fix one of them myself (getting killed while slowboating to an asteroid).

I put, what I thought, was a very reasonable way to fix it but every time, Evebot would throw back an "Invalid State" error and just die. How do I know if I did something wrong, or there's a bug in ISXEve?

Even more importantly, how does one step through the existing Evebot scripts like one would step through code in a Javascript or C# debugger? The Evebot code is so robust and complex now that I don't see how anyone that hasn't worked on it for months could possibly make any kind of meaningful addition to it without the ability to step through the code to see what's going on.

Perhaps there's a trace-to-file command for ISXEve? I've done some searching and can't find anything mentioned like this.

 

[GliderPro]

single step? I wish.

Sadly the only debug method for Lavishscript is the "echo" command.

 

[CyberTech]

I've submitted a couple of bug reports for the Evebot, and having some extra time this past weekend, I tried to see if I could fix one of them myself (getting killed while slowboating to an asteroid).

I put, what I thought, was a very reasonable way to fix it but every time, Evebot would throw back an "Invalid State" error and just die. How do I know if I did something wrong, or there's a bug in ISXEve?

Even more importantly, how does one step through the existing Evebot scripts like one would step through code in a Javascript or C# debugger? The Evebot code is so robust and complex now that I don't see how anyone that hasn't worked on it for months could possibly make any kind of meaningful addition to it without the ability to step through the code to see what's going on.

Perhaps there's a trace-to-file command for ISXEve? I've done some searching and can't find anything mentioned like this.

As glider said, no. You should come on IRC with ideas for fixing various things.. if it's not going to work I or a few others could tell you fairly quickly and save you time, if it is going to work and is simple one of us could put it directly into svn. there is a debug (full trace) option, but you will be reading thru megabytes of data trying to find something useful, and it won't help much.