[Bot] LoLEtal v1.0 - LATEST VERSION!

04/20/2012 17:13 Laнonda#3091
Quote:
Originally Posted by AzraiiL View Post
wie kann man viele Gleichzeitig öffnen ?
einfach einen nach den anderen öffnen ?
Indem du LoLEtal auf mehreren VMWare Maschinen laufen lässt
04/20/2012 19:00 solitudedude#3092
Problems now:

1. Still get "The server is currently busy. Please try again later" on a regular basis.

2. Bot puts the same name for Summoner Name, and gets error. Needs to put a random name for it to work.

3. Bot still soemtimes has problems at "team selection" screen where it gives error "The teams are unbalanced. You will not be receiving xp for this game. Do you wish to continue?"

Thanks
04/20/2012 19:12 Sumii#3093
Hmm did the bot on the tutorial surrender too?
04/20/2012 19:15 luio1#3094
Quote:
Originally Posted by AzraiiL View Post
wie kann man viele Gleichzeitig öffnen ?
einfach einen nach den anderen öffnen ?
ich frag mich ob manche leute sich den kompletten startpost durchlesen wo wirklich ALLES erklärt ist oder einfach nur "Bot" lesen und den download link suchen und anschließ0end sich wundern warum etwas nicht klappt, oder fragen stellen die bereits im OP stehen...
04/20/2012 19:19 Devil_Inc#3095
whats the changes from 1.28 to 1.30?
04/20/2012 19:19 Sumii#3096
Quote:
Originally Posted by Devil_Inc View Post
whats the changes from 1.28 to 1.30?
Fixed the Update From Riot.
04/20/2012 20:34 xUnkx#3097
Since the update I get some bugs like the accs dont buy the Exp Boost or if I stopped some acc at lvl 2 for example, the next time I put it on start with the tutorial :S
04/20/2012 21:24 Maxh95#3098
they fixxed battle training cause it just stacking in loading screen
04/20/2012 21:57 lilVaratep#3099
For some reason I get an error when trying to run in Virtualbox. direct3d error. anyone know how to fix this?
04/20/2012 22:02 primordius#3100
Hey mate, you should look into the new update, from etal and league of legends, since your update and lol's update, the bot cant make the sumuners name, it wont start a new costum game after one is finished, and when it leaves the Battle training he doesnt do anything, it was working at 100% before all that, ty :)
04/20/2012 22:43 kodon#3101
I have just one problem with bot. He doesn't create the summoner name. Except this one everything works just fine.
04/20/2012 23:06 jax812#3102
Quote:
Originally Posted by CJ2311 View Post
If your computer sleeps, it's basically shutting down all activity, including your connection to the Riot servers and the bot itself...
not sure if i was unclear earlier. i meant extend the length of time *before* it goes to sleep.

However, i would think that since the computer is going to sleep in the first place, all activity has already ceased (implying that the bot has disconnected already). Am i wrong to think this? Or is the program supposed to allow the computer to fall asleep, but when the computer falls asleep, it shuts down the internet connection?

tl;dr(or confused): in order to make the bot run all day, do i need to set my computer so that it never sleeps? or is something going wrong with the bot that leaves the computer idle, thus allowing it to sleep?
04/20/2012 23:13 Maxh95#3103
fixxed
04/20/2012 23:40 xUnkx#3104
Quote:
Originally Posted by primordius View Post
Hey mate, you should look into the new update, from etal and league of legends, since your update and lol's update, the bot cant make the sumuners name, it wont start a new costum game after one is finished, and when it leaves the Battle training he doesnt do anything, it was working at 100% before all that, ty :)
The same
04/21/2012 00:14 CJ2311#3105
Quote:
Originally Posted by jax812 View Post
tl;dr(or confused): in order to make the bot run all day, do i need to set my computer so that it never sleeps? or is something going wrong with the bot that leaves the computer idle, thus allowing it to sleep?
You're the one confused : I clearly said that your PC must not go to sleep at all or it will stop your virtual machines altogether.

Quote:
Originally Posted by xUnkx View Post
The same
Yeah, I've also have been having this issue with 1.3.0 :/
EDIT: Nvm, it's gone with the hotfix :D