Omnisight docs

Player Configs & Common Mistakes

Home

Player Configs & Common Mistakes

Per-player overrides, minimal example, and common editing pitfalls.

Player Configs (mods/OMNISIGHT/players/)

Each player has their own JSON file. These override the global defaults.

Common fields you may edit:

  • hudMode: OFF, SIMPLE, FULL, CLOCK
  • infoPosition, clockPosition, clockVisible, infoHudVisible
  • hudSize
  • clockDisplay
  • simpleDisplay

Fields like uuid, username, firstJoin, lastSeen, and lastOpenedSettingsCategory are managed by the mod and usually should not be edited.

Minimal Player Example

{
  "uuid": "069a79f4-44e9-4726-a5be-fca90e38aaf5",
  "username": "PlayerOne",
  "hudMode": "SIMPLE",
  "infoPosition": "top_right",
  "clockPosition": "top_left",
  "clockVisible": true,
  "infoHudVisible": true,
  "hudSize": "medium",
  "clockDisplay": {
    "layout": { "use24Hour": false, "textAlignment": "Left" },
    "elements": {
      "time": { "show": true, "color": "#ffffff", "secondRow": false }
    }
  },
  "simpleDisplay": {
    "block": {
      "features": {
        "features": { "blockId": true, "drops": false }
      }
    },
    "equipment": {
      "features": {
        "features": { "equipmentHud": true, "durability": true }
      },
      "position": "bottom_right"
    }
  }
}

Common Mistakes

  • JSON requires double quotes and no trailing commas.
  • features.features must be nested exactly, or your toggles will be ignored.
  • Positions are normalized to snake_case values.
  • Changes do not apply until the server restarts.