Skip to main content

MGE Event Management

MGE (Mightiest Governor Event) events are the competitive core of AoEM Historian. This guide covers how to manage the slot allocation process.

MGE Command​

/mge <subcommand>

Available subcommands:

  • activate - Start a new MGE event
  • configure-activated - Configure settings on the active MGE (open applications, minimum credits)
  • confirm - Preview and finalize event (deduct credits)
  • approve - Approve player applications
  • reject - Reject applications
  • slots-override - Manually assign any player to any slot
  • cancel - Cancel an event (before credits are deducted)
  • costs - Set tier costs for slots
  • status - View MGE schedule configuration
  • set-anchor - Set the MGE anchor Sunday

Players can view current event status and slot assignments with /slots.

Understanding the Event Cycle​

MGE events follow a biweekly cycle:

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Setup     │ ──▶ │    Open     │ ──▶ │   Review    │ ──▶ │  Finalize   │
│ Set costs   │     │ Applications│     │   Apps      │     │   Slots     │
└─────────────┘     └─────────────┘     └─────────────┘     └─────────────┘
  1. Setup - Configure tier costs before the event
  2. Open - Applications open for players (/mge activate)
  3. Review - Leaders review and approve/reject
  4. Finalize - Slots are assigned, credits deducted (/mge confirm)

Setting Tier Costs​

Before opening applications, configure the credit costs using a multiplier:

/mge costs

This opens a form where you enter a multiplier. Costs are calculated as medals × multiplier for each slot:

SlotMedalsCost (5x)Cost (3x)Cost (7x)
1st100500300700
2nd80400240560
3rd60300180420
4th40200120280
5th2010060140
6-7157545105
8-1010503070
Choosing a Multiplier

See Credit System Design for guidance on choosing a multiplier based on your empire's credit economy.

  • 5x (default) - ~2 seasons of perfect attendance for 1st place
  • 3x-4x - Faster slot turnover, good for smaller/less active empires
  • 6x-10x - Slower rotation, rewards long-term commitment

Activating an MGE Event​

To open applications for a new event:

/mge activate

Activation Window​

Before you can activate an MGE, you must be within the activation window:

  • Opens: 5 days before the MGE starts (Wednesday before event week)
  • Closes: 2 days after the MGE starts (Wednesday of event week)
  • Duration: 7-day window to activate

Check if you're in the activation window:

/mge status

This shows:

  • Your configured anchor Sunday
  • Next MGE start and end dates
  • Activation window dates
  • Whether the window is currently open

If there's an unconfirmed MGE, /mge status also shows:

  • All slot assignments with player names and credit costs
  • Pending applications (up to 5 shown)
  • Total credits to be deducted
  • Action required (confirm or cancel)

This comprehensive view means you don't need to run /slots separately - everything is in one place.

What Activation Does​

When you run /mge activate:

  • Creates a new MGE event with status applications_open
  • Posts announcement to your MGE channel (if configured)
  • Opens applications for players via /apply

Activation Rules​

  • One event at a time: Cannot activate if an event is already active
  • Must be in window: Activation only works during the 7-day window
  • Requires anchor: Must set anchor Sunday first via /mge set-anchor

Example​

# First, check the schedule
/mge status

# If in activation window, activate the event
/mge activate

# Optionally, open applications to all players (e.g. for new empires)
/mge configure-activated open_applications:true minimum_credits:10

Configuring the Active MGE​

After activating an MGE, you can adjust its settings with:

/mge configure-activated [open_applications] [minimum_credits]

Open Applications​

By default, players must have enough credits to cover the slot tier they're applying for. Open Applications mode removes this per-slot credit check, allowing anyone to apply for any tier.

/mge configure-activated open_applications:true

This is especially useful for new empires where players haven't accumulated enough credits to afford top slots. Leaders can then review applications manually and approve based on activity participation rather than credit balance.

When open applications is enabled:

  • Players can apply for any slot tier regardless of credit balance
  • Only the minimum credits threshold is checked (if set)
  • Players may go into negative credits after /mge confirm
  • Leaders retain full control over who gets approved

Minimum Credits​

Set a floor for who can apply:

/mge configure-activated minimum_credits:10

This ensures only players with at least some activity participation can apply. Combine with open applications to let active players apply for any tier:

/mge configure-activated open_applications:true minimum_credits:10

Checking Current Settings​

Use /mge status to see the current Open Applications and Minimum Credits values for the active event.

Viewing Applications​

Check current event status and applications:

/slots

This shows:

  • Event name and status
  • Application status (open/closed)
  • All applicants with their tier preferences
  • Current slot assignments

Approving Applications​

To approve a player's application:

/mge approve @Player <slot>
ParameterTypeRequiredDescription
@playerUser mentionYesPlayer to approve
slotNumberYesSlot number (1-10)

Approval Process​

  1. Review the player's application tier
  2. Verify credits are available
  3. Approve the application and assign a slot number
  4. Slot is reserved (credits deducted on confirmation)

Bulk Approvals​

Approve applications one at a time or in batches based on your review.

Rejecting Applications​

To reject an application:

/mge reject @Player

When to Reject​

  • Player doesn't meet requirements
  • Too many applications for available slots
  • Policy violations
  • Player requests cancellation

Credit Handling​

Credits are only deducted when /mge confirm is run. Rejections before confirmation have no credit impact.

Overriding Slot Assignments​

Sometimes you need to manually assign a player to a slot, even if they didn't apply through the normal process.

/mge slots-override <slot> @Player

When to Use​

  • Out-of-process agreements: Player committed via direct message or voice chat
  • Special circumstances: Late additions, leadership decisions, manual swaps
  • Corrections: Fixing mistakes in slot assignments
  • Non-applicants: Assigning someone who obtained a slot outside the application system

How It Works​

  1. Specify the slot number (1-10) and the player
  2. If someone else is in that slot, they're automatically unassigned
  3. Player is assigned to the slot (even if they never applied)
  4. You're prompted to run /mge confirm to review all changes

Example Workflow​

# Player A is in slot 3, but you need to swap them with Player B
/mge slots-override slot:3 @PlayerB

# Response shows: "PlayerB has been assigned to Slot 3, replacing PlayerA"

# Review the updated assignments
/mge confirm

Important Notes​

  • Works on active/unconfirmed MGEs only
  • Cannot override after /mge confirm completes
  • Automatically creates an application record for tracking
  • Always run /mge confirm after to review final state

Confirming the Event​

Once slots are assigned and you're ready to finalize the MGE:

/mge confirm

Confirmation Flow​

  1. Preview Display

    • Shows all 10 slots with player names and credit costs
    • Displays total credits that will be deducted
    • Warns about any unassigned slots (⚠️ Not assigned)

  2. Review & Adjust

    • If slots need changes, use /mge slots-override to reassign
    • Run /mge confirm again to see updated preview
    • Review carefully - confirmation cannot be undone

  3. Confirm or Cancel

    • Click "Cancel" to abort without changes
    • Click "Confirm MGE Slots and Deduct Credits Now" to finalize
    • Hash validation ensures preview matches current state

When to Confirm​

Available anytime after /mge activate:

  • During applications_open period
  • While event is in_progress
  • After event ends (awaiting_confirmation)
  • No need to wait for the event to end in-game

Safety Features​

  • Hash validation: If slots change after preview, button becomes invalid
  • Cancel option: Safe exit without deducting credits
  • Visual warnings: Clear indicators for unassigned slots
  • Confirmation preview: See exactly what will happen before committing

Warning: Once you click "Confirm MGE Slots and Deduct Credits Now", credits are permanently deducted and the action cannot be undone.

Canceling Events​

If an event needs to be canceled before confirmation:

/mge cancel

Cancellation Rules​

  • Can cancel at any time before credits are deducted - even after running /mge confirm (which shows a preview), as long as you haven't clicked the "Confirm" button
  • Once credits have been deducted via the confirm button, the event cannot be cancelled

When to Cancel​

  • Event is canceled in-game
  • Not enough participants
  • Technical issues

Managing Applications Fairly​

Review Criteria​

Consider establishing criteria:

  • Minimum participation requirements
  • Credit balance thresholds
  • Past event participation
  • Activity history

Handling Ties​

When multiple players want the same tier:

  • First-come-first-served
  • Credit balance tiebreaker
  • Activity history consideration
  • Random selection

Document your tiebreaker policy so players understand.

Communication​

Keep players informed:

  • When applications open
  • Application deadlines
  • Approval/rejection notifications
  • Final slot assignments

Best Practices​

Plan Ahead​

Timeline Example:

Wed (5 days before): Activation window opens
                     Set costs and activate event
Thu-Fri:             Players submit applications
Sat-Sun:             Review and approve/reject applications
Mon (event starts):  Make any final slot adjustments with /mge slots-override
                     Run /mge confirm to preview all assignments
                     Click "Confirm" button to finalize
Mon-Sun:             MGE runs in-game
Sun (event ends):    Can still confirm if you haven't yet

Document Decisions​

Keep records of:

  • Why applications were approved/rejected
  • How ties were resolved
  • Any special circumstances

Be Transparent​

Post event results publicly:

  • Who got which slot
  • How decisions were made
  • Thank participants

Gather Feedback​

After events, ask:

  • Was the process fair?
  • Were costs appropriate?
  • What could improve?

Troubleshooting​

Player Applied for Wrong Tier​

You have several options:

  1. Reject and reapply: Reject their application, have them apply again for correct tier
  2. Use slots-override: Directly assign them to the correct slot with /mge slots-override
  3. Post-confirmation adjustment: Use /bonus to adjust credits after the event (if already confirmed)

Not Enough Applications​

  • Extend the application period
  • Reduce tier costs
  • Encourage participation
  • Consider allowing multi-tier applications

Too Many Applications​

  • Stick to tier priorities
  • Use tiebreakers consistently
  • Consider increasing future event availability
  • Encourage lower-tier applications

Player Can't Participate After Approval​

  1. Cancel their slot (if before confirmation)
  2. Consider credit adjustment via /bonus (if after confirmation)
  3. Offer slot to next eligible applicant

Congratulations! You now have a complete understanding of leader responsibilities. For detailed command syntax, see the Command Reference.