Commands Reference

Commands Reference

This page documents the core commands exposed by MiniModes for players and server admins.

Note:
Command labels and permissions are written as defaults. You can change most of them using your permission plugin.

---

/minimodes and /mm

Main entry point into MiniModes for players.

Aliases

• /minimodes
• /mm

Summary

• Open the game selection menu
• List loaded games
• View basic stats
• (Optionally) reload configuration and extensions

Subcommands

/minimodes

• Use: Player menu entry point.
• Permission: minimodes.player.menu (suggested)
• Description: Opens the “MiniModes – Select a Game” GUI.

What players see:

• All loaded game types from extensions
• Icon, name, short description
• Minimum/maximum players
• Whether their current party can start the game:
  • Too few/many players
  • Not leader
  • Already in a game

Clicking a game:

• If the player is a party leader and requirements are met:
  • Starts the pre-game flow: teams → settings voting → actual game.
• Otherwise:
  • The GUI shows why they can’t start that game.

---

/minimodes list

• Permission: minimodes.admin.list
• Description: Prints all registered game types to chat / console.

Typical output includes:

• Game ID
• Display name
• Min/max players
• Whether it is Mashup-compatible
• Whether it is currently enabled

Use this to verify that extensions loaded correctly.

---

/minimodes stats

• Permission: minimodes.admin.stats
• Description: Shows a quick overview of MiniModes state.

Examples of reported data:

• Number of active games
• Number of parties
• Games per extension / category (implementation dependent)

Useful for quick debugging and monitoring.

---

/minimodes reload (if exposed)

The exact behavior depends on your configuration and implementation.
Only expose this command to trusted admins.

• Permission: minimodes.admin.reload
• Description: Reloads MiniModes config and re-scans extensions.

Common effects:

• Reloads configuration files from disk.
• Optionally attempts to unload and reload extension metadata.
• May not fully restart in-progress games; use with caution on production servers.

---

/party

MiniModes’ integrated party system.

Most player-facing behavior revolves around parties, not individuals:

• Every player is always in some party.
• If you’re not explicitly in a party, MiniModes gives you a solo party transparently.
• Only the party leader can start games, control Mashup mode, and manage membership.

Aliases

• /party

General Behavior

• A party has:
  • A unique ID
  • A leader
  • A set of members (including leader)
• When the leader leaves the party (or disconnects in some conditions), the party disbands:
  • Active rematch/mashup state is cleared.
  • Relevant GUIs are closed.

---

/party create

• Permission: minimodes.party.create
• Description: Explicitly creates a new party and makes you the leader.

Usage notes:

• Often not strictly necessary because MiniModes creates a solo party automatically.
• Useful when you want to clearly indicate “I’m forming a new group now”.

---

/party invite <player>

• Permission: minimodes.party.invite
• Restrictions: Party leader only.
• Description: Invite another player to your party.

Parameters:

• <player> – Online player name or selector (depending on your server setup).

Behavior:

• Sends an invitation message to the target player.
• Invitation is time-limited (implementation-dependent).
• When accepted, the player joins your party and your existing game context (for subsequent games).

---

/party accept <player>

• Permission: minimodes.party.accept
• Description: Accept an invitation from another player’s party.

Parameters:

• <player> – The leader (or inviter) whose party you’re joining.

Behavior:

• Joins the party if the invite is still valid.
• If you were already in a different party:
  • MiniModes either merges or first leaves your old party, depending on configuration.

---

/party leave

• Permission: minimodes.party.leave
• Description: Leave your current party.

Behavior:

• If you are not the leader:
  • You are removed from the party.
  • Your association with any in-progress game is updated accordingly.
• If you are the leader:
  • The party disbands.
  • Rematch and mashup state is cleaned up.
  • Active pre-game GUIs associated with that party may be closed.

---

/party kick <player>

• Permission: minimodes.party.kick
• Restrictions: Party leader only.
• Description: Remove a member from your party.

Parameters:

• <player> – A current party member.

Behavior:

• The player is removed from the party.
• Subsequent games you start will no longer include them.
• If they are in a MiniModes game with you, the behavior is implementation-dependent:
  • They may be removed from that game.
  • They may remain for the round but not be part of the party afterwards.

---

/party list

• Permission: minimodes.party.list
• Description: Show information about your current party.

Typical output:

• Party ID (debugging/administration)
• Leader (highlighted)
• Member list with online/offline status
• Current Mashup mode status (if applicable)
• Last/next game info (implementation-dependent)

---

/party rematch

• Permission: minimodes.party.rematch
• Restrictions: Party leader only.
• Description: Starts a new game with the same setup as your last one, if possible.

Rematch tries to reuse:

• Same game type
• Same players/teams (subject to who is still online)
• Same voted settings and options, when compatible

If rematch isn’t possible (e.g., game type removed, map missing), MiniModes will:

• Provide a clear error message
• Ask the leader to pick a new game from /minimodes

---

/party mashup <start|stop>

Controls MiniModes’ Mashup mode, a continuous playlist of random games.

• Permission: minimodes.party.mashup
• Restrictions: Party leader only.

/party mashup start

• Description: Start Mashup mode for your party.

Behavior:

• Picks compatible games at random from all loaded extensions.
• Only chooses games that:
  • Are marked as Mashup-compatible
  • Support your party size
• Avoids repeating the same game type back-to-back when possible.
• For games with settings:
  • Automatically randomizes or chooses valid defaults (no voting step).
• Automatically starts new rounds when:
  • Your party has online members and
  • Nobody in the party is currently in a MiniModes game.

/party mashup stop

• Description: Stop Mashup mode for your party.

Behavior:

• Stops the automatic playlist.
• Existing game may continue or stop depending on your settings and implementation.
• Mashup also stops automatically if the party disbands.

---

Admin / Force Helpers (if enabled)

Your plugin configuration may define extra subcommands for staff:

Examples (names/availability may vary):

• /party forcejoin <player> <leader>
  Force-move a player into another player’s party.

• /party forceremove <player>
  Force-remove a player from their current party.

Recommended permissions for such commands:

• minimodes.party.admin
• minimodes.party.force

---

/mm game ... (/mmgame)

Game-level control once a player is in a MiniModes game.

Aliases

• /mm game
• /mmgame (if mapped)
• Additional per-game aliases may exist, but MiniModes control is always via /mm game.

All subcommands respect party and game leadership.
In team games, the game leader is typically the party leader that started the match.

---

/mm game leave

• Permission: minimodes.game.leave
• Description: Leave your current game.

Behavior:

• Removes you from the current MiniModes game instance.
• Teleports you back to the configured lobby / fallback location.
• If everyone leaves:
  • The game is shut down by the GameManager.
• In party contexts:
  • The party remains; only your membership in the game ends.

---

/mm game spectate <player>

• Permission: minimodes.game.spectate
• Description: Teleport to another player’s active MiniModes game as a spectator, if allowed.

Parameters:

• <player> – Target player to spectate.

Behavior:

• If the target is in a MiniModes game:
  • Teleports you into that game in spectator mode (respecting per-game rules).
• If the target is not in a game, or the game disallows spectators:
  • MiniModes shows a clear error message.

---

/mm game stop

• Permission: minimodes.game.stop
• Restrictions: Game leader only (usually the party leader who started the game).
• Description: Force-end the current game.

Behavior:

• Immediately stops the game instance.
• Triggers any end-of-game cleanup: scoreboards, worlds, temporary state.
• Returns players to the configured lobby / fallback.

Use cases:

• A game is stuck or bugged.
• The leader wants to switch games without waiting for the round to finish.

---

/mm game win <players...>

• Permission: minimodes.game.win
• Restrictions: Game leader only.
• Description: Mark specific players as winners and end the game.

Parameters:

• <players...> – One or more player names.

Behavior:

• Flags the provided players as winners.
• Triggers the normal end-of-game flow:
  • Results broadcast
  • Statistics / achievements (if implemented by the game extension)
  • Teleport back to lobby

If no players are provided or they are invalid, MiniModes shows a clear error.

---

/mm game settings

Availability depends on whether the current game supports runtime settings.

• Permission: minimodes.game.settings.view for viewing
  minimodes.game.settings.edit for changing (leader only)
• Description: Open the Runtime Settings GUI for the current game.

Behavior:

• Shows a list of all runtime-exposed settings for that game:
  • Names and categories
  • Current values
  • Whether they’re changeable mid-game
• Everyone can view settings.
• Only the game/party leader can:
  • Change values
  • Use left/right clicks to cycle options
  • Shift-click to reset to defaults
• Changes are:
  • Reflected for all viewers in real time
  • Applied to the running game immediately, if allowed

---

Suggested Permission Layout

You can adapt these to your permission plugin (LuckPerms, etc.).

Player role

• minimodes.player.menu
• minimodes.party.create
• minimodes.party.invite
• minimodes.party.accept
• minimodes.party.leave
• minimodes.party.kick
• minimodes.party.list
• minimodes.party.rematch
• minimodes.party.mashup
• minimodes.game.leave
• minimodes.game.spectate
• minimodes.game.settings.view

Party leader enhancements

• minimodes.game.stop
• minimodes.game.win
• minimodes.game.settings.edit

Staff / admin

• minimodes.admin.list
• minimodes.admin.stats
• minimodes.admin.reload
• minimodes.party.admin
• minimodes.party.force

---

Command Flow Cheat Sheet

From a player’s perspective:

1. /party invite <friend>
   Your friend runs /party accept <you>.

2. As leader, /minimodes

   • Pick a game that matches your party size.

3. MiniModes runs:

   • Team selection GUI (if team-based)
   • Settings voting GUI (if the game supports it)

4. During game:

   • /mm game leave to exit the match
   • /mm game spectate <player> to watch friends
   • Leader can use /mm game settings if runtime settings exist

5. After game:

   • /party rematch to play the same setup again
   • /party mashup start for an endless randomized playlist

This command reference should give both players and admins a clear map of how to drive MiniModes from in-game chat.