Content generated with AI — it may contain mistakes.

ExyliaPracticeBot/ReferenceUpdated in v1.5.0

Commands

Every ExyliaPracticeBot command: /bot for players, /botadmin for staff, and what each refusal says.

Page 11 of 215 min read

There are two roots. /bot is for players: typed on its own it opens the main menu, and its subcommands act on your own bot. /botadmin is for staff and holds everything that needs exyliapracticebot.admin. There are no other aliases.

Every player subcommand but remove needs exyliapracticebot.use, and the ones that spawn or teleport also check their own feature node. Removing your bot never needs a node. See Permissions.

Player commands#

Everything here has to be typed by a player: each one works on the bot that belongs to whoever typed it, so the console has nothing to act on.

CommandWhat it doesPermission
/botOpen the main menu.exyliapracticebot.use
/bot spawnSpawn your bot where you stand. Also needs exyliapracticebot.spawn.exyliapracticebot.use
/bot removeRemove your bot. Never needs a permission.—
/bot tpmeBring the bot to you. Also needs exyliapracticebot.teleport.exyliapracticebot.use
/bot tptoGo to the bot. Only works while the bot is in sight, in your world. Also needs exyliapracticebot.teleport.exyliapracticebot.use
/bot resetPut all your bot settings back to the server defaults.exyliapracticebot.use

/bot spawn uses your saved settings and puts the bot one block above where you are standing.

/bot reset also updates a bot that is already out: the new settings are pushed to it rather than waiting for the next spawn. The reset row is saved to the database straight away.

/bot tpme and /bot tpto are asynchronous teleports — the confirmation arrives once the teleport has actually happened, not when the command is typed. /bot tpto only goes to a bot you can see, in your own world: the bot pearls and walks where a player cannot, and following it blind would carry you through walls into closed areas.

Spawning and removing wait two seconds between uses, and the teleports one second; a use inside that window is ignored without a message.

The menu does the same things

spawn, remove, tpme, tpto and reset all have a button on the main menu, wired to the same code; the menu's reset button asks for confirmation first, /bot reset does not. The commands exist so none of it depends on a menu file staying as it shipped. See Menus.

What each refusal says#

The lines below are the defaults from messages.yml; every one of them is editable, and each ships with a sound and, in one case, a particle. The key is what matters — the text is yours.

RefusedKeyDefault line
Spawning in a world that is not in worldsbot.world-not-allowedYou can't spawn a bot in this world. Please use /rtp first
Spawning when you already have onebot.already-has-botYou already have a bot. Use /bot remove first.
Spawning when the server is at its bot ceilingbot.limit-reachedThe server is already running %limit% bots. Try again in a moment.
remove, tpme or tpto with no bot outbot.no-botYou don't have an active bot.
tpto with the bot out of sight or in another worldbot.bot-out-of-sightYour bot must be in sight to teleport to it.
Spawning or teleporting without the feature nodebot.no-permissionYou don't have permission to do that.

%limit% is the ceiling that refused the spawn — for a player, max-bots minus reserved-for-matches — not a count of who is using them. See Limits.

A successful spawn answers with bot.spawned, a removal with bot.removed, the two teleports with bot.teleported-bot-to-you and bot.teleported-to-bot, and a reset with bot.settings-reset.

Admin commands#

Everything here needs exyliapracticebot.admin and runs from the console as well as in game, except /botadmin settings, which opens a menu and so needs a player. reload, export and import still answer to their old spelling, /bot reload, /bot export and /bot import, so existing scripts keep working; settings exists only under /botadmin.

CommandWhat it doesPermission
/botadmin reloadReload config.yml, messages.yml and the menus.exyliapracticebot.admin
/botadmin settingsOpen the in-game settings hub. Players only.exyliapracticebot.admin
/botadmin exportWrite the plugin's database to a dump file in the dumps folder.exyliapracticebot.admin
/botadmin import <filename>Read a dump from the dumps folder back in. Refuses to write over tables that already have rows.exyliapracticebot.admin

Reload#

Two named steps. configs re-reads config.yml and messages.yml and re-applies the message prefix; menus compiles every menu file again. The menus step also runs on its own when ExyliaLib itself is reloaded, so a menu edit picked up by an ExyliaLib reload does not need a second command here.

Reload does not touch player data — that lives in the database and is already what the plugin holds in memory — and it does not remove bots that are out. A bot keeps running with the settings it was given.

Settings#

/botadmin settings opens a hub with three cards: Defaults (the starting mode, difficulty and language), Spawning (the bot cap, the match reserve and respawn) and Fighting (the combat values). Each card opens a page of hand-written settings that say what the value does, show the current value and its default, and edit it on click. Only the settings an admin tunes while running the server are there; everything else stays in config.yml, the same file you edit by hand, so either way works. See Configuration.

Wiping player data#

There is no wipe or reset command here. The plugin's one table, practicebot_players, is classified for ExyliaLib as account data, so /exylialib wipe ExyliaPracticeBotV3 <table|*> [code] empties it and /exylialib resetplayer <player> [plugin|all] [@kind ...] [code] clears one player's saved bot settings. Both ask for a typed code before anything is deleted. See the ExyliaLib commands. A player resetting only their own settings uses /bot reset.

Export and import#

Both go through ExyliaLib's transfer module, both run on a background thread, and both answer with a report line when they finish: green when the transfer succeeded, red when it did not, and the line itself names the outcome, how many tables, how many rows and how long it took.

export writes into dumps/ inside the plugin's own data folder, creating it if it is not there. The file is named for the plugin, the database engine and the moment it was taken — ExyliaPracticeBotV3-<engine>-<yyyyMMdd-HHmmss>.exyliadump.gz — so two exports never overwrite each other.

import takes exactly one argument: the name of a file inside that same dumps/ folder, extension included, as export wrote it.

/botadmin export
/botadmin import ExyliaPracticeBotV3-h2-20260906-141355.exyliadump.gz

It is a name, not a path you choose: whatever you type is resolved under dumps/, so a dump copied from another server has to be dropped in there first. Being a single argument, it also cannot contain spaces — which the generated names never do.

Import refuses to write over rows that already exist

The import runs without the transfer module's force flag. If the table it is importing into already holds rows, nothing is written and the report says which table and how many rows stopped it. That is the safe half of the module on purpose: use it to move a database, not to merge two.

Something missing on this page? Tell us on Discord