[Open Source] Lucky's Spacebot

[Hunt87]

hi guys, im still having trouble with the power conversion sticking on shields or not activating at all, have tried the R261 and no different, was working perfectly before 1.5 patch, any ideas?
thanks

Luckys Spacebot v5.35 x86 (R261)

System details: X64 CPU, WIN_7(X64)
RAM total:9 GB,free:6 GB, used:31 %
Desktop dimensions: 1680x1050(32bpp, 120Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi

SWTOR Client is running with 1024x766

SWTOR Window:0,0 Win size:1040x804
Color scheme: Aero

On Target Time=50
Missile Delay=333
Timer Skew =50
IMG Tolerance=106
HD Status=1
Timing override=4
Mission bonus=4
PSX OTT enabled=1
PSX DBG enabled=1
Last mission=
Win / Loss 0 / 0

EDIT found the problem, had to go into interface editor and reset to default, working fine now

[UseTheForce]

Anybody tried this with a F2P account after buying the cartel coins to unlock a weekly space pass? It worked well for me, but there's a 3 mission limit on f2p users. I was wondering what the ban rate would be like

it'll be the same

[UseTheForce]

Is anyone still farming at all? All my accounts get banned before I reach 28 lvl (right at ~27ish)

don't bot 24/7 and don't bot level 27

[wn2142]

Is there a way to randomize the precision of the mouse clicks so as not to click the exact same spots in exactly the same sequence every single time? Like clicking randomly within a pre-determined pixel radius when selecting &/or using "sloppy" pointer navigation?

[TMichael]

Is there a way to randomize the precision of the mouse clicks so as not to click the exact same spots in exactly the same sequence every single time? Like clicking randomly within a pre-determined pixel radius when selecting &/or using "sloppy" pointer navigation?

The shield mover defensive function already clicks within a random radius, and most clicks during each mission (firing at targets) will vary every time because of the way PixelSearch() works. That being said, click location seems an unlikely bot indicator for BioWare; if it were being used, I suspect Untzbot (mission recording) would have had more success at avoiding the ban hammer.

[wn2142]

Click location may be a factor or not, I am trying to work with the "can't hurt/might help" philosophy here. What about randomizing the name/ID in memory either through a custom-compile or an adjustment in the default executable that actively spawns a different name each time its run (a la the way Pirox bot/etc used to work)? Someone will probably reply that memory scanning isn't implemented by bioware but again, I'm just trying to err on the side of caution...

Are there any definitive parameters / operating guidelines that minimize chance of detection while still allowing reasonable added value when using the bot?

[TMichael]

Click location may be a factor or not, I am trying to work with the "can't hurt/might help" philosophy here. What about randomizing the name/ID in memory either through a custom-compile or an adjustment in the default executable that actively spawns a different name each time its run (a la the way Pirox bot/etc used to work)? Someone will probably reply that memory scanning isn't implemented by bioware but again, I'm just trying to err on the side of caution...

Are there any definitive parameters / operating guidelines that minimize chance of detection while still allowing reasonable added value when using the bot?

I've tried random names as well as changed code compilations, and, unfortunately, it's made no difference regarding bans. I think frequently repeating space missions will simply flag an account for a closer look. New accounts seem to get the most attention.

The best advice I can give per detection is to use the bot in moderation, especially during the first few weeks of account life.

[sapik1980]

hello people,

Sorry that I have to be translated on google since I have no KNOWLEDGE English.
if I swtor and Lucky's Spacebot start work after the first 20-25 fights room hangs swtor.
please help.

MfG Sapik


hallo leute,

sorry das ich über google übersetzen lassen muss da ich kein englisch kentnisse habe.
wenn ich swtor und Lucky's Spacebot starte funktioniert die ersten 20-25 raumkämpfe danach bleibt swtor hängen.
bitte um hilfe.

MfG sapik

[TMichael]

hello people,

Sorry that I have to be translated on google since I have no KNOWLEDGE English.
if I swtor and Lucky's Spacebot start work after the first 20-25 fights room hangs swtor.
please help.

MfG Sapik


hallo leute,

sorry das ich über google übersetzen lassen muss da ich kein englisch kentnisse habe.
wenn ich swtor und Lucky's Spacebot starte funktioniert die ersten 20-25 raumkämpfe danach bleibt swtor hängen.
bitte um hilfe.

MfG sapik

If I understand you correctly, and your computer hangs after 20-25 minutes, that likely means you need more memory or processing power to run SWToR + the bot for any reasonable length of time. The game itself is extremely resource intensive.

[phagotron]

hello people,

Sorry that I have to be translated on google since I have no KNOWLEDGE English.
if I swtor and Lucky's Spacebot start work after the first 20-25 fights room hangs swtor.
please help.

MfG Sapik


hallo leute,

sorry das ich über google übersetzen lassen muss da ich kein englisch kentnisse habe.
wenn ich swtor und Lucky's Spacebot starte funktioniert die ersten 20-25 raumkämpfe danach bleibt swtor hängen.
bitte um hilfe.

MfG sapik

Hmm, sind ein bisschen wenig Infos, hört sich nach einem Speicherproblem an. Schau mal unter Tab About, da gibt es eine Sysinfo-Taste. Poste uns das aus dem Diag-Fenster doch mal, vielleicht können wir dann mehr sagen.

[sapik1980]

Luckys Spacebot v5.35 x86 (R260)

System details: X64 CPU, WIN_7(X86) Service Pack 1
RAM total:2 GB,free:0 GB, used:69 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)
Desktop theme: Custom

SWTOR Client is running with 1022x759
SWTOR Window:0,0 Win size:1040x804
Color scheme: Aero

On Target Time=50
Missile Delay=333
Timer Skew =50
IMG Tolerance=106
HD Status=0
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=
Win / Loss 0 / 0

ich habe auch alle funktionen probiert,aber leider erfolglos

[TMichael]

Luckys Spacebot v5.35 x86 (R260)

System details: X64 CPU, WIN_7(X86) Service Pack 1
RAM total:2 GB,free:0 GB, used:69 %
...

- Update to R261 (fixes an issue which occurred in patch 1.5)
- Upgrade system to 3GB+ RAM (2GB RAM really isn't enough to run SWToR + the bot without issues)

Good luck!

[sapik1980]

huhu,
super danke,lag doch meinem arbeitsspeicher.
ich kann nicht erklären warum mein arbeitsspeicher ausgelastet war.
aber hat die ganze nacht gelaufen.
MfG sapik

huhu,
super thank you was, but my RaM.
I can not explain why my RaM was busy.
But the whole night has gone.
MfG Sapik

[wilzy89]

New here so heya all!

This bot has caught my eye. If i download the file from the link on first page saying

"Current Build (rar/7z archived from subversion server)
x86 | x64"

is this the latest version? Am I likely to get banned for using it, or am I pretty safe if I use it correctly?

Thanks guys

[TMichael]

New here so heya all!

This bot has caught my eye. If i download the file from the link on first page saying

"Current Build (rar/7z archived from subversion server)
x86 | x64"

is this the latest version? Am I likely to get banned for using it, or am I pretty safe if I use it correctly?

Thanks guys

The x86 link is the latest version. Use with extreme care and in moderation - BioWare has been targeting space botters for some time now.

Good luck!