Terms
This glossary explains recurring terms. Concrete balance values are shown in the action preview in the game.
| Term | Category | Explanation | Example |
|---|---|---|---|
| Global balance | Economy | CryptoCoins (CC) belong to your account, not to a single server. Costs are paid from this available balance. An income rate and a transfer capacity are not additional coins. | Example: your account balance stays the same even when you switch servers. |
| Income rate (CC/h) | Economy | The rate describes income per hour. Mining, synergies, collective bonus and server role influence it. Under the existing crediting rule, passive income continues even during a server lock. A lock restricts server actions, not this income rate. Credits happen when the game processes them. | Example: a higher rate increases future income, not your balance right away. |
| Transfer capacity and vault | Economy | The crypto vault determines capacity limits for transfers. A large capacity is not a balance. Recipient, fees and the actual limits are shown in the transfer view before the transfer. | Example: with an empty account you cannot send coins despite a large vault. |
| Affordable, startable and free slots | Jobs | Affordable only checks the coins. Startable now also considers prerequisites, running jobs, free slots and locks. Research and upgrades apply to the selected server. When they expire, jobs are processed according to their respective rules. | Example: an affordable upgrade may not start yet because all slots are full. |
| Toolkit, data access and social engineering | Jobs | Completed levels only affect newly started jobs on the same server, with a bonus cap. The modular code toolkit shortens other research including the fiber backbone, not itself or hardware upgrades. Boosters and collective bonus are multiplicative; the general minimum research duration by hardware also applies to the toolkit itself. Data access strategies increase the gross yield of all automatic operations. Social engineering increases the gross yield only for phishing and landing pages and lowers the risk up to risk-free operations, not for keyloggers or direct attacks. Yield bonuses and IP scramblers are multiplicative without a shared yield cap. Costs and existing jobs do not change. | Example: if you research another level during a running operation, its start snapshot stays unchanged. The bonus only applies to the next operation; more gross yield does not mean the same percentage of net profit. |
| Server role and specialization | Server | A role changes the strengths of your server, for example mining or defense. Hardware and research remain per server. The role description shows the currently valid effects; check costs and prerequisites before switching. | Example: a mining rig is geared towards income instead of attacks. |
| Success and detection | Security | An attack success and its detection are separate results of the simulated game mechanics. Even a successful attack can be detected. Searching for a target or opening this help starts no attack. Only the confirmed game action counts. | Example: the report can show success and at the same time a detected trace. |
| Trace and traces | Security | Trace refers to attack traces in the game. Detection and protection mechanisms influence which traces are created. Forensics shows existing traces; log scrubbing is a separate paid game action, not an effect of this help link. | Example: read the report first before you clean up a trace. |
| Breach Protocol | Security | Breach is a simulated game puzzle for preparing an operation. Valid paths, time and prerequisites are checked by the game. It is not a guide to intruding into real systems and does not replace confirming a real game attack. | Example: an invalid path is not accepted as a completed preparation. |
| Breach sabotage in the Operation Center | Security | A confirmed successful breach temporarily weakens only the effective PvP defense. Damage heals automatically; new hits only add remaining damage up to the cap. Hardware, points and income are not destroyed. The report and your own server status explain the active loss and the recovery time. | Example: without new hits your server automatically becomes fully defensible again. The breach mini-game is a separate action. |
| Signal jammer and recon | Security | The jammer of the target's current collective only lowers the success chance of paid recon relatively; a minimum chance remains. Public nmap/probe node lists, separate detection and other attacks remain unchanged. The building description names the effect of each level. | Example: the jammer makes private hardware reconnaissance harder without inventing public scan targets. A public scan is not paid recon. |
| Distributed Attacks and newbie protection | Security | A Distributed Attack combines servers of several collective members against one hardware target. Servers under newbie protection (too few server points) and NPC servers are not valid targets; the game checks this before the start fee and again on execution. If the target is protected or an NPC on execution, the Distributed Attack ends and all fees go back to whoever paid them, including the start fee. If the leadership cancels a Distributed Attack itself, only fellow members get their join fee back; the start fee and the initiator's additional servers are forfeited. | Example: If a target falls under newbie protection after the start, executing the Distributed Attack returns your start fee instead of losing it on cancellation. |
| Firewall booster, mesh shield and IP scrambler | Security | The firewall booster makes the hardware firewall of all your servers count 1.5 times in defence against PvP attacks, takeovers and Distributed Attacks for 2 hours. The collective perk Syndicate Mesh Shield strengthens this firewall share for all members by 10, 20 or 30%; both combine multiplicatively. Both also lower the detection risk of your own operations. The IP scrambler hides your source IP for 1 hour in traces created during that time: forensics then only reconstructs the first three blocks. It also lowers the risk of your own operations by 20% and raises their yield by 15%. | Example: With booster and Mesh Shield level 3, a level 10 firewall defends like level 19.5. Traces from before the activation stay unchanged. |
| PvP lock and protection window | Security | Successful DDoS and rootkit attacks lock the target's Operation Center for a limited time. Further hits do not extend an active lock. After it expires, a 30-minute protection window follows in which no hit applies a new lock. Loot and other effects of a hit are not affected. | Example: A second DDoS during an active lock only reports the remaining time; the attack confirmation shows beforehand whether the target is currently protected. |
| Netwars raids: attack waves | Economy | A raid attack is possible every 15 seconds. Each person has an hour window starting with their first wave: the first 5 waves count fully, from the 6th 50% and from the 12th 10% damage. Damage and support score determine your share of the reward pool, so constant clicking brings little more than regular attacks. | Example: Attacking every 15 seconds for an hour yields about 31 full waves instead of 240; five waves per hour always count fully. |
| Buying and activating | Market | A purchased booster is first placed in your inventory. Buying does not activate an effect. Only the separate activation starts the effect and duration; effects that are already active can block further activations of the same category. | Example: buy an item and then check in the inventory when you want to use it. |
| Player level | Progress | Your player level comes from your account points: it rises by 1 for every 1,000 points, starting at level 1. It scales the CC rewards of daily tasks: base reward × level, × 1.5 for medium tasks and × 2.5 for hard tasks. Some tasks also require a minimum level. | Example: With 4,500 points you are level 5; an easy task with a 100 CC base reward then pays 500 CC. |
| Daily limit and daily all-clear | Progress | Daily tasks pay out at most 50,000 CC per day. Individual tasks and the daily all-clear share this limit. The daily all-clear (500 CC × player level) is granted once all countable tasks of the day are completed and fully claimed. If the limit is reached, the outstanding amount is kept and can be claimed on later days. The day changes at midnight server time. | Example: At level 10 the daily all-clear pays 5,000 CC as long as the daily limit is not used up. |
| Login streak | Progress | You get a login reward once per calendar day. On consecutive days it rises over 7 days: 150, 250, 400, 600, 900, 1,300 and 2,500 CC. Days 3 and 7 add an upgrade booster (15% faster for 4 h or 50% faster for 12 h), day 5 a research booster (25% faster for 6 h). After day 7 the cycle starts again at day 1; missing a day also restarts the streak at day 1. | Example: If you skip the fourth day, the fifth day pays the day 1 reward again. |
| Achievements and profile titles | Progress | Achievements whose condition is met are unlocked when you open the achievements page. You have to claim their reward there: CC and, for some achievements, a profile title. You can equip or remove claimed titles there; at most one title is active at a time. A title is purely cosmetic. | Example: The Netwars week podium grants no CC, but the title “[Netwars Podium]”. |
| Collective | Progress | A collective is a group of players. Members share perks such as the mining cluster (+5% income rate per level), collective buildings, contracts, operations and Distributed Attacks. Collective daily tasks only appear after 72 hours of membership in the same collective; after switching, this period starts again. | Example: If you join a collective today, you get collective daily tasks in three days at the earliest. |
| Netwars week | Progress | The Netwars week is a weekly ranking of Netwars raids from Monday 00:00 to Sunday 23:59 server time. Every attack wave that deals damage counts one point, at most 40 per day; the amount of damage does not count. Equal points share the same place. Places 1 to 3 with at least 40 points receive the profile title “[Netwars Podium]” once, but no CC. The ranking tab is read-only. | Example: 60 waves in one day yield 40 week points; further waves still count fully in the raid. |
| Finished and ready to collect | Jobs | Finished research and upgrades are processed automatically. Attack results and certain rewards, on the other hand, need their own collect action. Finished therefore does not mean already credited in every view. | Example: after a mission, check the status and explicitly collect an offered reward. |