Skip to content

Troubleshooting

Common issues

Solutions to the most frequent sofyCore problems, from the core disabling itself to permissions, names, encodings and Paper warnings.

sofyCore disables itself at startup

The database and Redis are both required. If the initial connection fails, or a health check finds a service down, the core rejects new work and disables itself. Check the console for the reason, verify storage.persistence and storage.redis in config.yml, restore the service and restart the server. There is no automatic re-activation.

Server name already in use, or the core stops after a crash

Every server.id must be unique in the network. A name that is already reserved disables the core without changing it. Leave server.id empty to generate a new one, and never copy server.instance-id between servers.

A module does not start after editing its file

If a module YAML is invalid, that module stays off and the console names the wrong key; the other modules keep working. Fix the file and run /sofycore module <module> reload again.

/access status shows SUSPENDED

LuckPerms or PermissionsEx is installed, so sofyCore pauses its own permissions to avoid conflicts. Import your ranks from LuckPerms or PermissionsEx and then remove it.

A staff member with the permission cannot freeze, vanish or sanction

Staff actions need the permission and STAFF authority from a rank of type STAFF, plus a strictly higher rank than the target. Granting OP does not create internal authority. If the ranks module is off or loading, freeze fails closed.

A player 'does not exist' in a command

Commands never invent a UUID from a name. The player must have joined the network at least once; older profiles may need a new join, or you can use the UUID.

Accents look like m├│dulo in the Windows console

The console is not using UTF-8. Start Java with -Dfile.encoding=UTF-8 -Dstdout.encoding=UTF-8 -Dstderr.encoding=UTF-8 and run chcp 65001 first. See Installation.

Paper shows warnings when loading sofyCore

On Paper 26.x the startup log may show informational warnings about PlayerLoginEvent or api-version. They are normal, they are not errors and they do not affect how sofyCore works.

Scoreboard numbers are still visible

hide-numbers only works for 1.20.3+ clients; older clients always show the numbers.

The nametags do not show for some players

If another plugin gives a player its own scoreboard, sofyCore does not take it away: that player will not see the nametags, and a warning is logged once.