[Open Source] Lucky's Spacebot

[neileusmaximus]

After 30 min or so of botting i get BSOD and force restart. I can run it fine of a separate pc but mine BSOD's. I have a vertex 3 SSD which is really the only difference between the computers. both win7 64bit

[phagotron]

It can't even finish jablim escort in my inquisitor ship, it seems to just randomly target other things on the screen, so the escorted ship just ends up dying.

Running "low" graphics settings.

In addition to what TM said - better do not run Jabiim with bonus. The imperial side tends to aim their own missiles.

[phagotron]

After 30 min or so of botting i get BSOD and force restart. I can run it fine of a separate pc but mine BSOD's. I have a vertex 3 SSD which is really the only difference between the computers. both win7 64bit

The prob seems to be the box itself, I'd suggest to clock down the proc and run a detailed memory test.

[Technicolor808]

Hey I recently started using lucky's spacebot and it worked great, but after about 3 days of botting overnight I got a week suspension, I dont have my characters that bot in guilds or with any people on their friends list so I was wondering if there was a way to better protect myself from being detected while I bot, or if I was just incredibly unlucky.

Thanks in advance

[Darkbounded]

The prob seems to be the box itself, I'd suggest to clock down the proc and run a detailed memory test.

Even if he really has a faulty RAM stick, mem test won't tell him that, I am telling you because I was having a lot of BSODs when I bought my PC and none of the tests showed any sign for error, until I swapped my stick with a friend for 4x 2GB (I was with 1x8GB) and then suddenly my BSODs stopped, and he received 3 in a week (while he never had that before), it still depends what it says on the BSOD.

Honestly, my advice is screw the memtests and just swap the memory sticks with the other PC if the other PC starts getting BSODs then you know what's your problem, try different variations, one stick, two sticks, swap their place, depending how many sticks you got, you didn't mention it.... If you have 2 sticks, and if they are in 1 and 3 slot, you can try using 2 and 4, or swap their places like I said above, if that doesnt help, just put them on the other PC and let it run for a few hours/days, personally I was using my friends sticks for almost a week... anyway, I did every possible memtest, none of them showed any error

Anyway I have another issue now I'm sick of this why can't they make Pandaria that cheap so that I can get 20 accs.. anyway, I changed to the 8.0.4 version of VM, most of the issues got fixed ( I am not sure about kalee didn't have the time to test it but probably will tomorrow) but now they are using more 30-35% of my CPU each of them.. and with one running on the host my CPU goes 70-90% while before that I was able to run 3 VMs at like ~80%, I thought that it's cuz I removed the overclock on my CPU, but now that I overclocked it again, almost no result except that it rarely goes above the 90% mark now... could be the new windows... or maybe I need to put that lite win edition again.. I dont know..

One more thing concerning the bot, every morning when I wake up, I find some (if not all) of them not running (neither the client or the bot) any idea what may cause that? Both of them to be closed, I think that if the client just crashes the bot should still be running but why would it close instead of keep trying to restart it? This happened on the host/the VMs/the laptop.. I've seen it everywhere

[mrmr]

[Bug Report]

- Activate crew skills in the bot
- Send the first crew member on a mission
- Start the bot

The bot will try to click the "crew skill button" (unavailable, cause the crew member is already at work) and searching for the right mission, will zoom out (cause the mission selection window isnt' there and I guess mouse wheel is used to scroll the mission window).

I suggest to "check" if the crew member is already at work, before select the mission (check for the little "yellow" man portrait on the right).
Also, some check to see if the "right" window is open (in this case the "Mission" window), would be much appreciated.

[Breathofthedying]

Honestly, my advice is screw the memtests and just swap the memory sticks with the other PC if the other PC starts getting BSODs then you know what's your problem, try different variations, one stick, two sticks, swap their place, depending how many sticks you got, you didn't mention it.... If you have 2 sticks, and if they are in 1 and 3 slot, you can try using 2 and 4, or swap their places like I said above, if that doesnt help, just put them on the other PC and let it run for a few hours/days, personally I was using my friends sticks for almost a week... anyway, I did every possible memtest, none of them showed any error

I have seen this a lot ... I think dark is right on. Once overheating is removed from the equation memory is usually answer. I swear I think some sticks just don't like each other... Alone they fine.
PC are more forgiving and usually bsod... Macs just smoke and pop.

[neileusmaximus]

Even if he really has a faulty RAM stick, mem test won't tell him that, I am telling you because I was having a lot of BSODs when I bought my PC and none of the tests showed any sign for error, until I swapped my stick with a friend for 4x 2GB (I was with 1x8GB) and then suddenly my BSODs stopped, and he received 3 in a week (while he never had that before), it still depends what it says on the BSOD.

Honestly, my advice is screw the memtests and just swap the memory sticks with the other PC if the other PC starts getting BSODs then you know what's your problem, try different variations, one stick, two sticks, swap their place, depending how many sticks you got, you didn't mention it.... If you have 2 sticks, and if they are in 1 and 3 slot, you can try using 2 and 4, or swap their places like I said above, if that doesnt help, just put them on the other PC and let it run for a few hours/days, personally I was using my friends sticks for almost a week... anyway, I did every possible memtest, none of them showed any error

Anyway I have another issue now I'm sick of this why can't they make Pandaria that cheap so that I can get 20 accs.. anyway, I changed to the 8.0.4 version of VM, most of the issues got fixed ( I am not sure about kalee didn't have the time to test it but probably will tomorrow) but now they are using more 30-35% of my CPU each of them.. and with one running on the host my CPU goes 70-90% while before that I was able to run 3 VMs at like ~80%, I thought that it's cuz I removed the overclock on my CPU, but now that I overclocked it again, almost no result except that it rarely goes above the 90% mark now... could be the new windows... or maybe I need to put that lite win edition again.. I dont know..

One more thing concerning the bot, every morning when I wake up, I find some (if not all) of them not running (neither the client or the bot) any idea what may cause that? Both of them to be closed, I think that if the client just crashes the bot should still be running but why would it close instead of keep trying to restart it? This happened on the host/the VMs/the laptop.. I've seen it everywhere

Oddly it follows the same 30-45 min crash. Now, i turn my monitor off cause i only do it over night and log off when i leave for work. so max of 7 hours. I went for a walk today with friend and left monitor on. it did 18 runs for about ~1 1/2 hours. i dont know how turning off my monitor would affect it though

[Darkbounded]

I have seen this a lot ... I think dark is right on. Once overheating is removed from the equation memory is usually answer. I swear I think some sticks just don't like each other... Alone they fine.
PC are more forgiving and usually bsod... Macs just smoke and pop.

It can happen with 1 stick too, that was my case I was with 1x8GB Corsair Vengeance 1600MHz 9-9-9-24, it was defective they replaced it and it's just working ever since, a while after that I bought a second stick to get the Dual Channel up... anyway like I said screw memtests just do some sticks swapping if you can, that's your best test

So anyway, as I said, what can cause both the client AND the bot to close and when I wake up none of them to be working?

[TMichael]

Oddly it follows the same 30-45 min crash. Now, i turn my monitor off cause i only do it over night and log off when i leave for work. so max of 7 hours. I went for a walk today with friend and left monitor on. it did 18 runs for about ~1 1/2 hours. i dont know how turning off my monitor would affect it though

Hi neileus,

The game itself has been crashing more since patch 1.4. Normally, the starter would help with this, but crashes in general have been bugging out in the latest bot versions; the ending time for Run Time sessions and scheduled sessions has been changing after each crash.

I'm in the process of leveling up a few new accounts, but I should be able to spend some time on the fix within the next day or two. Once we get it working, the bot should weather most crashes consistently (with the exception of hardware failure and internet connectivity crashes - there are some things for which you can't adjust).

So anyway, as I said, what can cause both the client AND the bot to close and when I wake up none of them to be working?

@Dark: I have seen this happen as well. Obviously, starter fixes won't be much help if the bot itself crashes along with the game client!

So, the question of the day: Is the game client or the bot responsible? :confused: I'm really hoping it's the bot, because that means we can fix it. If it's the game client, well... I anticipate more bot babysitting in our futures...

[Darkbounded]

Well bot or client it really doesn't matter, because there is still a solution, and that solution is the starter to get "unintegrated" and be a separate .exe like it was before the integrating that will monitor both the client and the bot so even if they both crash, the starter will get them both back on, and I guess that all u need to do is just put ur fixes in the other restarter and save urself the time of making a new one, but from what I've seen the client crashes first then the bot... altho I couldn't see what's on the debug line, I was in the other side of the room sleeping o_O and since AutoIT can't do multiple tasks at the same time like u said, I guess u can't make it make logs for easier troubleshooting :>

[TMichael]

Well bot or client it really doesn't matter, because there is still a solution, and that solution is the starter to get "unintegrated" and be a separate .exe like it was before the integrating that will monitor both the client and the bot so even if they both crash, the starter will get them both back on, and I guess that all u need to do is just put ur fixes in the other restarter and save urself the time of making a new one, but from what I've seen the client crashes first then the bot... altho I couldn't see what's on the debug line, I was in the other side of the room sleeping o_O and since AutoIT can't do multiple tasks at the same time like u said, I guess u can't make it make logs for easier troubleshooting :>

Whether the process is running integrated or not, a crash is a crash. If the game client is causing AutoIt to crash, then separating it into two scripts won't make a difference.

Besides, the fact that we are running inside VMs is probably a factor as well.

[Darkbounded]

Whether the process is running integrated or not, a crash is a crash. If the game client is causing AutoIt to crash, then separating it into two scripts won't make a difference.

Besides, the fact that we are running inside VMs is probably a factor as well.

Like I said I've seen it happening on the host, on the laptop and the VMs, so I don't think that it's cuz of that...

[UseTheForce]

I switched to VMWare 8 (8.04) but still use the same OS (windows 7 32 bit). Only thing that i did was that i installed AMD GFX drivers directly to the VMWare OS, rebooted and i still had the same issue with red screen until i pressed ctrl+u then the red screen went away and i got a screen like you got in the link. After that i got tired of fighting with it so i turned off the VMwares for the night. Today i changed some settings for the VMwares such as disable page trimming (edit virtual machine settings/options/advanced), changed ram to 3512 mb, changed to "center guest" (preferences/display) and powered up and it worked. So i can't actually say what i did...

OFC i have installed all the stuff such as directx, net 3-4 and c++.

i have the same red screen issue on a computer running an i7-920 and i tried all 3 changes to vmware that you said and i still get the red screen. anyone know how to fix this?

maybe i need to install the game normally and not copy it from another computer?

[Darkbounded]

Just get vmware 8.0.4