Playerbot Command Guide - Tarecgosa Realm

17 Aug 2026 #1

The following guide is for Tarecgosa realm and might be subject to change unnoticed.
Player reminder: Replace names and values shown in capital letters. Commands beginning with a period are server commands; bot instructions sent in chat do not use a period.

At a Glance

Goal	Command	Notes
Log in your character as a bot	`.bot add PLAYERNAME`	`.bot login` is an alias.
Log out a bot	`.bot remove PLAYERNAME`	`.bot logout` and `.bot rm` are aliases.
Request a tank	`.bot addrole tank`	Requests an available random bot.
Request a healer	`.bot addrole healer`	Requests an available random bot.
Request a damage dealer	`.bot addrole dps`	`damage` is also accepted.
Open the assist flow	`.bot assist`	Shows eligible characters.
Make a bot follow	`follow`	Send as normal chat.
Make a bot stay	`stay`	Send as normal chat.
Stop combat	`stop attack`	Clears the current target.
Recover the AI	`reset` or `recover`	Send to the affected bot.
See available actions	`help`	Depends on class and current state.

Quick Start

.bot add CharacterName

.playerbots is an equivalent command prefix. Once the bot is online and in your group, send instructions through party chat, raid chat, or a whisper.

follow

A whisper is the safest way to address one bot. Use a period only for server commands such as .bot add; conversational instructions do not use one.

Playerbot Management Commands

Login and Logout

Command	Purpose
`.bot add PLAYERNAME`	Log in a character as a bot.
`.bot login PLAYERNAME`	Alias for `add`.
`.bot remove PLAYERNAME`	Log out a bot.
`.bot logout PLAYERNAME`	Alias for `remove`.
`.bot rm PLAYERNAME`	Alias for `remove`.

Logging out removes the bot from the world but does not delete the character.

Multiple names may be separated with commas:

.bot add TankAlt,HealerAlt,RangedAlt
.bot remove TankAlt,HealerAlt

For a character target, * means all other members of your current group:

.bot remove *

Use this carefully: it can target non-bot group members too, although normal ownership checks still apply.

Add a Random Bot by Role

Command	Requested role
`.bot addrole tank`	Tank
`.bot addrole healer`	Healer
`.bot addrole dps`	Damage dealer
`.bot addrole damage`	Alias for `dps`

This requests an available random bot near your level and asks it to join as the selected role. It does not guarantee a specific class, specialization, item level, or exact behavior. The request can fail if the group is full or no suitable bot is available.

Assist Flow

Command	Purpose
`.bot assist`	Open the assist flow.
`.bot assist PLAYERNAME`	Use the default assist action for a character.
`.bot assist add PLAYERNAME`	Log in the selected character.
`.bot assist logout PLAYERNAME`	Log out the selected bot.

Normal checks apply: you cannot select your current character as its own bot, and an assisted character normally must be within two levels of the controlling character.

Trusted Account Linking

If the server supports trusted account control, use a private security key:

Command	Purpose
`.playerbots account setKey <securityKey>`	Set or replace your security key.
`.playerbots account link ACCOUNTNAME <securityKey>`	Link another account.
`.playerbots account linkedAccounts`	List your linked accounts.
`.playerbots account unlink ACCOUNTNAME`	Remove an account link.

These commands do not log a character in by themselves; use .bot add PLAYERNAME afterward. Never share the security key.

Chat Instructions

Send these as normal chat to an active bot:

Instruction	What it does
`follow`	Follow the controlling player and resume active behavior.
`stay`	Stop following and remain in place.
`flee`	Follow while using passive/fleeing behavior.
`runaway`	Run away from the current situation.
`stop attack`	Stop attacking, clear the target, and return to non-combat behavior.
`attack my target`	Attack the leader's selected target.
`tank attack`	Ask a tank bot to begin tank behavior.
`max dps`	Prioritize maximum damage output.
`save mana`	Prefer conserving mana.
`summon`	Attempt to come to the leader's location when legal.
`eat` / `drink`	Manually consume food or drink. Not available during combat and requires a suitable item.
`reset` / `reset ai` / `recover`	Rebuild or recover the bot's AI state.
`help`	Show actions available to the bot's current AI context.
`who` / `position` / `tell target`	Request information when supported.
`spell` / `talents`	Request spell or talent information when supported.

Movement can fail when the bot is too far away, on another map, dead, teleporting, or otherwise unable to reach the leader. Role-specific commands only work when the bot has the required role.

Direct One-Time Actions

Prefix a one-time action with do or d:

do heal
d buff
do summon
do attack my target
do equip upgrades
do accept all quests

Response	Meaning
`done`	Executed successfully.
`impossible`	Known, but prerequisites are not met.
`useless`	No useful effect in the current situation.
`failed`	Attempted but did not complete.
`unknown action`	Unavailable to this bot.

The full action vocabulary varies by class, specialization, state, and source version. Use help first.

Common Workflows

Leveling with Alts

.bot add TankAlt,HealerAlt
follow

Lead the route and let normal combat, quest, loot, and recovery behavior operate. Use stay when a bot must hold position.

Replacing a Missing Role

.bot addrole healer

Wait for the confirmation that a random healer was requested. If none is available, try again later or use an eligible character from your own account.

Recovering a Stuck Bot

Use stop attack if it is fighting.
Whisper reset or recover.
Move close and use follow or summon.
If needed, log out and back in:

.bot remove PLAYERNAME
.bot add PLAYERNAME

Permission and Troubleshooting

Message	Meaning and next step
Playerbot system is currently disabled	The server is not accepting management commands; contact the administrator.
Character not found	Check spelling and account ownership.
Player is offline	The selected character is not currently online as a bot.
Player already logged in	Wait for the current login to finish or use the logout command.
Not in your account or linked accounts	Use your own character or complete supported account linking.
Impossible / useless / failed	The command was understood, but its current prerequisites were not satisfied.

Permission Rules

You can control eligible characters on your own account.
A character controlled by another player cannot be taken over by naming it.
Trusted-account control requires a valid account link.
Random bots may be restricted by group, guild, level, role, or ownership state.
Management commands can fail while the character is offline.
Combat, distance, map, missing items, missing spells, group state, and role can make an understood command impossible.

Quick Reference

.bot add PLAYERNAME
.bot login PLAYERNAME
.bot remove PLAYERNAME
.bot logout PLAYERNAME
.bot rm PLAYERNAME
.bot addrole tank|healer|dps|damage
.bot assist
.bot assist PLAYERNAME
.bot assist add PLAYERNAME
.bot assist logout PLAYERNAME
.playerbots account setKey <securityKey>
.playerbots account link ACCOUNTNAME <securityKey>
.playerbots account linkedAccounts
.playerbots account unlink ACCOUNTNAME

follow
stay
flee
runaway
stop attack
attack my target
tank attack
max dps
save mana
summon
eat
drink
reset
recover
do <action>
d <action>
rtsc
rtsc enable

Enjoy your playerbot group!