Kbot -- Discussion

Amadeus · Feb 3, 2009

This is the new discussion thread for KBot.

Since ALL of the original authors are MIA, I have moved all of the files to the official SVN repository and released a new .zip file on a new release thread, found here: http://www.isxgames.com/forums/showthread.php?t=3102. After downloading and installing that ZIP file (as described on that thread), be sure that you update regularly via SVN.

If you wish to help update and/or make improvements to kbot (and feel confident in your lavishscript/isxvg skills), send me an email and I will give you SVN write access.

Otherwise, please note that this script is no longer supported by its original authors! I will try to keep it "running as is" for as long as possible and may tweak some things and/or fix any bugs if they are posted here and easily doable. However, do not expect anything grand to come of kbot in the future unless someone else decides to work on it. The "active" vanguard bot, as of right now, is VGA.

Amadeus · Feb 3, 2009

Again, let me reiterate that kbot is no longer supported by its original authors. However, the script entitled VGA is, as of this date, actively developed and maintained.

It is my belief that in the near future VGA will surpass kbot as the bot script of choice by isxvg users.

Amadeus · Feb 6, 2009

Ok -- I updated kbot on SVN to fix the errors that were reported specifically so far on the thread here (ie, Kelly71's)4 ...the necro stuff should be working now. Frankly, there were things like THIS in CJ's code ...which made no sense at all....in fact, I can't tell you just how fucked up this block of code is ...I am sure it didn't work like he thought it would at all.

Code:

if ${Me.Class.Equal[Necromancer]}
call Necropsy
while !${Return}
wait 1

Anyway..I fixed it. You REALLY need to be using what's on SVN ...so just get this 2007 version of kbot out of your head...it's gone forever.

But...that weirdness aside, I see what CJ forgot to send Xeon back in 2007 and made that change in the SVN.

Either way, we need to get away from *ALL* of these old versions and start using the one that is on SVN. Get it, and report the CRITICAL bugs and I will fix them. I'm not going to go around chasing old versions and shit. I made changes today so see how those affect the bugs that Kelly71 was getting.

-----------------

Now, other than bug reports of what people see in the game, the other thing that would be helpful is if someone went back through all 40+ pages of the kbto discussion thread and compiled a list of actual code edits that were submitted by users into one document (easy-to-read) for me. If I got that I could go through the current version and make sure that they're all there.

Otherwise, the kbot that is on the SVN right now ...when installed properly using the CURRENT kbot release thread instructions should function properly.

mattsworld06 · Feb 7, 2009

not working for me, crashes every time.

Code:

Software: Inner Space Kernel 1.09 Build 4839 (Sun Jan 18 00:30:13 2009)
Crash: 0x0E585F9D: Exception 0xc0000005 reading from address 0x0E585F9D
 
Registers:
-----------------------------------
eax=00000001 ebx=0E585F3A ecx=0000D7F2 edx=77C2807C
edi=0012ED38 esi=0E514D04 ebp=0012ECF0 esp=0012EA7C
 
Stack:
-----------------------------------
7C885780 00000000 7C864031 0012ED38 80000003 01DB1E90 7C38B4E0 00000000
0000001C 0400FEA6 10C92000 0400FF0F 0405664C 10C92000 00000000 0012ED1C
0400FF23 04031CD0 0405664C 0012EB01 0054BF00 00000001 0012EB18 2F867478
0012EBB8 2F867440 00000000 0012EC48 00639D51 00000105 00000087 00000002
00000000 C73CAE00 43C80000 450CD000 C73CAE00 441B6000 00000000 48800000
C8800000 48800000 48800000 488001B0 488001B0 48800020 0000003B 3E9AAC00
FFFFFFFF 00000001 04495B94 0012EAD8 0012EBDC 0078C610 00000000 0012EBE8
0054BF82 00000001 0012EBA8 2F8674C8 2F8674AC 2F867440 C536B000 450CD000
C73CAE00 00000000 00000000 00000005 C5610000 45610000 00000000 00000000
00000000 0012ED38 00000000 00000004 C9000000 49000000 49000000 00000000
490000D8 49000010 0012EBC8 00000000 00000000 00000001 0E066790 0012EB68
0012EC50 0078C610 00000000 0012EC5C 0054E2E4 00000001 008FB5E4 00000001
00000040 0012FB3C 00000000 00000000 00000000 00000000 00000000 00000000
00000000 7F800000 7F800000 BC5901C9 00000001 3D0A3D71 FFFFFFF8 101E4370
00000008 00793180 00000000 0012EC34 0012FA24 10170990 00000000 00000034
10103BB0 0000003C 00000001 00000000 0012FA30 0012FB3C 00FFE1D8 00FFE1D8
00FFE1D8 0012ECD8 7C3598AD 0012EE2C 0012FDC0 0012EE4C 0012EE00 00FFE1D8
FFFFFFFF 00000000 00000000 19930520 00FFE1D8 00000000 0012F1B0 7C910303
10B91D5A 10900000 10900000 10900120 C7011EFD 0400FF44 00005D25 0012EA8C
0012E6A0 0012ED58 7C839AC0 7C864948 FFFFFFFF 0012ED0C 7C34C456 0012ED38
00000000 00000000 00000000 80000003 0012FFC0 10B92269 80000003 0012ED38
7C34246E 0012ED40 00000000 0012ED40 00000000 00000000 00000000 0012EE2C
0012EE4C 0012ED64 7C9032A8 0012EE2C 0012FFB0 0012EE4C 0012EE00 0012F190
7C9032BC 0012FFB0 0012EE14 7C90327A 0012EE2C 0012FFB0 0012EE4C 0012EE00
10B91D5A 00000001 0012EE2C 0012FFB0 7C92A9EF 0012EE2C 0012FFB0 0012EE4C
0012EE00 10B91D5A 309C0000 0012EE2C 31910000 0012F248 0012F2D8 3EBECC00
00000000 0012F2D0 1013454A 0012F2D0 2E0D9600 0012EE08 0012F2D0 10133794
0012F2D0 0012F750 00000000 0012EDB0 0012F708 0078EC50 00000000 00000000
10133686 10133794 0012F2D8 00130000 000E8000 0012FB74 309C0078 7C90E46A
00000000 0012EE4C 0012EE2C 0012EE4C 80000003 00000000 00000000 2FA63194
00000003 00000000 00B500A0 10D7A138 0001003F 00000000 00000000 00000000
00000000 00000000 00000000 FFFF027F FFFF4D65 FFFFFFFF 2FA63183 00D8001B
00000000 FFFF0023 00000000 00000000 00008000 00000000 00000000 68000000
F5DF2827 00003FFC 43000000 BFFBC8B4 00000000 00000000 B8000000 00000020
400AB1E0 00000000 00000000 00000000 B3000000 400AA92E 00000000 00000000
0000003B 00000023 00000023 309C0000 31910000 00000000 10D7A138 00B500A0
000000B5 309C0078 2FA63194 0000001B 00200202 0012F118 00000023 4D65027F
00D80000 2FA63183 0000001B 00000000 00000023 00001FA4 0000FFFF 00000000
00000000 00008000 00000000 00000000 00000000 00000000 00000000 68000000
F5DF2827 00003FFC 00000000 00000000 C8B44300 0000BFFB 00000000 00000000
00000000 00000000 00000000 0020B800 B1E00000 0000400A 00000000 00000000
00000000 00000000 00000000 00000000 A92EB300 0000400A 00000000 00000000
00000000 00000000 00000000 00000000 40000000 00000000 00000000 00000034
00000000 00000433 00000000 20000000 3FF147AE 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 20000000 3FF147AE 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 309C0000
31910000 309C0078 0012F138 00000000 10D7A138 00B500A0 000000B5 31910000
2FA8B597 0012F24C 31920000 00000000 028D6B98 8F976EC9 4C7CF2F0 0012F248
02716850 0012F248 309C0078 31910000 0012F210 309E0000 17176864 65746600
72756272 0072656E 4C7CB378 00000000 0000000F 0012F210 2FAA3188 FFFFFFFF
02663124 0012F24C 4C7CF2F0 00000000 028D6B98 156A5B38 00000000 0012F2F8
0012F284 4C7CB378 0112EFBC 4C7CB310 0012F274 7C90E900 7C9101C0 FFFFFFFF
00001000 4C7CF2F0 02510000 00000000 00001000 4C7CF2F0 0012F260 02716850
0012F214 0268A8D6 00000020 028D6B98 00000000 0012F274 026C52A8 00000008
026633EF 0012F2F8 00000003 00000000 156A58BC 4C7CB5A8 02716850 4C7C75B8
0112F25C 02716850 4C7CB378 309C0000 282BFC00 00000078 4C7CC530 4C7CB5B0
0012F280 026924B5 4C7CF128 00000000 0012F6E8 00000008 0012F2C8 026C52F0
 
Module addresses in stack:
-----------------------------------
kernel32.dll+85780
kernel32.dll+64031
MSVCR71.dll+4B4E0
InnerSpace.dll+FEA6
vgclient.exe+392000
InnerSpace.dll+FF0F
InnerSpace.dll+5664C
vgclient.exe+392000
InnerSpace.dll+FF23
InnerSpace.dll+31CD0
InnerSpace.dll+5664C
Engine.dll+15BF00
Engine.dll+249D51
Engine.dll+39C610
Engine.dll+15BF82
Engine.dll+39C610
Engine.dll+15E2E4
Engine.dll+50B5E4
Core.dll+E4370
Engine.dll+3A3180
Core.dll+70990
Core.dll+3BB0
SGOEngineCore.dll+2E1D8
SGOEngineCore.dll+2E1D8
SGOEngineCore.dll+2E1D8
MSVCR71.dll+198AD
SGOEngineCore.dll+2E1D8
SGOEngineCore.dll+2E1D8
ntdll.dll+10303
vgclient.exe+291D5A
vgclient.exe+120
InnerSpace.dll+FF44
kernel32.dll+39AC0
kernel32.dll+64948
MSVCR71.dll+C456
vgclient.exe+292269
MSVCR71.dll+246E
ntdll.dll+32A8
ntdll.dll+32BC
ntdll.dll+327A
vgclient.exe+291D5A
ntdll.dll+2A9EF
vgclient.exe+291D5A
Core.dll+3454A
Core.dll+33794
Engine.dll+39EC50
Core.dll+33686
Core.dll+33794
ntdll.dll+E46A
isxvg.dll+23194
Engine.dll+7600A0
vgclient.exe+47A138
isxvg.dll+23183
d3dx9_31.dll+2001B
vgclient.exe+47A138
Engine.dll+7600A0
isxvg.dll+23194
d3dx9_31.dll+20000
isxvg.dll+23183
vgclient.exe+47A138
Engine.dll+7600A0
isxvg.dll+4B597
IS-Kernel.dll+136850
Engine.dll+33656E
isxvg.dll+63188
IS-Kernel.dll+83124
ntdll.dll+E900
ntdll.dll+101C0
IS-Kernel.dll+136850
IS-Kernel.dll+AA8D6
IS-Kernel.dll+E52A8
IS-Kernel.dll+833EF
IS-Kernel.dll+136850
IS-Kernel.dll+136850
IS-Kernel.dll+B24B5
IS-Kernel.dll+E52F0
 
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 3/2600.xpsp_sp3_gdr.080814-1236
Process Memory Usage: 535MB
System Physical RAM: 1915/3326MB
Page File: 3884/5210MB
Virtual Memory: 1172/2047MB (Extended: 0MB)
CPU 1: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz @ 3000MHz
CPU 2: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz @ 3000MHz
CPU Affinity Mask: 0x3
Video 1: //./DISPLAY1/NVIDIA GeForce GTX 260
Video 2: //./DISPLAYV1/NetMeeting driver
Video 3: //./DISPLAYV2/RDPDD Chained DD
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 7.0.5730.13
 
Loaded Modules:
-----------------------------------
Module 0x00330000-0x003E3000: C:/Program Files/Sony/Vanguard/bin/SGOUnrealAbstractionLayer.dll (Wed Jan 28 22:13:47 2009)
Module 0x003F0000-0x00D5C000: C:/Program Files/Sony/Vanguard/bin/Engine.dll (Wed Jan 28 22:13:37 2009)
Module 0x00D60000-0x00FC7000: D:/WINDOWS/system32/d3dx9_31.dll (Thu Sep 28 22:13:05 2006)
Module 0x00FD0000-0x01018000: C:/Program Files/Sony/Vanguard/bin/SGOEngineCore.dll (Wed Jan 28 22:13:50 2009)
Module 0x01020000-0x01031000: C:/Program Files/Sony/Vanguard/bin/SGOExceptionHandler.dll (Wed Jan 28 22:12:07 2009)
Module 0x01040000-0x01049000: D:/WINDOWS/system32/Normaliz.dll (Thu Jun 29 15:05:42 2006)
Module 0x01050000-0x010E0000: C:/Program Files/Sony/Vanguard/bin/VGCommon.dll (Wed Jan 28 22:13:58 2009)
Module 0x010E0000-0x01101000: C:/Program Files/Sony/Vanguard/bin/SGOLoader.dll (Wed Jan 28 22:13:52 2009)
Module 0x01110000-0x01129000: C:/Program Files/Sony/Vanguard/bin/SGOSQLDatabase.dll (Wed Jan 28 22:11:54 2009)
Module 0x01130000-0x01138000: C:/Program Files/Sony/Vanguard/bin/SGONetwork.dll (Wed Jan 28 22:13:53 2009)
Module 0x01140000-0x0177B000: C:/Program Files/Sony/Vanguard/bin/xul.dll (Fri Jan 26 03:38:38 2007)
Module 0x01780000-0x017E8000: C:/Program Files/Sony/Vanguard/bin/js3250.dll (Fri Jan 26 02:56:04 2007)
Module 0x017F0000-0x017F8000: C:/Program Files/Sony/Vanguard/bin/plc4.dll (Fri Jan 26 02:53:41 2007)
Module 0x01800000-0x01806000: C:/Program Files/Sony/Vanguard/bin/plds4.dll (Fri Jan 26 02:53:37 2007)
Module 0x02210000-0x0222E000: C:/Program Files/InnerSpace/Lavish.dll (Tue Oct 30 17:12:23 2007)
Module 0x025A0000-0x025C3000: C:/Program Files/InnerSpace/IS-D3D9.dll (Fri Dec 19 22:30:28 2008)
Module 0x025E0000-0x02749000: C:/Program Files/InnerSpace/IS-Kernel.dll (Sun Jan 18 00:28:34 2009)
Module 0x02E60000-0x02EC4000: C:/Program Files/InnerSpace/IS-D3D8.dll (Tue Apr 08 19:39:58 2008)
Module 0x02EE0000-0x02EF8000: C:/Program Files/InnerSpace/IS-OpenGL.dll (Sat Oct 04 18:41:59 2008)
Module 0x02F20000-0x02F5D000: C:/Program Files/InnerSpace/IS-VirtualInput.dll (Thu Jan 22 04:18:11 2009)
Module 0x03000000-0x03118000: C:/Program Files/Sony/Vanguard/bin/dbghelp.dll (Wed Jun 22 02:52:04 2005)
Module 0x03320000-0x03580000: D:/WINDOWS/system32/d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x04000000-0x0405F000: C:/Program Files/InnerSpace/InnerSpace.dll (Sun Jan 18 00:30:13 2009)
Module 0x04A60000-0x04A68000: D:/WINDOWS/assembly/GAC_MSIL/Lavish.LavishVMRuntime/1.0.0.0__9029a3ab4cbe108d/Lavish.LavishVMRuntime.dll (Mon Dec 17 20:36:15 2007)
Module 0x04B00000-0x04B14000: D:/WINDOWS/assembly/GAC_MSIL/Lavish.InnerSpace/1.0.0.0__9029a3ab4cbe108d/Lavish.InnerSpace.dll (Sat Dec 20 01:29:59 2008)
Module 0x04B20000-0x04DE5000: D:/WINDOWS/system32/xpsp2res.dll (Sun Apr 13 17:39:24 2008)
Module 0x05000000-0x05151000: C:/Program Files/InnerSpace/ISUI.dll (Sun Jan 11 16:21:09 2009)
Module 0x0D260000-0x0D2DB000: C:/Program Files/Sony/Vanguard/bin/D3DDrv.dll (Wed Jan 28 22:15:34 2009)
Module 0x0E0F0000-0x0E194000: D:/WINDOWS/system32/nvapi.dll (Thu Jan 15 04:18:15 2009)
Module 0x0E430000-0x0E44A000: C:/Program Files/Sony/Vanguard/bin/ALAudio.dll (Wed Jan 28 22:15:01 2009)
Module 0x0E480000-0x0E49E000: C:/Program Files/Sony/Vanguard/bin/AudioDrv.dll (Tue Nov 14 03:47:22 2006)
Module 0x0E4A0000-0x0E4BE000: C:/Program Files/Sony/Vanguard/bin/OpenAL32.dll (Fri Oct 27 18:37:19 2006)
Module 0x0E4E0000-0x0E52B000: C:/Program Files/Sony/Vanguard/bin/isactwin.dll (Tue Nov 14 07:02:03 2006)
Module 0x0F320000-0x0F329000: C:/Program Files/Sony/Vanguard/bin/ogg.dll (Sat Nov 15 23:54:16 2003)
Module 0x0F440000-0x0F548000: C:/Program Files/Sony/Vanguard/bin/vorbis.dll (Sun Nov 16 16:47:58 2003)
Module 0x0FCC0000-0x0FE0D000: D:/Program Files/Common Files/SYSTEM/MSMAPI/1033/MSMAPI32.DLL (Sun Aug 03 08:23:15 2003)
Module 0x0FF40000-0x0FF57000: D:/Program Files/Common Files/TortoiseOverlays/TortoiseOverlays.dll (Wed Jan 16 16:52:49 2008)
Module 0x10000000-0x1007E000: C:/Program Files/Sony/Vanguard/bin/SpeedTreeRT.dll (Wed Jan 28 22:11:53 2009)
Module 0x10100000-0x102E6000: C:/Program Files/Sony/Vanguard/bin/Core.dll (Wed Jan 28 22:12:25 2009)
Module 0x10300000-0x1034F000: C:/Program Files/Sony/Vanguard/bin/SGOFoundation.dll (Wed Jan 28 22:11:51 2009)
Module 0x10560000-0x1056E000: D:/Program Files/TortoiseSVN/bin/TortoiseStub.dll (Sat Jan 24 22:10:53 2009)
Module 0x10590000-0x1064A000: D:/Program Files/TortoiseSVN/bin/TortoiseSVN.dll (Sat Jan 24 22:12:53 2009)
Module 0x10680000-0x10692000: D:/Program Files/TortoiseSVN/bin/intl3_tsvn.dll (Thu Nov 22 09:48:29 2007)
Module 0x10700000-0x10727000: C:/Program Files/Sony/Vanguard/bin/IpDrv.dll (Wed Jan 28 22:13:44 2009)
Module 0x10900000-0x10D7E000: C:/Program Files/Sony/Vanguard/bin/vgclient.exe (Wed Jan 28 22:18:01 2009)
Module 0x10E80000-0x10F21000: D:/Program Files/Common Files/SYSTEM/MSMAPI/1033/outex.dll (Mon Jul 28 17:31:48 2003)
Module 0x11000000-0x1105C000: C:/Program Files/Sony/Vanguard/bin/Window.dll (Wed Jan 28 22:13:44 2009)
Module 0x11100000-0x11176000: C:/Program Files/Sony/Vanguard/bin/WinDrv.dll (Wed Jan 28 22:17:49 2009)
Module 0x12000000-0x12242000: C:/Program Files/Sony/Vanguard/bin/xerces-c_2_7.dll (Fri Aug 26 16:38:07 2005)
Module 0x12250000-0x12DF7000: D:/Program Files/Common Files/Microsoft Shared/office11/mso.dll (Fri Aug 08 07:10:06 2003)
Module 0x15D50000-0x15D6B000: C:/Program Files/Sony/Vanguard/bin/Fire.dll (Wed Jan 28 22:15:02 2009)
Module 0x15EF0000-0x15EFD000: C:/Program Files/Sony/Vanguard/bin/gksvggdiplus.dll (Fri Jan 26 03:44:03 2007)
Module 0x15F00000-0x15F09000: C:/Program Files/Sony/Vanguard/bin/mozilla/components/pipboot.dll (Fri Jan 26 03:41:18 2007)
Module 0x16080000-0x160A5000: D:/Program Files/Bonjour/mdnsNSP.dll (Thu Aug 14 22:54:04 2008)
Module 0x2FA40000-0x2FAEA000: C:/Program Files/InnerSpace/Extensions/isxvg.dll (Sat Feb 07 07:22:48 2009)
Module 0x30000000-0x30028000: C:/Program Files/Sony/Vanguard/bin/nspr4.dll (Fri Jan 26 02:53:36 2007)
Module 0x38090000-0x380B1000: C:/Program Files/Sony/Vanguard/bin/Vehicles.dll (Wed Jan 28 22:14:42 2009)
Module 0x4EC50000-0x4EDF6000: D:/WINDOWS/WinSxS/x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5581_x-ww_dfbc4fc4/gdiplus.dll (Tue Apr 15 17:47:33 2008)
Module 0x4FDD0000-0x4FF76000: D:/WINDOWS/system32/d3d9.dll (Mon Apr 14 00:09:13 2008)
Module 0x5AD70000-0x5ADA8000: D:/WINDOWS/system32/uxtheme.dll (Mon Apr 14 00:11:10 2008)
Module 0x5B860000-0x5B8B5000: D:/WINDOWS/system32/NETAPI32.dll (Wed Oct 15 16:34:24 2008)
Module 0x5D090000-0x5D12A000: D:/WINDOWS/system32/COMCTL32.dll (Mon Apr 14 00:09:44 2008)
Module 0x5E3A0000-0x5E42D000: D:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/diasymreader.dll (Fri Jul 25 15:26:58 2008)
Module 0x5ED00000-0x5EDCC000: D:/WINDOWS/system32/OPENGL32.dll (Mon Apr 14 00:11:06 2008)
Module 0x60610000-0x60616000: D:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/fusion.dll (Fri Jul 25 13:53:36 2008)
Module 0x61E00000-0x61E1F000: D:/WINDOWS/system32/MAPI32.DLL (Sat Aug 18 05:35:00 2001)
Module 0x637A0000-0x63CD6000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/System.Xml/773a9786013451d3baaeff003dc4230f/System.Xml.ni.dll (Tue Nov 25 05:00:32 2008)
Module 0x64890000-0x64981000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/System.Configuration/b82c00e2d24305ad6cb08556e3779b75/System.Configuration.ni.dll (Fri Jul 25 14:08:52 2008)
Module 0x662B0000-0x66308000: D:/WINDOWS/system32/hnetcfg.dll (Mon Apr 14 00:09:46 2008)
Module 0x68000000-0x68036000: D:/WINDOWS/system32/rsaenh.dll (Tue Mar 18 14:39:32 2008)
Module 0x688F0000-0x688F9000: D:/WINDOWS/system32/HID.DLL (Mon Apr 14 00:09:41 2008)
Module 0x68B20000-0x68B40000: D:/WINDOWS/system32/GLU32.dll (Mon Apr 14 00:09:34 2008)
Module 0x6CE10000-0x6CE48000: D:/WINDOWS/system32/DINPUT8.dll (Mon Apr 14 00:09:48 2008)
Module 0x6D990000-0x6D996000: D:/WINDOWS/system32/d3d8thk.dll (Mon Apr 14 00:09:12 2008)
Module 0x6EE60000-0x6EE89000: D:/Program Files/TortoiseSVN/bin/libaprutil_tsvn.dll (Sat Jan 24 22:08:31 2009)
Module 0x6EEC0000-0x6EEE0000: D:/Program Files/TortoiseSVN/bin/libapr_tsvn.dll (Sat Jan 24 22:08:26 2009)
Module 0x71A50000-0x71A8F000: D:/WINDOWS/system32/mswsock.dll (Fri Jun 20 17:46:57 2008)
Module 0x71A90000-0x71A98000: D:/WINDOWS/System32/wshtcpip.dll (Mon Apr 14 00:12:30 2008)
Module 0x71AA0000-0x71AA8000: D:/WINDOWS/system32/WS2HELP.dll (Mon Apr 14 00:12:20 2008)
Module 0x71AB0000-0x71AC7000: D:/WINDOWS/system32/WS2_32.dll (Mon Apr 14 00:12:19 2008)
Module 0x71AD0000-0x71AD9000: D:/WINDOWS/system32/WSOCK32.dll (Mon Apr 14 00:12:32 2008)
Module 0x72D10000-0x72D18000: D:/WINDOWS/system32/msacm32.drv (Sat Aug 18 05:33:30 2001)
Module 0x72D20000-0x72D29000: D:/WINDOWS/system32/wdmaud.drv (Mon Apr 14 00:11:24 2008)
Module 0x73000000-0x73026000: D:/WINDOWS/system32/WINSPOOL.DRV (Mon Apr 14 00:11:19 2008)
Module 0x732E0000-0x732E5000: D:/WINDOWS/system32/RICHED32.DLL (Sat Aug 18 05:33:28 2001)
Module 0x73760000-0x737AB000: D:/WINDOWS/system32/DDRAW.dll (Mon Apr 14 00:09:28 2008)
Module 0x73BC0000-0x73BC6000: D:/WINDOWS/system32/DCIMAN32.dll (Mon Apr 14 00:09:27 2008)
Module 0x73EE0000-0x73EE4000: D:/WINDOWS/system32/KsUser.dll (Mon Apr 14 00:09:58 2008)
Module 0x73F10000-0x73F6C000: D:/WINDOWS/system32/dsound.dll (Mon Apr 14 00:10:30 2008)
Module 0x746F0000-0x7471A000: D:/WINDOWS/system32/msimtf.dll (Mon Apr 14 00:12:16 2008)
Module 0x74720000-0x7476C000: D:/WINDOWS/system32/MSCTF.dll (Mon Apr 14 00:11:24 2008)
Module 0x74C80000-0x74CAC000: D:/WINDOWS/system32/OLEACC.dll (Sat Aug 18 05:33:18 2001)
Module 0x74D90000-0x74DFB000: D:/WINDOWS/system32/usp10.dll (Mon Apr 14 00:11:09 2008)
Module 0x74E30000-0x74E9D000: D:/WINDOWS/system32/RICHED20.dll (Mon Apr 14 00:10:44 2008)
Module 0x74ED0000-0x74EDE000: D:/WINDOWS/system32/wbem/wbemsvc.dll (Mon Apr 14 00:11:21 2008)
Module 0x74EF0000-0x74EF8000: D:/WINDOWS/system32/wbem/wbemprox.dll (Mon Apr 14 00:11:20 2008)
Module 0x75290000-0x752C7000: D:/WINDOWS/system32/wbem/wbemcomn.dll (Mon Apr 14 00:11:14 2008)
Module 0x755C0000-0x755EE000: D:/WINDOWS/system32/msctfime.ime (Mon Apr 14 00:11:25 2008)
Module 0x75690000-0x75706000: D:/WINDOWS/system32/wbem/fastprox.dll (Mon Apr 14 00:09:30 2008)
Module 0x75CF0000-0x75D81000: D:/WINDOWS/system32/mlang.dll (Mon Apr 14 00:10:25 2008)
Module 0x76080000-0x760E5000: D:/WINDOWS/system32/MSVCP60.dll (Mon Apr 14 00:12:55 2008)
Module 0x76380000-0x76385000: D:/WINDOWS/system32/MSIMG32.dll (Mon Apr 14 00:12:15 2008)
Module 0x76390000-0x763AD000: D:/WINDOWS/system32/IMM32.DLL (Mon Apr 14 00:10:15 2008)
Module 0x763B0000-0x763F9000: D:/WINDOWS/system32/comdlg32.dll (Mon Apr 14 00:09:45 2008)
Module 0x76600000-0x7661D000: D:/WINDOWS/System32/CSCDLL.dll (Mon Apr 14 00:10:06 2008)
Module 0x76780000-0x76789000: D:/WINDOWS/system32/SHFOLDER.dll (Mon Apr 14 00:10:58 2008)
Module 0x767A0000-0x767B3000: D:/WINDOWS/system32/NTDSAPI.dll (Mon Apr 14 00:11:03 2008)
Module 0x76B40000-0x76B6D000: D:/WINDOWS/system32/WINMM.dll (Mon Apr 14 00:11:40 2008)
Module 0x76BF0000-0x76BFB000: D:/WINDOWS/system32/PSAPI.DLL (Mon Apr 14 00:10:42 2008)
Module 0x76C30000-0x76C5E000: D:/WINDOWS/system32/WINTRUST.dll (Mon Apr 14 00:11:22 2008)
Module 0x76C90000-0x76CB8000: D:/WINDOWS/system32/IMAGEHLP.dll (Mon Apr 14 00:10:00 2008)
Module 0x76D60000-0x76D79000: D:/WINDOWS/system32/iphlpapi.dll (Mon Apr 14 00:09:52 2008)
Module 0x76E80000-0x76E8E000: D:/WINDOWS/system32/rtutils.dll (Mon Apr 14 00:10:55 2008)
Module 0x76E90000-0x76EA2000: D:/WINDOWS/system32/rasman.dll (Mon Apr 14 00:10:43 2008)
Module 0x76EB0000-0x76EDF000: D:/WINDOWS/system32/TAPI32.dll (Mon Apr 14 00:11:01 2008)
Module 0x76EE0000-0x76F1C000: D:/WINDOWS/system32/rasapi32.dll (Mon Apr 14 00:10:39 2008)
Module 0x76F20000-0x76F47000: D:/WINDOWS/system32/DNSAPI.dll (Fri Jun 20 17:46:57 2008)
Module 0x76F60000-0x76F8C000: D:/WINDOWS/system32/WLDAP32.dll (Mon Apr 14 00:11:26 2008)
Module 0x76FB0000-0x76FB8000: D:/WINDOWS/System32/winrnr.dll (Mon Apr 14 00:11:14 2008)
Module 0x76FC0000-0x76FC6000: D:/WINDOWS/system32/rasadhlp.dll (Mon Apr 14 00:10:38 2008)
Module 0x76FD0000-0x7704F000: D:/WINDOWS/system32/CLBCATQ.DLL (Mon Apr 14 00:09:29 2008)
Module 0x77050000-0x77115000: D:/WINDOWS/system32/COMRes.dll (Mon Apr 14 00:09:50 2008)
Module 0x77120000-0x771AB000: D:/WINDOWS/system32/OLEAUT32.dll (Mon Apr 14 00:10:58 2008)
Module 0x773D0000-0x774D3000: D:/WINDOWS/WinSxS/x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83/comctl32.dll (Mon Apr 14 00:08:52 2008)
Module 0x774E0000-0x7761D000: D:/WINDOWS/system32/ole32.dll (Mon Apr 14 00:10:57 2008)
Module 0x77920000-0x77A13000: D:/WINDOWS/system32/SETUPAPI.dll (Mon Apr 14 00:10:51 2008)
Module 0x77A20000-0x77A74000: D:/WINDOWS/System32/cscui.dll (Mon Apr 14 00:10:07 2008)
Module 0x77A80000-0x77B15000: D:/WINDOWS/system32/CRYPT32.dll (Mon Apr 14 00:09:59 2008)
Module 0x77B20000-0x77B32000: D:/WINDOWS/system32/MSASN1.dll (Mon Apr 14 00:11:18 2008)
Module 0x77B40000-0x77B62000: D:/WINDOWS/system32/appHelp.dll (Mon Apr 14 00:09:35 2008)
Module 0x77BD0000-0x77BD7000: D:/WINDOWS/system32/midimap.dll (Mon Apr 14 00:10:20 2008)
Module 0x77BE0000-0x77BF5000: D:/WINDOWS/system32/MSACM32.dll (Mon Apr 14 00:11:03 2008)
Module 0x77C00000-0x77C08000: D:/WINDOWS/system32/VERSION.dll (Mon Apr 14 00:11:09 2008)
Module 0x77C10000-0x77C68000: D:/WINDOWS/system32/msvcrt.dll (Mon Apr 14 00:12:56 2008)
Module 0x77C70000-0x77C94000: D:/WINDOWS/system32/msv1_0.dll (Mon Apr 14 00:12:53 2008)
Module 0x77DD0000-0x77E6B000: D:/WINDOWS/system32/ADVAPI32.dll (Mon Apr 14 00:09:22 2008)
Module 0x77E70000-0x77F02000: D:/WINDOWS/system32/RPCRT4.dll (Mon Apr 14 00:10:46 2008)
Module 0x77F10000-0x77F59000: D:/WINDOWS/system32/GDI32.dll (Thu Oct 23 12:36:14 2008)
Module 0x77F60000-0x77FD6000: D:/WINDOWS/system32/SHLWAPI.dll (Mon Apr 14 00:11:02 2008)
Module 0x77FE0000-0x77FF1000: D:/WINDOWS/system32/Secur32.dll (Mon Apr 14 00:11:07 2008)
Module 0x78000000-0x78045000: D:/WINDOWS/system32/iertutil.dll (Thu Oct 16 20:38:41 2008)
Module 0x78050000-0x78120000: D:/WINDOWS/system32/WININET.dll (Thu Oct 16 20:38:39 2008)
Module 0x78130000-0x781CB000: D:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.3053_x-ww_b80fa8ca/MSVCR80.dll (Fri Jul 25 13:33:13 2008)
Module 0x78480000-0x7850E000: D:/WINDOWS/WinSxS/x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e/MSVCP90.dll (Tue Jul 29 10:54:01 2008)
Module 0x78520000-0x785C3000: D:/WINDOWS/WinSxS/x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_6f74963e/MSVCR90.dll (Tue Jul 29 10:53:57 2008)
Module 0x79000000-0x79046000: D:/WINDOWS/system32/mscoree.dll (Fri Jul 25 13:53:32 2008)
Module 0x79060000-0x790BB000: D:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorjit.dll (Tue Nov 25 04:46:57 2008)
Module 0x790C0000-0x79BB7000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/mscorlib/6d667f19d687361886990f3ca0f49816/mscorlib.ni.dll (Tue Nov 25 04:47:06 2008)
Module 0x79E70000-0x7A400000: D:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorwks.dll (Tue Nov 25 04:44:49 2008)
Module 0x7A440000-0x7ABC5000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/System/80978a322d7dd39f0a71be1251ae395a/System.ni.dll (Fri Jul 25 14:08:58 2008)
Module 0x7ADE0000-0x7AF68000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/System.Drawing/3da96ee075bab9202626ae44c18d226c/System.Drawing.ni.dll (Fri Jul 25 14:10:10 2008)
Module 0x7AFD0000-0x7BBAE000: D:/WINDOWS/assembly/NativeImages_v2.0.50727_32/System.Windows.Forms/63406259e94d5c0ff5b79401dfe113ce/System.Windows.Forms.ni.dll (Fri Jul 25 14:10:47 2008)
Module 0x7C340000-0x7C396000: C:/Program Files/Sony/Vanguard/bin/MSVCR71.dll (Fri Feb 21 12:42:20 2003)
Module 0x7C3A0000-0x7C41B000: C:/Program Files/Sony/Vanguard/bin/MSVCP71.dll (Wed Mar 19 04:14:51 2003)
Module 0x7C800000-0x7C8F6000: D:/WINDOWS/system32/kernel32.dll (Mon Apr 14 00:11:24 2008)
Module 0x7C900000-0x7C9AF000: D:/WINDOWS/system32/ntdll.dll (Mon Apr 14 00:11:24 2008)
Module 0x7C9C0000-0x7D1D7000: D:/WINDOWS/system32/SHELL32.dll (Mon Apr 14 00:10:57 2008)
Module 0x7E410000-0x7E4A1000: D:/WINDOWS/system32/USER32.dll (Mon Apr 14 00:11:07 2008)
 
LavishScript Execution Stack:
-----------------------------------
Me:Afterburner
Me:Afterburner
Me:Afterburner
Script[KBot]:ExecuteAtom[Afterburner]
Script[KBot]:ExecuteAtom[Afterburner]
Script[KBot]:ExecuteAtom[Afterburner]
 
Running Scripts:
-----------------------------------
kbot
forestrun

Amadeus · Feb 7, 2009

Crashing everytime you click on "Afterburner"? That dump indicates that you clicked on that button.

In the console, type: echo ${ISXVG.Version} ...tell me what it says.

Also, type: echo ${Script[kbot].Variable[Current_Version]} ...while kbot is running (but paused) ...and tell me what it says.

mattsworld06 · Feb 7, 2009

yea everytime I click on afterburner it crashes. also nothing seems to work for some reason. craftbot works fine though. port ui never becomes ready and after I set everything up and hit start...nothing happens. not sure exactly what to do, I have deleted everything and redownloaded..etc.

I will type those commands and see what happens.

mattsworld06 · Feb 7, 2009

ok both of those commands come back saying NULL

Amadeus · Feb 7, 2009

Then you typed them wrong or else isxvg isn't loaded or kbot isn't running. Type ext isxvg first to make sure that isxvg is loaded ...then to run kbot ...type run kbot.

Oh, and you DID redownload/reinstall kbot recently and updated from svn like what was described in the new release thread, right?

mattsworld06 · Feb 7, 2009

ok got an error w/ first code

when typing echo ${ISXVG.version} I get

Error: No such 'ISXVG' member 'version' @ ${isxvg.version}

Amadeus · Feb 7, 2009

That's because you didn't type it correctly. It's Version, not version.

And, to be clear, you followed this thread to the letter? (ie, you deleted the /Scripts/kbot.iss file after installing the new zip) http://www.isxgames.com/forums/showthread.php?t=3102

Either way, you need to calm down and just provide the information I'm requesting ...stop pressing the afterburning button and causing yourself to crash...or starting the script, or whatever. Just load up ISXVG ...tell me what echo ${ISXVG.Version} says ...also, while you're there ...tell me what ${ISXVG.IsReady} says ....then, start kbot (but don't hit the start button ...and then tell me the other echo variable that I requested in my previous posting.

mattsworld06 · Feb 7, 2009

ok thats cool, sorry if it seems as if I'm not calm. ok

echo ${ISXVG.Version} is 2090205.0013

${ISXVG.IsReady} is TRUE

and

echo ${Script[kbot].Variable[Current_Version]} is 4.00

Thank you for your help

brmaloy · Feb 8, 2009

mattsworld06 said:
yea everytime I click on afterburner it crashes. also nothing seems to work for some reason. craftbot works fine though. port ui never becomes ready and after I set everything up and hit start...nothing happens. not sure exactly what to do, I have deleted everything and redownloaded..etc.

I will type those commands and see what happens.

Afterburner and Port are disabled in ISXVG and shouldn't work in Kbot.

Make sure you have added a waypoint for the chunk you are in. The add a waypoint button is on the main screen with start quit etc. After you've added a waypoint press the quit button then launch the script again and try start.

If it still isn't killing then check the tab where you can specify targets and ensure that you do not have targeting of the mobs next to you disabled somehow.

Try checking the console when it isn't working and see if anything is being reported as to why it isn't working.

Kelly71 · Feb 8, 2009

the way point function also have a 60 second timer before its available and refresh use.

Also Ama im still getting the same necro errors on Kbot and im at version 4. I updated everything thru SVN.
1st i tried just necropsy and got the same errors.
then i stoped the necropsy and try to get minions and same errors.

Could not calculate "KB_GETMINIONS"
Error:Unparsable in Calculation of "KB_GETMINIONS": 'K' @cState:Set[KB_GETMINIONS]
Could not calculate "KB_GETMINIONS"
Error:Unparsable in Calculation of "KB_GETMINIONS": 'K' @cState:Set[KB_GETMINIONS]

Also see this alot but dosent seem to effect anything really.

The 'TargetEffect' MEMBER of the 'character' datatype should no longer be used!!!

I know your not supporting this and I can live with out it so if its not a easy fix then Bleh with it.

mattsworld06 · Feb 8, 2009

brmaloy said:
Afterburner and Port are disabled in ISXVG and shouldn't work in Kbot.

Make sure you have added a waypoint for the chunk you are in. The add a waypoint button is on the main screen with start quit etc. After you've added a waypoint press the quit button then launch the script again and try start.

If it still isn't killing then check the tab where you can specify targets and ensure that you do not have targeting of the mobs next to you disabled somehow.

Try checking the console when it isn't working and see if anything is being reported as to why it isn't working.

well I guess if they are disabled that would explain a lot. wonder why they are disabled?

Amadeus · Feb 8, 2009

Afterburner and Port are disabled in ISXVG and shouldn't work in Kbot.

Read this:
http://www.isxgames.com/forums/showthread.php?t=2184

Also Ama im still getting the same necro errors on Kbot and im at version 4. I updated everything thru SVN.
1st i tried just necropsy and got the same errors.
then i stoped the necropsy and try to get minions and same errors.

Hmmm....if you're using the latest version from SVN, that shouldn't be happening. Open up /Scripts/kbot/Common/KB_Init.iss and go to line 27 -- it should say:

Code:

#define KB_GETMINIONS    37

If it does, then you shouldn't be getting that error.

mordacai · Feb 14, 2009

Incoming Tells problem

No 'TellsOut' function found in script
Call failed
Dumping script stack
--------------------
-->C:/Program Files/InnerSpace/Scripts/kbot/common/KB_autorespond.iss:327 AutoRespond() call TellsOut "${aText}"
C:/Program Files/InnerSpace/Scripts/kbot/kbot.iss:3282 KBot_onIncomingText() call AutoRespond "${aText}" "${ChannelNumber}"
C:/Program Files/InnerSpace/Scripts/kbot/kbot.iss:265 main() WaitFrame
-- Ending KBot --

Is it just me or does the script end now when a tell is received, I never used the autorespond option before.

Kelly71 · Feb 14, 2009

mordacai said:
No 'TellsOut' function found in script
Call failed
Dumping script stack
--------------------
-->C:/Program Files/InnerSpace/Scripts/kbot/common/KB_autorespond.iss:327 AutoRespond() call TellsOut "${aText}"
C:/Program Files/InnerSpace/Scripts/kbot/kbot.iss:3282 KBot_onIncomingText() call AutoRespond "${aText}" "${ChannelNumber}"
C:/Program Files/InnerSpace/Scripts/kbot/kbot.iss:265 main() WaitFrame
-- Ending KBot --

Is it just me or does the script end now when a tell is received, I never used the autorespond option before.

Yes mine is doing that also..

vah shir · Feb 15, 2009

same.. but somehow my innerspace viewer now is also just 2 horizonal bars one line high, one near the top of the screen and one near the bottom, preventing me from seeing what error's have occured.

Amadeus · Feb 15, 2009

Well, what happened was that there was a line in kbot.iss that was not right, so I fixed it. And, obviously whoever wrote it never had tested it working right, so there was a function missing (TellsOut()) ...how someone wrote a routine with a function and didn't include the function, is completely beyond me.

But, anyway, I updated SVN and it should work now.

vah shir · Feb 15, 2009

you the man, tnx again maestro

Midas · Feb 17, 2009

Has anyone figured out a fix for the "bonus yield" window that rarely shows up after harvesting? kbot doesn't seen to be able to work as long as that window is up.

I've messed around with the /hidewindow command (and it does indeed hide the window) but kbot still won't function properly.

mordacai · Feb 22, 2009

Post # 329 by Brigand in the original Kbot feedback thread has a solution for the harvest window, Basically it sets up a mouse click at a certain place on the screen so as long as you have the close window buttun under that point you will be golden.

Kelly71 · Mar 5, 2009

Since your last patch Ama when im skinning mobs it will do it for 3 seconds then target a nother mob and start attacking. Can this be fixed?

maras · May 3, 2009

Often the script "forgets" resting and begins a fight with low health and/or mana.
Probably this causes the harvest break too, because skinnng works properly after resting. If the script tries skinning without resting, it breaks off and attacks after 2-3 seconds.

vah shir · Jun 1, 2009

Midas, I tried to get brigand's code to work but was having non looting items & kbot crashing issues.
By no means am I a programmer but I was able to figure out that the consolidate feature was not working and so i removed it. I then had to change the loot commands in the harvest & skinning parts.. here's an example of what seems to be working well for me now for harvesting. I'm sure you can determine what needs to be done for skinning.

function Harvest()
{
if ${Me.Target.ID(exists)} && ${doHarvest} && ${Me.Target.Type.Equal[Resource]}
{
if ${HarvestBlackList.Element[${Me.Target.ID}](exists)}
return

; Check for Agro Mobs or other dangers
;call AreWeSafe
;if !${Return}
;{
; call DebugIt ". Harvest: Harvesting area NOT safe"
; HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]
; return
;}

HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]

call DebugIt ". Harvest: Harvesting Resource: ${Me.Target.Name}"
VGExecute /autoattack

wait 20

call DebugIt "Now harvesting..."

; Now wait for the Harvesting to finish
while (${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80) && !${GV[bool,IsHarvestingDone]})
{
wait 5
}

; by brig: begin added click routine for stuck bonus loots
while (${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80) && ${GV[bool,IsHarvestingDone]})
{
call DebugIt ". Harvesting looks stuck, click at close button spot"
Mouse:SetPosition[200,436]
wait 5
Mouse:LeftClick
wait 5
Mouse:ReleaseLeft
wait 5
}
; by brig: end added click routine for stuck bonus loots

wait 10

VGExecute /endharvest
wait 2
VGExecute /lootall
wait 2
VGExecute /cleartargets

}
}

mordacai · Jun 1, 2009

Consolidate works for me. But thanks for reminding me to add it to skinning

Denthan · Jun 30, 2009

Sorry

Amadeus said:
Again, let me reiterate that kbot is no longer supported by its original authors. However, the script entitled VGA is, as of this date, actively developed and maintained.

It is my belief that in the near future VGA will surpass kbot as the bot script of choice by isxvg users.

I am sorry that I had to stop work on kbot back in 2007, it was as much fun and a challenge for me as playing VG ever was. When I left to take a break as my wife was about to have our 3rd child and first boy I had hoped to come back to it. To make a very long story short, after a two year struggle my wife and I are divorced.

While I am sorry that Amadeus and others had to fill the void I am glad to see that there are some die hard kbot users still around. Thank you.

bricky2690 · Jul 11, 2009

Forgive me if this question has been asked/answered. I looked through the post and could not find it. Any ways, is there a fix for checking if the mob is being taken by someone else. When I first started using this it would run around and if someone else was killing the mob it would keep going to the next available mob. Thanks

Kelly71 · Jul 11, 2009

bricky2690 said:
Forgive me if this question has been asked/answered. I looked through the post and could not find it. Any ways, is there a fix for checking if the mob is being taken by someone else. When I first started using this it would run around and if someone else was killing the mob it would keep going to the next available mob. Thanks

Nope :/ there isnt.

bricky2690 · Oct 17, 2009

Everything is working great since the changes. However, just picked harvesting bac up and I am having an issue. The extra yield from a node window. I tried the changes from the original KBOT post. I change the mouse pointer location usingthe ECHO command inside the isx command wondow. That dd not work. The bot still hangs up when on the open window. I tried chaging the it to the script change that was listed in this thread. However, again, that did not work. Is there something else that someone has tried to get this too work?

Thanks in advance.

mmoaddict · Oct 17, 2009

Denthan said:
I am sorry that I had to stop work on kbot back in 2007, it was as much fun and a challenge for me as playing VG ever was.

Kbot is a nice program for leveling up.. no doubt.. Denthan if you are bored and want to look into VG again, feel free. It truly is the game we hoped it would have been when it released. I play end game material and there is still a crapload to do. Vanguard is much more challenging than the old days due to higher end mobs various resists, buffs, debuffs and reactions. It makes combat extremely difficult to generalize. It would be awesome to have you back.

Thanks for kbot.

mmo

Vstarr1961 · Oct 18, 2009

Been having a problem with my monk getting stuck in the downtime routine since the last patch for VG removed the need for monks and disciples to meditate to regain jin. I readily admit that I am not a programmer so I am not sure where I need to be looking to try and find the code that is causing the hang up. If anyone can give me some tips on what to look at so that I can get my monk moving again while running kbot would be greatly appreciated.

Thanks

mordacai · Oct 18, 2009

Hey Vstarr in Kbot under SETTING - HEAL tab, change "rest until energy at" to %0
enjoy.

Vstarr1961 · Oct 19, 2009

Thanks Mordacai

vah shir · Dec 3, 2009

Bricky.. i've messed around with the code some and also have had issues getting stuck once again with the 'bonus yeild' window. Unfortunately it's beyond my abilities atm, hopefully someone smarter than I(which thare are many i'm sure) can look into this once again.

Not giving up, it's just looking cloudy overhead..

Delorian76 · Apr 19, 2010

I too get stuck on the bonus yield window on harvesting. The other problem I have is that my toon runs around like a moron even when I have set waypoints like four million time. lol.

mordacai · Apr 20, 2010

Pathing seems fine to me, the only time it ever gives me problems is when I start the bot, occaisonly it will spaz out and run in the wrong direction, I find If I tag a mob it sets it straight. I have made my own changes to pathing to make the bot run the waypoints as a loop instead of it getting to the last waypoint and doubling back on itself, this is very handy for how harvesting nodes spawn and also some hunting paths benfit from this type of pathing. Could you describe what happens and when it happens, I know that if you have a zero roaming distance or an invalid entry there the bot will get to a waypoint and spin in circles. There is also the backing up bug sometimes you kill a mob and the bot justs starts backing up till its gets aggro or a chunk line or a cliff, these for me dont occur very often.

Dixi · Jun 5, 2010

Delorian76 said:
I too get stuck on the bonus yield window on harvesting.

I "fixed" it

Code:

function Harvest()
{

	if ${Me.Target.ID(exists)} && ${doHarvest} && ${Me.Target.Type.Equal[Resource]}
	{
			if ${HarvestBlackList.Element[${Me.Target.ID}](exists)}
				return

			; Check for Agro Mobs or other dangers
			;call AreWeSafe
			;if !${Return}
			;{
			;	call DebugIt ". Harvest:  Harvesting area NOT safe"
			;	HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]
			;	return
			;}

			HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]

      call DebugIt ". Harvest:   Harvesting Resource: ${Me.Target.Name}"
      VGExecute /autoattack

			isHarvesting:[TRUE]
			; Now wait for the Harvesting to finish
			;while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			;{
			;	wait 5
			;}

			wait 200	
		
			; by brig: begin added click routine for stuck bonus loots
			;while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			;{
				call DebugIt ". Harvesting looks stuck, click at close button spot"
				Mouse:SetPosition[200,436]
				wait 5
				Mouse:SetPosition[200,436]
				wait 15
				Mouse:LeftClick
				wait 5
				Mouse:ReleaseLeft
				wait 10
				Mouse:LeftClick
				wait 5
				Mouse:ReleaseLeft
				wait 5
			;}
			; by brig: end added click routine for stuck bonus loots
			isHarvesting:[FALSE]			

			wait 10

			; Then loot!
      Me.Target:LootAll

      VGExecute /cleartargets
      call ConsolidateResources

	}

It looks like the code get's stuck in the while-crafting-loop

Code:

while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			{
				wait 5
			}

so, I excluded that part and put in a longer pause (wait 200 = 20seconds; a harvest-session usually takes between 18sec and 19sec)

Oh yea! The clicky-part doesn't work all the time on my pc .. so I copied that part so it does it twice

Zandros · Jun 5, 2010

I looked at the code in the previous message and did some thinking...
the way I would go about closing them pesky harvesting windows I would try doing something like the following:

Code:

[COLOR="SeaGreen"];; update these coordinates by putting mouse over the close button during loot
;; and then go into the control panel and type in  echo ${Mouse} to get the current 
;; mouse coordinates then putting those values here[/COLOR]

variable int HarvX = 968
variable int HarvY = 924

function Close_HarvestingWindow()
{
	[COLOR="SeaGreen"];; If we are still harvesting, not done harvesting, but our progress is stuck at 0, then close that pesky harvesting window[/COLOR]
	if ${GV[bool,bHarvesting]} && !${GV[bool,IsHarvestingDone]} && ${GV[int,HarvestingTargetSI]}==0
	{
		VGExecute /endharvesting
		VGExecute /hidewindow Harvesting
		wait 10
	}

	[COLOR="seagreen"];; If we are harvesting but the system reports we are done, then close that pesky harvesting window[/COLOR]
	if ${GV[bool,bHarvesting]} && ${GV[bool,IsHarvestingDone]}
	{
		VGExecute /endharvesting
		VGExecute /hidewindow Harvesting
		wait 10
	}

	[COLOR="seagreen"];; Harvesting variables never lie -- yeah right![/COLOR]
	if ${GV[bool,bHarvesting]} && ${GV[bool,IsHarvestingDone]}
	{
		echo [${Time}] bHarvesting=${GV[bool,bHarvesting]}, IsHarvestingDone=${GV[bool,IsHarvestingDone]}, HarvestingRareItemsPresent=${GV[bool,HarvestingRareItemsPresent]}

		[COLOR="seagreen"];; Move cursor to last known position[/COLOR]
		Mouse:SetPosition[${HarvX},${HarvY}]
		
		[COLOR="seagreen"];; Hide Harvesting window[/COLOR]
		VGExecute /hidewindow Harvesting
		wait 10
		
		[COLOR="seagreen"];; cursor should be where the close button is when we show the harvesting window[/COLOR]
		VGExecute /showwindow Harvesting
		wait 10

		[COLOR="seagreen"];; Click at that location - nice, close button responds now :)[/COLOR]
		Mouse:LeftClick
		Mouse:LeftClick

		[COLOR="seagreen"];; Wait a good 10 seconds or until system reports we are not harvesting[/COLOR]
		wait 100 !${GV[bool,bHarvesting]}

		[COLOR="seagreen"];; Is Harvesting Window still open?[/COLOR]
		if ${GV[bool,bHarvesting]} && ${GV[bool,IsHarvestingDone]}
		{
			echo "WARNING:  Please close the Harvesting Window"
			vgecho "Please close the Harvesting Window to save the X Y coordinates of the close button"
			
			[COLOR="seagreen"];; Not thoroughly tested but this was true when the yield window was up[/COLOR]
			wait 600 !${GV[bool,HarvestingRareItemsPresent]}
			
			[COLOR="seagreen"];; save the X,Y coordinates[/COLOR]
			HarvX:Set[${Mouse.X}]
			HarvY:Set[${Mouse.Y}]

			[COLOR="seagreen"];; Wait a good 10 seconds or until system reports we are not harvesting[/COLOR]
			wait 100 !${GV[bool,bHarvesting]}
			
			if ${GV[bool,bHarvesting]}
			{
				echo "FAILED - Time ran out to close the pesky window"
				vgecho "FAILED - Time ran out to close the pesky window"
			}
			else
			{
				echo "New Mouse Coordinates to close Harvesting Window are X:${HarvX}, Y:${HarvY}"
				vgecho "Successfully learnt closing Harvesting Window"
			}
		}

		[COLOR="seagreen"];; just in case, hide any windows and end harvesting[/COLOR]
		VGExecute /hidewindow Harvesting
		VGExecute /endharvesting
	}
}

Next is the code in Kbot which is edited

Code:

[COLOR="seagreen"];; Initiate harvesting[/COLOR]
if ${Me.Target.IsHarvestable}
{
	[COLOR="seagreen"];; Move cursor to last known position[/COLOR]
	Mouse:SetPosition[${HarvX},${HarvY}]

	VGExecute /autoattack
	wait 5

}

isHarvesting:[TRUE]	

[COLOR="seagreen"];; wait until harvesting is done or our health is below 80%[/COLOR]
wait 200 !${GV[bool,bHarvesting]} || ${Me.HealthPct} < 80

[COLOR="seagreen"];; this will check and close the pesky harvesting window[/COLOR]
call Close_HarvestingWindow

isHarvesting:[FALSE]			

[COLOR="seagreen"]; Then loot![/COLOR]
Me.Target:LootAll
waitframe
VGExecute /cleartargets
call ConsolidateResources

Our goal here is put our cursour where the close button will be and start harvesting.
When the harvesting window shows, you will notice that the close button is clickable.
If the Bonus Yield window is up, we click and it closes. If for some reason we do not have
the correct coordinates, just put the mouse over the close button during harvesting and
go to the panel and type in echo ${Mouse} and save those x,y coordinates in the
script.

Oh, if you are wondering what HarvestingTargetSI is, it is the harvesting progress percentage.

Let me know if this successfully closes that pesky harvesting window.

Zandros · Jun 6, 2010

Ironically, it should work but it didn't.

So here is the scoop....

1) Start harvest a node
2) Manually move cursor over the close button
3) Let the script do its thing with the following bit of code:

Code:

if ${GV[bool,bHarvesting]} && ${GV[bool,IsHarvestingDone]}
{

	[COLOR="SeaGreen"];; cursor should be where the close button is when we show the harvesting window[/COLOR]
	VGExecute /showwindow Harvesting
	wait 10

	[COLOR="seagreen"];; Click at that location - nice, close button responds now :)[/COLOR]
	Mouse:LeftClick
	Mouse:LeftClick
			
	[COLOR="seagreen"];; Not thoroughly tested but this was true when the yield window was up[/COLOR]
	wait 600 !${GV[bool,HarvestingRareItemsPresent]}

	[COLOR="seagreen"];; just in case, hide any windows and end harvesting[/COLOR]
	VGExecute /hidewindow Harvesting
	VGExecute /endharvesting
}

What is happening is when we move the cursor using MouseTo or Mouse:Setposition, the Harvesting Close button is not highlighted. I thought that by hiding the harvesting window and re-show it would toggle the the highlight of the close button, but it didn't happen. So you have to move the cursor to the close button and leave it there. The script will -click- it and it will close the harvesting window.

Its lame but sofar it works AWSOME!

Turbodog · Jul 12, 2010

pathing

was trying to set this up but the pathing portion doesnt seem to work:

1) so i set up the path i want the character to take but he doesnt immediately start to path ( occasionally the character will start pathing but not always) Is there a time delay on the path start? if so which file do i need to modify to speed up pathing between kills

2) also sometimes the character just starts walking backwards seemingly randomly

3) also having trouble with the targeting( ie the character can be standing right beside an npc and wont attack the target -- sometimes i can click the target to attack and then the character will be back on track and start killing and following the path)..i think sometimes the target gets stuck on mobs that are already dead and thats whats causing this...perhaps some setting i can adjust?

i know that kbot isnt supported anymore, but i was just wondering if anyone had similiar experiences as me and knew something that perhaps i was doing wrong with the setup.

Thanks

mordacai · Jul 13, 2010

1/ How much of a delay? not having that problem myself. Make sure after you create waypoints you quit and then restart kbot before you first use a path. Downtime between kills is caused by the bot waiting until your health and energy is at acceptable percentages before continuing, so buy food and make sure "Use food if below Health%" is ticked set it nice and high like %90 so it will always chow down. The rest routine is pretty poor and needs work (add it to the list I guess)
2/ Yes this happens, but not very often.
3/Yes the targeting is a little temperamental. But I am just watching a bot right now seems to be targeting and killing like a champ. Do you mean that it has a mob targeted but wont Kill? This can happen if you are bow pulling and the mob is inside the minimum range of bow/ranged attack.
Getting stuck on a dead corpse is more a game bug, it usually only happens when the dead mob doesn't go through it's death animation properly and the name of the mob doesn’t turn grey, I know the bot doesnt specifically check either of those things just an observation, the bot then never goes to loot mode and stands around waiting till mob despawns before it moves on.

Turbodog · Jul 14, 2010

1) yea your right i fixed this; there was a problem with the downtime settings

2) fixed. only happens when waypoints havent been set or accidently erased.

3) figured out a work around for this with the g15 keyboard. also would be nice if there was somekind of /assist check to see if group members were being attacked...maybe there is and i just didnt see it. anyways i just made the same g15 macro do that for me anyways.

i really like this script btw for those of you that put the time in effort into development. Great job! I have other issues and questions but i think those belong in another thread. thanks for the feedback mordacai

DukeJohn · Sep 8, 2010

Dixi said:

I "fixed" it

Code:

function Harvest()
{

	if ${Me.Target.ID(exists)} && ${doHarvest} && ${Me.Target.Type.Equal[Resource]}
	{
			if ${HarvestBlackList.Element[${Me.Target.ID}](exists)}
				return

			; Check for Agro Mobs or other dangers
			;call AreWeSafe
			;if !${Return}
			;{
			;	call DebugIt ". Harvest:  Harvesting area NOT safe"
			;	HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]
			;	return
			;}

			HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]

      call DebugIt ". Harvest:   Harvesting Resource: ${Me.Target.Name}"
      VGExecute /autoattack

			isHarvesting:[TRUE]
			; Now wait for the Harvesting to finish
			;while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			;{
			;	wait 5
			;}

			wait 200	
		
			; by brig: begin added click routine for stuck bonus loots
			;while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			;{
				call DebugIt ". Harvesting looks stuck, click at close button spot"
				Mouse:SetPosition[200,436]
				wait 5
				Mouse:SetPosition[200,436]
				wait 15
				Mouse:LeftClick
				wait 5
				Mouse:ReleaseLeft
				wait 10
				Mouse:LeftClick
				wait 5
				Mouse:ReleaseLeft
				wait 5
			;}
			; by brig: end added click routine for stuck bonus loots
			isHarvesting:[FALSE]			

			wait 10

			; Then loot!
      Me.Target:LootAll

      VGExecute /cleartargets
      call ConsolidateResources

	}

It looks like the code get's stuck in the while-crafting-loop

Code:

while ${GV[bool,bHarvesting]} && (${Me.HealthPct} > 80)
			{
				wait 5
			}

so, I excluded that part and put in a longer pause (wait 200 = 20seconds; a harvest-session usually takes between 18sec and 19sec)

Oh yea! The clicky-part doesn't work all the time on my pc .. so I copied that part so it does it twice

Thank you, this worked for me... I didn't bother with the clicking part just the wait worked

wolfstrike · Nov 1, 2010

Kbot Mouse Position

I cant seem to find where to find the mouse postion loc so I can fix Kbot so it wont get stuck on Bonus yields.Can anyone let me know.

Thanks

Zandros · Nov 2, 2010

Harvesting Patch for Kbot

Try this... this works great for me and I haven't experienced the problem you mentioned. Let me know if this works for you.

Code:

function Harvest()
{
	if ${Me.Target.ID(exists)} && ${doHarvest} && ${Me.Target.Type.Equal[Resource]}
	{
		if ${HarvestBlackList.Element[${Me.Target.ID}](exists)}
		{
			return
		}

		call DebugIt ". Harvest:   Harvesting Resource: ${Me.Target.Name}"
		VGExecute /autoattack
		wait 20

		isHarvesting:Set[TRUE]

		; Now wait for the Harvesting to finish
		while ${GV[bool,bHarvesting]} && ${Me.HealthPct} > 80 && ${Me.Encounter}==0 && !${Me.Target.ContainsLoot}
		{
			wait 5
		}
		isHarvesting:Set[FALSE]

		if ${Me.Encounter}==0
		{
			HarvestBlackList:Set[${Me.Target.ID},${Me.Target.ID}]
			wait 10

			; Then loot!
			Me.Target:LootAll
		}
		VGExecute /cleartargets
	}
}

mart1n · Feb 11, 2011

kbot bugs out when fighting

Is anyone else having problems with kbot? the script bugs out when a mob is standing still. if a mob is moving and it gets pulled my char everything goes well. but if the mobs stays still and my char pulls it my char. keeps on running back and forth. only way i saw to correct this is to hit the forward botton. any info or tips are greatly appriciated

Kelly71 · Feb 18, 2011

I used Kbot for almost 2 years.. one of the best things out there for VG. I never had this problem ever. I havent used it for about 3 months but i dont think the pathing has changed at all.

When your stuck on a mob not moving is there any message in the isx window?

Mobs move ever 5+ seconds so i cant see this being a issue

Zandros · Feb 21, 2011

You know, I kinda noticed that too but it was more like inching his way closer to the Mob/Target which was annoying and obvious... I do believe I fixed it. Try using SVN to download the latest and let me know if that fixed it.

If it is still bugged, I will trace the code when I return home in March from my training.

BTW, did you try adjusting your distance to pull and attack?

wolfstrike · Mar 24, 2011

Bonus Yield work around

I had to reinstal Kbot and have now lost he Mouse setposition function for my kbot to work around the Bonus yield problem.Could someone post there KBFunctions so I could paste it over what I have....Thanks

Zandros · Mar 25, 2011

Its been a while since I used Kbot and I thought I had patched it so that after 20 seconds force exiting out of harvesting and loot everything. Is it still bugging out on you? Just in case, update your Kbot scripts via SVN and see if that fixed it. If not, let me know and I will tinker around with it

For the following snippet of code to work, you will need to move the cursor to the spot where the button is to end harvesting:

Code:

	;; alright, try -clicking- on the close button provided you left your cursor there
	;; Is Harvesting Window still open?
	if ${GV[bool,bHarvesting]} && ${GV[bool,IsHarvestingDone]}
	{
		MouseClick -hold left
		wait 3
		MouseClick -release left
		wait 3
		Mouse:LeftClick
		wait 5
	}

wolfstrike · Mar 25, 2011

I updated SVN at said I was at revision 2786...nothing updated

I had this before a friend sent me an updated .iss file and was able to work.I had to reinstall with no luck

wolfstrike · Mar 26, 2011

So I updated again via the svn and now I have 3 new function .iss files.
one is a .iss.mine file
one is a .iis.r2746 file
and the last one is .issr2776

No idea what those are.

THanks

Amadeus · Mar 26, 2011

Code:

So I updated again via the svn and now I have 3 new function .iss files.
one is a .iss.mine file
one is a .iis.r2746 file
and the last one is .issr2776

It means you manually edited the file at some point, so that's why you got 'conflicts'.

Best thing to do is just delete all three files and then update from SVN again (Or, you can move them to a 'backup' directory or something in case you want to make sure you don't lose any changes you might have made.)

wolfstrike · Apr 4, 2011

So im still not able to get those fixes downloaded and inserted into the script in a fashion that the bot will work.Can someone just send me a fized version of the fuction.iss so I can get back to harvesting =-)

Thanks

Zandros · Apr 8, 2011

Amadeus took the time a while back to get us up and running allowing us to use the script repository. He explains this in this message thread and I highly recommend reading it: http://www.isxgames.com/forums/showthread.php?p=2186#post2186

You will also see a link in that post that points to where all the files are in which you can manually download which is not the prefered method but since you are having problems with SVN to work correctly, it is the only other way I can think of without reposting the Zip.... http://www.isxgames.com/isxScripts/Vanguard%20(LavishScript)/Scripts/

One of the reasons why we don't post the zip is because svn will track every change so when we rezip the folder, it can get large.

wolfstrike · May 15, 2011

Ok,So ive been out of the game for sometime.I dont know what happened but my kbot will no longer even target a mining node.......Can someone take a quick look at it?At least all accounts for sony are free for next 45days!

wolfstrike · May 29, 2011

I completely deleted and downloaded Kbot.When the Bot paths back and forth it never targets the node what so ever.The bot works fine for everything else except harvesting.

Any thoughts?Anyone having this problem?

Sharedor · May 18, 2012

I have a problem with Kbot.
When i start Kbot, everything runs fine. He fights everything he should and he even harvest all the things i've told him.
But then, after a time, mostly 30mins-2hours, he runs his waypoints, maybe target the mob or the node, but don't fight.
I have to restart Kbot, then it works well again, for 30mins - 2hours...

ib_yoduh · Jun 16, 2012

Sharedor said:
I have a problem with Kbot.
When i start Kbot, everything runs fine. He fights everything he should and he even harvest all the things i've told him.
But then, after a time, mostly 30mins-2hours, he runs his waypoints, maybe target the mob or the node, but don't fight.
I have to restart Kbot, then it works well again, for 30mins - 2hours...

Mine is doing the same thing now too but it only takes about 15 minutes for this to start happening. Very frustrating. I wish I knew how to code.

propaine · Jun 30, 2012

I'm having the same problem with harvesting, it words fine for a few minutes then it starts harvesting and stops at around 83 % and goes for the next node.

Sharedor · Sep 4, 2012

First 1 or 2 Rounds work fine, but then:

Code:

Roaming: No Paths: Moving to waypoint_17 directly: 46351.035156 69366.148438
MOVETO called
Timeout: 27
MoveToXYZ called
Timeout: 36
Roaming: No Paths: Moving to waypoint_19 directly: 37463.734375 71276.507813
MOVETO called
Roaming: No Paths: Moving to waypoint_20 directly: 29127.230469 66083.781250
MOVETO called
Timeout: 40
Roaming: No Paths: Moving to waypoint_21 directly: 27342.599609 62257.781250
MOVETO called
MoveToXYZ called
Timeout: 41
Roaming: No Paths: Moving to waypoint_23 directly: 36084.066406 62819.718750
MOVETO called
Roaming: No Paths: Moving to waypoint_22 directly: 28315.046875 59846.117188
MOVETO called

move to random waypoints is not activated

bricky2690 · Feb 13, 2013

Ok, having an issue with my monk. I set the rest until energy is at 0. however, it will not move to waypoints. it keeps going to rest. it is working on all my other toons but not the monk. Is there a code line for energy rest that I can REM out?

Kbot -- Discussion

The Maestro

The Maestro

The Maestro

Active Member

The Maestro

Active Member

Active Member

The Maestro

Active Member

The Maestro

Active Member

Active Member

Active Member

Active Member

The Maestro

Active Member

Active Member

Active Member

The Maestro

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Active Member

Original Script Author: VGA

Active Member

Active Member

Active Member

Active Member

Member

Active Member

Active Member

Script Author: VGA

Script Author: VGA

Member

Active Member

Member

Member

Active Member

Script Author: VGA

Active Member

Active Member

Script Author: VGA

Active Member

Script Author: VGA

Active Member

Active Member

The Maestro

Active Member

Script Author: VGA

Active Member

Active Member

Active Member

Active Member

Member

Active Member

Active Member