Main Page
Project Overview[edit]
Idle Server Defender is a system-management simulation and incremental defense platform where the primary objective is to maintain the integrity of a central server core. The operational loop involves neutralizing a constant stream of digital threats—including viruses, malware, and data packets—while simultaneously managing long-term hardware and software evolution.
Unlike standard tower defense titles where upgrades are instantaneous, this system utilizes a time-gated installation process known as the Download System. This mechanic requires the administrator to manage computational bandwidth effectively, as every defensive or utility improvement requires a specific duration to reach operational status.
Progression Architecture[edit]
System progression is organized into a hierarchical structure of Cups and Tiers. Each Cup represents a distinct operational environment, containing ten difficulty Tiers that must be cleared to unlock Milestones and higher-level network challenges.
When the system reaches a performance bottleneck, the Ascension Protocol can be executed. This is a prestige-style reset that clears current session progress in exchange for permanent, account-wide architectural bonuses. This protocol is essential for scaling the server's power to meet the requirements of advanced Tiers.
Defensive Subsystems[edit]
The server core is protected by several specialized hardware and software subsystems:
- Turret Arrays: Automated orbiting defense units. Their efficiency is calculated as a percentage of the server's total defensive output.
- Shockwave Generator: A kinetic displacement protocol used to maintain distance between the server core and active malware.
- Bit Vortex: An advanced weapon system that utilizes the server's current health metric to calculate the damage scaling of its projectile output.
- Resource Extractor: A utility beam designed to optimize currency acquisition by siphoning Bits directly from threats during active combat.
Meta-Progression and Background Processes[edit]
Persistent systems maintain server uptime and growth even outside of active combat cycles:
- Daemon Protocols: Permanent background scripts that provide significant stat-based boosts. Notable protocols include the CacheDaemon (resource optimization) and the ArchiveDaemon (damage scaling based on historical wave data).
- Automated Workers: Background processes that manage experience (XP) and currency generation during server "offline" states.
- Executables: Consumable software drops from boss-level threats that provide short-term operational spikes and buffs.
Threat Assessment[edit]
Malicious entities are categorized by their digital behavior and impact on server integrity. Threats range from high-velocity speed viruses to shielded Packets that deploy sub-processes (splitting) upon integrity failure.
In the latest system overhaul (Version 2.3.0), the defensive shield was transitioned to a Hit Blocker system. This protocol prioritizes mitigating a specific number of incoming hits rather than relying on traditional health regeneration, requiring a strategic focus on hit-count management and system durability.
Contribute[edit]
Want to add info? Visit Wiki Guidelines and Tips
