Wildbuddy - Getting Started

Wildbuddy is our newest bot for Wildstar!

This is our first bot diving into the realm of x64-only support. That means, 32 bit versions of the game are not supported! (Please see the current release thread for .NET and C++ Redist download information)

The following is a quick guide to the UI for Wildbuddy. (Note: this is not a thread for developer questions! Please ask those in the developer forum where they can be properly discussed)

Upon Login you will be presented with the following screen:



Simply input your key that you received when purchasing Wildbuddy. If you have any issues logging in, please see the support sections for more information.

Once you have logged in, you will see various information regarding the bot, as well as a few buttons near the top of the window.



Starting from Right to Left, the buttons are as follows:

• LUA - Opens up a Lua console to help in debugging Lua-related code. Includes the ability to dump the _G variable, as well as full-dump on an object (table). Also supports simple running of lines as it would come from C#.
• PEC (Python Execution Console) - Allows you to execute Python code (using IronPython, so that all of Wildbuddy's API is available) to help debug, and test things. (Especially useful for conditionals in profiles)
• START (and STOP) - This will instruct the bot to start, and stop the bot.
• SETTINGS - This will open a flyout with current global settings for the bot.
• STATS - This will open the developer-bindable Stats flyout window. This may or may not have information in it. By default, Wildbuddy does not provide any stats. This is solely for 3rd party developers to have stats shown on the main window.
• LOAD PROFILE (using Profile Bot) - This button will change depending on what Bot is currently loaded (and if the bot wants a button on the UI). Currently, Wildbuddy ships with a single bot called "Profile Bot", and provides a button called "LOAD PROFILE" that handles profile loading for the user.
• TPS - This is just simple a "Ticks Per Second" display. The bot will report how fast it is running (accurate to 5 seconds or so) to help tell when the bot is slowing down.

On the right-hand side of the UI, are two dropdowns.

• Bot - This is simply a selector for which bot Wildbuddy is going to be using. By default, Wildbuddy only ships with Profile Bot which handles all the required logic.
• Routine - This selects the combat routine (similar to all of our bots) that the bot will use when dealing with combat-related tasks. (Fighting, healing, resting, etc)
• Routine Settings Button (The cog-wheel) - If the Routine has a UI to show the user for configuration, or other things, this button will be shown. Otherwise, it will be hidden to avoid confusion.

The bottom of the UI (bottom ~70%) is a log window, showing what the bot is doing, and any other information that may be relevant.


The following are some possible error-screens when the game is not in a currently supported state:



This screen will display when the bot could not find a supported build of the game. This can mean one of two options:

1. You currently do not have the game loaded, and running. (As shown in the image above)
2. You are using a version of Wildbuddy that does not support the version of the game running. (Possible running versions of the game will be displayed in the "Found similar processes" list)

If this window is shown, then the game has most likely updated, or you are simply not running a client that the bot can attach to!