Settings

settings holds the log level, how messages are serialized, what Socialismus changes about the server's own behaviour, and how it listens to events. Sync, the updater, commands and chats have documents of their own.

Level

level controls how much Socialismus writes to the logger.

level: 3

{
  "level": 3
}

Use 2 for normal operation and 3 when you are actively debugging chat routing, listeners, or sync behavior.

serialization

serialization controls how Socialismus turns configured message strings into components.

type

• Takes: "MINIMESSAGE", "GSON", "LEGACY_AMPERSAND", "LEGACY_SECTION", or "PLAIN"
• Current default: "MINIMESSAGE"
• Affects: the default serializer adapter used by Socialismus message rendering

MINIMESSAGE is the normal choice for modern Socialismus configuration. Use a legacy adapter only when you intentionally want older color-code conventions to be your primary format.

enableLegacyColors

• Takes: true or false
• Current default: false
• Affects: whether legacy & and § color codes are converted during serialization

This is useful when you want to keep MINIMESSAGE as the main format but still accept legacy color codes in input or migrated config content. It is marked as a warning because this translation adds extra work during message serialization, so each serialized message becomes slightly more expensive.

serialization:
  type: "MINIMESSAGE"
  enableLegacyColors: true

{
  "serialization": {
    "type": "MINIMESSAGE",
    "enableLegacyColors": true
  }
}

vanilla

vanilla switches what the server itself does that Socialismus can take over.

joinMessage

• Takes: true or false
• Current default: false
• Affects: whether the server's own message about a joining player, such as "Alice joined the game", is shown

quitMessage

• Takes: true or false
• Current default: false
• Affects: whether the server's own message about a leaving player is shown

sending

• Takes: true or false
• Current default: true
• Affects: whether a formatted chat message is handed back to the server's chat event, so other plugins see it, instead of being sent by Socialismus itself

On Paper and Bukkit the message then continues through the server's own chat path. Velocity cannot take a message back, so Socialismus sends it there whatever this is set to.

vanilla:
  joinMessage: false
  quitMessage: false
  sending: true

{
  "vanilla": {
    "joinMessage": false,
    "quitMessage": false,
    "sending": true
  }
}

listeners

Listener settings control whether selected platform listeners are registered and what priority they use. Platform-specific listener classes and registration details depend on the platform integration in use.

events

• Takes: a map keyed by fully qualified event class name
• Affects: registration and priority for matching listeners

listeners:
  events:
    com.velocitypowered.api.event.player.PlayerChatEvent:
      register: true
      priority: "LOWEST"

{
  "listeners": {
    "events": {
      "com.velocitypowered.api.event.player.PlayerChatEvent": {
        "register": true,
        "priority": "LOWEST"
      }
    }
  }
}

register

• Takes: true or false
• Affects: whether that event listener is registered at all

If you set this to false, Socialismus skips registration for that specific listener. That can be useful for advanced integration experiments, but it can also break chat, join, quit, world-change, or synchronization-related behavior depending on the event.

priority

• Takes: "LOWEST", "LOW", "NORMAL", "HIGH", or "HIGHEST"
• Affects: the Socialismus listener priority used for that listener, which is then mapped onto the current platform's event-priority model

If the event entry exists but no priority is set, the current code falls back to NORMAL.