KalOnline GM commands: use permissions, not guesswork

Why command lists disagree

Old community threads show that command availability and rank behavior can differ by package or customization. A command may exist in one executable, be renamed in another, or require a permission value stored in the database. Copying a long list into production is not a safe test.

Discover commands on a lab server

1. Use a disposable administrator account.
2. Back up authentication and game databases.
3. Check package documentation and source, if lawfully available.
4. Test one harmless command. Prefer status or navigation commands over item or character changes.
5. Record syntax, required rank and side effects.
6. Restore the lab if the command creates unexpected data.

Use least privilege

Separate support, moderator and administrator roles when the package supports it. A helper who only answers player questions should not have database-level control or the ability to create items. Review privileged accounts regularly and do not reuse ordinary player passwords.

Safety boundary

This guide is for administration of a server you own or are authorized to manage. It does not provide methods for obtaining GM access on someone else’s server, bypassing permissions or exploiting commands.

Operating privileged accounts responsibly

Keep an audit trail

Where the package supports logging, retain records of administrator logins and commands. If it does not, document high-impact actions manually. This helps distinguish a software bug from an administrative change.

Test commands away from players

Use a closed lab zone and disposable character. Item creation, teleportation or event commands can alter database state, trigger scripts or affect other players. Back up first and confirm the command’s scope.

Do not store maximum privilege in the normal account

Use a separate administrator identity only when needed. A stolen everyday account should not automatically grant full server control.

Package documentation beats universal lists

Community command lists are useful historical clues, but custom builds add, remove or redefine commands. Verify against your executable, source code if legitimately available, or trusted documentation for that exact release.