[Bot] GIBot

Is there any fix for "waiting for client" problem ?
The bot doesn't detect the client ?!

The developer is aware of the issue that the latest patch is NOT currently compatible with the current version, 1.8.1
Please wait. A new update will be out soon.

riot offset the clients starting position by 14 pixels up. I did some testing as I have my own bot. Pretty easy fix. Just subtract 14 from every y value and it should work.

Quote:

Originally Posted by sanxownage23 riot offset the clients starting position by 14 pixels up. I did some testing as I have my own bot. Pretty easy fix. Just subtract 14 from every y value and it should work.

that.. and for some reason (only for me?) if you use ONE shared client folder it will (as soon as 1 bot has to restart the client, after reaching lvl10) stuck on the patcher with a unkown exception.
have to delete the RiotRadsIO.dll in lolclient\RADS folder before starting up the client.

i acutally solved this a lot easier than i thought i had to. there is a command in autoit called mouse click drag. drag it in the y plane by 14 down. PROBLEM SOLVED :D

Quote:

Originally Posted by sanxownage23 i acutally solved this a lot easier than i thought i had to. there is a command in autoit called mouse click drag. drag it in the y plane by 14 down. PROBLEM SOLVED :D

guess autohotkey didnt want me to have it easy xD

IMO i think this solution is much better in case next patch riot decides to go back to the original starting position.

use auto it. i used ahk at first too. Autoit is SOOOOOOOOOOOO much better. Alot easier because there are alot more prebuilt function libraries.

Right now, I've opened the bot and it just sits at the nasus login screen not typing anything in.

Would anyone care to share the autoit fix for the 14 pixels up? Cause I guess that's what is causing issue :)

If not, maybe fix soon?

nvm all this i suck at these stuffs

Quote:

Originally Posted by Martin0432 Right now, I've opened the bot and it just sits at the nasus login screen not typing anything in. Would anyone care to share the autoit fix for the 14 pixels up? Cause I guess that's what is causing issue :) If not, maybe fix soon?

I have created a temporary fix. Drag the 3.14fix into the host and player shared vm folder (Z drive in VMWARE) and run it when it gets stuck on the loading screen. If this doesn't fix the problem, you will just have to unfortunately wait for the creator to patch the program.

[Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by sanxownage23 I have created a temporary fix. Drag the 3.14fix into the host and player shared vm folder (Z drive in VMWARE) and run it when it gets stuck on the loading screen. If this doesn't fix the problem, you will just have to unfortunately wait for the creator to patch the program. [Only registered and activated users can see links. Click Here To Register...]

protected? cant download...

Quote:

Originally Posted by arthasdk protected? cant download...

[Only registered and activated users can see links. Click Here To Register...]

No, the media fire file is under "private" setting.

It's not public so people have to request to download it first! :P

change to public ?

[Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by Martin0432 No, the media fire file is under "private" setting. It's not public so people have to request to download it first! :P change to public ?

Im sorry, this is my first time sharing files like this.

Did it work?

When you compiled the script, I don't think you used x86 format, this .exe file is not a valid win32 application.

For it to work on windows XP VM's, which is what most ppl run, it'd have to be x86 version, not x64.


what are you running VM's or bot on? Win 7?