MMOViper.com

============================================
========= MMOViperBot Change Notes =========
============================================
<B>Oct 18, 2013 MMOViperBot Version 2.0.7.3</B>

All Bots:
- Bugfix: Fixed Task->PressKey so that you can use Shift, Ctrl, etc.
- Bugfix: Fixed delete pointer in Patrol Areas (when deleting multiple waypoints)

FFXIV:ARR Bot:
- Added: Multi-client working (you can run multiple copies of ffxiv and viper on the same computer)
- Added: Grouping support. The bot will now pick up other members in your group if options/grouping is set to Leader/Follow mode.
- Bugfix: Multiple fixes for agro detection

GW2 Bot:
- Bugfix: Working with latest patches.

TERA Bot:
- Bugfix: Working with latest patches.


Did you know?
Viper now supports multiple clients for some games (background mode ones, like FFXIV). What does this mean for you? Well it means you can run multiple copies of the game and the bot all on the same machine! Yep right now in the FFXIV Bot you can open up 4 clients, group them all together, and have them all helping each other out to fight those really tough mobs.

wonderful testing now!!!

woot

Ok so it is attaching to the multiple windows. It will move the character around but it doesnt seem to be sending the key presses. It says in the log pressing numpad 0 but nothing is happening in game.

going to try and launch the games with out isboxer and see if that makes a difference.

it is targeting the nodes just sending the keystrokes to the game isnt working


edit: Ok no difference i launched just 1 copy of the game and 1 copy of the bot. it seems its not sending any of the keystrokes to the actually game. but it is moving the characters around.

You are the only one having the issue it seems. Reboot?

I hope the random stuck issue when gathering is no more in 2.0.7.3
Thanks Viper for the constant updates!

No, that fix did not make the cut. But it will go in next patch.

How can i choose which window i want bot to attach? By default it attaches to window with lowers PID (which opened earlier)

just hit NO
then the next one pops up

oh, can you just make a dropdown list for PIDs?

Yea I can make it a drop down in the next version. Thanks for the suggestion.

Please give feedback on muti-client. I have not had much chance to test things and want to get out fixes as quick as I can.

got my first .net error today.

Was using fine before the update then updated and this error.
Not sure whats the issure as i restarted game and client.
Really looking forward to grouping

what .net error? Might need to fully close game and viper and restart.

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

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'MMOViper.x5fc530570b97df70' threw an exception. ---> System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.
Parameter name: length
at System.Text.StringBuilder.ToString(Int32 startIndex, Int32 length)
at Magic.xd944b6e205388fe9.MMOViperBot.exe(IntPtr x96e7d32425e52ebf, Int32 xb3c050b04417be93)
at Magic.xd944b6e205388fe9.MMOViperBot.exe(IntPtr x96e7d32425e52ebf)
at Magic.xc29c2fdc9529e395.MMOViperBot.exe(String x8184dcb5534380d2, String x4c5ed57c233121f6)
at MMOViper.x367e8cb104a07d23..ctor()
at MMOViper.x5fc530570b97df70.ZYDNGuard()
at MMOViper.x5fc530570b97df70..cctor()
--- End of inner exception stack trace ---
at MMOViper.x14be83b45e88773f.MMOViperBot.exe(Object xe0292b9ed559da7d, EventArgs x5fafe85d958f1609)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(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.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
MMOViperBot
Assembly Version: 2.0.7.4
Win32 Version: 2.0.7.4
CodeBase: file:///C:/Users/Alix/Desktop/New%20folder/MMOViperBot.EXE
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.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.

PitViper wrote:Yea I can make it a drop down in the next version. Thanks for the suggestion.

Please give feedback on muti-client. I have not had much chance to test things and want to get out fixes as quick as I can.

Drop down menu would be perfect. Anyway for it to detect character name. I dont really know which 83050 window ID is which character hehe