-
KickKitty Auto Kicker
#EDIT
This project is no longer supported. This is because BotKitty has been rewritten.
Also it had a bunch of problems.
This tool is based an automatic spell kicker which kicks at beginning of channelled spells and in the end of other spells. This software is based on jozsab1's Spell Kicker and is merely a port with some bugfixes to it using BotKitty. The original version is here. All credit goes to him. I have tested it on Legion and 3.3.5. The reason this bot is written is to explore the real world applicability of BotKitty which provides an scripting environment for general bot programming (Disclaimer, I am the author of it). If you try it out make sure to follow the instructions of this thread and not joszab1s. Because even though we use pretty much the same LUA addon the other stuff work very differently.
This is what is supported now: (Copied from jozsab1's version)
- hard to detect by blizz
- interrupt main target spell casting
- interrupt focus target spell casting
- interrupt any arena opponent spell casting even if not targeted ( if possible ) ( you have to add keybinds for it )
- lag compensation
- adjustable timers to fine tune moment of interrupt ( end of the cast bar at millisecond precision )
- setting to avoid interrupting instant cast spells
- most class interrupt spells included by default ( let me know if i forgot some )
- optional spell white list( only interrupt these spells ) ( by default list is empty )
- optional spell blacklist( interrupt anything but these ) ( by default list is empty )
- optional to only interrupt if target is bursting ( included some names by default but you need to set NumberOfBurstAuras = 1 )
- do NOT interrupt if target is spell shielded ( enabled by default )
- anti bot fake cast protection ( check if target is specced for that spell + only interrupt at last moment )( default list is empty )
- option to only interrupt spells that are buffed by specific auras ( bad ex : only interrupt Exorcism if target has Holy Avenger )
- GUI for quick keybind setup
- option to resend spell cast on failed cast ( latency / silence.. )
- option to use cyrilic ( UTF-8 ) keys for keybinds ( not practically tested )
- free, open source. You can change it and use your own version. Please post all your changes here, even if it is very small ( it makes me happy )
However there is two bugs which the original version does have which is fixed here. And that is that you can run BotKitty and WoW in different "bitness" versions and it will just work. I would love to pull them to the original version but this version does not use AutoIt which is where the problem lies.
Bugs:
- Currently window fullscreen does not work
Setup(Notice this was changed 7 january):
- Download KickKitty
- Extract it in a directory where you want to keep it
- Run KickKitty/addon/GenerateRandomName.exe file.
- In the KickKitty root directory there will be a directory with a random name
- Copy that directory to your WoW addon directory
- Download and install BotKitty.
- Start BotKitty and in the BotManager add the KickKitty bot.
- Start WoW, and make sure that your addon is loaded. It is the same name as the generate random name tool generated.
- Enter world.
- There will be a green frame in the middle of screen now. Move it by ctrl+drag the frame to any appropriate location. But make sure it is not hidden.
- In BotKitty select KickKitty and hit start.
- Congratz, bot is now running.
How it might look:
Attachment 47245
Improve the bot
- Report bugs with KickKitty on github
- Report bugs with BotKitty here.
- If you hate it, let me know^^
- If you like it, say thanks^^
Virustotal:
https://www.virustotal.com/sv/file/7...is/1482058889/
If you think this antivirus check is not good enough, let me know.
Download:
- x86 BotKitty: http://product.botkitty.com/BotKitty_installer_x86.exe
- x64 BotKitty: http://product.botkitty.com/BotKitty_installer_x64.exe
- KickKitty: Github
Blog
If you want to explore how it is written I have written a blog about it.
Edit:
Special thanks to JasDevi and Vekom for reporting bugs! Really appreciate it
Last edited by Kickupx; 02-17-2017 at 11:10 AM.
Reason: BotKitty is rewritten and this program is broken anyways.
-
Post Thanks / Like - 2 Thanks
ev0,
Miksu (2 members gave Thanks to Kickupx for this useful post)
-
I have no use for this, but +rep for open sourcing!
-
Post Thanks / Like - 1 Thanks
Kickupx (1 members gave Thanks to ev0 for this useful post)
-
Corporal
i keep getting this error bot.js@67: Result of expression 'wow_window' [undefined] is not an object.
-
Post Thanks / Like - 1 Thanks
Kickupx (1 members gave Thanks to JasDevi for this useful post)
-
Originally Posted by
JasDevi
i keep getting this error bot.js@67: Result of expression 'wow_window' [undefined] is not an object.
Yeah that is because the window is not found. I have now update KickKitty to error report this and also improved the window search so the window
should now be found.
Really thanks for the bug report
-
Member
I have installed everything but when i try to start the bot this is happening
Dec:23 - 0:58
bot.js@17: Could not open process with pid 0
Dec:23 - 0:58
Bot stopped
Any Suggestions?
-
Originally Posted by
Vekom
I have installed everything but when i try to start the bot this is happening
Any Suggestions?
You need to run the WoW first and then you are good^^
Then an random number will pop up in the Instances combobox.
Actually it is a bug that the number zero is popping up. It should not contain anything.
-
Corporal
bot.js@59: Only numbers between 0-9 or A-Z is allowed. it keep stopping but i only have numbers in my addon
-
Post Thanks / Like - 1 Thanks
Kickupx (1 members gave Thanks to JasDevi for this useful post)
-
Originally Posted by
JasDevi
bot.js@59: Only numbers between 0-9 or A-Z is allowed. it keep stopping but i only have numbers in my addon
Hmm, I can not reproduce this. Does it happen alot? And what WoW version are you using?
PM me so this thread does not get spammed^^
+rep for reporting
I also changed the bot to not report this instantly and instead be smooth about it.
Last edited by Kickupx; 12-23-2016 at 10:51 AM.
-
Member
To work in legion I need to change the parameter "## Interface: 30000" to what number?
-
Originally Posted by
kickit
To work in legion I need to change the parameter "## Interface: 30000" to what number?
70000, they follow the wow expansion count. So WOD would be 60000, MOP 50000 etc.
-
Member
Is not working ....
Error:
"KickBot Lua frame has an enexpected value. Manually set $ LuaFramePosX and $ LuaFramePosY"
My WOW is running on 64bit and Directx 11
Procedures performed:
1) Download and unzip KickKitty-master.zip
2) Run GenerateRandomAddonName.exe (For example - PostalOld)
3) Move PostalOld to the WOW addon folder
4) Edit value "## Interface: 70000" in PostalOld.toc
5) Open WOW, enable addon
5) Run PostalOld.x64.exe
Have I forgotten a procedure?
-
Originally Posted by
kickit
Is not working ....
Error:
"KickBot Lua frame has an enexpected value. Manually set $ LuaFramePosX and $ LuaFramePosY"
My WOW is running on 64bit and Directx 11
Procedures performed:
1) Download and unzip KickKitty-master.zip
2) Run GenerateRandomAddonName.exe (For example - PostalOld)
3) Move PostalOld to the WOW addon folder
4) Edit value "## Interface: 70000" in PostalOld.toc
5) Open WOW, enable addon
5) Run PostalOld.x64.exe
Have I forgotten a procedure?
Kickkitty does not use the addons own exexutable. Instead of running PostalOld.x64.exe you have to download and use botkitty. You can download that here. And then add kickkitty in the botmanager.
-
Member
Originally Posted by
Kickupx
Kickkitty does not use the addons own exexutable. Instead of running PostalOld.x64.exe you have to download and use botkitty. You can download that
here. And then add kickkitty in the botmanager.
I asked why I already used the "Plug and Play" version of jozsab1, which consisted of just doing the steps I wrote. Bot worked as an addon
I thought your version worked the same way.
-
Originally Posted by
kickit
I asked why I already used the "Plug and Play" version of jozsab1, which consisted of just doing the steps I wrote. Bot worked as an addon
I thought your version worked the same way.
Oh alright, it has some differences. The complete picture is basicly that we have the LUA addon, then we got BotKitty which is an programming/scripting environment where KickKitty then run.
I would say that the combination of BotKitty and KickKitty serves the same goal as the file you call PostalOld.x64.exe. Because of that I have now removed all unnecessary files
from the addon directory of KickKitty to hopefully make that abit more clear.
-
Member
Originally Posted by
Kickupx
Oh alright, it has some differences. The complete picture is basicly that we have the LUA addon, then we got BotKitty which is an programming/scripting environment where KickKitty then run.
I would say that the combination of BotKitty and KickKitty serves the same goal as the file you call PostalOld.x64.exe. Because of that I have now removed all unnecessary files
from the addon directory of KickKitty to hopefully make that abit more clear.
After cleaning the files and testing this new procedure, I generated the addon, for example, DeadlyBossModsOld (DeadlyBossModsOld.lua / DeadlyBossModsOld.xml), but the files have only 1KB!
Contents of the files:
DeadlyBossModsOld.lua
Local MyNewAddonNameIs = "DeadlyBossModsOld"
DeadlyBossModsOld.xml
<! - this is a comment: DeadlyBossModsOld ->
Is correct ?