Myths and Legends Commands

This page documents the commands provided by the Myths and Legends mod. All commands start with the base command `/mythsandlegends` or its alias `/mal`.

Access to these commands is generally restricted by Permissions. Most commands require at least the base access permission (`mythsandlegends.command.base`). Specific subcommands often require additional, more specific permissions.

/mythsandlegends <subcommand> [arguments...]

or

/mal <subcommand> [arguments...]

Many commands allow specifying an optional `[player]` argument to target another player. If omitted, the command typically targets the player executing the command.

Lists the tracked key items held by a player according to the mod's data.

/mal items [player]

• [player]: (Optional) The name of the player whose items should be listed. Defaults to the command executor.

• `mythsandlegends.command.items`

Retrieves the list of key items (like those defined in items) that the mod has registered for the target player. This relies on the mod's internal tracking, which is updated via `syncitems`.

Synchronizes the player's inventory with the mod's tracked key item data.

/mal syncitems [player]

• [player]: (Optional) The name of the player whose inventory should be synchronized. Defaults to the command executor.

• `mythsandlegends.command.syncitems`

Scans the target player's inventory for items defined as key items by the mod and updates the mod's internal list of which key items the player possesses. This should be run if items were added or removed through means other than standard gameplay interactions tracked by the mod.

Lists the Pokémon currently in a player's party.

/mal party [player]

• [player]: (Optional) The name of the player whose party should be listed. Defaults to the command executor.

• `mythsandlegends.command.party`

Displays the species and nicknames of the Pokémon in the target player's Cobblemon party.

Checks if a player has a specific Pokémon species in their party.

/mal haspokemon <pokemon_species> [player]

• <pokemon_species>: (Required) The name of the Pokémon species to check for (e.g., `pikachu`, `mewtwo`). Must be a valid species name.
• [player]: (Optional) The name of the player whose party should be checked. Defaults to the command executor.

• `mythsandlegends.command.haspokemon`

Checks the target player's current Cobblemon party for the presence of the specified Pokémon species and reports whether it was found.

Places a block at a specific location *only if* a target player has a specific Pokémon in their party.

/mal placeifhas <pokemon_species> <pos> <block> [player]

• <pokemon_species>: (Required) The name of the Pokémon species required in the player's party.
• <pos>: (Required) The block coordinates (X Y Z) where the block should be placed.
• <block>: (Required) The block state to place (e.g., `minecraft:stone`, `minecraft:redstone_block[powered=true]`).
• [player]: (Optional) The name of the player whose party is checked. Defaults to the command executor.

• `mythsandlegends.command.placeifhas`

This command first checks if the target player has the specified `<pokemon_species>` in their party. If they do, the command attempts to place the specified `<block>` at the given `<pos>`. If the player does not have the Pokémon or the block placement fails, an error message is shown.

Opens the Myths and Legends configuration GUI for the player executing the command.

/mal settings

• None

• `mythsandlegends.command.base` (or potentially a specific settings permission)

Opens a graphical user interface allowing the player to view and potentially modify mod configuration settings, provided they have the necessary permissions. This requires the mod to be installed on the client.

Manages item usage cooldowns and voucher counts.

Checks the current cooldown and voucher status for a specific item for a player.

/mal cooldown check <item> [player]

• <item>: (Required) The identifier of the key item to check (e.g., `mythsandlegends:azure_flute`).
• [player]: (Optional) The name of the player whose cooldown status should be checked. Defaults to the command executor.

• `mythsandlegends.command.cooldown.check`

Displays how many times the target player has used the specified item (voucher count), the maximum allowed uses (based on config), the remaining cooldown time before the next use is allowed, and whether the player can currently use the item (considering both vouchers and cooldown). Also indicates if global cooldowns/vouchers are affecting the status.

Clears the cooldown and usage history for a *specific* item for a player.

/mal cooldown clear <item> [player]

• <item>: (Required) The identifier of the key item whose cooldown should be cleared.
• [player]: (Optional) The name of the player whose cooldown should be cleared. Defaults to the command executor.

• `mythsandlegends.command.cooldown.clear`

Resets the usage timestamps and effectively the voucher count and cooldown for only the specified `<item>` for the target player.

Clears *all* item cooldowns and usage history for a player.

/mal cooldown clearall [player]

• [player]: (Optional) The name of the player whose cooldowns should be cleared. Defaults to the command executor.

• `mythsandlegends.command.cooldown.clearall`

Resets all usage timestamps for all tracked key items for the target player, effectively resetting all their cooldowns and voucher counts.

Attempts to trigger a Pokémon spawn associated with a specific key item.

/mal forcespawn <keyitem> [player] [consumeVoucher] [ignoreCooldown]

• <keyitem>: (Required) The identifier of the key item used to trigger the spawn (e.g., `mythsandlegends:mystic_ticket`).
• [player]: (Optional) The name of the player for whom the spawn should be triggered. Defaults to the command executor.
• [consumeVoucher]: (Optional Boolean) If `true`, attempts to consume a voucher/use count for the item. Defaults to `false`.
• [ignoreCooldown]: (Optional Boolean) If `true`, ignores any existing cooldown for the item. Defaults to `false`.

• `mythsandlegends.command.forcespawn`

Initiates the force spawning logic tied to the specified `<keyitem>` for the target player. This typically involves checking player location, cooldowns, and voucher counts unless overridden by the optional arguments. Success depends on configured spawning conditions and whether the checks pass. The optional arguments allow administrators to bypass normal usage restrictions.

Commands provide feedback messages for success and failure. Common error types include:

• Player not found.
• Command requires a player executor (cannot be run from console without specifying a player).
• Invalid Pokémon species name provided.
• Invalid or untracked key item identifier provided.
• Failure to place a block.
• Cooldown active or insufficient vouchers for `forcespawn`.
• Conditions for `forcespawn` (e.g., location) not met.

These messages use translatable keys for localization.

The following text keys are used by the commands in this class for user feedback and errors:

• `commands.mythsandlegends.error.requires_player`
• `commands.mythsandlegends.error.player_not_found`
• `commands.mythsandlegends.error.invalid_species`
• `commands.mythsandlegends.error.invalid_key_item`
• `commands.mythsandlegends.error.invalid_cooldown_item`
• `commands.mythsandlegends.error.item_not_tracked`
• `commands.mythsandlegends.items.none`
• `commands.mythsandlegends.items.success`
• `commands.mythsandlegends.syncitems.success`
• `commands.mythsandlegends.party.none`
• `commands.mythsandlegends.party.success`
• `commands.mythsandlegends.haspokemon.yes`
• `commands.mythsandlegends.haspokemon.no`
• `commands.mythsandlegends.placeifhas.failure_condition`
• `commands.mythsandlegends.placeifhas.failure_setblock`
• `commands.mythsandlegends.placeifhas.success`
• `commands.mythsandlegends.forcespawn.success`
• `commands.mythsandlegends.forcespawn.success_no_spawn`
• `commands.mythsandlegends.settings.success`
• `commands.mythsandlegends.cooldown.check.global_note`
• `commands.mythsandlegends.cooldown.check.global_vouchers`
• `commands.mythsandlegends.cooldown.check.status`
• `commands.mythsandlegends.cooldown.check.can_use`
• `commands.mythsandlegends.cooldown.check.cannot_use`
• `commands.mythsandlegends.cooldown.clear.success`
• `commands.mythsandlegends.cooldown.clearall.success`