On the issue I reported earlier with step 218. I first thought it could be that my VM lagged but then I tried it on my normal OS which never laggs but it occurred again. I added one bot manually so it worked but there is definitely a bug somewhere
Got some new accounts. Will release the update over the weekend.Quote:
On the issue I reported earlier with step 218. I first thought it could be that my VM lagged but then I tried it on my normal OS which never laggs but it occurred again. I added one bot manually so it worked but there is definitely a bug somewhere
I am glad I left this error in there. Error on Line 55 means the path to your lol.launcher.exe is not input properly. Please check config.ini and make sure the path to lol.launcher.exe is correct. It should look like {path}\lol.launcher.exe. {path} is the part that you were suppose to input when the bot asked you for the folder path to lol.launcher.exe.Quote:
i have problem with step 55 :/ it dont start^^
This project is my baby. Sorry, but I really don't want anyone else touching my baby. I showed you how to make your own baby, and you will be able to make one when you are ready. The fact that you can't open WinAutomation source tells me you are not ready. Sorry again.Quote:
Can you tell me how to open source files? Got Winautomation installed but no chance to get the source files inside. Btw files have no endings?! I'm really looking forward to get inside the technics of your bot and maybe help you finding bugs.
Hope to hear from you!
i for got to tell you that my account was in-game with 93 mins past and the afk/disconnect message thing (if that helps in anyway).Quote:
Thank you nymkhan8. I got 1 more report about the same line. I'll most certainly fix it on next update.
Working on the afk issue. Fixed the browser issue on the upcoming update. The bot will look for and close iexplore.exe, firefox.exe, and chrome.exe before every game.Quote:
i for got to tell you that my account was in-game with 93 mins past and the afk/disconnect message thing (if that helps in anyway).
another error:
[Only registered and activated users can see links. Click Here To Register...]
another thing to note in that picture is the tribunal ie explorer thing. that's one of the problems that happens when the bot restarts after an error and reopens LOL. it'll miss-click and click the tribunal a few times before clicking "play".
Fixed on the upcoming update.Quote:
same thing here step 218
time 22:56
Glad it worked. It is not possible to change bot difficulty yet.Quote:
oh i found the problem i didnt wrote the path to lol^^
the bot is nice . can you change the allie bots into difficult? it would be easier to win than
Quote:
Changelog v2.01 to v2.12:
- Automatically closes all IE, FF, Chrome windows.
- Fixed failure to select CS in game selection.
- Fixed failure to Lock In after game setup.
- Shopping is done now after level checks.
- Added SXLSA.exe which accelerates manual account creation. Read more above in Instructions.
- Added meaningful message for when bot can't find path to LoL executable.
- Battle Training can now be played using BT.exe. Read more above in Instructions.
- Added options for 3 day exp boost, and 1 day + 4 win exp boost.
- Battle Training should now be recorded in status.txt so that you can check if an account went through BT.
- taskkill.exe can now terminate all included executables.
- Battle Training should now be fixed in the main bot. There should be no more AFK issue.