Parties & Mashup Mode

MiniModes is built around parties. Almost everything runs “for a party”, not for a single player.
This guide shows you:

How parties work
All core /party commands
How to use Mashup mode for endless random games
Tips for admins & server owners

1. Party basics

A party is a group of players who play games together.
MiniModes always assumes you’re in some party:

If you’re not in a party, MiniModes creates a solo party for you automatically.
Games, Mashup, rematches, and most flows are based on your current party.

Each party has:

A unique ID
A leader (one player)
A set of members (leader + invited players)

Only the leader can:

Invite / kick players
Start games from /minimodes
Start or stop Mashup mode
Trigger some game-related commands (e.g. win/stop in many setups)

If the leader leaves, the party is disbanded and related state is cleaned up (rematches, Mashup sessions, some GUIs, etc.).

2. Core party commands

All party commands are under /party. Exact permissions may vary per server.

Basic lifecycle

/party create
Create a fresh party where you are the leader.
Often you won’t need this, because MiniModes creates a solo party for you when needed.
/party leave
Leave your current party.
- If you are the leader, this disbands the party.
- If you are a member, you simply leave and everyone else stays.
/party list
Show who is in your party and who the leader is.

Inviting and managing players

/party invite <player>
Invite another player to your party.
Only the party leader can invite.
/party accept <player>
Accept an invite from <player>.
Usually <player> is the party leader who invited you.
/party kick <player>
Remove a member from your party.
Only the party leader can kick.

A few notes:

Invites are usually time-limited (depending on your server’s configuration).
Invited players join your party; they leave any other party they were in.

3. Starting games as a party

Once your party is set up:

Leader opens the game menu:
- /minimodes or /mm
The MiniModes – Select a Game GUI opens, listing all games from loaded extensions.
Each game shows:
- Name and description
- Min/max players
- Whether your current party is allowed to start it (size checks, leader checks, etc.).
The leader clicks a game:
- If party size is valid and no one’s busy in another game, pre-game flows start:
  - Optional team selection GUI
  - Optional settings voting GUI
- If something is wrong (too few/many players, not leader, etc.), the GUI clearly tells you why.

These are usually available via /mm game ...:

/mm game leave
Leave your current game instance.
/mm game spectate <player>
Teleport into someone else’s game to watch.
/mm game stop
End the game early. Typically leader-only.
/mm game win <players...>
Mark specific players as winners and end the game. Typically leader-only.
/mm game settings
Open the runtime settings GUI if the game supports in-game settings.

4. Rematch: play “one more round”

MiniModes can remember previous game setups (players, teams, settings) for fast rematches.

/party rematch
Ask MiniModes to re-run the last game for your current party, when possible.

Behavior depends on the game and server configuration, but usually:

Works best when the same party still exists.
Tries to reuse:
- The same game mode
- Similar player list (same members still online & in party)
- Previous settings / teams if appropriate

If rematch is not possible (party changed too much, game no longer available, etc.), you’ll get a clear message.

5. Mashup mode: endless random games

Mashup mode turns your party into a continuous playlist of games.
Think: “Just keep us playing something fun” with zero micromanagement.

Commands

/party mashup start
Turn Mashup on for your party. Only the leader can do this.
/party mashup stop
Stop Mashup for your party.

Once Mashup is running, MiniModes will:

Automatically pick games at random from all loaded extensions
Only choose games that:
- Are marked as Mashup-compatible
- Support your current party size (within min/max players)
Avoid running the exact same game twice in a row when possible
For games with settings:
- Automatically randomize settings
- Skip pre-game voting UIs, so rounds start quickly

It also:

Gives your party a short fall-damage protection window at the start of each round for smoother spawns.
Keeps trying to start new rounds whenever:
- Your party has at least one online member
- Nobody in the party is currently in a game

When Mashup stops automatically

Mashup will auto-stop if:

The party disbands (for example, the leader leaves)
The plugin/server is shutting down
Your server’s configuration or a specific game aborts it due to errors

You can always stop it manually with:

/party mashup stop

6. Typical player flows

A. Playing a single game together

Player A: /party create (optional if solo-party already exists)
Player A: /party invite B, /party invite C
Players B and C: /party accept A
Player A (leader): /minimodes
Leader chooses a game:
- Team selection GUI (if team-based)
- Settings voting GUI (if the game supports voting)
Game starts and your party plays together.
Optional: /party rematch for another round with a similar setup.

B. “We just want to play random games”

Player A creates/invites just like above.
Once everyone is in the party:
```
/party mashup start
```
MiniModes:
- Automatically picks a compatible game
- Randomizes settings
- Starts one round after another
When you’re done:
```
/party mashup stop
```

7. Tips for server owners & admins

Permissions

Depending on your permission plugin, you might want to:

Allow everyone:
- /party create
- /party invite
- /party accept
- /party leave
- /party list
- /party mashup start
- /party mashup stop
- /minimodes / /mm
- Basic /mm game commands
Restrict admin/force helpers (if present in your setup):
- Force-joining parties
- Force-starting or stopping games
- Bypassing player count checks

Check your MiniModes command/permission reference (often in plugin.yml or the reference section of this site) and wire them into your permission system.

Player size tuning

Mashup and standard games both respect min/max players per game:

If your server is usually low-population:
- Prefer games with low minimum player counts.
- Disable or not load games that demand many players.
If you run a big network:
- Keep a mix of small and large games.
- Mashup will choose only compatible games for the current party size.

Communication and UX

Consider:

Adding help lines to your MOTD or /help:
- “Use /party to play with friends.”
- “Try /party mashup start for endless random games.”
Creating a short tutorial area explaining:
- Party creation
- Game selection
- Mashup

8. Troubleshooting

Likely causes:

You’re not the party leader.
Solution: Ask your leader to start the game, or have them leave so you become leader of a new party.
Your party size is outside the game’s limits.
Solution: Either:
- Invite more friends, or
- Ask someone to leave, or
- Pick a different game that supports your size.

“Mashup keeps failing to start games”

Check:

At least one Mashup-compatible game is loaded.
The current party size fits at least one game’s min/max players.
No one in the party is stuck in another game or world.

Server owners should also look at the console logs for any exceptions from game extensions.

9. Summary

Everyone is always in a party; MiniModes creates solo parties automatically.
Parties define who plays together and who controls starting/stopping games.
/party commands let you invite, list, leave, kick, rematch, and run Mashup.
Mashup mode is a hands-off playlist of random compatible games, perfect for casual sessions.
Server owners should tune permissions and game lists so parties and Mashup fit their community.

Use parties as your main way of grouping players, and let Mashup handle the rest when you just want the server to “keep the fun coming”.