Troubleshooting
Common issues and how to fix them.
Bot Not Connecting
"PLEASE SET YOUR BOT TOKEN!"
Cause: The bot token is missing or still set to the default.
Fix:
- Open
config/AetherLink/config.json - Replace
"YOUR_BOT_TOKEN_HERE"with your actual bot token - Restart the server
Bot is online in Discord but not responding
Possible causes:
- Message Content Intent not enabled
- Go to Discord Developer Portal
- Select your bot → Bot → Privileged Gateway Intents
-
Enable Message Content Intent
-
Wrong channel ID
- Verify the channel ID in
config.jsonis correct -
Make sure you copied the channel ID, not the server ID
-
Bot not in the server
- Re-invite the bot using the OAuth2 URL
"Channel not found or bot lacks access"
Cause: The bot cannot see the configured channel.
Fix:
- Check the channel ID is correct
- Ensure the bot has View Channel permission
- If the channel is in a category, check category permissions too
Messages Not Sending
Discord → Hytale not working
Check:
- The channel's
readOnlyis set tofalse - The channel's
enabledis set totrue - Console shows no permission errors
Hytale → Discord not working
Check:
- At least one channel is configured and
enabled: true - Bot has Send Messages permission in the channel
- Check console for error messages
"Missing permissions in #channel"
Cause: The bot lacks required Discord permissions.
Required permissions:
View Channel– See the channelSend Messages– Post messagesRead Message History– Read past messagesManage Channel– Set slowmode and channel topic (optional)
Fix:
- Go to Server Settings → Roles
- Find the bot's role
- Enable the required permissions
- Or set permissions per-channel in Channel Settings → Permissions
Commands Not Working
"/aetherlink" command not found
Possible causes:
- Server didn't fully start
- Check console for "AetherLink events registered!"
-
If missing, there was a startup error
-
Commands not registered
- This is a bug – please report it on GitHub
"/aetherlink reload" does nothing
Cause: Reload is rate-limited to once every 5 seconds.
Fix: Wait 5 seconds and try again.
Spam Control Issues
Slowmode not being set
Cause: Bot lacks Manage Channel permission.
Fix: Grant the bot Manage Channel permission.
Messages being grouped incorrectly
The aggregation groups duplicate events within hytaleAggregateSeconds.
To disable aggregation:
"spamControl": {
"hytaleAggregateSeconds": 0
}
Performance Issues
High CPU usage
Possible causes:
- Too many channels configured
- The bot updates topics for all channels every 60 seconds
-
Consider disabling some channels
-
Rapid reconnection attempts
- If Discord is unreachable, the bot retries with exponential backoff
- Check your network connection
Memory leaks
If memory usage grows over time:
- Check for errors in the console
- Restart the server periodically
- Report the issue on GitHub with logs
Getting Help
If your issue isn't listed here:
- Check the console for error messages
- Enable debug logging (if available)
- Open an issue on GitHub with:
- Your
config.json(remove the bot token!) - Relevant console logs
- Steps to reproduce the issue
Other information
If you are comfortable with downloading and building, if one day aetherlink doesn't work because of an hytale update you can modify and build the .jar file yourself in Build It Yourself.
Known Limitations
| Limitation | Reason |
|---|---|
| Max players shows "?" | Hytale API doesn't expose max players yet |
| Death messages don't work | Waiting for Hytale death event API |
| Advancement messages don't work | Waiting for Hytale advancement API |
| Linking not implemented | Planned for future release |