
      <p>Managing access differs between editions. We normalized the UX while respecting file formats and identity systems.</p>

      <h2>Java</h2>
      <ul>
        <li><strong>Identity:</strong> Mojang UUID (online-mode=true)</li>
        <li><strong>Files:</strong> <code>ops.json</code>, <code>whitelist.json</code>, <code>banned-players.json</code></li>
        <li><strong>Lookup:</strong> Mojang API by username → UUID</li>
      </ul>

      <h2>Bedrock</h2>
      <ul>
        <li><strong>Identity:</strong> Xbox Live XUID</li>
        <li><strong>Files:</strong> <code>whitelist.json</code>, <code>permissions.json</code></li>
        <li><strong>Ops:</strong> via <code>permissions.json</code> with role <code>operator</code></li>
      </ul>

      <h2>How we apply changes</h2>
      <ul>
        <li>Write JSON into the container’s mounted <code>/data</code></li>
        <li>Reload: quick restart or in-game command (where supported)</li>
        <li>Skins & avatars: optional lookup for a nicer UI</li>
      </ul>
    

GlitchNode Blog

Player Management: Java vs Bedrock

Java

Bedrock

How we apply changes