[VoliBot] Auto Queue Bot

[Double Negative]

Originally Posted by Maufeat

Will try to fix it. Could you copy&paste your config.ini?

config

[General]
LauncherPath=C:\Users\Boost\Desktop\League of Legends
MaxBots=1
ReplaceConfig=false

[Account]
Region=EUW

But I also get the same error with the default one. Not using BoL.

edit: the only thing I changed was the path to league
edit2: running tiny7 on vmware

[Maufeat]

Originally Posted by Schlumpfpirat

config

[General]
LauncherPath=C:\Users\Boost\Desktop\League of Legends
MaxBots=1
ReplaceConfig=false

[Account]
Region=EUW

But I also get the same error with the default one. Not using BoL.

edit: the only thing I changed was the path to league
edit2: running tiny7 on vmware

C:\Users\Boost\Desktop\League of Legends

add a \

should be now

C:\Users\Boost\Desktop\League of Legends\

[Double Negative]

Originally Posted by Maufeat

C:\Users\Boost\Desktop\League of Legends

add a \

should be now

C:\Users\Boost\Desktop\League of Legends\

Still the same error. Also tried to add "" & to run it normal & as administrator.

Originally Posted by Maufeat

C:\Users\Boost\Desktop\League of Legends

add a \

should be now

C:\Users\Boost\Desktop\League of Legends\

Still the same error. Also tried to add ""s to the path & to run it normal & as administrator.

Startup routine:
- Boot VM
- start VoliBot.exe
- get errors & freeze thrown at my face


edit: as I said, I also got the error, when I used the default config.

[Tim1337Tim]

Works fine with BoL. Good job dude!

[Maufeat]

Originally Posted by Schlumpfpirat

Still the same error. Also tried to add "" & to run it normal & as administrator.



Still the same error. Also tried to add ""s to the path & to run it normal & as administrator.

Startup routine:
- Boot VM
- start VoliBot.exe
- get errors & freeze thrown at my face

Which OS? And you need .NET 4.5 Framework (don't know if your VM already have it?)

[AbsinteTR]

Help pls.If you want i can share my teamviewer.

[winstonfang]

Title^

[Double Negative]

Originally Posted by Maufeat

Which OS? And you need .NET 4.5 Framework (don't know if your VM already have it?)

.NET Framework 4.5 did the trick. How stupid of me not to think about that. I'd add it to the requirements at the first page though.

[Maufeat]

Originally Posted by AbsinteTR

Help pls.If you want i can share my teamviewer.

You can only queue ARAM if you are level 6.

Originally Posted by winstonfang

Title^

BoL ... uhm ... just Google it, the official site:

[blackrider1234]

if the game stard i get this error
and the bot crashed

[Maufeat]

Originally Posted by blackrider1234

if the game stard i get this error
and the bot crashed

In der config.txt ist der LauncherPath falsch oder der Pfad existiert gar nicht. Schau mal ob du auf deiner VM oder Host OS hier drauf kommst:

C:\Riot Games\League of Legends\RADS\solutions\lol_game_client_sln\release s

[silbermond09]

habe denn selben fehler wie blackrider. weis leider nicht was du mit vm oder host meinst. oder sind das programme die wir ( ICH ) brauche


allso bei mir startet er das game und dann stürtzt der bot ab

[Maufeat]

Originally Posted by silbermond09

habe denn selben fehler wie blackrider. weis leider nicht was du mit vm oder host meinst. oder sind das programme die wir ( ICH ) brauche


allso bei mir startet er das game und dann stürtzt der bot ab

VM = Virtual Machine (virtueller Rechner) und Host OS dein physikalischer Rechner.

Starte mal den Bot als Admin? Oder wie oben gesagt, schau ob es den Pfad "C:\Riot Games\League of Legends\RADS\solutions\lol_game_client_sln\release s" überhaupt bei euch existiert.

#Version 1.2.0 out, read changelog in the main post.

[.Paro]

'Unable to get Auth Key' - es bleibt bei 'in queue' hängen.

Lösungsvorschläge?

€ : Hat sich geklärt. Die Fehlermeldung erscheint zwar immer noch aber der Bot funktioniert nun. Danke

[Maufeat]

Originally Posted by Kingsfall

'Unable to get Auth Key' - es bleibt bei 'in queue' hängen.

Lösungsvorschläge?

'Unable to get Auth Key', schau ob die Region richtig abgekürzt ist, oder ob du noch Zugang zum Account hast oder sonstige Einschrenkungen (test login mit dem offiziellem client oder auf der webseite).

Falls trotzdem der Fehler weiterhin kommt, mach ein Screenshot und schick mir den Link per pn.