commands.yml

Overview

commands.yml controls whether most of Youer's built-in commands are registered to the server. Note that worlds.enable also controls initialization of the world management module (not just command registration).

bash

How It Works

On first startup, if commands.yml does not exist, Youer creates it automatically.
Every config entry is a boolean (true / false):
true → register and enable the corresponding command
false → do not register the command (unusable in-game)
If an entry is missing, Youer auto-fills it as false and saves. So to enable a command, you must manually change its value to true.
Command registration happens at server startup; after changing the config, you must restart the server for it to take effect.

Config Entries

`worlds.enable`

yaml

Default	Description
`false`	Enable the world management module and the `/worlds` command

This config controls two behaviors at once: initialization of the world management module (WorldManage) and registration of the /worlds command. Setting it to false disables both.

Related world-management configs are in WorldManage.md and WorldsConfig.md.

`warps.enable`

yaml

Default	Description
`false`	Enable the warp management command `/warps`

/warps supports subcommands: set (create a warp), del (delete), tp (teleport), gui (open the GUI).

`tpa.enable`

yaml

Default	Description
`false`	Enable teleport-request commands

When enabled, three commands are registered:

Command	Description
`/tpa <player>`	Send a teleport request to a player
`/tpaccept`	Accept an incoming teleport request
`/tpadeny`	Deny an incoming teleport request

`back.enable`

yaml

Default	Description
`false`	Enable the `/back` command (return to the position before the last teleport / death)

`menus.enable`

yaml

Default	Description
`false`	Enable the menu command `/menus [open] [name]`

`hideall.enable`

yaml

Default	Description
`false`	Enable `/hideall` (hide/show all players, bidirectional)

`hide.enable`

yaml

Default	Description
`false`	Enable `/hide` (hide/show other players, only for yourself)

`hat.enable`

yaml

Default	Description
`false`	Enable `/hat` (wear the held item on your head)

`vanish.enable`

yaml

Default	Description
`false`	Enable `/vanish` (vanish mode)

`openinv.enable`

yaml

Default	Description
`false`	Enable `/openinv` (open another player's inventory)

`entitylimits.enable`

yaml

Default	Description
`false`	Enable `/entitylimits` (entity-count limit management)

The actual entity-limit rules live in a separate youer-config/entitylimits.yml; this config only controls whether the command is usable.

`deepseek.enable`

yaml

Default	Description
`false`	Enable `/deepseek` (chat with the AI)

Note: this config only controls registration of the /deepseek command. The AI feature itself (API address, key, model, persona, etc.) is controlled by the deepseek section in youer-config/youer.yml. See YouerConfig.md.

Always-Enabled Commands

The following commands are not controlled by commands.yml and are always registered:

Command	Description
`/lightfix [world\|corrupt]`	Light repair (fix corrupted chunk lighting data)
`/pregen <start\|status\|pause\|resume\|stop\|cancel>`	Chunk pregeneration (verify whether chunk/world-optimization mods overstate their claims)
`/plugin [load\|reload\|unload] <plugin>`	Plugin hot-management (load/reload/unload)
`/logfilter [list\|reload\|on\|off]`	Console log-filter rule management
`/enchantlimit [add\|list\|remove]`	Enchantment max-level limit
`/entitydamage [add\|list\|remove]`	Entity final-damage reduction

Full Config Example

yaml

FAQ

Q: I set warps.enable to true, but after restarting I still can't use /warps in-game?

A: Make sure the indentation is correct. The proper format is:

yaml

not warps.enable written at the top level. Also confirm it's youer-config/commands.yml (not youer-config/youer.yml).

Q: What happens if a command's config entry is missing?

A: At startup Youer auto-fills it as false and saves, so the command will not be registered.

Q: Why aren't /lightfix and /pregen in the config file?

A: These two are persistent commands, always registered, and cannot be disabled via this file.

Related configs: for the plugin's main config see YouerConfig.md; for world-management config see WorldsConfig.md and WorldManage.md.