Multiplayer with No Time Passing While Offline

Tags: server-config, gameplay, time, hosting, automation, mods, scripts, multiplayer

7 Days to Die dedicated servers continue running game time even when no players are connected, which can lead to unwanted blood moons, resource depletion, and base decay during offline periods. This comprehensive guide provides multiple strategies to prevent or minimize time progression when your server is empty, including server configuration, automation scripts, mod solutions, and best practices for different playgroup sizes.

Understanding the Time Progression Problem

When a 7DTD dedicated server runs without players:

• Game time continues: Day/night cycles progress at normal speed
• Blood moons accumulate: Missed blood moon nights still count against the frequency counter
• Resource systems active: Loot respawn timers, wandering hordes, and zombie spawning continue
• Base decay occurs: Land claim blocks lose durability over time
• World events progress: Traders restock, weather changes, and environmental effects continue

This can result in players returning to find they've missed critical blood moon nights, their bases have deteriorated, and valuable resources have despawned or been consumed by wandering zombies.

Server Configuration Approaches

Adjusting server settings is the first and most straightforward method to minimize offline progression impact:

Example serverconfig.xml Configuration

<property name="DayNightLength" value="90"/ > <!-- 90 minute days -- > <property name="BloodMoonFrequency" value="10"/ > <!-- Blood moon every 10 days -- > <property name="LandClaimOfflineDurabilityModifier" value="10"/ > <property name="LandClaimDecayMode" value="2"/ > <!-- No decay when offline -- > <property name="LootRespawnDays" value="21"/ > <!-- 3 week loot respawn -- > <property name="WanderingHordeFrequency" value="7"/ > <!-- Weekly wandering hordes -- > <property name="MaxSpawnedZombies" value="48"/ > <!-- Reduced zombie count -- > 

Manual Server Management Strategies

For small groups with predictable play schedules, manual management can be effective:

1. Scheduled Server Operation

• Defined Play Sessions: Agree on specific days/times when the server will be active
• Designated Admin: Assign responsibility for starting/stopping the server
• Communication Protocol: Use Discord, WhatsApp, or group chat for coordination
• Grace Periods: Allow 15-30 minutes after last player logs off before shutting down

2. Quick Start/Stop Procedures

Create simple scripts for non-technical players to control the server:

• Windows Batch File (start_server.bat): start 7DaysToDieServer.exe -configfile=serverconfig.xml
• Windows Batch File (stop_server.bat): taskkill /F /IM 7DaysToDieServer.exe
• Linux Bash Script (start_server.sh): ./startserver.sh -configfile=serverconfig.xml
• Linux Bash Script (stop_server.sh): pkill -f 7DaysToDieServer

3. Player-Led Shutdown Protocol

1. Last player announces they're logging off in group chat
2. Wait 5 minutes for any late joiners
3. Execute shutdown script or manually stop server
4. Confirm shutdown in group chat
5. Next session: First player starts server and announces readiness

Automation Solutions

Automated systems provide the most reliable time-freezing without player intervention:

LinuxGSM Auto-Shutdown Script Example

LinuxGSM includes player detection features. Create a cron job to check for empty servers:

#!/bin/bash
# /home/7dtd/check_empty.sh
PLAYER_COUNT=$(/home/7dtd/7dtdserver monitor | grep "Players:" | awk '{print $2}')

if [ "$PLAYER_COUNT" -eq "0" ]; then
  # Server empty for more than 30 minutes
  if [ -f /tmp/server_empty ]; then
    EMPTY_TIME=$(cat /tmp/server_empty)
    CURRENT_TIME=$(date +%s)
    if [ $(($CURRENT_TIME - $EMPTY_TIME)) -gt 1800 ]; then
      /home/7dtd/7dtdserver stop
      rm /tmp/server_empty
    fi
  else
    echo $(date +%s) > /tmp/server_empty
  fi
else
  rm -f /tmp/server_empty
fi

Add to crontab: */5 * * * * /home/7dtd/check_empty.sh

Windows Task Scheduler Automation

1. Create a PowerShell script to check for active connections
2. Schedule it to run every 10 minutes via Task Scheduler
3. Stop server after 30 minutes of emptiness
4. Log all actions for troubleshooting

Mod and Third-Party Tool Solutions

Several community-developed solutions address the time progression problem:

CSMM (Custom Server Mod Manager) Setup

1. Install CSMM following official documentation
2. Enable the "Auto Pause" module in settings
3. Configure empty server timeout (default: 30 minutes)
4. Set up notifications for server state changes
5. Test with a staging server before production

Alloc's Server Fixes Configuration

<!-- In serveradmin.xml or mod config -- > <property name="PauseWhenEmpty" value="true" / > <property name="EmptyTimeoutMinutes" value="30" / > <property name="ResumeWhenPlayerJoins" value="true" / > 

Best Practices by Group Size

Different approaches work best depending on your player count and schedule:

Small Groups (2-4 Players)

• Recommended: Manual shutdown + longer day cycles
• Schedule: Coordinated play sessions 2-3 times per week
• Configuration: 90-minute days, 10-day blood moon frequency
• Tools: Simple batch/bash scripts for easy control

Medium Groups (5-10 Players)

• Recommended: Automated monitoring + server manager
• Schedule: Semi-regular play with overlapping schedules
• Configuration: 75-minute days, enhanced land claim protection
• Tools: CSMM or 7DTD Server Manager with auto-pause

Large Groups (10+ Players)

• Recommended: 24/7 operation with configuration adjustments
• Schedule: Nearly always someone online
• Configuration: Normal 60-minute days, focus on performance
• Tools: Full server management suite with monitoring

Public/Community Servers

• Required: 24/7 operation with optimized settings
• Focus: Performance, stability, and fair play for all timezones
• Configuration: Standard timing with boosted land claim protection
• Tools: Professional server management with DDoS protection

Troubleshooting Common Issues

Server Won't Start Automatically

• Check permissions: Scripts may need administrator/root privileges
• Verify paths: Absolute paths work better than relative in scheduled tasks
• Test manually: Run scripts directly before automating
• Review logs: Check server log files for startup errors

Time Still Progressing with "Pause" Mods

• Verify mod installation: Ensure mods are in correct Mods folder
• Check configuration: Review mod config files for correct settings
• Test with empty server: Join and leave to verify time freezing
• Update mods: Ensure compatibility with your game version

Players Returning to Destroyed Bases

• Increase LandClaimOfflineDurabilityModifier: Set to 10 or higher
• Change LandClaimDecayMode: Set to 2 (no decay when offline)
• Reduce zombie spawns: Lower MaxSpawnedZombies during offline periods
• Implement backup system: Daily server backups to restore if needed

Blood Moon Occurring at Inconvenient Times

• Adjust BloodMoonFrequency: Increase to 10-14 days
• Use blood moon resets: Admin commands to skip or reschedule
• Coordinate play sessions: Plan around expected blood moon nights
• Implement grace period: Don't count first blood moon after server restart

Advanced: Custom Time Manipulation

For technical users, direct time manipulation is possible:

Save File Editing

Warning: Editing save files directly can corrupt your world. Always backup first.

1. Locate save file: ~/7DaysToDie/Saves/[WorldName]/[Seed]/
2. Find and edit gameprefs.xml or equivalent time-tracking files
3. Adjust DayTime values to roll back or freeze time
4. Use tools like 7D2D Save Editor for safety

REST API Automation

If using CSMM or similar tools with REST API:

# Example: Check if server empty via API
curl -X GET "http://yourserver:8081/api/getgamestats" | grep "playerCount"

# Example: Send pause command via Telnet
echo "say Server pausing due to inactivity" | nc localhost 8081
echo "serverpause" | nc localhost 8081

Communication and Coordination Tips

• Establish Clear Rules: Document server operation procedures
• Use Dedicated Channels: Discord server with specific channels for server status
• Implement Status Notifications: Automated messages when server starts/stops
• Create Play Schedule: Shared calendar for planned sessions
• Designate Admins: Multiple trusted players with shutdown privileges
• Regular Check-ins: Weekly discussion about server timing issues

Recommended Complete Solution Stack

For most private servers, this combination works well:

1. Server Configuration: 90-minute days, 10-day blood moons, enhanced land claim protection
2. Automation Tool: CSMM with auto-pause module (30-minute timeout)
3. Communication: Discord server with status bot integration
4. Backup System: Daily automated backups to separate storage
5. Monitoring: Simple uptime monitoring with alerts for unexpected restarts