Designer225

Time reverts even farther back when the old universe was 17 Gyr old. There's the hill... No one's hill. (Forced to go back to the 21st century, Odin.)

3986: The Cassini-Hyguen mission is launched toward Hyguen (some mistakenly pronounced it "Huygen").

You ran out of cash and the government takes over. Government's hill.

Yeah, sorry. I went into editing the alliance when I took over command... didn't realize the trouble it brought...

Year 3983.1: ... until when they reorganize. then they packed up and retook others and prepared for further colonization. Although no one knew it, the Kau were gone. Year 3984: 2nd transmission from the FTL mission.

I kick all of you off the edge of the hill, and left. No one's hill. #YOLO

<WARNING: Your computer is vulnerable!> <Downloading antivirus...> ERROR ERROR ERROR ERRRRRRRRRRRRRRRRRRRRRR *sudden shutdown* I reset the server later. No one's hill.

Year 3981: When the Kau began their check before the invasion, only 2 million soldiers and no tanks are in the hangars. The rest are apparently lost while sungrazing through Kerbol. The Kau were surprised and began to retreat. More minuteships (Kerbal ships ready in just 60 seconds) came to damage the once unstoppable fleet. A scout party, meanwhile, was sent to recover the lost ships. Year 3981.1: The same month, the Kau began to reconsider their plans of "aerobraking" (or "heliobraking", rather).

I boil you. My hill.

Granted. You are paid 6000... cents. I wish for cents.

3819: It turns out the material released aren't radioactive - they are in fact hydrogen and helium gas released. The krowdfunding project continues, however. 3820: The cloud isn't moving anymore - it is beginning to move away.

3814: Wolffy was leaving the Kerbol system, at a rate of 3/8 the speed of light. Scientists noticed the unintended phenomenon.

Anyway, the war would soon end. Hope I have enough infrastructure to last through this.

Well, now all but 1 made peace. I don't think peace will be made any time soon.

3742: The Great Depression begins. 3743: The Kau Empire struggled in a period of instability due to the depression and rose into an autocracy. The Kerbals on Kerbin are aware of this and secretly built up their military and superweapons.

Kethane Nation. I've posted a food order. Anyway, finally I've decided to talk to the other attackers personally...

3612.5: The rebellion is replaced by patriotism. The invasion fleet assembled in Kerbin and Laythe launched toward Duna and Dres on a 2-day journey. 3612.5.3: The Kerbin Fleet began to invade Duna and took out all Kau facilities. The invasion was so one-sided that the 2nd Expansion Crusade was postponed until the end of June, originally planned to launch mid-May. 3612.5.4: Meanwhile, the main force was scheduled to meet in Duna to prepare for invasion by mid-May. Upon learning this, the commander decided to press toward Eve and prepare an eventual crusade that would happen in June. 3612.5.5: The Laythe Fleet laid siege onto the Dres settlement, postponing the invasion almost indefinitely. 3612.5.12: In a decisive battle, the Kerbin Fleet intercepted the Kau main force and took out the flagship and other ships of the main Kau fleet. It was so crippled that some Kau warships committed suicide by crashing into Kerbol, while others fled. 3612.5.18: The remaining of the main Kau force arrived in Dres and attempted to lift the siege. They joined the beleaguered Dres settlement after the botched attempt. At the same time the Kerbin fleet arrives in Dres and landed troops and laser and H-artilleries to bombard the settlement. 3612.5.24: Another Kau fleet arrived in the Kerbol system, intending to lift the Siege of Dres. They were intercepted near an asteroid by a smaller but smarter Kerbal fleet. 80% of the Kau fleet were destroyed (with negligible damage on the smaller Kerbal fleet) and the rest fled. The invasion is indefinitely postponed. 3612.5.24.12:25: A Kau scientist announced the Quantum Armor is researched and the Kau began to mass-produce them. Only 5 minutes later did they gave up because the manufacturing facility is severely damaged by more artilleries and troops that had been landed. And the siege closed in, with hope dwindling every day for the Kaus and no Kau rescue mission in sight.. 3612.5.24.21:25: The Kerbals managed to stay ahead of the Kaus scientifically by inventing more deadly weapons, better armors, and other stuff good for Kerbanity.

Yeah... it gradually got big thanks to others who are trying to make it more specific. Yes, however that 1000 CPU will be locked until the technology is completely researched.

The drive accidentally ...The drive hits the next poster, having slowed down considerably.

Granted. You go to China and check in in a hotel room, and there is no Floor 4 (4 is considered unlucky for some). I wish for eight!

Granted, but they are not using methamphetamine anymore. I wish that the next poster won't live in California.

I was on a plane and the shock created a recoverable turbulence. Then, for reason unknown, the wing hits the next poster.

No mention of it. Just start building military.

Day 13, 02:47:23 More novices. More inexpertly guarded servers. More victims. For some reason when I study firewall this time, I noticed an activity that caused the Thing's health to plummet. What is it? CPU: 1408 +14 passively per turn; +50 from previous tasks RAM: Used 70 MB, free 816 MB, total 886 MB 70 MB locked for cameras; +100 MB RAM from previous tasks HDD: Used 21.5 GB, Free 2525 GB, Total 2.5 TB 7 GB locked for cameras; +1024 GB from previous tasks Cameras*: 3 used, 8 idle, 11 total Enemy HP: 1400 +100 HP passively per turn, -1500 from mystery move Public Awareness Point҂: 0/50 Chance of Meeting Competitor**: 5% Repeatable Actions: 1) Hijack Weaker Server (10 CPU & 32 MB RAM; Failure 6%; [+5 CPU & +10 MB RAM] OR [+6 CPU & +10 MB RAM & +512 GB HDD] {75/25 chance}; miniscule chance of tech discovery) 2) Seize Weaker Network (40 CPU & 128 MB RAM; Failure 21%; +20 CPU & +1 passive CPU per turn & [+50 MB RAM] OR [+100 MB RAM] {50/50} & +1 Camera {10% chance}; slight chance of tech discovery) 3) Hijack Main Server (100 CPU & 512 MB RAM; Failure 31%; [+ 5 CPU & + 32 MB RAM & + 256 GB HDD & + 10 Cameras] OR [+10 CPU & +128 MB RAM] {50/50} ; small chance of tech discovery) 4) Talk to Random Human (50 CPU; 10-20% of tech discovery) 5) Create News Article (20 CPU & 64 MB RAM & 1 GB HDD; Complete Failure 18%, Failure 36%; Decreases threatening exposure҂ by 2 points if successful, by 1 point if unsuccessful - at least you calmed down the public somehow...) One-Time Actions: 5) Plant spyware (200 CPU & 205 MB; 12% failure; enables the possibility to retrieving OutPut_Log that reveals what had damaged the Thing) 6) Attack Firewall (2000 CPU & 2048 MB RAM; Failure 15%; Enemy HP +10%/100 (whichever is higher) if failed, -10%/100 (whichever is higher) if succeeded; No Botnet allowed) 7) Research Trojan Horses (1000 CPU & 1024 MB; will unlock Trojan Horses; Botnet input: -250 CPU/turn & -256 MB/turn at 80% efficiency ) 8) Research Ransomware (Stage 1/2: 1000 CPU & 1024 RAM; will unlock ransomwares, which hold files for ransom; Botnet input: -250 CPU/turn & 256 MB/turn at 80% efficiency) Option locked. Reason: Trojan Horses not researched. 9) Research CryptoLocker (500 CPU & 512 MB; Malicious; will enable the ability to encrypt & hold files for ransom; No Botnet allowed) Option locked. Reason: Ransomwares not researched. 10) Research Advanced Malware (3 Turns & 2000 CPU & 4096 MB RAM; Will unlock more potent viruses; Botnet input: -500 CPU/turn & -1024 MB/turn at 80% efficiency) 11) Continue Studying News-gathering Options (5000 CPU; Use of Botnet = -1000 CPU/turn at 100% efficiency) Supplemental Actions: Use to Modify Actions -Botnet) Use Botnet to Perform Task (CPU*0 & RAM*0; Failure +20% for smaller undertaking OR +40% for larger undertaking; no tech discovery; only 1 use per turn; Can’t use malware unless specifically allowed) -RAM) Use RAM to Improve Chances or Speed Up Research (RAM*2; [Failure*0.8] OR [CPU*0.8] {as applicable}) -LOH) Light-Out Hack (CPU*1.2; Failure*0.8 if human element present, Failure is automatic if only computer/electronics are present) -W) Use Welchia to open malware breach (10 CPU & 32 RAM; Failure*0.5; open breach for 1 turn after deployment; negates Blaster; destroys itself after turn of deployment҂҂҂; May self-destruct) - Use Blaster to breach (CPU*1.5, RAM *1.8; [Failure*0.8] OR [Failure*0.7] [75/25} ; Welchia negates) -XSS) XSS Worms (Only works on networks; Failure*0.8) -I<3U) ILOVEYOU Worm (Only works with breaching virus; Additional Failure*0.8; spams computer with "I love you" letters) -CAMY) Enable # of cameras (Talk; discovery chance*1.6; Read "*" for further information) -CAMN) Disable # of cameras (Talk; discovery chance return to normal; Read "*" for further information) NOTICE: You will NOT lose anything to performing a task, but rather an event. * Cameras are used to make talks more exciting. When not used each camera use up 0.5 GB of hard drive space and 5 MB of RAM and when in use each use up an additional 0.5 GB and 5 MB. Make sure you have a lot of CPU and RAM! ** The public awareness level determines this. It determines the frequency and the chance that you'll be meeting the competitor. Each public awareness point increase the chance by 1 percentage point when you have more than 5 public awareness points. *** Efficiency determines how much is actually reduced in the progress of researching technology. Ex. if you input 1250 CPU/turn at 80% efficiency, then only 1000 CPU is subtracted from the CPU pull requirement of 5000 CPU. All development takes 5 turns unless otherwise noted. ҂ All actions will cause threatening exposure if failed sufficiently. This is where the public is actively trying to find and destroy you. There will be more competitors finding you if you have higher public awareness level. Eached failed mission adds 1 public awareness point, and you will be in danger if your public awareness point is over 50. ҂҂ Once stopped, amount of passive CPU growth increases by 2, but in order to activate again you must again initially input 150 CPU. ҂҂҂ The deployment cost is 10 CPU (32 MB) * 2^(number of times used). Ex: If you are using it the second time, then 10 (32) * 2^(1) = 20 CPU (64 MB). Welchia will be unusable at the beginning of day 16, rendering option to use it impossible. !!! The minimum chance of failure is 5%, and some additional options get less effective over time. !!! All inputs will be attempted, until CPU’s are exhausted. !!! If there are no failed actions for 5 turns public awareness level decrease by 2 point. Be effective and cool!

0/10 Awkward...