Frequently Asked Questions

Installation and startup

The panel does not open

1. Confirm the panel process is running.
2. Confirm the address and port, default http://127.0.0.1:18233.
3. Confirm the access scope allows the current source.
4. Check logs/ for port conflicts or permission errors.

Port already in use

The panel, daemon or plugin port may be occupied. Change the panel port and restart; the plugin port advances automatically.

Initial account lost

The initial account is printed in the first startup log. If the log is gone, stop the panel and reset the administrator account with the maintenance tool.

Instances

The instance exits immediately after startup

Read the instance log. Common causes are an invalid server path, insufficient memory, corrupted configuration or mod conflicts.

Cannot find worlds after import

Confirm the selected directory contains Worlds. If the layout differs, set the world directory path manually.

Instance state looks wrong

The instance appears offline when the daemon cannot reach it. Wait for reconnection or restart the panel and daemon.

Players

Player list is empty

• Confirm the plugin is loaded and connected.
• Confirm the instance is running.
• Confirm the PlayerEntities directory exists.
• Check the resolved directory in the panel log.

Inventory is not shown

The panel hides the inventory card while the player is in creative mode. Switch to survival mode and reopen the player details.

Actions fail or time out

Confirm the account has player management permission, the plugin is online and the player is still online. Some actions are unavailable for offline players.

AI assistant

The assistant cannot use a feature

Check the tool catalog for switch state and permissions. Default-off tools must be enabled manually.

The assistant keeps trying the wrong approach

Rejected tools return a reason. If the assistant repeats the attempt, ask it to state which tool is missing.

Approval is rejected

Read the reason, adjust the request, or switch to manual approval.

Network and real-time data

Remote data refreshes slowly

• Disable response buffering in the reverse proxy (proxy_buffering off or flush_interval -1).
• Ensure the TLS terminator does not compress or cache text/event-stream.
• Confirm there are no additional proxies between the client and the panel.

Pages load slowly

The first load downloads front-end assets; later loads are served from browser cache. If slowness persists, inspect the network path and proxy configuration.

Upgrades and data

Sign-in is required after upgrading

Session files are preserved during upgrades. If the installer reset sessions, sign in again. This is expected.

The plugin reports a version mismatch after upgrading

Reinstall the plugin from the instance page and restart the instance.

Can backups be restored across versions

Yes. Backups archive the instance directory and are independent of the panel version.

Reporting issues

Include the following:

• Panel and plugin versions.
• Operating system and server type.
• Relevant log excerpts.
• Steps to reproduce and expected behavior.

Repository: public Gitee repository