nchebrov/azerothcore_installer
1
0
Fork 0
mirror of https://github.com/hermensbas/azerothcore_installer.git synced 2026-01-13 00:28:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

wiki updated

Browse Source
This commit is contained in:
bash
2026-01-09 11:35:43 +01:00
parent 22de5861dc
commit 5d137ba76b
8 changed files with 522 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
wiki/Home.md
View File

@@ -1,6 +1,6 @@
Welcome to the mod-playerbots wiki! If you are new to this project, it is strongly recommended to take the time to read through each section to get a better understanding of what you can or can't do with Playerbots as well as how best to configure your setup for success.
## [Playerbot Addons](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Add%E2%80%90ons)
## [Playerbot Addons and Sub‐Modules](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Addons-and-Sub‐Modules)
Recommended addons which allow for a smoother experience in controlling your Playerbots.
## [Playerbot Commands](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Commands)

7
wiki/Playerbot-Addons-and-Sub‐Modules.md
View File

@@ -1,11 +1,8 @@
## Multibot (by Macx-Lio)
Multifunctional tool designed to help control your playerbots. Actively maintained.
* [MultiBot](https://github.com/Macx-Lio/MultiBot)
* [MultiBot](https://github.com/Macx-Lio/MultiBot)
## Unbot (by Liyunfan)
Original Playerbot addon used to control your playerbots, not actively maintained.
* Chinese version: [Unbot Addon (zh)](https://github.com/liyunfan1223/unbot-addon).
* English version (translated by @Revision): [Unbot Addon (en)](https://github.com/noisiver/unbot-addon/tree/english).
Note: The official version of MultiBot is currently inactive, it's recommend to use the one maintained by Wishmaster117 found [here](https://github.com/Wishmaster117/MultiBot) for now
## Other Recommended Addons
* https://gitlab.com/Tsoukie/compactraidframe-3.3.5

156
wiki/Playerbot-Commands.md
View File

@@ -8,8 +8,8 @@ command | action
``.playerbots bot add [name1,name2,name3]`` | login altbots. Note that you are also able to login altbots from other accounts depending on your configurations.
``.playerbots bot addaccount [accountname]`` | login an entire account of altbots. Depending on your configurations you can login other accounts.
``.playerbots bot remove name1,name2,name3`` | logout altbots
``.playerbots bot add *`` | login all altbots
``.playerbots bot remove *`` | logout all altbots
``.playerbots bot add *`` | login all altbots that are in your party/raid
``.playerbots bot remove *`` | logout all altbots that are in your party/raid
``maintenance`` | enable altbot to learn all available spells and skills, supplement consumables, enchant gear, and repair. Can also be used on rndbots, but they automatically do this. Whisper for an individual bot or use /p or /r to simultaneously target multiple bots.
``autogear`` | automatically gear your altbot, with quality based on your .conf settings AutoGearQualityLimit and AutoGearScoreLimit. Can also be used on rndbots, but they automatically do their own gear initilization upon level up.
``talents`` | check current spec of bot
@@ -40,7 +40,7 @@ command | action
``follow`` | run toward player (/w for individual or /p or /r for party/raid)
``flee`` | run toward player ignoring everything else (/w for individual or /p or /r for party/raid)
``stay`` | stay in place
``runaway`` | kite mob
``runaway`` | kite mob // note: currently non-functional
``grind`` | attack anything
``disperse set x`` | force bots to maintain a distance of x yards from each other
``disperse disable`` | resets disperse distance to default value
@@ -49,10 +49,9 @@ command | action
Furthermore, you can specify by group or type for some commands like "attack" and "follow", such as:
- "@group1 follow"
- "@group2 attack"
- "@tank follow"
- "@ranged attack"
- "@rangeddps attack"
- "@meleedps attack"
This following are other groups that can be targeted:
- @tank, @dps, @heal, @ranged, @rangeddps, @meleedps, @[className]
You can also command multiple groups at a time like below:
- "@Group1,4"
@@ -65,23 +64,31 @@ command | action
``spells`` | show bot's spells
``cast [spell_name]`` | /w a bot to cast a spell
``cast [spell_name] on [PlayerName]`` | /w a bot to cast a spell on a specified Player
``ss +[spell id]`` | add spell to ignored spells list
``ss -[spell id]`` | remove spell from ignored spells list
``ss +[spell id]`` | add spell to exclude spells list
``ss -[spell id]`` | remove spell from exclude spells list
``ss reset`` | removes all spells from exclude spells list
``trainer`` | show what bot can learn from the selected trainer
``trainer learn`` | learn from the selected trainer
## Party/Raid Target Selection
RTSC is a system that enables players to save locations for specified bots to go to using the "aedm" spell that is given when the "rtsc" command is used. Aedm is a spell you use to point and click a particular location that can be saved and used via some of the commands below.
RTI is a system that enables players to focus bots on specified targets using standard WoW icons.
command | action
:---|:---
``rtsc`` | toggles on rtsc and gives players the "aedm" spell which will appear in the general category of their spellbook
``rtsc cancel`` | toggles off rtsc and removes the "aedm" spell from the spellbook
``rtsc save [#]`` | while rtsc is enabled, this command will save a location as the specified number when the player uses the aedm spell and clicks on a location
``rtsc unsave [#]`` | clears the saved location
``rtsc go [#]`` | command bots to go to the saved location, this command can be whispered to individual bots or filtered in party/raid chat with the same chat filters listed in Party/Raid General Commands (e.g., "@Tank rtsc go 5" will send all tanks to saved location 5)
``[name/group] rtsc toggle`` | toggles the ability to point and click with mouse button to save a location for specified bots to move to, can specify by group or class (ie "@druid rtsc toggle" or "@group1 rtsc toggle")
``rtsc go save`` | command bots to move back into saved rtsc position
``rti <icon>`` | sets the target icon for the bot to prioritize (icons: skull, cross, circle, star, square, triangle, diamond, and moon)
``attack rti target`` | commands bots to attack their rti target
``<name/group> rtsc toggle`` | toggles the ability to point and click with mouse button to save a location for specified bots to move to, can specify by group or class (ie "@druid rtsc toggle" or "@group1 rtsc toggle")
``rtsc go save`` | command bots to move back into saved rtsc position
``rtsc cancel`` | cancel rtsc toggle
``rti cc <icon>`` | sets a specific icon as the cc target (the default is moon)
Video demonstration:
Video guide:
https://www.youtube.com/watch?v=Pwt7schIC08
## Strategies
@@ -102,13 +109,13 @@ nc ?
### Combat Strategies
General
strategy | description
:---|:---|
``tank`` | use threat-generating abilities (warrior, paladin, druid will use ``bear``)
``tank assist`` | make tank pull mobs off of others
``dps`` | use dps abilities (rogue, hunter, shaman, priest, druid will use ``cat``)
``cc`` | use cc abilities (requires cc rti target, default is moon icon; it is useful to know that bots will not attack rti target and will not try to use cc if target is not stunnable)
``caster`` | wasn't in docs but is in game
``assist`` | target one mob at a time
``aoe`` | target many mobs at a time
``boost`` | bots will use big cds (useful to use -boost and +boost on macros to control when to burst on bosses)
@@ -121,25 +128,57 @@ strategy | description
``healer dps`` | healers cast damage spells if they have enough mana
``tank face`` | ensure the current target does not face ranged players in the group (to counter breath and cleave-like spells)
``behind`` | move to the target's back (rear flank) when they are not positioned behind the target
``frost``, ``fire`` | mage only
``bear``, ``cat``, ``caster`` | druid only
``bdps`` | buff dps (paladin will use seal of might)
``bspeed`` | buff movement speed (hunter only)
``bhealth``, ``bmana`` | buff health or mana (paladin will use seal of light vs seal of wisdom)
``rfire``, ``rfrost``, ``rshadow``, ``rnature`` | resistance strategies (paladin auras and hunter aspects)
``meta melee`` | default strategy for demonology warlocks, makes warlock go melee while using metamorphosis and immolation aura (demonology warlock only)
Druid
strategy | description
:---|:---
``bear``, ``cat``, ``caster`` | dictates overall strategy for druids, note that these are already handled by their talent selection
Hunter
strategy | description
:---|:---
``trap weave`` | enables the trap weave strat for hunters, dropping an explosive trap as part of their rotation (hunter only)
Mage
strategy | description
:---|:---
``frost``, ``fire`` | mage only, note that these are already handled by their talent selection
``firestarter`` | enables the firestarter strat for fire mages, resulting in the mage going into melee to utilize the instant cast flamestrike from the firestarter talent (fire mage only)
Shaman
strategy | description
:---|:---
``[totem name]`` | shaman will add totem into their call of the elements cast (ie "co +tremor" will add that totem for the shaman)
Warlock
strategy | description
:---|:---
``meta melee`` | default strategy for demonology warlocks, makes warlock go melee while using metamorphosis and immolation aura (demonology warlock only)
### Non-Combat Strategies
General (WIP)
General
strategy | description
:---|:---
``food`` | initiate or stop eating/drinking
``pvp`` | turn on or off pvp mode
``loot`` | enable looting everything by bots. For add or remove that strategy for randombots is required GM level > 1
``loot`` | enable looting everything by bots. Note: adding or removing that strategy for randombots requires GM level
Priest
strategy | description
:---|:---
``rshadow`` | priest will cast shadow protection
Paladin
strategy | description
:---|:---
``bdps``, ``bmana``, ``bstats``, ``bhealth`` | paladin blessing strategies (might, wisdom, kings, and kings/sanctuary depending on context, respectively)
``rfire``, ``rfrost``, ``rshadow``, ``baoe``, ``barmor``, ``bcast``, ``bspeed`` | paladin aura strategies (fire, frost, shadow, retribution, devotion, concentration, and crusader aura respectively)
Hunter
strategy | description
:---|:---
``bdps``, ``bspeed``, ``bmana``, ``rnature`` | hunter aspect strategies (dragonhawk/hawk, pack/cheetah, viper, and wild respectively)
Warlock Pet Strategies (Note that defaults are as follows: Affliction uses felhunter, Demonology uses felguard, and Destruction uses imp)
strategy | description
@@ -175,14 +214,6 @@ uld | enable Ulduar strats (Note: Strats implemented up to Hodir and Freya, WIP
onyxia | enable Onyxia's Lair strats
icc | enable Icecrown Citadel strats (Note: all normal mode currently doable, HC is WIP)
### Defaults
- Tank classes default w/ ``tank aoe``
- Non-tank classes default w/ ``attack weak``
- Strategies that are incompatible, such as ``stay`` and ``follow``, are ignored
## Loot
You can control which items to loot (``ll`` stands for loot list):
@@ -235,14 +266,26 @@ command | action
``talk`` | talk to the selected npc (to complete a quest)
``u [game object]`` | use game object (use "los" command to obtain the game object link)
## Hunter Pet Commands
## General Pet Commands
command | action
:---|:---
``pet name "name"`` | summon a tameable pet by name
``pet id "id"`` | summon a tameable pet by database creature ID
``pet family "family"`` | randomly summon a tameable pet of the given family
``pet rename "new name"`` | rename the current pet and refresh its name in the client UI
``pet aggressive`` | changing pet stance on aggresive
``pet passive`` | changing pet stance on passive
``pet defensive`` | changing pet stance on defensive
``pet stance`` | display current pet stance
``pet attack`` | pet attack selected target
``pet follow`` | pet follow his master
``pet stay`` | pet stay in place
## Hunter Tame Commands
command | action
:---|:---
``tame`` | tame help
``tame name "name"`` | summon a tameable pet by name
``tame id "id"`` | summon a tameable pet by database creature ID
``tame family`` | tame family help
``tame family "family"`` | randomly summon a tameable pet of the given family
``tame rename "new name"`` | rename the current pet and refresh its name in the client UI
## Account linking for Altbot control
@@ -255,6 +298,12 @@ command | action
``.playerbots account linkedAccounts`` | Shows a list of accounts, which are currently linked with this account
``.playerbots account unlink ACCOUNTNAME`` | Remove a linked account (this will remove the link for both sides, ensuring that access to the characters can be canceled from both sides anytime)
## Professions
strategy | description
:---|:---
``master fishing`` | The strategy is automatically added when ``EnableFishingWithMaster`` is enabled in the config. Strategy can be added manually. Strategy is automatically removed if further than ``EndFishingWithMaster`` from water. Strategy also overrides the follow distance to `FishingDistanceFromMaster`.
## Miscellaneous Commands
command | action
@@ -265,7 +314,7 @@ command | action
``playerbot bot initself`` | CAREFUL WITH THIS - re-rolls YOUR character
``playerbot bot list`` | lists your altbots (and your other characters you can add as bots if you have that enabled, but I'd be very careful if you do that as you can then re-roll your other characters using the init command)
``playerbot bot tweak`` | sets the tweakvalue (seems to be related to a config value that's no longer present and the variable it changes doesn't seem to actually do anything anymore)
``playerbot bot self`` | make yourself into a bot, you have to logout to turn this off, dont run it twice without doing so (it wont toggle it back off like its supposed to, it actually seems to apply multiple AI's onto yourself all fighting to do different things, sounds fun until it crashes the server)
``playerbot bot self`` | make yourself into a bot, use it again to disable
``playerbot bot lookup`` | doesn't do anything but print out a useless usage message (which says you're supposed to give it a class parameter but doing so doesn't change anything because the function called is literally *just* the usage message there's no functionality there)
``.playerbots bot init=rare name1,name2,name3`` | respawn bot at your level with talents & rare gear (gearing currently bugged, recommend autogear instead)
``who`` | show bot race, spec, talents, class, level, average item level, current zone
@@ -278,36 +327,9 @@ You can override everything and instruct the bot to do something specific:
command | description
:---|:---|
``do attack`` | attack target
``do loot`` | loot target
``do attack my target`` | attack my target
``do add all loot`` | check every corpse and game object for loot
## Example Macros
To make bots flee with you from the danger:
```
/p reset
/p nc -stay,+follow,+passive
/p co +passive
/p do follow
```
To make bots follow you and assist you in attack:
```
/p nc -stay,+follow,-passive
/p co -passive
/p do follow
```
To make bots stay in place and assist you in attack:
```
/p nc -follow,+stay,+passive
/p co +passive
/p do stay
```
``do loot`` | loot target // note: currently non-functional
``do add all loot`` | check every corpse and game object for loot // note: currently non-functional
## Help

35
wiki/Playerbot-Configuration.md
View File

@@ -1,5 +1,36 @@
## MySQL Tuning
The default MySQL configuration is not adequate for use with Playerbots, and will lead to increased disk activity and decreased performance.
You should add/change the below config options, in your MySQL configuration where ```innodb_buffer_pool_size``` ideally should be 50% of your total RAM:
```
#
# * Fine Tuning
# Example with 64 GB RAM
# INNODB
innodb_buffer_pool_size = 32G
innodb_io_capacity = 500
innodb_io_capacity_max = 2500
innodb_use_fdatasync = ON
innodb_buffer_pool_instances = 12
innodb_log_buffer_size = 32M
# Max age of binary logs - 5 days to prevent binary log pileups
binlog_expire_logs_seconds = 432000
# Optionally:
# Prevent SQL Deadlocks as much as possible
transaction_isolation="READ-COMMITTED"
```
Recommended configuration to extend lifespan of your hard drive:
- in mysql configuration file change/add line `skip-log-bin` which reduce ~75-90% of writes because skipping binary logging (Use at own risk)
- in playerbots configuration file enable `AiPlayerbot.DisabledWithoutRealPlayer` to make sure no bots are logged in, while no players are
- use as few bots as possible or limit yourself to only using altbots to minimize the amount of writes
## Bot activity profiles and performance
Before going into the configuration options we need explain the logic abit. Every update tick of the server its calculated whether a bot can
Before going into the configuration options we need explain the logic a bit. Every update tick of the server its calculated whether a bot can
or can't be active. An active bots takes and eats alot more resources then an idle bot.
The following logic is applied to determine whether a bot is active or not, applied in the explained order.
@@ -146,11 +177,9 @@ AiPlayerbot.RandomBotFixedLevel = 0
AiPlayerbot.DisableRandomLevels = 0
AiPlayerbot.RandombotStartingLevel = 5
AiPlayerbot.SyncLevelWithPlayers = 0
AiPlayerbot.DisableDeathKnightLogin = 1
AiPlayerbot.SyncQuestWithPlayer = 1
AiPlayerbot.AutoDoQuests = 1
#-------------------------------------------------------------------
# command (gear: 1 = normal, 2 = uncommon, 3 = rare, 4 = epic, 5 = legendary)
#-------------------------------------------------------------------

64
wiki/Playerbot-Macro-Collection.md
View File

@@ -1 +1,63 @@
### todo
## Pull
To make bots engage target and let tank build aggro (requires Slashin or ElvUI (not all versions) addon)
/in 8 determine delay before pull to other bots engage
```
/p @dps co +passive
/p @heal co +passive
/p @tank attack
/in 8 /p @dps co -passive
/in 8 /p @heal co -passive
```
## Bloodlust/Heroism
Stop bots using bloodlust/heroism
```
/p @shaman ss +2825,32182
```
Start bots again using bloodlust/heroism
```
/p @shaman ss -2825,32182
```
## Moving in fight
To make bots flee with you from the danger:
```
/p reset
/p nc -stay,+follow,+passive
/p co +passive
/p do follow
```
To make bots follow you and assist you in attack:
```
/p nc -stay,+follow,-passive
/p co -passive
/p do follow
```
To make bots stay in place and assist you in attack:
```
/p nc -follow,+stay,-passive
/p co +passive
/p do stay
```
## Targeting predefinied creature
To focus bots on target for example Web Wrap:
```
/target Web Wrap
/stopmacro [noharm][dead]
/script SetRaidTarget("target", 8)
```

32
wiki/Playerbot-Raid-Completion-Status.md
View File

@@ -1,5 +1,5 @@
## Raid Completion Status
This page is intended to keep track of raids that are currently possible to complete with playerbots and note which raids have active strategies implemented. A pure list of implemented raid strategies can be found here: https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Commands#raid-specific-strategies
This page maintains a brief overview of raids that are currently possible to complete with playerbots and note which raids and bosses have active strategies implemented. A more detailed list of implemented strategies can be found here: https://github.com/mod-playerbots/mod-playerbots/wiki/Playerbot-Raid-Strategy-Guide
"Unknown" denotes raids that have not been thoroughly tested and verified.
@@ -7,7 +7,7 @@ This page is intended to keep track of raids that are currently possible to comp
Raid | Completion Status | Notes
:---|:---|:---
``Molten Core`` | Completable | Raid strategy implemented for: Baron Geddon. Otherwise every boss is defeatable with minimal knowledge and planning.
``Molten Core`` | Completable | Raid strategy implemented for all bosses.
``Blackwing Lair`` | Completable | Raid strategy implemented for: added automatic Onyxia Scale Cloak buff to playerbots, bots automatically disable suppression devices, and bots automatically clear Brood Affliction: Bronze on Chromaggus. Otherwise every boss is defeatable with minimal to moderate knowledge and planning.
``Zul'Gurub`` | Completable | No raid strategies implemented. Every boss is defeatable with minimal to moderate knowledge and planning.
``Ruins of Ahn'Qiraj`` | Completable | Raid strategy implemented for: Ossirian. Otherwise every boss is defeatable with basic knowledge and planning.
@@ -18,13 +18,13 @@ Raid | Completion Status | Notes
Raid | Completion Status | Notes
:---|:---|:---
``Karazhan`` | Completable | No strategies implemented, but bosses are doable with little to significant planning depending on the boss. Chess event not coded but is possible to solo.
``Magtheridon`` | Completable | No strategies implemented, but they are not needed. Boss is defeatable with moderate knowledge and planning.
``Gruul’s Lair`` | Completable | No strategies implemented, but they are not needed. Every boss is defeatable with moderate knowledge and planning.
``Serpentshrine Cavern`` | Unknown | Unknown
``Hyjal Summit`` | Unknown | Unknown
``Tempest Keep`` | Unknown | Unknown
``Black Temple`` | Unknown | Unknown
``Karazhan`` | Completable | Raid strategy implemented for all bosses except the Chess Event, which is soloable without any bot involvement.
``Magtheridon's Lair`` | Completable | Raid strategies have been implemented for Magtheridon.
``Gruul’s Lair`` | Completable | Raid strategies have been implemented for both bosses.
``Serpentshrine Cavern`` | Partially completable | Strategy is currently in PR, but some bosses are defeatable with moderate knowledge and planning except for Lady Vashj who will require strats.
``Tempest Keep`` | Not completable| It is not possible to pass A'lar until strategies are implemented.
``Hyjal Summit`` | Completable | No strategies implemented, but every boss is defeatable with moderate knowledge and planning.
``Black Temple`` | Partially completable | Every boss is completable without strategy except Council and Illidan. Council is hard and requires proper RTI marks. Illidan looks unkillable without strategy.
``Zul’Aman`` | Unknown | Unknown
``Sunwell Plateau`` | Unknown | Unknown
@@ -32,12 +32,22 @@ Raid | Completion Status | Notes
Raid | Completion Status | Notes
:---|:---|:---
``Naxxramas`` | Completable | Raid strategy implemented for: most bosses. Otherwise every boss is defeatable with moderate knowledge and planning. Not applicable for 40 man
``Naxxramas`` | Completable | Raid strategy implemented for most bosses. Otherwise every boss is defeatable with moderate knowledge and planning. Not applicable for 40 man
``Vault of Archavon`` | WIP | Raid strategy implemented for: Emalon. Needs more strategies. Archavon is defeatable with minimal knowledge and planning.
``Obsidian Sanctum`` | Completable | Raid strategy implemented for: Sartharion up to two drakes. Must kill Vesperon first.
``Eye of Eternity`` | Completable | Raid strategy implemented for: Malygos.
``Ulduar`` | WIP | Raid strategy implemented for: Up to General Vezax.
``Ulduar`` | WIP | Raid strategy implemented for: Up to Yogg-Saron.
``Trial of the Crusader`` | WIP | Needs strategies.
``Onyxia’s Lair`` | Completable | Raid strategy implemented for: Onyxia.
``Icecrown Citadel`` | Completable | All necessary raid bosses have implemented raid strategies. Heroic mode is still WIP.
``Ruby Sanctum`` | Unknown | Unknown
## Special Thanks
Special thanks to all of the contributors who designed these raid strategies:
Bobblybook: Obsidian Sanctum, Eye of Eternity
Crow: Karazhan, Gruul's Lair, Magtheridon's Lair
Gromleq: Vault of Archavon, Ulduar
Liyunfan: Naxxramas
Noscopez: Icecrown Citadel
Revision: Karazhan

314
wiki/Playerbot-Raid-Strategy-Guide.md Normal file
View File

@@ -0,0 +1,314 @@
## Raid Strategy Status
This guide works alongside https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Raid-Completion-Status by going into detail on each strategy coded per boss for each raid, as well as note expected player actions where the coded strategy may be insufficient or not necessary. Please note that the strategies and overall feasibility are made assuming appropriate level gear for that content, although many are also completable using the Individual Progression module nerfs.
## Vanilla
### Molten Core
*This raid is completable with IP nerfs.
**Lucifron**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Shadow resistance aura will be automatically applied.
* Tips & Tricks: None
**Magmadar**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied.
* Tips & Tricks: Use Bots to place fear ward on tank, and have shamans use tremor totems to help with fear; may be added as a strat in the future.
**Gehennas**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Shadow resistance aura will be automatically applied.
* Tips & Tricks: None
**Garr**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied. Disabled aoe dps abilities via multiplier to help prevent multiple simultaneous explosions.
* Tips & Tricks: None
**Baron Geddon**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied. Bots will run away from the raid if they get Living Bomb and will run away from boss during Inferno.
* Tips & Tricks: None
**Shazzrah**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Ranged bots will position themselves at maximum distance in order to avoid the arcane explosion while still being able to dps and heal.
* Tips & Tricks: None
**Sulfuron Harbinger**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied.
* Tips & Tricks: Use Skull icon to focus target down individual boss adds.
**Golemagg the Incinerator**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied. Disabled aoe dps via multiplier. Offtanks pull Core Ragers away from Golemagg to remove their buff.
* Tips & Tricks: None
**Majordomo Executus**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Shadow resistance aura will be automatically applied.
* Tips & Tricks: Use Skull icon to focus target down individual boss adds.
**Ragnaros**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Fire resistance aura will be automatically applied.
* Tips & Tricks: None
### Blackwing Lair
*Note that all Playerbots are automatically granted the Onyxia Scale Cloak buff and will automatically disable suppression devices. This raid is completable with IP nerfs.
**Razorgore the Untamed**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: Player will need to control Razorgore to destroy the eggs in Phase 1.
**Vaelastrasz the Corrupt**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: None
**Broodlord Lashlayer**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: None
**Firemaw**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: None
**Ebonroc**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: None
**Flamegor**
* Defeatable Solo with Bots: Yes, without coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: None
**Chromaggus**
* Defeatable Solo with Bots: Yes, with coded strategies and some manual control needed.
* Coded Strategies: Bots will automatically clear Brood Affliction: Bronze
* Tips & Tricks: Depending on gear, some manual bot control may be necessary using RTSC to place Chromaggus by the door to LOS during certain breath attacks.
**Nefarian**
* Defeatable Solo with Bots: Yes, with some degree of manual control needed.
* Coded Strategies: None
* Tips & Tricks: In Phase 2, use RTSC to place main tank for Nefarian by the stairs facing away from the raid. Use commands for shamans to use tremor totem, and remove tank assist (co -tank assist) from main tank to avoid him moving Nefarian around when the skeleton adds spawn in Phase 3.
## Burning Crusade
### Karazhan
*This raid is completable with suggested IP nerfs. Strategies were written and tested with 1) bot damage and healing each reduced to 50% of normal strength, and 2) HP of all raid mobs restored to Patch 2.4.3 levels (reverting the global 30% nerf to HP of TBC raid mobs from Patch 3.0.2).
**Attumen the Huntsman & Midnight**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* The main tank will tank Midnight, and bots will focus DPS on Midnight.
* When Attumen spawns, the assist tank will pick him up and move him away from the raid because he cleaves.
* When Midnight reaches 25% health and Attumen mounts Midnight, the main tank will pick up Attumen, and other bots will briefly pause DPS. All bots other than the tank will stack up behind Attumen, inside the minimum range of his Berserker Charge.
* Tips & Tricks: Although not required, the easiest way to pull Midnight is to have bots stay out of line-of-sight behind the haycart and pull Midnight yourself (and then take bots off of stay once Midnight gets around the haycart).
**Moroes**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* The main tank will target Moroes for the duration of the encounter.
* Other bots will mark adds with the skull icon and prioritize accordingly based on the standard kill order (Millstipe first, Von’indi second, etc.), taking into account which four adds were randomly chosen.
* Tips & Tricks: In practice, the adds will likely be grouped up, and bots will AoE them down (with classes without AoE capabilities targeting the add marked with a skull). If you want bots to only single-target prioritize adds, you will need to disable their standard AoE DPS strategies. However, it is likely (even when playing with IP nerfs) that AoEing down the adds will be fast and effective.
**Maiden of Virtue**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* The main tank will position Maiden in the middle of the room, and ranged bots will fan out around the center, between the pillars.
* When Maiden casts Repentance, the tank will move her to a healer to use the Holy Ground to break the healer’s stun.
* Tips & Tricks: Each ranged bot has an assigned position between pillars—if you are also playing a ranged class, make sure to find an open spot so you do not chain Holy Wrath.
**Opera Event**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* Bots will switch the skull icon back and forth between Romulo and Julianne as needed to try to kill them at about the same time.
* Bots will mark the Wizard of Oz bosses with the skull icon and prioritize accordingly based on the standard kill order (Dorothee, Tito, Roar, Strawman, Tinhead, Crone). Mage bots will spam Scorch on Strawman to disorient him.
* The main tank will position the Big Bad Wolf in the front left corner of the stage (from the perspective of facing the stage). Bots that are transformed into Little Red Riding Hood will attempt to run around the stage to get away from the Big Bad Wolf.
* Tips & Tricks: To speed up your clear, you can talk to Barnes and initiate the Opera Event while letting bots clear the final trash mobs. You will likely still have plenty of time to prepare to engage the boss due to the long intro to the event.
**The Curator**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* The main tank will position Curator in a designated spot in the center of the hallway near the entrance to the Guardian’s Library.
* Ranged bots will spread out, and all bots will mark and prioritize destroying Astral Flares.
* The assist tank will stay on Curator (instead of picking up Flares) to try to stay second on aggro to absorb Hateful Bolts.
* Bots will save Bloodlust/Heroism until Curator uses Evocation and is vulnerable to double damage.
* Tips & Tricks: Set bots to “co -boost” before the fight to prevent them from using other major cooldowns and activate “co +boost” when Curator uses Evocation.
**Terestian Illhoof**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Bots will mark and prioritize targets with the skull icon in the following order: (1) Demon Chains, (2) Kil’rek, and (3) Terestian Illhoof.
* Tips & Tricks: If you are playing DPS, consider using a /target macro for the Demon Chains.
**Shade of Aran**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* Ranged bots will attempt to maintain spread positions outside of Aran’s Counterspell range.
* When Aran casts Massive Magnetic Pull, bots will run to the edge of the room to escape the Arcane Explosion.
* When Aran casts Flame Wreath, and for the duration of the Flame Wreath aura being active, bots will stop moving.
* When Aran summons Conjured Elementals, bots will mark and prioritize them with the skull icon.
* Tips & Tricks:
* Coded strategies do not persist after Aran dies so if Flame Wreath is active when he dies, make sure to manually command bots to stay or they will blow up the raid.
* An Azerothcore bug exists that sometimes causes Flame Wreath to persist long beyond its correct duration. If Aran casts Arcane Explosion while Flame Wreath is still active, there is not much you can do, and it is probably a wipe.
**Netherspite**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Bots are assigned to block beams during the Portal Phase, and proper raid composition is important to ensure sufficient beam coverage.
* Tank bots are assigned to block the red beam. Each tank will block the red beam for an entire Portal Phase and will dance in and out of the beam to avoid taking too many stacks of the debuff.
* DPS bots (excluding Rogues and Warriors) are assigned to block the blue beam. They will transition at 24 stacks of the debuff, and therefore two such bots are required for each Portal Phase.
* Healer, Rogue, and DPS Warrior bots are assigned to block the green beam. Rogues and DPS Warriors will be prioritized, and if they are assigned, they will remain in the beam for the duration of the Portal Phase (since there is no disadvantage to them from the debuff). Only if there are not enough eligible Rogues and DPS Warriors will healers block the green beam, and they will transition at 24 stacks of the debuff.
* Bots are coded to avoid Void Zones and to avoid beams that they are not assigned to block.
* Bots will briefly pause DPS when Netherspite is pulled and again upon each transition into the Portal Phase.
* Tips & Tricks:
* Netherspite is bugged in Azerothcore in that the beams cannot be blocked inside of Netherspite’s hitbox (18 yards from his center), even though they visually continue to his center (and were blockable inside his hitbox in retail). The bots are coded to account for this, but the player should also be aware in the event that the player needs to block a beam. Additionally, this makes it important to pull the boss in the middle of the room since if the boss is too close to a portal, it will be impossible to block the beam.
* The player’s primary role during the Portal Phase (other than filling in for a bot that dies without replacement) should be to back up the bots on beams. Bots may not transition blocking duties as quickly as competent players (who would be prepared next to a beam when they are about to take over blocking to ensure an instant transition—for various reasons, trying to code this for bots is problematic). In particular, any gap in blocking of the Green Beam can be disastrous. Accordingly, if a healer bot is blocking the Green Beam, players should be prepared to block the Green Beam temporarily then the transition occurs.
* Bot tanks are coded not to attempt to avoid Void Zones while moving in and out of the Red Beam. The ability to control their movement is not sufficiently precise or dynamic to allow for their avoidance without ensuring that the boss does not move (and cause all beam blockers to get out of position). Therefore, tanks will need to be healed through the extra damage.
* The only strategy coded for the Banish phase is for bots to avoid Void Zones, and therefore it is the player’s choice whether to continue to DPS the boss or to bring the raid out of range of Netherbreath and wait for the next Portal Phase to reengage.
**Chess Event**
* Defeatable Solo with Bots: Yes, no bot involvement needed.
* Coded Strategies: None.
* Tips & Tricks: From White’s point of view, use your first three turns to move pawns forward to b3, d3, and g3. Use your next two turns to move rooks to a2 and g2. If Medivh sets a fire under your king or queen, stop what you are doing and immediately move them out of the fire. Thereafter, generally focus on controlling the queen and using Fireball (Horde) or Elemental Blast (Alliance) to target the opposing king. This method is effective but not guaranteed, as success is dependent on RNG (including where Medivh moves the king and what cheats he uses and when). Depending on the situation, it may be helpful to capture other pieces before the king (in particular, the opposing bishops and/or queen).
**Prince Malchezaar**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies:
* Bots that are Enfeebled will run out of Shadow Nova range and should select escape vectors that do not come in range of any Netherspite Infernal’s Hellfire.
* All bots will attempt to avoid Infernals. The tank will attempt to stay a bit further from the Infernals than other bots to try to give players and other bots (particularly melee DPS) some room to maneuver.
* Bots will save Bloodlust/Heroism until phase 3 (Malchezaar at 30% HP), when the Infernal spawn rate increases drastically.
* Tips & Tricks: Bots may get “stuck” behind an Infernal that lands between them and Malchezaar, as they will refuse to run into the Hellfire and are unable to move around Infernals. If this happens, briefly activate “flee” and lead the bots slightly off to the side of the Hellfire (or even into or through the Hellfire if they are able to survive) so that they can reach the boss by moving in a straight line after the flee strategy is removed.
**Nightbane**
* Defeatable Solo with Bots: Yes. During phase changes, the player will be responsible for leading bots to the correct positions in anticipation of combat (discussed below). No RTSC is needed; just make sure to run to the general area called for by the strategies at the right time.
* Coded Strategies:
* The tank and ranged bots have fixed positions near the Northeastern door to the Master’s Terrace. After summoning the boss, players should lead the bots to that general area to wait for combat to begin.
* The tank will attempt to move Nightbane in a manner that results in him being positioned perpendicularly from the raid, facing the edge of the balcony (though this is imperfect, and he may end up at a slight angle).
* Priest bots will cast Fear Ward on the tank.
* There are three fixed positions coded for ranged bots. The ranged bots will stack and cycle through the positions if Charred Earth spawns underneath them. It is a known issue that bots will sometimes arrive at a safe position but continue to cycle—this is due to the fact that the bots determine whether they are in an unsafe position by the presence of the Charred Earth aura on themselves. It is possible for the aura not to have faded before the bot arrives at the next position, even if the next position is safe, resulting in the bot thinking it is not safe and continuing to cycle. However, they should eventually settle into a safe position.
* When the flight phase starts, bots will mark Nightbane with a moon and stop attacking. They will stack at a position near Nightbane’s flight phase position so he does not use Fireball Barrage. When Rain of Bones is cast and Restless Skeletons spawn, all bots will move away and stack in a new position that is outside of the Rain of Bones AoE before killing the Skeletons.
* Hunter and Warlock pets are set to passive during the flight phase. Players should make sure to do this as well. The maps on the Master’s Terrace are extremely buggy, and pets will chase Nightbane into midair and may even run out of the tower grounds, which can cause Restless Skeletons to spawn in odd places and even aggro mobs from other parts of the instance. Because of this, bots are disabled from using any temporary pets (e.g., Spirit Wolves, Water Elementals, Treants) during the encounter.
* The flight phase lasts for 45 seconds, but Nightbane is not aggressive during the final 10 seconds (when he is preparing to land). Nightbane will yell that he is landing, at which point the player will need to lead the bots back to the ground phase combat area.
* Bots will pause DPS after the pull and after each transition into the ground phase to allow the tank to get aggro.
* Tips & Tricks:
* Because of the buggy maps, there is a tendency for mobs to pull through the floor, and it is suggested that prior to the encounter, you clear all mobs from the Livery Stables, including the upper level, and the Scullery.
* AoE avoidance is intentionally disabled for the tank. This is necessary to prevent the tank from spinning Nightbane and causing him to face the raid, as bot movement is not sufficiently precise or dynamic to avoid the Charred Earth while still keeping Nightbane properly positioned. As a result, the tank will need to be healed through Charred Earth.
* Ultimately, Nightbane may be the most challenging boss in T4 content. At appropriate gear levels with IP nerfs, it is likely that three healers will be needed (even though two is likely sufficient for the rest of Karazhan).
### Magtheridon's Lair
*This raid is completable with IP module nerfs. Strategies were written/tested with (1) bot damage and healing each reduced to 50% of normal strength, and (2) HP of all raid mobs restored to Patch 2.4.3 levels (i.e., reverting the global 30% nerf to HP of TBC raid mobs from Patch 3.0.2).
**Magtheridon**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: The strategy is designed for a raid with three traditional tanks, but having that many is not critical.
* During phase one, the main tank (determined by setting the client-side main tank flag) will tank three of the Hellfire Channelers, and the second and third off tanks will each tank one Channeler, dragging them away from the raid out of Shadow Bot Volley range. DPS bots will prioritize Channelers by RTI marks (in order, Square, Star, Circle, Diamond, and Triangle).
* Also during phase one, Warlocks will be assigned to Banish the Burning Abyssals (and Fear any in excess of the number of Warlocks in the raid).
* After the first three Channelers are down, the main tank will wait in the center of the room to pick up Magtheridon while the remainder of the raid finishes the final two Channelers. When Magtheridon is released, the main tank will pull him to the Northern point of the room. DPS bots will wait a few seconds before attacking Magtheridon to prevent them from pulling aggro while the tank gets positioned.
* To handle the Manticron Cubes, one ranged DPS bot (excluding Warlocks) will be assigned to click each Cube. Warlocks are excluded for Cube assignments so they can keep residual Abyssals crowd controlled and focus their high DPS on the boss. However, the strategy will automatically reassign a Cube clicker if the previously assigned bot dies, and if there are not five living non-Warlock ranged DPS alive, then any living non-tank bot can be selected.
* Magtheridon will cast Blast Nova approximately every 55 seconds. About 6 seconds before the cast, each bot that is assigned to a Cube will move to their Cube and wait in position a short distance away. They will move in to use the Cube as soon as the Blast Nova cast begins. Once Blast Nova is interrupted, they will return to the fight and will repeat the cycle until the boss is down.
* Tips & Tricks:
* During the brief lull between the final Channeler dying and Magtheridon becoming released, bots will be idle and follow their player master. The player should make sure not to lead the bots in front of Magtheridon at this time, or the bots may be killed immediately when Magtheridon is released.
* It is helpful (though not required) for Warriors and/or Druids to tank the fourth and fifth Channelers because they will be able to keep the Channelers consistently interrupted (particularly their Dark Mending heals).
* You may want to have bots manually pause DPS before Magtheridon reaches 30% HP if his Blast Nova cast is imminent, and wait for the Blast Nova to be interrupted before taking him to 30% HP. Otherwise, the combination of the ceiling collapsing at 30%, followed by an immediate Blast Nova with the raid stunned, can cause a wipe.
### Gruul’s Lair
*This raid is completable with IP nerfs. Strategies were written/tested with (1) bot damage and healing each reduced to 50% of normal strength, and (2) HP of all raid mobs restored to Patch 2.4.3 levels (i.e., reverting the global 30% nerf to HP of TBC raid mobs from Patch 3.0.2).
**High King Maulgar**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: The strategy is designed for a raid with three traditional tanks, a Mage tank with 9000+ buffed max HP, and a Moonkin Druid tank (special gearing not necessary).
* The main tank (determined by setting the client-side main tank flag) will tank Maulgar. The other two traditional tanks will tank Olm and Blindeye. The Mage tank (which the strategy selects as the Mage bot in the raid with the highest max HP) will tank Krosh by Spellstealing Krosh’s Spell Shield. The Moonkin tank (Moonkin bot in the raid with the highest max HP) will tank Kiggler, but it is not truly necessary, and the fight can be completed with no Moonkin Druid in the raid.
* Ranged DPS will prioritize targets in the following order: Blindeye, Olm, Krosh, Kiggler, Maulgar
* Melee DPS will prioritize targets in the following order: Blindeye, Olm, Kiggler, Maulgar
* Tips & Tricks:
* Pull the boss head-on and send your traditional tanks in to start the encounter.
* All tanks (except the Moonkin tank) have designated spots in the room—be careful not to stand too close to Krosh.
* If playing with IP nerfs, the fight will likely be difficult without a Mage tank with sufficient HP not to get one-shot by Krosh. At pre-raid gear levels, achieving enough HP will likely require some intentional stacking of stamina gear and/or enchants.
**Gruul the Dragonkiller**
* Defeatable Solo with Bots: Yes, no manual control or command of bots needed.
* Coded Strategies: Two tanks are needed, a main tank and an offtank to absorb Hurtful Strike.
The main tank will attempt to keep Gruul in the center of the room, and ranged bots will spread in a circle around the center point.
Bots will attempt to spread out as much as possible after Ground Slam is used in advance of Shatter.
* Tips & Tricks: In appropriate gear levels, the bots are likely to start dying to Shatter before 10 stacks of Growth, as they do not spread as well as coordinated players. This should be plenty of time to kill Gruul with IP nerfs and pre-raid gear (not even pre-raid BiS needed), but if you are struggling to get the kill before then, you may need to farm more gear or better optimize the composition of your raid.
## Wrath of the Lich King
### Naxxramas
**Anub'Rekhan**
* Defeatable Solo with Bots: Yes, with coded strategies, with some manual control recommended.
* Coded Strategies: ??
* Tips & Tricks: For better ranged bot positioning use `/ra @ranged disperse set 20` to avoid [Impale](https://wowgaming.altervista.org/aowow/?spell=28783).
**Grand Widow Faerlina**
* Defeatable Solo with Bots: Yes, with no coded strategies or manual control needed.
* Coded Strategies: None
* Tips & Tricks: Focus all damage on boss using skull mark. Adds will die from aoe.
**Maexxna**
* Defeatable Solo with Bots: Yes, with with some manual control needed.
* Coded Strategies: None
* Tips & Tricks: To command bot to free from [Web Wrap](https://wowgaming.altervista.org/aowow/?spell=28622) use [targeting macro](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Macro-Collection#targeting-predefinied-creature). Use [bloodlust/heroism macro](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Macro-Collection#bloodlustheroism) to focus damage when boss reach 30% HP and use [Frenzy](https://wowgaming.altervista.org/aowow/?spell=28747)
**Patchwerk**
* Defeatable Solo with Bots: Yes, with with some manual control needed.
* Coded Strategies: None
* Tips & Tricks: Melee bots will be targeted by [Hateful Strike](https://wowgaming.altervista.org/aowow/?spell=41926) then take more tanks or ranged. Use [bloodlust/heroism macro](https://github.com/liyunfan1223/mod-playerbots/wiki/Playerbot-Macro-Collection#bloodlustheroism) to focus damage when boss reach 5% HP and use [Frenzy](https://wowgaming.altervista.org/aowow/?spell=28131)
### Vault of Archavon
To set proper faction which controls Wintergrasp use commands \
`.bf switch 1` \
`.bf timer 1 0h00m01s`
**Koralon the Flame Watcher**
* Defeatable Solo with Bots: Yes, with coded strategies, with some manual control recommended.
* Coded Strategies:
* auto apply fire resistance aura
* Tips & Tricks: For better ranged bot positioning use `/ra @ranged disperse set 6` to avoid [Flaming Cinder](https://wowgaming.altervista.org/aowow/?spell=66684).

1
wiki/d.md
View File

@@ -1 +0,0 @@