• The project current goal is to support Burning Crusade Classic

• Addon: https://github.com/FreeHongKongMMO/Happy-Pixels to read the game state. Over the time its been heavily rewritten and optimized.

• Frontend: uses Blazor to show the state in a browser.

• Backend: written in C#. Screen capture, mouse and keyboard clicking. No memory tampering and DLL injection.

• Further detail about the architecture can be found in Blog post.

• Pathing: Indoors pathfinding only works properly if PathFilename is exists. For outdoor there are multiple solutions:

  • V1 Local - In processs PPather.
  • V1 Remote - Out of process PPather.
  • V3 Remote - Out of process AmeisenNavigation

• Game fullscreen or windowed mode
• Addon supports all available client languages
• Most of the classes should work. Some classes have more support than others.
• Highly configurable Combat rotation described in ClassConfiguration
• Utilizing the Actionbar related APIs to retrive ActionbarSlot(usable, cost)
• Based on the ClassConfiguration file populate Actionbar
• Pathfinding in the current zone to the grind location
• Grind mobs in the described PathFilename
• Blacklist certain NPCs
• Loot and Skinning
• Vendor goods
• Repair equipments
• Corpse run

Create an issue with the given template.

You are welcome to create pull requests. Some ideas of things that could be improved:

• This readme
• The route recording and editing
• More route and class profiles

• Runtime Class Profile picker
• Runtime Path Profile autocomplete search
• Frontend Dark mode
• Improved Loot Goal
• Added Skinning Goal
• Introduced a concept of Produce/Consume corpses. In short killing multiple enemies in a single combat, can loot and skin them all.
• ActionbarPopulator based on class config
• DataConfig: change where the external data(DBC, MPQ, profiles) can be found
• Edit the loaded profile from frontend
• NPCNameFinder: extended to friendly/neutral units
• Remap essential keybindings and support more Actionbar slots up to 34
• Added a new input system to handle modifier keys
• Support more 4:3 aspect ratio based resolution
• Addon is rewritten/reorganized with performance in mind(caching and reduce cell paint) to achive game refresh rate speed

Put the contents of the repo into a folder. e.g "C:\WowClassicGrindBot". I am going to refer to this folder from now on, so just substitute your own folder path.

This files are required for to find paths from where you are to the grind area, vendor and repair.

• Classic: common-2.MPQ (1.7Gb)
• TBC: expansion.MPQ (1.8Gb)

Copy the previusly mentioned files to \Json\MPQ folder (e.g. C:\WowClassicGrindBot\Json\MPQ)

• Windows 7 and above
• .netCore 3.1 x86 SDK
• Nvidia Control panel settings
  • Make sure the Image Sharpening under the Manage 3D Settings-> Global settings or Program Settings(for WoW) is set to Sharpening Off, Scaling disabled!
• Resultions which based on 4:3 aspect ratio 1024x768, 1920x1080, 4k
• Check these settings in the game client. Other values will stop the bot from being able to read the addon data.
  • System > Advanced > Constrast: 50
  • System > Advanced > Brightness: 50
  • System > Advanced > Gamma from: 1.0
  • System > Render Scale: 100%
  • Disable Glow effect - type in the chat /console ffxGlow 0
  • To keep/save this settings make sure to properly shutdown the game.

I would highly suggest to replace the default World of Warcraft font with a much Bolder one with this guide

Should be only concerned about Friz Quadrata: the "Everything Else" Font which is the FRIZQT__.ttf named file.

Example - Robot-Medium - Shows big improvement to the NpcNameFinder compontent which is responsible to find - friendly, enemy, corpse - names above NPCs head.

One of the following IDE or command line

• Visual Studio
• Visual Studio Code
• Powershell

You will need .net core 3.1 x86 SDK installed. Note: you need the x86 version, not the x64 one.

e.g. Build from Powershell

cd C:\WowClassicGrindBot
dotnet build

The bot reads the game state using small blocks of colour shown at the top of the screen by an Addon. This needs to be configured.

1. Edit the batch script in C:\WowClassicGrindBot\BlazorServer called run.bat, change it to point at where you have put the repo BlazorServer folder

   e.g.

   start "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" "http://localhost:5000"
   c:
   cd C:\WowClassicGrindBot\BlazorServer
   dotnet run
   pause

2. Execute the run.bat. This will start the bot and Chrome, Wow must be already running. If you get "Unable to find the Wow process is it running ?" in the console window then it can't find exe.

3. When running the BlazorServer for the first time you will have to follow a setup process:

   • Just start the game and wait in the character selection screen.
   • Click 2. Addon Configuration
   • Click Find InstallPath -> InstallPath should be filled otherwise, fill out manually
   • Fill the Author freely
   • Fill the Title freely
   • Then press Install & Save button -> Log should see AddonConfigurator.Install successful
   • Required to restart the Game
   • Enter world with your desired character
   • Click 5. Frame Configuration
   • Click Auto Configure and Restart

4. Under the Addon Configuration you can check if theres a newer version available for the addon. In that case just press the install button then have to restart the game client and the bot it self in order to use it properly.

We need to make sure that certain interface options are set. The most important are Click to move and screen flashing on low health. See the list below.

From the main menu (ESC) set the following under Interface Options:

The "Interact with Target" keybind is super important as it allows the bot to turn towards and approach the target. The "Target Last Target " keybind helps with looting.

From the main menu (ESC) set the following:

"Movement Keys" Key Bindings:

"Targeting" Key Bindings:

The default class profiles assumes the following Keybinds setup and using English Keyboard layout. In total, 34 key supported.

Highly recommended to use the default setup, in order to get properly working the ActionBarSlotCost and ActionBarSlotUsable!

Bindpad allows keys to be easily bound to commands and macros. Type /bindpad to show it.

For each of the following click + to add a new key binding.

Each class has a configuration file in \Json\class e.g. the config for a Rogue it is in file C:\WowClassicGrindBot\Json\class\Rogue.json.

The configuration file determines what spells you cast when pulling and in combat, where to vendor and repair and what buffs you give yourself.

Take a look at the class files in /Json/class for examples of what you can do. Your class file probably exists and just needs to be edited to set the pathing file name, but note they may be set up for level 60.

Normally, the bot would try to click your wows window for two reasons: target selecting and looting. To achieve this it will move your cursor. If you have multiple screens or simply do not want the bot to move your cursor, you can set KeyboardOnly to true.

Notice that when KeyboardOnly is enabled, the bot will only loot by selecting last target and tap interact key, which may fail to loot every target if there are many. And it will not be able to skin, either. The target selecting will also be limited to using TargetNearestTargetKey key, which would significantly reduce the range of selecting target.

The path that the class follows is a json file in /Json/path/ which contains a list of x & y coordinates the bot will traverse while looking for mobs.

"PathFilename": "58_Winterspring.2.json",   // the path to walk when alive
"PathThereAndBack": true,                   // if true walks the path and the walks it backwards.
"PathReduceSteps": true,                    // uses every other coordinate.

Each KeyAction has its own properties to describe what the action is all about.

Can specify conditions with Requirement(s) in order to create a matching action for the situation.

Some of these properties are optional and not required to be specified. However can create pretty complex conditions and branches to suit the situation.

e.g. - bare minimum for a spell which has castbar. Note: there are some spells which dosen't have visible castbar. like "Throw", "Shoot", "Auto Shot"

{
    "Name": "Frostbolt",
    "Key": "1",
    "HasCastBar": true,   //<-- Must be indicated the spell has a castbar
}

e.g. - bare minimum for a spell which is instant (no castbar)

{
    "Name": "Earth Shock",
    "Key": "6"
}

Theres are only two specially named KeyAction Food and Water which is reserved for eating and drinking.

They already have some prebaked Requirement conditions in order to avoid mistype the definition.

The bare minimum for Food and Water is looks something like this.

{
    "Name": "Food",
    "Key": "-",
    "Requirement": "Health%<50"
},
{
    "Name": "Water",
    "Key": "=",
    "Requirement": "Mana%<50"
}

e.g. for Rogue ability

{
    "Name": "Slice And Dice",
    "Key": "3",
    "MinEnergy": 25,
    "MinComboPoints": 2,
    "Cooldown": 3000,
    "Requirement": "not Slice And Dice"
}

This is the Sequence of KeyAction(s) that are used when pulling a mob.

e.g.

"Pull": {
    "Sequence": [
        {
            "Name": "Concussive Shot",
            "Key": "9",
            "StopBeforeCast": true,
            "Requirements": ["HasRangedWeapon", "!InMeleeRange", "HasAmmo"]
        }
    ]
}

The Sequence of KeyAction(s) that are used when in combat and trying to kill a mob.

The combat goal does the first available command on the list.

The goal then runs again re-evaluating the list before choosing the first available command again, and so on until the mob is dead.

e.g.

"Combat": {
    "Sequence": [
        {
            "Name": "Fireball",
            "Key": "2",
            "HasCastBar": true,
            "MinMana": 30,
            "Requirement": "TargetHealth%>20"
        },
        {
            "Name": "AutoAttack",
            "Requirement": "not AutoAttacking"
        },
        {
            "Name": "Approach",
            "Log": false
        }
    ]
}

These Sequence of KeyAction(s) are done when not in combat and are not on cooldown. Suitable for personal buffs.

e.g.

"Adhoc": {
    "Sequence": [
        {
            "Name": "Frost Armor",
            "Key": "3",
            "MinMana": 60,
            "Requirement": "not Frost Armor"
        },
        {
            "Name": "Food",
            "Key": "=",
            "Requirement": "Health%<30"
        },
        {
            "Name": "Water",
            "Key": "-",
            "Requirement": "Mana%<30"
        }
    ]
}

These Sequence of KeyAction(s) are done when not in combat and are not on cooldown.

The keypresses happens simultaneously on all KeyAction(s) which mets the Requirement.

Suitable for Food and Water.

e.g.

"Parallel": {
    "Sequence": [
        {
            "Name": "Food",
            "Key": "=",
            "Requirement": "Health%<50"
        },
        {
            "Name": "Water",
            "Key": "-",
            "Requirement": "Mana%<50"
        }
    ]
}

These command are for vendoring and repair.

e.g.

"NPC": {
    "Sequence": [
    {
        "Name": "Repair",
        "Key": "C",
        "Requirement": "Items Broken",
        "PathFilename": "Tanaris_GadgetzanKrinkleGoodsteel.json",
        "Cost": 6
    },
    {
        "Name": "Sell",
        "Key": "C",
        "Requirement": "BagFull",
        "PathFilename": "Tanaris_GadgetzanKrinkleGoodsteel.json",
        "Cost": 6
    }
    ]
}

The "Key" is a key that is bound to a macro. The macro needs to target the NPC, and if necessary open up the repair or vendor page. The bot will click the key and the npc will be targetted. Then it will click the interact button which will cause the bot to move to the NPC and open the NPC options, this may be enough to get the auto repair and auto sell greys to happen. But the bot will click the button again in case there are further steps (e.g. SelectGossipOption), or you have many greys or items to sell.

e.g. Sell macro - bound to the "C" key using BindPad or Key bindings

/tar Jannos Ironwill
/run DataToColor:sell({"Light Leather","Cheese","Light Feather"});

e.g. Repair macro

/tar Vargus
/script SelectGossipOption(1)

e.g. Delete various items

/run for b=0,4 do for s=1,GetContainerNumSlots(b) do local n=GetContainerItemLink(b,s) if n and (strfind(n,"Slimy") or strfind(n,"Red Wolf") or strfind(n,"Mystery") or strfind(n,"Spider L")) then PickupContainerItem(b,s) DeleteCursorItem() end end end

Because some NPCs are hard to reach, there is the option to add a short path to them e.g. "Tanaris_GadgetzanKrinkleGoodsteel.json". The idea is that the start of the path is easy to get to and is a short distance from the NPC, you record a path from the easy to reach spot to the NPC with a distance between spots of 1. When the bot needs to vend or repair it will path to the first spot in the list, then walk closely through the rest of the spots, once they are walked it will press the defined Key, then walk back through the path.

e.g. Tanaris_GadgetzanKrinkleGoodsteel.json in the Json/path folder looks like this:

[{"X":51.477,"Y":29.347},{"X":51.486,"Y":29.308},{"X":51.495,"Y":29.266},{"X":51.503,"Y":29.23},{"X":51.513,"Y":29.186},{"X":51.522,"Y":29.147},{"X":51.531,"Y":29.104},{"X":51.54,"Y":29.063},{"X":51.551,"Y":29.017},{"X":51.559,"Y":28.974},{"X":51.568,"Y":28.93},{"X":51.578,"Y":28.889},{"X":51.587,"Y":28.853},{"X":51.597,"Y":28.808}]

If you have an NPC that is easy to get to such as the repair NPC in Arathi Highlands then the path only needs to have one spot in it. e.g.

[{"X":45.8,"Y":46.6}]

Short Path Example:

In theory if there is a repeatable quest to collect items, you could set up a NPC task as follows. See 'Bag requirements' for Requirements format.

{
    "Name": "Handin",
    "Key": "K",
    "Requirements": ["BagItem:12622:5","BagItem:12623:5"],
    "PathFilename": "Path_to_NPC.json",
    "Cost": 6
}

A requirement is something that must be evaluated to be true for the KeyAction to run.

Not all KeyAction needs a requirement, some just rely on a Cooldown or MinMana/MinRage/MinEnergy.

A requirement can be put into a list if there is more than one.

e.g.

{
    "Name": "Soul Shard",
    "Key": "9",
    "HasCastBar": true,
    "Requirements": ["TargetHealth%<36", "not BagItem:6265:3"],     //<--- Requirement List
    "MinMana": 55
},
{
    "Name": "Curse of Weakness",
    "Key": "6",
    "WhenUsable": true,
    "ResetOnNewTarget": true,
    "Requirement": "!Curse of Weakness",                           //<--- Single Requirement
    "MinMana": 20
}

Every requirement can be negated by adding one of the Negate keyword in front of the requirement.

Formula: [Negate keyword][requirement]

e.g.

"Requirement": "not Curse of Weakness"
"Requirement": "!BagItem:6265:3"

Two or more Requirement can be merged into a single Requirement object.

By default every Requirement is concataneted with [and] operator which means in order to execute the KeyAction, every member in the RequirementsObject must be evaluated to true. However this consctruct allows to concatanete with [or].

Formula: [Requirement1][Operator][[RequirementN]

Note: Currently only one type of the [Operator] is handled in a single Requirement. So mixing [&&] and [||] is not supported.

e.g.

"Requirements": ["Has Pet", "TargetHealth%<70||TargetCastingSpell"]     // || in action
"Requirements": ["not Form:Druid_Bear", "Health%<50||MobCount>2"]       // || in action

Value base requirement is the most basic way to create a condition.

Formula: [Keyword][Operator][Numeric integer value]

Note: [Numeric integer value] always the right-hand side expression value

For the MinRange and MaxRange gives an approximation range distance between the player and target.

Note: Every class has it own unique way to find these values by using different in game items/spells/interact ways.

e.g.

"Requirement": "Health%>70"
"Requirement": "TargetHealth%<=10"
"Requirement": "PetHealth%<10"
"Requirement": "Mana%<=40"
"Requirement": "BagCount>80"
"Requirement": "MobCount>1"
"Requirement": "MinRange<5"
"Requirement": "MinRange>15"
"Requirement": "MaxRange>20"
"Requirement": "MaxRange>35"
"Requirement": "LastAutoShotMs<=500"
"Requirement": "LastMainHandMs<=500"

If a particular npc is required then this requirement can be used.

Formula: npcID:[Numeric integer value]

e.g.

• "Requirement": "not npcID:6195" - target is not 6195
• "Requirement": "npcID:6195" - target is 6195

If an itemid must be in your bag with given count quantity then can use this requirement.

Useful to determine when to create warlock Healthstone or soul shards.

Formula: BagItem:[itemid]:[count]

e.g.

• "Requirement": "BagItem:5175" - Must have a Earth Totem in bag
• "Requirement": "BagItem:6265:3" - Must have atleast 3x Soulshard in bag
• "Requirement": "not BagItem:19007:1" - Must not have a Lesser Healthstone in bag
• "Requirement": "not BagItem:6265:3" - Must not have 3x Soulshard in bag

If the player must be in the specified form use this requirement.

Useful to determine when to switch Form for the given situation.

Formula: Form:[form]

e.g.

"Requirement": "Form:Druid_Bear"       // Must be in `Druid_Bear` form
"Requirement": "not Form:Druid_Cat"    // Shoudn't be in `Druid_Cat` form

If the character must be the specified race use this requirement.

Useful to determine Racial abilities.

Formula: Race:[race]

e.g.

"Requirement": "Race:Orc"          // Must be `Orc` race
"Requirement": "not Race:Human"    // Shoudn't be `Human` race

If a given Spell name or id must be known by the player then you can use this requirement.

Useful to determine when the given Spell is exists in the spellbook.

It has the following formulas:

• Spell:[name]. The name only works with the English client name.
• Spell:[id]

e.g.

• "Requirement": "Spell:687" - Must have know id=687
• "Requirement": "Spell:Demon Skin" - Must have known the given name
• "Requirement": "not Spell:702" - Must not have known the given id=702
• "Requirement": "not Spell:Curse of Weakness" - Must not have known the given name

If a given Talent name must be known by the player then you can use this requirement.

Useful to determine when the given Talent is learned. Also can specify how many points have to be spent minimium with rank.

Formula: Talent:[name]:[rank]. The name only works with the English client name.

e.g.

"Requirement": "Talent:Improved Corruption"    // Must known the given `name`
"Requirement": "Talent:Improved Corruption:5"  // Must know the given `name` and atleast with `rank`
"Requirement": "not Talent:Suppression"        // Must have not know the given `name` 

If you feel the current Requirement toolset is not enough for you, you can use other addons such as WeakAura's Trigger to control a given bit.

1. The regarding in-game Addon API is looks like this

   YOUR_CHOOSEN_ADDON_NAME_FROM_ADDON_CONFIG:Set(bit, value)
   -- bit: 0-23
   -- value: 0 or 1 or true or false
   
   --e.g. by using default addon name
   DataToColor:Set(0,1)
   DataToColor:Set(0,0)
   DataToColor:Set(23,true)
   DataToColor:Set(23,false)

   e.g. you can make your awesome WeakAura. Then you can put the following Addon API in the

   WeakAura -> Actions -> On Show -> Custom

   DataToColor:Set(0,1) -- enable Trigger 0

   WeakAura -> Actions -> On Hide -> Custom

   DataToColor:Set(0,0)  -- disable Trigger 0

   Example Weakaura for hunter pet in 10y range for feed pet

   !WA:2!1rvWUTTrq0O6dPGOiXXT1afTaLWT1ibTiW2fnfOO9GOmvScKTuiPJtApqUK7qXnMC3f7Uu2khf6HCwFc6CpXpH8fqi0Va)j4VGUlPQHBrIoioZUZS78EZ82o93Qyl8w43(DcwPkNqbXOtdgo4exXLJstLGQtfMi55OzbWLQpALmdHzx8Q29(Q7uHOjzmXygHQI75EsGRh3(wjeMYefivipurkG1ED4BMukvScteNYXif4btbQ6kuPEvKIKCgbRYC6QDfOefHrLpXtQqc1UlWSW2SJIB)Y)SdrkuaRhlNj(fFq9W9(H9FKdHsuBxF)S4uTLmB367hvV57l29E0CLGmzciK3BxXAZ3(1ZjkO4eub05kzzCt9nwaPKl98h7oC41LsiSaKs0eiyghIENzH)nNi(dmUtanHss8ZyxmIgT6)4ELS5tpglxZO05M4l11CKJ5)d4GYtGOtGD2FVQMJMovxHqwtGzikoAHKd55nLOJsxc12x1KriJdcKM625x)TLyiUmn1uHIJChoU)Pdx0Gftc8pF8WUVY1l0Z9PUNeE4a)UodDpCL5gsB59bhgDd891he5YQWED9dc9d66f0e5nhxuScLRTTCm9zRARkpt5y3ldsoVHEIHm0uctKTsaOC)Bk)MZ5g0enVXCawATWSrdOIQUfHN5r1XTEBLEe58OQB1l4B27OUbHh7)0WZoAGUD5TOKUUXAXFGbztHGw)Jzy4VUd)lFVdTTgEMzx816rCqqr5Vq3g0mZFSqc5PTt(oJccgDSg2ufFZ(cYBSFEjcR7bi7GGLA(ZdMygITCYzi8lAk7KCKugvV32EfL5kILJg0jBxpWYRzNDJLe6KCi(OtnQk96osYBataZn3JV25lwlhFzRCCJLIMRXqboknqwMWOysJ8XI)nFyzjxajedM2yLwbQ1ZJ4TjjMT(raXR1sns6m94r)GLkwY0ws4JhV9oem)BZknKJTEO1MqT3FVz2nnnB99yNca2SZbLeCL354H)0lF4Zrf)EvQq3e9vgAAJRBFiPVzjt9h73ZZ19eVeJq9zBO)fRbtkzI18lyc8zceF(zRn4F)hgA4z6jfssOktaAbxoEwvlN18cWZ60PZgl1d1aU5fN)8tQi02dqdoRfikP18j13RF9UougfEhGKMQgOtuz3DfUu0erOrbO1Ngkxo3eJbg1eNceHQZTMu)67wFEDEDH28t))RSL07hF8p)4d2A6F)Y)5

2. Then outside of the game, you can specify the following in the ClassConfiguration file ex. class/Hunter_62.json

   Formula: Trigger:[bit]:[name]

   Where the bit is 0-23 and the name is a free text which shows up in the frontend.

   e.g.

   "Requirement": "Trigger:0:Pet in range"           // Trigger 0 must be true
   "Requirement": "Trigger:23:My Awesome trigger"    // Trigger 23 must be true
   "Requirement": "not Trigger:6:Suppression"        // Trigger 6 must be false

Allow requirements about what buffs/debuffs you have or the target has or in general some boolean based requirements.

e.g.

"Requirement": "not Well Fed"      // I am not well fed.
"Requirement": "not Thorns"        // I don't have the thorns buff.
"Requirement": "AutoAttacking"     // "Auto Attack" spell is active.
"Requirement": "Shooting"          // "Shoot" spell is active.
"Requirement": "Items Broken"      // Some of my armor is broken (red).
"Requirement": "BagFull"           // Inventory is full.
"Requirement": "HasRangedWeapon"   // Has an item equipped at the ranged slot.
"Requirement": "InMeleeRange"      // Determines if the target is in melee range (0-5 yard)

Allow requirements about spell range to be used, the spell in question depends upon the class being played.

"SpellInRange:0" or "not SpellInRange:0" for a Warrior is Charge and for a Mage is Fireball.

This might be useful if you were close enough for a Fireball, but not for a Frostbolt.

Formula: SpellInRange:[Numeric integer value]

e.g.

"Requirement": "SpellInRange:4"
"Requirements": ["Health%<80", "SpellInRange:2"]

Combined with the KeyAction.UseWhenTargetIsCasting property, this requirement can limit on which enemy target spell your character will react or ignore.

Firstly "TargetCastingSpell" as it is without mentioning any spellID. Simply tells if the target is doing any cast at all.

Secondly can specify the following Format "TargetCastingSpell:spellID1|spellID2|..." which translates to "if Target is casting spellID1 OR spellID2 OR ...".

e.g. Rogue_20.json

{
    "Name": "Kick",
    "UseWhenTargetIsCasting": true
},
{
    "Name": "Kick",
    "Requirement": "not TargetCastingSpell"
},
{
    "Name": "Kick",
    "UseWhenTargetIsCasting": true,
    "Requirement": "TargetCastingSpell:9053|11443"
},
{
    "Name": "Kick",
    "Requirement": "not TargetCastingSpell:11443"
}

The default mode for the bot is to grind, but there are other modes. The mode is set in the root of the class file.

e.g. Rogue.json

{
    "PathFilename": "Herb_EPL.json",
    "Mode": "AttendedGather",
    "GatherFindKeys":  [1,2]
}

The available modes are:

The user interface is shown in a browser on port 5000 http://localhost:5000. This allows you to view it from another device on your lan.

To access you PC port 5000 from another device, you will need to open up port 5000 in your firewall.

Control Panel\System and Security\Windows Defender Firewall - Advanced Settings

• Inbound Rules
• New Rule
• Port
• TCP
• Specific local ports: 5000
• Allow the Connection
• Private, Public, Domain (You may get away with just Private)
• Name "Wow bot"

The UI has the following components:

Show the player state. A hyper link to wowhead appears for the mob you are fighting so you can check out what it drops.

This component shows:

• The main path
• The spirit healer path
• Your location
• The location of any deaths
• Pathed routes

Pathed routes are shown in Green.

This component contains a button to allow the bot to be enabled and disabled.

This displays the finite state machine. The state is goal which can run and has the highest priority. What determines if the goal can run are its pre-conditions such as having a target or being in combat. The executing goal is allowed to complete before the next goal is determined.

Some goals (combat,pull target) contain a list of spells which can be cast. The combat task evaluates its spells in order with the first available being cast. The goal then gives up control so that a higher priority task can take over (e.g. Healing potion).

The visualisation of the pre-conditions and spell requirements makes it easier to understand what the bot is doing and determine if the class file needs to be tweaked.

Various path are needed by the bot:

The path to run when grinding (PathFilename in root of class files).

"PathFilename": "16_LochModan.json",
"PathThereAndBack": true,
"PathReduceSteps": false,

The short path to get to the vendor/repairer when there are obstacles close to them (PathFilename withing NPC task):

{
    "Name": "Sell",
    "Key": "C",
    "Requirement": "BagFull",
    "PathFilename": "Tanaris_GadgetzanKrinkleGoodsteel.json",
    "Cost": 6
}

To record a new path place your character where the start of the path should be, then click on the 'Record Path' option on the left hand side of the bot's browser window. Then click 'Record New'.

Now walk the path the bot should take.

If you make a mistake you can remove spots by clicking on them on the list on the right. Then either enter new values for the spot or click 'Remove'.

For tricky parts you may want to record spots close together by using the 'Distance between spots' slider (Smaller number equals closer together).

Once the path is complete click 'Save'. This path will be saved with a generic filename e.g. Path_20201108112650.json, you will need to go into your /Json/path and rename it to something sensible.

"PathThereAndBack": true

These paths are run from one end to the other and then walked backwards back to the start. So the end does not need to be near the start.

"PathThereAndBack": false

These paths are run from one end to the other and then repeated. So the path needs to join up with itself i.e. the end needs to be near the start.

Try to avoid the path getting too close to:

• Obstactles like trees, houses.
• Steep hills or cliffs (falling off one can make the bot get stuck).
• Camps/groups of mobs.
• Elite mob areas, or solo elite paths.

The best places to grind are:

• Places with non casters i.e. beasts. So that they come to you when agro'd.
• Places where mobs are far apart (so you don't get adds).
• Places with few obstacles.
• Flat ground.

Pathing is built into the bot so you don't need to do anything special except download the MPQ files. You can though run it on its own server to visualise routes as they are created by the bot, or to play with route finding.

The bot will try to calculate a path in the following situations:

• Travelling to a vendor or repair.
• Doing a corpse run.
• Resuming the grind path at startup, after killing a mob, or if the distance to the next stop in the path is not a short distance.

In visual studio just set PathingAPI as the startup project or from the command line:

cd C:\WowClassicGrindBot\PathingAPI
dotnet run

Then in a browser go to http://localhost:5001

There are 3 pages:

• Watch API Calls
• Search
• Swagger

Requests to the API can be done in a new browser tab like this or via the Swagger tab. You can then view the result in the Watch API calls viewer.

http://localhost:5001/api/PPather/MapRoute?map1=1446&x1=51.0&y1=29.3&map2=1446&x2=38.7&y2=20.1

Search gives some predefined locations to search from and to.

In visual studio right click the solution and set Multiple startup projects to BlazorServer and PathingApi and run.

Or from 2 command lines dotnet run each.

cd c:\WowClassicGrindBot\PathingAPI
dotnet run

cd c:\WowClassicGrindBot\BlazorServer
dotnet run

The bot will use the PathingAPI to work out routes, these are shown on the route map as green points.

Warlock heal macro used in warlock profiles.

#showtooltip
/cast [nocombat] Create Healthstone
/use Minor Healthstone
/use Lesser Healthstone
/use Healthstone
/use Greater Healthstone
/use Major Healthstone
/use Master Healthstone

Hunter feedpet macro replace Roasted Quail with the proper diet

#showtooltip
/cast Feed Pet
/use Roasted Quail

Hunter sumpet macro

#showtooltip
/cast [target=pet,dead] Revive Pet
/cast [target=pet,noexists] Call Pet

Rogue weapon enchant (use 17 for second weapon):

/use Instant Poison V 
/use 16
/click StaticPopup1Button1 

Melee weapon enchant:

/use Dense Sharpening Stone
/use 16
/click StaticPopup1Button1