Community Features
Enhance your Palworld server community with Discord integration and player activity tracking.
Discord Integration
Connect your server to Discord for real-time notifications and community engagement.
Setting Up Discord Webhooks
Step 1: Create a Webhook in Discord
- Open Discord and navigate to your server
- Right-click the channel where you want notifications
- Select "Edit Channel" → "Integrations"
- Click "Webhooks" → "New Webhook"
- Name your webhook (e.g., "Palworld Server")
- Copy the Webhook URL
- Click "Save"
Step 2: Configure in Control Panel
- Go to your server's Settings tab
- Navigate to "Community" → "Discord Integration"
- Paste the webhook URL into "Discord Webhook URL"
- Configure notification preferences (see below)
- Save your configuration
Discord Webhook URL
The full webhook URL from Discord.
Format: https://discord.com/api/webhooks/1234567890/abcdefghijklmnopqrstuvwxyz
Security: Keep this URL private! Anyone with this URL can post to your channel.
Notification Settings
Control which events trigger Discord notifications.
Suppress @everyone Pings
Disable notification sounds/highlights for Discord messages.
- Disabled (Default): Messages trigger @everyone notifications
- Enabled: Silent messages (no pings)
Recommendation: Enable to avoid annoying frequent pings, especially for high-activity servers.
Notify on Server Start
Send a message when the server starts up.
Example message:
[ONLINE] Palworld Server Online
Server is now accepting connections!
IP: 123.45.67.89:8211
Use when:
- Server has scheduled restarts
- Players want to know when it's available
- Tracking uptime
Notify on Server Stop
Send a message when the server shuts down.
Example message:
[OFFLINE] Palworld Server Offline
Server has shut down.
Reason: Scheduled maintenance
Use when:
- Informing players about downtime
- Tracking unexpected crashes
- Scheduled maintenance
Notify on Player Join
Announce when players connect to the server.
Example message:
[JOIN] Player joined: Steve
Current players: 3/16
Good for:
- Small community servers
- Knowing when friends are online
- Activity tracking
Not recommended for:
- High-population servers (spam)
- Privacy-conscious communities
Notify on Player Leave
Announce when players disconnect.
Example message:
[LEAVE] Player left: Steve
Current players: 2/16
Considerations:
- Same as player join notifications
- Can create notification spam on busy servers
- Useful for small communities
Recommended Configurations
Small Private Server (< 10 players)
Suppress Pings: Enabled
Server Start: Enabled
Server Stop: Enabled
Player Join: Enabled
Player Leave: Enabled
Players get full activity awareness without annoying pings.
Medium Community Server (10-20 players)
Suppress Pings: Enabled
Server Start: Enabled
Server Stop: Enabled
Player Join: Disabled
Player Leave: Disabled
Server status only, no player spam.
Large Public Server (20+ players)
Suppress Pings: Enabled
Server Start: Enabled
Server Stop: Enabled
Player Join: Disabled
Player Leave: Disabled
Minimal notifications, focus on server status.
Player Activity Tracking
Monitor and log player connections for administration and analytics.
Enable Player Logging
Records all player join/leave events in server logs.
Benefits:
- Track player activity patterns
- Security and moderation
- Usage analytics
- Troubleshooting connection issues
What gets logged:
- Player name/ID
- Join timestamp
- Leave timestamp
- Session duration
- Connection IP (if enabled)
Logging Poll Period
How frequently to check player status (seconds).
- Default: 5 seconds
- Recommended range: 5-30 seconds
Performance impact:
| Poll Period | Accuracy | CPU Usage |
|---|---|---|
| 1 second | Excellent | High |
| 5 seconds | Very Good | Low |
| 15 seconds | Good | Minimal |
| 30 seconds | Acceptable | Negligible |
Best practices:
- 5 seconds: Recommended for most servers
- 1-3 seconds: High-activity servers needing precise logs
- 15-30 seconds: Low-priority logging, resource-constrained servers
Auto-Pause System
Automatically pause the server when no players are online to save resources.
Enable Auto-Pause
Pauses server processes when empty.
Benefits:
- Reduced CPU usage (50-70% savings)
- Lower power consumption
- Reduced infrastructure costs
- Automatic resume on player join
How it works:
- Last player leaves the server
- Countdown begins (timeout period)
- If still empty at timeout, server pauses
- When player attempts to join, server resumes
- Player connects after brief resume delay
Auto-Pause Timeout
Wait time after last player leaves before pausing (seconds).
- Default: 180 seconds (3 minutes)
- Recommended range: 120-600 seconds
Timeout selection:
| Timeout | Use Case |
|---|---|
| 60-120s | Development/testing servers |
| 180-300s | Small private servers |
| 300-600s | Community servers with breaks |
| Disabled | Public servers, 24/7 operations |
Considerations:
- Longer timeout = less pause/resume cycles
- Shorter timeout = more resource savings
- Account for players taking short breaks
Pro tip: 180 seconds (3 minutes) handles bathroom breaks and quick disconnects without unnecessary pausing.
Community Best Practices
Discord Channel Setup
Create dedicated channels for different notifications:
Recommended structure:
#palworld-server
├── #server-status (Start/Stop notifications)
├── #player-activity (Join/Leave, if enabled)
├── #server-logs (Direct log feed via webhook)
└── #announcements (Manual maintenance notices)
Benefits:
- Organized information
- Easy to follow
- Players can mute channels selectively
Notification Etiquette
Do:
- Suppress @everyone pings for automated messages
- Use separate channels for different notification types
- Inform players about notification setup
- Test webhooks before going live
Don't:
- Spam main chat with server notifications
- Enable all notifications on high-population servers
- Use @everyone for routine events
- Forget to test your webhook URL
Privacy Considerations
Player privacy:
- Some players prefer anonymous gameplay
- Join/leave notifications reveal activity patterns
- Consider community preferences before enabling
Best approach:
- Ask community about notification preferences
- Start conservative (server status only)
- Add player notifications if requested
- Respect privacy concerns
Engagement Ideas
Use Discord integration to build community:
Server start notifications:
Good morning! Server is online!
Today's event: Double XP Weekend
Join now: steam://connect/123.45.67.89:8211
Scheduled events:
Weekly Boss Hunt starts in 30 minutes!
Meet at the base at 8 PM EST
Prize: Legendary Pal egg!
Milestone celebrations:
Congratulations!
Server has reached 1000 hours uptime!
Thanks to all our amazing players!
Troubleshooting
Discord Webhook Not Working
Check:
- Is the webhook URL correct and complete?
- Is the Discord channel still valid?
- Has the webhook been deleted in Discord?
- Check server logs for webhook errors
Solution:
- Verify webhook exists in Discord settings
- Create new webhook if necessary
- Update URL in control panel
- Save and test
Too Many Discord Notifications
Solutions:
- Enable "Suppress @everyone Pings"
- Disable player join/leave notifications
- Use a separate, muted channel
- Increase polling period to reduce frequency
Player Logging Not Recording
Verify:
- Player logging is enabled
- Poll period is reasonable (< 60s)
- Server has write access to logs
- Sufficient disk space available
Auto-Pause Not Working
Common issues:
- Feature not enabled in settings
- Players still connected (check player count)
- Timeout period too long
- Server configuration error
Solutions:
- Verify auto-pause is enabled
- Check timeout setting
- Review server logs
- Test with known empty server
Next Steps
- Troubleshooting - Solve common server issues
- Advanced Configuration - RCON, REST API, and custom configs