[Open Source] Lucky's Spacebot

[phagotron]

Will you guys be adding functions to start SWTOR if it crashes?

ive already created the coding myself and added it to the source and complied, but with every new update i have to re-add it and its kinda a pain.

Contribute your code, we might add it :) ( with or without your secrets ;)

I am not sure if this a feature would be such a good idea. For a general functionality it would mean that all your questions have the same answer. If we save your credentials in .ini there would be a high risk to deface your account if you send a copy of your bot to anyone (or maybe for some less experieced users). Last but not least - political issues. Currently we seem to be tolerated. I appreciate that and guess that currently all parties benefit from the bot since there is no risk and no harm potential. That might change then.

[vapor311]

It would require storage of the user password. Security questions answers wont matter as they are only needed once. However storage of the password could provide troublesome due to liability if the team wishes not to get involved with that.

[Nhuts]

Perhaps the username / pw could be in an ini file stored elsewhere. The bot has admin-rights, so it could create one in the %user%\appdata folder. So if someone makes a copy of his bot dirctory, this ini-file won't be copied.

[phagotron]

Perhaps the username / pw could be in an ini file stored elsewhere. The bot has admin-rights, so it could create one in the %user%\appdata folder. So if someone makes a copy of his bot dirctory, this ini-file won't be copied.

The most easy way would be to run it as a seperate program.

[phagotron]

It would require storage of the user password. Security questions answers wont matter as they are only needed once. However storage of the password could provide troublesome due to liability if the team wishes not to get involved with that.

Hmm, for me this seems to be only sometimes true. I havent payed much attention to it yet, but I usually get the questions more than once a day. Anyway, with disabled hibernation the bot will wait infinite for the client to recover, so a separate app that revives the client would do without any issues. Waiting for the first request of a tokenized user then

[mcinsane]

Contribute your code, we might add it ( with or without your secrets

I am not sure if this a feature would be such a good idea. For a general functionality it would mean that all your questions have the same answer. If we save your credentials in .ini there would be a high risk to deface your account if you send a copy of your bot to anyone (or maybe for some less experieced users). Last but not least - political issues. Currently we seem to be tolerated. I appreciate that and guess that currently all parties benefit from the bot since there is no risk and no harm potential. That might change then.

The password file is located outside the bot folder, it allows me to share my bot folder without worry.

It would require storage of the user password. Security questions answers wont matter as they are only needed once. However storage of the password could provide troublesome due to liability if the team wishes not to get involved with that.

I was apart of a team that created packet reading bots for Silkroad online and this was one of the biggest complaints, my answer to this question was:
Somewhere in the terms of agreement is a sentence that says "3rd party programs are not allowed, regardless of there methods and could lead to a(n) account ban", so if you want to use this bot then understand the consequences of using it.
But we always made it optional to store your password, if you wanted to take the risk, then you benefited more from it. if not, then you just had to check your bot every few hours and re-log if needed.

Perhaps the username / pw could be in an ini file stored elsewhere. The bot has admin-rights, so it could create one in the %user%\appdata folder. So if someone makes a copy of his bot dirctory, this ini-file won't be copied.

I have the ini file that contains the password not located in the bot folder, it its located at a location i choose.
On startup the bot asks for the location and will store the location until the bot is terminated and then delete it.
password is also encrypted with _StringEncrypt to help with security.

This helps so i can share my folder without worry.

The most easy way would be to run it as a seperate program.

this is what i do, its to much work to incorporate the whole program into the bot and with each new update it would take forever!
the main program just sends variables to the Login program like how the Main() program sends variables to ImageSearch.

Hmm, for me this seems to be only sometimes true. I havent payed much attention to it yet, but I usually get the questions more than once a day. Anyway, with disabled hibernation the bot will wait infinite for the client to recover, so a separate app that revives the client would do without any issues. Waiting for the first request of a tokenized user then

You receive security questions when the SWTOR servers notice you logging in from a new location, so this could possibly mean you have a dynamic ip instead of a static ip.

[Altmaster]

One thing I've observed here is that there seems to be a small group of people (myself included) who are finding the bot just won't pick up the timer init, and gets into the quit/relog loop. I know the standard advice is check your settings, adjust the tolerance, etc, but I've found for most of the missions even running 125 tolerance doesn't help; taking a new screencap of the timer does the trick, however.

Indeed, some of the included timer caps look nothing like my screen: they have a noticeable amount of background space to the right, where my timer is always flush against the 's' for seconds. I'm wondering if something is causing certain clients to display the timer differently.

[vapor311]

Feel like I just got hit with a big wall of spam lol, but valid none the less.

[Nhuts]

Anyway, with a proper system set it is not really necessary to relog. I set up my virtual machines as i posted before, the client crashed 1 time in 7 days (second didn't). Before i was testing with windows XP, there the client crashed 3-4 times a day. I just did kalee with my jedi with 208/11. With the sloppy XP-VM i weren't be able to.

[phagotron]

One thing I've observed here is that there seems to be a small group of people (myself included) who are finding the bot just won't pick up the timer init, and gets into the quit/relog loop. I know the standard advice is check your settings, adjust the tolerance, etc, but I've found for most of the missions even running 125 tolerance doesn't help; taking a new screencap of the timer does the trick, however.

Indeed, some of the included timer caps look nothing like my screen: they have a noticeable amount of background space to the right, where my timer is always flush against the 's' for seconds. I'm wondering if something is causing certain clients to display the timer differently.

Yes, this was what I too have seen from the posted images. They differ, reason unknown. Guess we need to include an alternate image set and make it selectable. Since I cant produce these pics I need someone else to do it. Once I get the set (all the space_ ones) I will add the feature.

[phagotron]

Anyway, with a proper system set it is not really necessary to relog. I set up my virtual machines as i posted before, the client crashed 1 time in 7 days (second didn't). Before i was testing with windows XP, there the client crashed 3-4 times a day. I just did kalee with my jedi with 208/11. With the sloppy XP-VM i weren't be able to.

Nice, sounds as if the bot runs like a machine. Yesterday I've seen more users in space then have been on fleet before the big move. We should rename the baby to Luckys SpaceInvader.

[TMichael]

Great update, bonus rocks! Havent much time to test today, but just uploaded it into SVN so happy testing for everyone!




I'd say the mission now is a big step closer to 6.0 ... The 5.x attack functions are quite similar and repetitive, but they are short, easy to handle and have only few side effects. Even if quite simple, we now have narrow-band, broadband and filtered attacks, each used for its special purpose and maybe (so the plan) exchangeable and tunable in some future version. I wanted every click go to mmove to make sure that the click inhibit works safe and secure if no client is detected. Also it enables the debug mode which sometimes helps to sort out wrong pixels and further mmove will provide a position prediction depending on its actual position some day. Switching shield in an attack did lead to problems, since it tended to mutual failures. Alas the pixelsearch in there might be a good way to avoid that. In the next days there wont be much time, but I'd want stitch and tie it together so shield_on/off, evader and sway become equipped with the new abilities to reduce the need of special functions for each mission as soon as possible.

And - beside all discussion - the new functions do great and are a real advance, so big thanks again!

Quite welcome! It was a fun use of my time, and besides that, it's nice to work on some of these missions knowing there are credits to be made.

Integrating attack types into mmove sounds like the way to go. In the case of ImpossibleX(), I needed a simple subroutine to locate pixel color, verify red crosshair, and then fire a left and right click, so having something like this in mmove (narrow band?) would be perfect. On my part, I was loathe to tinker with that function since all the other missions rely upon it.

Per the actual mission, after more testing, it seems that the primary and bonus objectives can still fail ~ 20% of the time in level 48 vendor ship gear. I'll post more updates as I find ways to get that percentage smaller.

I appreciate the help on missions TMichael! I am sure our resident 5.3 master feels the same. Phagotron is a machine but even he still needs some help lol. I just got back and I am going to be working on 6.0 with the little time I have. I want to know if you would like to be a permanent member of the team and I will give you a trunk on the work server where you can submit your work. That way we can all collect the stuff at one place and I think it would benefit Phago and myself as well as you in the future. Lemme know and if so I need an email address I can send the invite from Assembla. If you have any questions on how or what to do I am sure Assembla could help you as well as myself or Phago. Phago fell in love with Assembla all ready and is considering a having babies with it, LOL!

Sure thing - honored to be able to help out! I'll send you a PM with my email and read up on Assembla.

[vatoloco]

one question...will this work on laptop 1366x768 after rezising it to 1024x768?

[Cystacae]

Will you guys be adding functions to start SWTOR if it crashes?

ive already created the coding myself and added it to the source and complied, but with every new update i have to re-add it and its kinda a pain.

We may consider it, submit your code to Phagotron and perhaps he will add it to the next version.

[Cystacae]

It would require storage of the user password. Security questions answers wont matter as they are only needed once. However storage of the password could provide troublesome due to liability if the team wishes not to get involved with that.

This is my only issue... I am not going to be liable for someone using this feature and then getting their account hacked. So, if it goes it, beware!