bad argument #1 to 'sprintf' <got nil>
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
bad argument #1 to 'sprintf' <got nil>
Not sure how to fix this
Re: bad argument #1 to 'sprintf' <got nil>
not sure how you got this error
-
- Posts: 12
- Joined: Sat Oct 24, 2009 10:18 pm
Re: bad argument #1 to 'sprintf' <got nil>
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
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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
Re: bad argument #1 to 'sprintf' <got nil>
can you be more specific on where the error occurred? like, the line number?
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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
scripts\rom\bot.lua:616: bad argument #1 to 'sprintf' <got nil>
Still cant seem to get it fixed
Re: bad argument #1 to 'sprintf' <got nil>
Which SVN version do you have. Can you look into file bot.lua at line 616. What's the lines coding?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
How is your waypoint file looking?
The RoM Bot Online Wiki needs your help!
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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
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
Re: bad argument #1 to 'sprintf' <got nil>
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.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
The RoM Bot Online Wiki needs your help!
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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?
Re: bad argument #1 to 'sprintf' <got nil>
SVN 390 shoudl avoid that error. The overrun and skip waypoints function will now not be used if you use the 'wander' mode.
The RoM Bot Online Wiki needs your help!
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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?
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?
Re: bad argument #1 to 'sprintf' <got nil>
Yes. That's now also a little more clear.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?
The RoM Bot Online Wiki needs your help!
-
- Posts: 57
- Joined: Wed Jul 01, 2009 12:52 am
Re: bad argument #1 to 'sprintf' <got nil>
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.
Re: bad argument #1 to 'sprintf' <got nil>
Please describe, what you are doing and post the content of your MM window.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.
The RoM Bot Online Wiki needs your help!
Re: bad argument #1 to 'sprintf' <got nil>
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.
Re: bad argument #1 to 'sprintf' <got nil>
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 '/'?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.
The RoM Bot Online Wiki needs your help!
Re: bad argument #1 to 'sprintf' <got nil>
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.
Who is online
Users browsing this forum: No registered users and 4 guests