Originally Posted by LcDog (Post 5858386)

Two ideas i think should be added.

You should add waypoints. So if we want to move from one point to another. We type in 1-1000(however many we want) diff points our character will move and he goes there while killing shit. You can also make it wont atk anything until the next point. Time INTERVAL movements so lets say i want to move to point 2 every 5m or so id put 4-8m then randomly between that time my char would move. Make it more human like and not bot like.

Also a random change realm. Same thing a time INTERVAL of our choice of say 5-10m(Random) and between that time the bot will pick a random time and will change to a random realm.

Originally Posted by LcDog (Post 5858386)

Two ideas i think should be added.

You should add waypoints. So if we want to move from one point to another. We type in 1-1000(however many we want) diff points our character will move and he goes there while killing shit. You can also make it wont atk anything until the next point. Time INTERVAL movements so lets say i want to move to point 2 every 5m or so id put 4-8m then randomly between that time my char would move. Make it more human like and not bot like.

Also a random change realm. Same thing a time INTERVAL of our choice of say 5-10m(Random) and between that time the bot will pick a random time and will change to a random realm.

Originally Posted by kay0s (Post 5858551)

You are a god. This is an amazing bot. I literally downloaded it and just guessed on the settings without reading any information and this shit just started raping. I genuinely appreciate your efforts, thank you sir. :)
Please continue this work in your free time! :handsdown:

//Edit: although the HP threshold isn't working and that's a major issue....

Originally Posted by V2usah6969 (Post 5858790)

Indeed, HP/MP and Buffs is currently bugging out.

Originally Posted by hattyhat (Post 5871117)

When doing crusade or poseidon in a party, the actual kill count do increase faster than the bot's current kill count.

So is it possible to add feature to allow changing the kill count instead of the default: 62?

Anyway big thanks for this great program.

Originally Posted by pizdulica (Post 5822591)

since yesterday i have this error:



See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Value was either too large or too small for an Int32.
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at BIOBB3.Bot_Session.LoadAddresses(IniFile iFil)
at BIOBB3.AddressUpdater.MemAddr_Check_Version(Proces s proc)
at BIOBB3.BIOBB3.Form_Load_CharList()
at BIOBB3.BIOBB3.btn_Bot_RefreshCharList_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
BIOBB3
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Administrator/Desktop/Release/BIOBB3.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Originally Posted by alaor (Post 5675839)

error... MSVCP100.dll
help?