Skip to content

Interface & Game Controls

The SillyCore interface is designed to be your central command hub. Everything from granular settings to match execution is managed through a single, intuitive GUI.

SillyCore – Configuration
Settings
Settings
Reload Plugin
Reload Plugin
Modules
Modules
Prepare for start
Prepare for start
Game Phases
Game Phases
Loot Tables
Loot Tables
Start Game
Start Game

The Launch Sequence

To start a new game session, follow these standardized steps:

  1. Configure: Ensure all required settings (Phases, Teams, Map) are complete.
  2. Prepare: Select Prepare for Start. SillyCore will validate your configuration. If successful, the game state is locked, and the match is ready to launch.
  3. Start: Select Start Game to begin the automated countdown and ignite the match.

Core Controls

Validation & Readiness

  • Select this to perform a comprehensive check of all requirements (player counts, world settings, and active configurations).
  • Ready State: Once validation passes, the game is "locked," ensuring no settings are changed accidentally during the countdown.

Ignite the Match

  • Automatically triggers the "Prepare" step if it hasn't been completed yet.
  • Commences the game session with your pre-configured countdown duration.

Instant Reset

  • Instantly reloads SillyCore and all active modules.

User Confirmation

  • To prevent accidental interruptions, you must confirm the reload by typing yes in the chat.

Critical Interruption

  • Reloading will immediately terminate any running games and reset all module states. Use this only during initial setup or between rounds.

GUI Interaction

  • Navigation: Click on any item to open its dedicated submenu or trigger a specific action.
  • Live Feedback: Incomplete or invalid settings are displayed in the item’s lore (hover text).
  • Confirmations: Critical actions provide sound and chat feedback to ensure intentional execution.

Zero Commands Required

You do not need to memorize any complex commands. Every essential feature is accessible through the /sic interface.