Make Yourself OP on a Minecraft Server (GlassHosting)

What “OP” means

Operator status lets a trusted player run admin commands in Minecraft—teleport, gamemode, ban, whitelist edits, and more. On GlassHosting (Glass Gaming — powered by GlassHosting), you grant OP from the game panel console or by editing ops.json carefully. Treat OP like root access for your realm.

This guide is for Java-style servers (Vanilla, Paper, Spigot). Bedrock permission systems differ—do not mix edition workflows.

Safest path: panel console

1. Open your Minecraft service in panel.glasshosting.com and confirm the server is running.
2. Join once with the exact Java username (or online UUID username) you want as operator.
3. Open the Console tab. Type: op YourExactUsername and press Enter.
4. In-game, you should see a confirmation. Try a harmless check such as /gamemode creative then switch back to survival when done testing.

If the console says the player is not online or not found, fix the name spelling first—offline-mode vs online-mode and Bedrock bridges can change identity. Related: whitelist players and panel beginner guide.

OP levels (keep them boring)

• Level 4 is the usual full operator set on Vanilla/Paper—enough for day-to-day admin.
• Prefer the fewest OPs possible. Friends who only need build help do not need OP; use a permissions plugin later if you outgrow console ops.
• Never share the panel login instead of granting OP. Panel access is broader than in-game commands.

ops.json file edit (when console is awkward)

1. Take a named panel backup first. Related: backups before mods.
2. Stop the server cleanly from the panel.
3. Open ops.json in the file manager or via SFTP. It is a JSON array of player objects (uuid, name, level, bypassesPlayerLimit).
4. Prefer letting the running server rewrite the file via op rather than hand-editing UUIDs unless you know what you are doing.
5. Start the server and verify in console that ops loaded without JSON parse errors.

Broken JSON will drop operators or prevent a clean start—restore the backup if the console complains.

De-op and hygiene

• Remove access with deop Username in console when someone leaves the admin circle.
• After a world upload or migration, re-check ops—old ops.json may not match the new community. See upload your Minecraft world.
• Private SMPs should still use a whitelist. OP without a whitelist is how griefers become permanent features of your spawn.

MSP note

GlassHosting keeps the process always-on in a datacenter so admin work is console and files—not fighting home CGNAT. Grant OP sparingly, keep backups before permission changes, and ticket with console lines if ops will not stick.

Order or manage plans at billing.glasshosting.com. Deeper how-tos live in the GlassHosting knowledgebase.