Skip to content

Troubleshooting

Narcilioo edited this page Jul 23, 2026 · 1 revision

Troubleshooting

Complete troubleshooting guide for GlowPlayersPro.

Common Issues

Plugin Doesn't Load

Symptoms:

  • Error message in console when starting server
  • /glow command doesn't exist

Solutions:

  1. Check Minecraft version

    • Plugin requires Minecraft 1.21 or higher
    • Check console for version errors
  2. Check Java version

    • Plugin requires Java 21 or higher
    • Run java -version to check
  3. Check JAR file

    • File must be in the plugins/ folder
    • Name must be GlowPlayersPro-1.3.0.jar
  4. Check console

    • Look for error messages
    • Verify plugin is listed in startup

/glow Command Not Working

Symptoms:

  • Command not recognized
  • "Command not found" message

Solutions:

  1. Check permissions

    • Players need glowplayers.use permission
    • Use /glow reload to verify plugin is loaded
  2. Restart server

    • Stop and start the server again
    • Check console for errors
  3. Check plugin.yml

    • Command must be defined in plugin.yml
    • Check for syntax errors

Glow Doesn't Appear

Symptoms:

  • Command works but no visible effect
  • Success message but no visual change

Solutions:

  1. Check configuration

    • use-teams: true for standalone use
    • use-teams: false for TAB integration
  2. Check permissions

    • Players need glowplayers.use permission
    • Check for conflicting permissions
  3. Test with different color

    • Use a more visible color like red or blue
    • Check if color is working
  4. Check scoreboard

    • Other plugins may be conflicting
    • Disable other plugins temporarily to test

Glow Disappears After Reconnecting

Symptoms:

  • Glow works but doesn't persist after reconnection
  • Player needs to use /glow every time they join

Solutions:

  1. Check players.yml file

    • File must exist in plugins/GlowPlayersPro/
    • Check if data is being saved
  2. File permissions

    • Server needs write permission to the folder
    • Check if file is read-only
  3. Check console

    • Look for errors when saving data
    • Check for permission issues

Neon Effect Not Working

Symptoms:

  • /glow neon command works but doesn't animate
  • Glow stays static on one color

Solutions:

  1. Check speed setting

    • neon-speed-ticks must be greater than 0
    • Very low values may cause issues
  2. Check colors

    • neon-colors must have at least one color
    • Invalid colors are ignored
  3. Check performance

    • Too many players with neon can cause lag
    • Increase neon-speed-ticks if needed

Placeholder Not Working

Symptoms:

  • %glowplayerspro_color% returns empty
  • TAB doesn't show glow color

Solutions:

  1. Check PlaceholderAPI

    • Plugin must be installed and enabled
    • Use /papi list to check
  2. Check expansion

    • Use /papi list to see if glowplayerspro is listed
    • Use /papi reload to reload
  3. Test placeholder

    • Use /papi parse <player> %glowplayerspro_color%
    • Check if it returns expected color

Outdated Configuration

Symptoms:

  • Console message about outdated config
  • New options don't appear in config.yml

Solutions:

  1. Back up

    • Copy current config.yml
    • Note your customizations
  2. Delete config.yml

    • Remove file from folder
  3. Restart server

    • New configuration will be generated
    • Re-apply your customizations

Sounds Not Working

Symptoms:

  • Sound effects not playing
  • Sound not found message

Solutions:

  1. Check configuration

    • sounds.enabled: true
    • Valid sound names
  2. Check console

    • Look for sound errors
    • Check if sound exists in version
  3. Test with different sound

    • Use a known sound like entity.experience_orb.pickup
    • Check if problem is specific sound

Common Console Errors

"Message not found: [path]"

Cause: Message not found in language file.

Solution:

  1. Check if language file exists
  2. Check if message is defined
  3. Restart server

"Could not create players.yml"

Cause: Problem creating data file.

Solution:

  1. Check folder permissions
  2. Check disk space
  3. Check if antivirus is blocking

"Could not save players.yml"

Cause: Problem saving data.

Solution:

  1. Check write permissions
  2. Check if file is open
  3. Check disk space

"Config outdated"

Cause: Outdated configuration.

Solution:

  1. Back up config.yml
  2. Delete config.yml
  3. Restart server
  4. Re-apply customizations

Advanced Solutions

Complete Cleanup

If you're experiencing persistent issues:

  1. Stop the server
  2. Back up important files
  3. Remove the plugins/GlowPlayersPro/ folder
  4. Remove the JAR file
  5. Restart the server (to clear other plugin data)
  6. Reinstall the plugin
  7. Reconfigure from scratch

Checking for Conflicts

To identify conflicts with other plugins:

  1. Disable all other plugins
  2. Test GlowPlayersPro alone
  3. Enable plugins one by one
  4. Identify which plugin causes the conflict

Debug Logs

For more information:

  1. Enable debug.log-sounds: true in config.yml
  2. Check console for detailed messages
  3. Look for errors or warnings

Getting Help

If none of the above steps work:

  1. Check the full documentation
  2. Search for similar issues on GitHub
  3. Open a new issue with:
    • Minecraft version
    • Plugin version
    • Full console output
    • Steps to reproduce the problem

System Information

When reporting a problem, include:

  • Minecraft Version: (e.g., 1.21.4)
  • Plugin Version: (e.g., 1.3.0)
  • Other Plugins: List of installed plugins
  • Console: Complete error messages
  • Configuration: Your config.yml (without sensitive information)