Ok I know I need the craft.log..however, I can't seem to find where its located. Now for the problem...it is anytime I load the bot it will craft a couple of (Rush Orders) writs then crash. when I hit the ~ key to pull up the term, it says there's no more writs to craft...however I know that most of the bots problem are due to human error, I have well over 1,000 mats of everything that is required to craft...there is no reason for it to be crashing..any ideas?
Bot Crashing.
- Thread starter deeje
- Start date
Read your own post, and the answer will come to you...
see it yet? keep reading.
anything?
I know you can find it. keep trying.
ok, here's the answer.
see it yet? keep reading.
anything?
I know you can find it. keep trying.
ok, here's the answer.
Why didn't I think of that....
Wait..I did, I just forgot to mention it. The other problem is every time that it crashes it has another rush order ready to go in my quest journal and it doesn't start crafting it, then it says "there was a problem obtaining the writ request --ending script"...now funny thing is I also have auto mouseclicker going so it can craft while i'm watching movies and what not, and I know my X an Y coords are accurate, however for somereason the bot still keeps crashing on me, so with this new bit of info, what would be the solution to my problems?
Wait..I did, I just forgot to mention it. The other problem is every time that it crashes it has another rush order ready to go in my quest journal and it doesn't start crafting it, then it says "there was a problem obtaining the writ request --ending script"...now funny thing is I also have auto mouseclicker going so it can craft while i'm watching movies and what not, and I know my X an Y coords are accurate, however for somereason the bot still keeps crashing on me, so with this new bit of info, what would be the solution to my problems?
Writs to craft
yes this is true, however I just sat here and watched it..I even took off the auto clicker software to test it, and it did the same thing..it crafted one rush order when I told it to craft 5 and this is what it said in the console.
Checking inventory for recipe books that need to be scribed
remaining writs to make: 4
There was a problem obtaining a writ quest --ending script
So just from the console alone you can determine that it is in fact crashing and it is indeed only crafting 1 out of the 5 writs before it decides to kick the can...I'm very computer savvy, however I do lack in scripting..i'm not trying to piss in anyone's cheerios here, I just want to know the technical reason of whats going on and the reason behind it as well as how to address it.
yes this is true, however I just sat here and watched it..I even took off the auto clicker software to test it, and it did the same thing..it crafted one rush order when I told it to craft 5 and this is what it said in the console.
Checking inventory for recipe books that need to be scribed
remaining writs to make: 4
There was a problem obtaining a writ quest --ending script
So just from the console alone you can determine that it is in fact crashing and it is indeed only crafting 1 out of the 5 writs before it decides to kick the can...I'm very computer savvy, however I do lack in scripting..i'm not trying to piss in anyone's cheerios here, I just want to know the technical reason of whats going on and the reason behind it as well as how to address it.
you're deleting the writ from your journal before trying to restart the bot, right? if you have a writ in your journal when you start the bot, it will end with that error.
when it goes back to the writ giver, it's targeting the right person? hailing correctly? choosing the right chat option? accepting the quest?
you're the only person that has a problem. this leads me to believe the problem is something on your end, especially since NOTHING has changed with craft in around a month.
when it goes back to the writ giver, it's targeting the right person? hailing correctly? choosing the right chat option? accepting the quest?
you're the only person that has a problem. this leads me to believe the problem is something on your end, especially since NOTHING has changed with craft in around a month.
Deleting Writ
Yes every time before I even start the bot I delete the writ and fire the bot up, however even when I do so the above still happens, the bot crashes, then when I pull up the journal a rush order is in it, even though I deleted it before. So to my knowledge what is happening is the bot somehow crashes after a writ, and then has unfinished rushorder, so it doesn't know where to begin..which brings me back to the original question of why is it crashing..I'll post a craft.log if you tell me how. I read it was in the extensions folder, and I tried to fire craft -debug, and it says "debugging enabled" yet when I go into the proper folder there is no craft.log.
Yes every time before I even start the bot I delete the writ and fire the bot up, however even when I do so the above still happens, the bot crashes, then when I pull up the journal a rush order is in it, even though I deleted it before. So to my knowledge what is happening is the bot somehow crashes after a writ, and then has unfinished rushorder, so it doesn't know where to begin..which brings me back to the original question of why is it crashing..I'll post a craft.log if you tell me how. I read it was in the extensions folder, and I tried to fire craft -debug, and it says "debugging enabled" yet when I go into the proper folder there is no craft.log.
Nuprecon
Active Member
Plain and simple, your usage of the bot is not supported... Stop using the clicker and come back with your results.
You can do 5 writs at a time, which is about 30 minutes. Reaching over and clicking the Create Rush Order button every 30 minutes should not be that bad.
Also, you will encounter problems with your bot if your second run trys to start with out the writ giver targeted. Make sure your not pressing any stupid ESC's with your mouse clicker, and make sure your mouse clicker is turned off, uninstalled, and your computer reformatted... Before you try again.
I'm not going to uninstall anything from my pc, and reformatting is not a option..I have my hard drive encrypted with AES/Blowfish encryption, so I am NOT going to reformat as its a bitch to encrypt again.
Now that thats settled, the mouse clicker was not on..in fact it works perfectly regardless, however for testing purposes I disabled it and made sure it wasn't running. I currently have the bot set to craft 2 writs, and when it finishes the first writ, it crashes...this is WITHOUT the clicker or anything else, just the bot crashing. I would give more detailed info, however the craft.log is not generating for some reason as well. If you can tell me how to debug it and get the craft.log to show up, then I can paste the problem and perhaps read it myself and maybe come to a conclusion.
there's no debugging information for that part of the script in the log anyway. why? because THAT PART OF THE SCRIPT WORKS PERFECTLY FOR EVERYBODY BUT YOU.
there is something wrong on your end.
when did the problem start? did you change any eq2 options before it happened? what changed between it working and it not working?
there is something wrong on your end.
when did the problem start? did you change any eq2 options before it happened? what changed between it working and it not working?
Ok mouse clicker aside and everything else aside, to get a craft.log you need to launch craft in debug mode. sooo craft -debug and you will get one.
The script will end if it can't parse a recipie which to you could appear to be a "crash" what level is your crafter and what type.
The script will end if it can't parse a recipie which to you could appear to be a "crash" what level is your crafter and what type.
Solution
After a few hours of troubleshooting myself and a friend concluded that it would only crash when I preselected the writ person and fired up the bot, when I didn't select anything and then fired the bot up everything works fine. FTR the mouse clicker does work, you just have to know how to implement it
.
After a few hours of troubleshooting myself and a friend concluded that it would only crash when I preselected the writ person and fired up the bot, when I didn't select anything and then fired the bot up everything works fine. FTR the mouse clicker does work, you just have to know how to implement it
.Bit of a necro post, but having the same error. This only happens occasionally. The bot is picking up the new quest but can't seem to get the recipes from the work order clipboard, of which I have 5 on the wall behind the Rush Order agent right in front of the bot. Any ideas?
Console says:
EQ2Craft:: Remaining Writs to Make: 5
EQ2Craft:: Processing Writ Recipes...
EQ2Craft:: Moving to Device: 'Chemistry Table 2'
EQ2Craft:: Remaining Writs to Make: 4
EQ2Craft:: There was a problem obtaining a writ quest -- ending script.
One additional observation: sometimes it finds the recipes to make, but then stalls with the same error before going to the table.
Console says:
EQ2Craft:: Remaining Writs to Make: 5
EQ2Craft:: Processing Writ Recipes...
EQ2Craft:: Moving to Device: 'Chemistry Table 2'
EQ2Craft:: Remaining Writs to Make: 4
EQ2Craft:: There was a problem obtaining a writ quest -- ending script.
One additional observation: sometimes it finds the recipes to make, but then stalls with the same error before going to the table.
Last edited:
bjcasey
ISX Specialist
Make sure that the clipboards are rendering. Laggy guildhalls usually make the bot screw up much more often.
Ok checked all the logs. I was wrong. The problem is the bot is backing up too far away from the crafting table and getting an error "you are too far away to interact with that." The script then times out and goes back to the Rush Order agent. It only looks different depending on whether I catch it during the timed period or after. I have re-done the paths like 3 times, think it may just be lag.
bjcasey
ISX Specialist
If that's the case then search my post history. I had that same problem a bit back and got some advice on how to tweak the craft bot settings to make things better.
I never really understood why the nav lib seems to think that pressing back 5 times is better than pressing back once. If it doesn't stop you after one press, wtf is it going to do with 5, other than piss someone off and look incredibly botty?
I may put this on my todo list to tweak. Meanwhile, removing any kind of speed buffs may also solve your problem.