Troubleshooting & FAQ
Having issues getting StarChat running perfectly? Check these common solutions before opening a ticket.
Common Errors
Error: "Invalid configuration format"
Cause: You have a YAML syntax error in one of your configuration files (usually format-components.yml). YAML relies strictly on spaces (not tabs) for indentation.
Solution: Run your configuration file through a YAML validator website or paste it into the Nebula AI web interface and ask where the syntax error is.
PlaceholderAPI tags returning literally (e.g. %player_name%)
Cause: You haven't downloaded the required eCloud expansions for PlaceholderAPI.
Solution: Run /papi ecloud download Player and /papi reload in-game. Do this for any other placeholder prefixes you are trying to use (like Vault, Server, etc).
Players have no prefix/suffix in chat
Cause: Either LuckPerms is not installed, or your format-components.yml group names do not match your LuckPerms group names.
Solution: Ensure your group names in format-components.yml identically match the exact lowercase internal names of the LuckPerms groups (e.g., admin, vip, default). Also ensure the priority weights are correct (higher number = higher priority).
Database Connection Issues
If you see HikariPool or Communications link failure exceptions in your console, this means StarChat cannot connect to your MySQL/MariaDB database.
- Verify your host IP, port (usually 3306), username, and password in
config.yml. - Ensure the database user has full
GRANT ALL PRIVILEGESon the specified database schema. - If your Database is on a different hosting provider than your game server, ensure the Database firewall (Remote MySQL) allows connections from your game server's IP.
- If you don't need Redis/Cross-server syncing, simply change the database type to
SQLITEin your config to use a local flatfile database instead.
💬 Still need assistance?
If these steps don't resolve your issue, please join our Discord and open a support ticket with a link to your server console log (using mclo.gs or Pastebin).