SolarStrike Software

Not sure how to fix this

not sure how you got this error

go to the rom bot first sticky and follow svn then move rom folder to desktop and then make a new rom folder in scripts and u do the svn checkout

ive redone the svn checkout and only kept profiles and waypoints i still get error. works for 5 - 10 mins then i get the error. I redone a new profile and still happens

can you be more specific on where the error occurred? like, the line number?

after bout 5-10 mins i get exactly this line

scripts\rom\bot.lua:616: bad argument #1 to 'sprintf' <got nil>

Still cant seem to get it fixed

extremeuser wrote:after bout 5-10 mins i get exactly this line

scripts\rom\bot.lua:616: bad argument #1 to 'sprintf' <got nil>

Still cant seem to get it fixed

Which SVN version do you have. Can you look into file bot.lua at line 616. What's the lines coding?

How is your waypoint file looking?

cprintf(cli.green, "We overrun waypoint #%d, skip it and move on to #%d\n",currentWp.wpnum, nextWp.wpnum);

Thats the requested line.

Using revision 389 SVN. I always update, deleted all files and updated again and updated profiles also. Works fine till i get that message. Im currently using a wander path of 500

extremeuser wrote:cprintf(cli.green, "We overrun waypoint #%d, skip it and move on to #%d\n",currentWp.wpnum, nextWp.wpnum);

Thats the requested line.

Using revision 389 SVN. I always update, deleted all files and updated again and updated profiles also. Works fine till i get that message. Im currently using a wander path of 500

Ok. It's a bug with the overrun function for waypoints. That's not very usefull for wandering around. I have to think about how to fix that.

Glad it wasnt just me, I couldnt see any1 else reporting this error either lolz. Would making a waypoint and changing to waypoint instead of wander for time being fix this temporarily?

SVN 390 shoudl avoid that error. The overrun and skip waypoints function will now not be used if you use the 'wander' mode.

thank you heaps for the speedy SVN update. I try it now and let you know if run into any more weird errors

Just a note: the macro test sending the macro to my macro hotkey is now coming up! which is fine as it used to always but for the last few SVN updates, this never came up lolz. Thats changed too?

extremeuser wrote:thank you heaps for the speedy SVN update. I try it now and let you know if run into any more weird errors

Just a note: the macro test sending the macro to my macro hotkey is now coming up! which is fine as it used to always but for the last few SVN updates, this never came up lolz. Thats changed too?

Yes. That's now also a little more clear.

Any chance you know the error to item update error, and the chat dialog opens, hence the bot stops, and dies lol! says empty or wrong bagID etc.

extremeuser wrote:Any chance you know the error to item update error, and the chat dialog opens, hence the bot stops, and dies lol! says empty or wrong bagID etc.

Please describe, what you are doing and post the content of your MM window.

I've got that bug too, the chat dialog opens, and you die. i think it has something to do with working with the bot on background.

droppen wrote:I've got that bug too, the chat dialog opens, and you die. i think it has something to do with working with the bot on background.

Yes. If the chat dialog opens, then no keystrokes will go to the action buttons. So there will be the 'update' errors, because the MACRO function will not be executed. But why does the bot open the chat? What's the keystroke to open the chat? I suppose 'ENTER'? or '/'?

ooh, got it. i had control+r bind on relpy to whisper, so if i has control down, and the bot used a skill bound to r it opens the chat dialog.