MrFade

This issue was fixed with the user - using his email to login instead of his username.

Hey mate, this means your PC doesn't have the c++ redis you can download and install them here : https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-160

Hello mate, if you're still having this issue please try the following : * Try login with your email or username * Try changing your password on our site If you're still having issues feel more than free to contact me on discord and we can sort it out faster for you.

Great work, if you're okay with it I'll be adding these to the default files ! ❤️

>>>>>>> Join WEPW discord <<<<<<<<<

https://discord.gg/HEWQkzhYHg

Test // Amount of milliseconds since the bot last attempted an action public long LastAction; // Amount of milliseconds the bot has been in combat public long TimeInCombat; // Amount of milliseconds the bot has been out of combat. public long TimeOutOfCombat; // Local Player Unit public LocalPlayer Player; // Player's pet unit. Null if no pet exists. public GameUnit Pet; // Players targeted unit. Null if no target exists. public GameUnit Target; // Players last targeted unit. Null if no last target exists. public GameUnit LastTarget; // Get the amount of npc/player units around the local player. // MaxRange => Default 10. Maximum distance of unit allowed. // NotDead => Default True. Don't count dead units, or ghost players. public uint UnitsNearMe(double MaxRange, bool NotDead); // Get amount of Npc/Player units in combat, and targeting the player. public uint UnitsAttackingMe(); // Get amount of Npc/Player units targeting the local player public uint UnitsTargetingMe(); // Check if player can cast a spell by the Spell ID // IsCasting => Default true. Check will return false if player is casting or channelling // Unit => Default null. If input unit is not null, check if unit is within spell info Min/Max range. public bool CanCast(uint SpellID, bool Casting, GameUnit Unit, float MaxRange = 5.5f); public bool CanCast(string Name, bool Casting = false, GameUnit U = null, float MaxRange = 5.5f); public bool HasSpell(uint SpellID); public bool HasSpell(string Name); public bool HasSpell(string Name, int Rank); public long SpellCooldown(uint SpellID); public long SpellCooldown(string Name); public bool SpellInRange(uint SpellID, GameUnit u, float MaxRange = 5.5f); public bool SpellInRange(string Name, GameUnit u, float MaxRange = 5.5f); These are the open calls to gather basic item information. // Checks if the player currently has an item by name or item id. // BagOnly => If true will only look in the players backpack and bag slots, else will include bank items as well. // BagOnly defaults to TRUE, and does NOT need to be included in calls unless setting as false. public bool HasItem(string Name, bool BagOnly = true); public bool HasItem(uint ItemID, bool BagOnly = true); // Example: WoW.HasItem("Soul Shard") And/Or WoW.HasItem(2770, false); // Checks if an item is currently on cooldown by name or item id. // CheckSpell => Will check cooldown for the associated spell id of an item // CheckSpell defaults to FALSE, and does NOT need to be included in calls unless setting as true. public long ItemCooldown(uint ItemID, bool CheckSpell = false); public long ItemCooldown(string Name, bool CheckSpell = false); // Example: WoW.ItemCooldown("Health Potion") And/Or WoW.ItemCooldown("Hearthstone", true); // Checks if an item is currently in range of input unit. public bool ItemInRange(uint ItemID, GameUnit u, float MaxRange = 5.5f); public bool ItemInRange(string Name, GameUnit u, float MaxRange = 5.5f); Generic calls to use Spell, items, macros and in game commands. // Attempt to cast a spell by either name or spell id. public bool Cast(string Name); public bool Cast(uint SpellID); // Attempt to use an item by either name or spell id. public bool Use(string Name); public bool Use(uint ItemID); // Attempt to use an in game macro. // The macro MUST be bound to a handled key (Numpad would be best) public bool Trigger(string Name); // Attempt to send a wow command in game. // The command MUST be bound to an accepted key first. // Commands can be found: https://wowpedia.fandom.com/wiki/BindingID public bool Send(string Name); // All return true if the action binding has been found, and it registered an attempted keypress. False otherwise. Some wow commands are auto bound by ReBinder. // Used to dismount if player is mounted. public bool Dismount(); // Used to start player auto attack public bool StartAttack(); // Used to start players pet attack public bool StartPetAttack(); // Will stop using Shoot/Attack. public bool StopAttack(); // Used to stop casting the players current spell public bool StopCasting(); // Used to target your targets target public bool AssistTarget(); // Used to target the player public bool TargetSelf(); // Used to target the players pet public bool TargetPet(); // These last four do exactly as they say public bool TargetLastTarget(); public bool TargetNearestEnemy(); public bool TargetNearestFriendly(); public bool TargetLastEnemy(); // All these calls just call WoW.Send("COMMAND"); internally, and are just here to provide simple access. // These calls will return whatever WoW.Send("COMMAND"); calls. See above for more info.

*[Items]Fixed a bug with item management, this bug would not correctly update item keybinds after a item was deleted or a new item was looted. This will hopefully improve mounting as well as other item management. *[Items]Fixed a bug that would cause item keybind loading to fail resulting in the BOT using incorrect items (failing to eat, drink or mount), This bug would only happen if the user was running a combat rotation. *[Auto-loot]The BOT will now check for near by loot (within ~20 yards) if there is no other loot the BOT will mount after looting. *[Auto-loot] Fixed a bug that would cause the BOT to think it was stuck in a mesh hole and back peddle for ~ 2 seconds after looting or skinning mobs. *[Skinning]Fixed a bug that would cause the BOT to stop pathing after skinning (only happened if you had both auto-loot and auto-skin enabled) *[Auto-Loot] Auto-loot & Skinning have both been added to the unstuck list, if the player gets stuck on its path to loot or skin the BOT will now correctly attempt to unstuck. *[Auto-loot] Improved auto-loot and skinning speed, previously the BOT would take ~ 2 seconds before attempting to loot or skin this has been greatly improved. *[Auto-loot] The BOT will now prioritize looting over auto-targeting. *[Drinking]Fixed drinking, The BOT will now drink at the currect mana target. Previously it would always drink after combat. *[Config]Fixed config errors, the BOT will now only attempt to save/write to the config file every ~12 seconds. *[Config]Fixed a bug that would make the config file save as a blank file. *[Pulling] Mages,Warlocks and Preists will now also stay at range while pulling. *[Pulling] Ranged classes will attempt to correctly face a mob if it gets the error message "Target needs to be in front of you." [still in testing] *[Pulling] Mage,Warlocks and Preists will press 3 on your action bar ONCE (if a rotation is loaded) to pull agro of the MOB from afar. This can be used for stunning or fearing etc etc... *[Pulling] Added better tapped checks to the BOT, the BOT will no longer attempt to kill or loot a mob that has been tapped. *[Combat] Added checks to prevent the BOT from runing through its target multiple times during combat. *[Combat] Loading a rotation file with errors in it will now no longer crash WEPW.(The rotation wont run but the exact syntax error will be displayed in the console window.) *[Addon]Fixed addon to correct keybind all spells in players spellbook previously there was a bug that skipped a page of the spellbook this often caused issues for ferals and those with a lot of spells. *[Addon/Selling Grays]Fixed addon to create all macros again...This will fix issues with vendoring/mailing. *[Selling grays] Fixed a bug that would prevent the BOT from correctly reading the amount of free slots in the players inventory this would result in the player FAILING to sell grey items and getting stuck. *[Unstuck] Reworked unstucking logic once again...If jumping or strafing slightly fails to unstuck the player, the BOT will now generate a path to a random point within a 50 yard radius. *[Unstuck] If the BOT dismounts during the unstuck method, it will remount at the next waypoint. *[Minor]Removed old debug lines. *[Minor]The BOT will now attempt to mount a second time if the first fails. *[Minor]Auto-Target and Gather-Distance both have a default of 40 yards.(this can be seen in the UI and of course loading a profile will still set this automatically) *[Minor] When loading a profile or rotation the file explorer will now default to the Profiles or Rotations folder. *[Minor] Keybind thread will now only start once the user has attached to a WoW previously started on sucesfull login. *[Crashes]Improved stability of client (should reduces crashes)

Hello guys and welcome. This guides assumes you've read and are update to date with the Getting Started Guide. At the top of WEPW you'll find all the tabs of the BOT here is where most of the BOTs features and settings live (some have their own windows) In this guide we'll be having a quick look over the profile tab and what everything does. --Load Profile-- As most things on the UI this is rather self explanatory, If you click this button a selection window will appear where you can select what profile you wish to load. Profiles can contain a lot of information and are super helpful for creating a "click and forget system" some info that can be stored in profiles are : *Mailbox location *Vendor location *Whitelists of nodes to gather *List of waypoints (or a path) to follow *Whitelists of mobs to kill (and to auto loot or skin them) etc etc --Vendor-- Upon clicking the vendor button the BOT will check if you are currently targeting a NPC in-game. If you are, the BOT will ask you if wish to save this NPC as a vendor to either repair or sell junk at. If you are not targeting any NPC in-game the BOT will open a new window that has various settings allowing you decide when the BOT will repair or sell junk items. --Mail Items-- If you are standing near a mailbox in-game the BOT will ask if you wish to save and use this mailbox to mail items to an alt or bank. If you are not standing near a mailbox in-game the BOT will open a new window that allows you to setup a list of items to mail and whom to mail them to. --Eating-- The BOT will open a new window that will allow you select food & drink to use after combat and set the percent of health / Mana to drink / eat at. --Saving a profile-- If you load a profile you may notice a lot of the above information automatically populate including information in the Gathering or Combat tab. If you edit any of this information IE change what objects to gather or what mobs to kill and then save the profile all your changes will be saved on that profile. Making it super easy to edit existing profiles. Or just simply creating your own.

Hello and welcome, If you've just purchased WEPW and have no idea how to get started you're in the right place. First and for most it's important to ensure that your WoW has our addon (Re-Binder) installed if you have no idea how to install addons to wow follow this guide Once you've got your addon correctly installed start up your WoW, login and enter the world on a character you would like to BOT on. Once you're in-game start up the WEPW exe and you'll be greeted by the following(subject to change) : -Login- Simply input your username (or email) & password into the login handler (the same login information you use on our site.) Once you've hit "Log In" after a few seconds you should be greeted with the following messages : (If you get an error when attempting to login please read over this guide otherwise create a support thread Here.) Now that you've logged in you should notice your WoW window has been renamed to " [Number]WoW " this is on purpose to make selecting the correct WoW simple. To the right of the Login Handler you get the Client Manager as you can see in the image above we have not yet attached to any WoW process and so all our other tabs are grayed out. Attaching to a WoW process is as easy as clicking the drop down and selecting your WoW process. As I only currently have one WoW process running that's all that will be listed. After clicking attach the may take a second then all the other tabs should appear available if you get any "Incorrect game version" errors it's important to rather wait for us to update our client and ensure everything is safe and running before attempting to BOT. That's about it for the getting started guide ! If you are having any issues that you can't seem to solve please create a thread in our support section Here