Repository navigation
Troubleshooting
This page covers common ReinChat issues and steps to help identify their cause.
- Confirm that both ReinChat and its required dependency, ReinCore, are installed in the server's
plugins/directory. - Check the server console for startup errors or dependency messages.
- Make sure the JAR files are installed directly in
plugins/, not inside another subdirectory. - Check that the server and plugin versions are compatible.
For more details, see Installation.
- Check the edited file for YAML indentation and formatting errors.
- Confirm that you edited the correct file in
plugins/ReinChat/. - Run
/reinchat reload. - Check the server console for errors during the reload.
Some changes to commands or dynamically registered channel commands may require a full server restart if they do not register correctly after reloading.
Keep a backup of your configuration files before making significant changes.
- Check that the command is available in ReinChat.
- Verify that the sender has the required permission.
- Check whether the command or alias conflicts with another plugin.
- For chat channel commands, check the relevant YAML file in
plugins/ReinChat/channels/.
Refer to Commands and Permissions.
If a channel command is unavailable or messages are not being sent or received:
- Check the channel's YAML file in
plugins/ReinChat/channels/. - Confirm that
enabledis not set tofalse. - Check the configured
commandandaliases. - Verify the sender's
permissionand the recipient'sread-permission. - Check the channel's
apply-filterssetting if messages are being blocked or modified. - Review the console for configuration or command-registration errors.
See Chat Channels for details.
- Confirm that the tag or color is configured in the appropriate file.
- Use the configured ID rather than its display name when selecting an option.
- Check the relevant permission and any applicable permission-bundle settings.
- If you changed menu settings, close and reopen the menu after reloading.
See Tags & Chat Colors.
If [item], [inv], or [ec] does not produce the expected preview:
- Confirm that the relevant shortcut is configured in
config.yml. - Check that the sender has the corresponding
reinchat.show.*permission. - For
[item], make sure the sender is holding an item. - Check whether the chat display cooldown is active.
- For inventory snapshots, check whether the snapshot has expired and whether the viewer has the required permission.
See Item & Inventory Previews.
- Confirm that PlaceholderAPI is installed and enabled.
- Check the console for messages or errors related to the PlaceholderAPI integration.
- Verify that you are using the correct placeholder spelling.
- Make sure the feature or configuration field supports PlaceholderAPI placeholders.
ReinChat provides its own placeholders for equipped tags. See PlaceholderAPI.
- Confirm that
enabledis set totrueinbroadcasts.yml. - Check
interval-seconds. - Make sure the
messageslist contains entries. - Check the console for configuration or reload errors.
- Confirm that
manual.enabledis set totrue. - Check the permission configured under
manual.permission. - Verify that the sender has the required permission.
See Broadcasts.
The server's latest log is located at:
logs/latest.log
When investigating a problem, look for errors or warnings mentioning ReinChat, ReinCore, or the feature that is failing. Include the relevant error and stack trace when reporting an issue.
Avoid sharing database credentials, webhook URLs, passwords, or other secrets from your configuration files.
If the problem persists, provide the following information when reporting it:
- ReinChat version.
- ReinCore version.
- Paper server version.
- A clear description of the problem and how to reproduce it.
- Relevant console errors or stack traces.
- The relevant configuration section, with secrets removed.
- Any steps you have already tried.
Providing these details makes it easier to identify and reproduce the issue.
For feature-specific guidance, see Configuration, Commands, and Permissions.