These forums are archival. Please visit us on discord!
== 7.009 ==* Fixed a bug where 7.008 wasn't reading in some recent saves correctly (looking for "True" or "False" instead of "1" or "0" on some of the "has this planet had this hack before" flags), causing those saves to not be playable.** Thanks to Zair for the report and save.
== 7.008 More Dirty Tricks ==* Spirecraft Scouts no longer count as "major weapons" (like all other spirecraft) for the purpose of alerting planets. So in general they shouldn't cause much alert.** Thanks to TechSY730 and many others for inspiring this change.=== Hacking, Round 3 ===* Added new type of placeable for the Hacker: Sabotage Hacker** In-game description:*** Only works on a planet with an intact AI command station, but hacks into that station's network to destroy an important AI-controlled structure on the planet. Eligible targets include fortresses, forcefields, ion cannons, mass drivers, warhead interceptors, armor inhibitors/boosters, blackhole machines, distribution nodes, Zenith reserves, interplanetary munitions boosters, raid engines, alarm posts, radar jammers, gravity drills, troop accelerators, and AI Eyes.*** If more than one eligible target is present on the planet, the one closest to the hacker will be destroyed. If multiple sabotage hackers are used, each will destroy a separate target.*** The AI will notice the hacking in progress and respond against your units both on that planet and nearby.*** NOTE: Successfully destroying a unit via sabotage reduces your Hacking-Progress by 2. Each hack after that costs 1.5x the previous.* Added new type of placeable for the Hacker: Sensor Hacker** In-game description:*** Only works on a planet with an intact AI command station, but hacks into that station's network to disrupt the entire local AI sensor net. This grants all human ships on the planet the normal cloaking ability and suppresses all AI tachyon sources. All normal "must recharge cloak after firing" rules still apply. In addition, all AI cloaked/camouflaged units are revealed for the duration of the hack.*** The hack takes 30 seconds to start, and lasts for 35 seconds. Further sensor hacks during that time (by the original hacker or another one) simply refresh the duration, but also trigger the hacking-progress cost again.*** The AI will notice the hacking in progress and respond both on that planet and nearby.*** NOTE: Successfully performing a sensor-hack reduces your Hacking-Progress by 10. Each hack after that costs 1.5x the previous.* Fixed a bug where the hacking response logic that was supposed to trigger a 30-second wave against the planet being hacked would instead do warp-anywhere logic if that particular planet was ineligible for normal waves. Counterwaves are valid hacking responses too (at a certain point) but are supposed to give 4 minutes warning.** Thanks to Zeyrun, Eternaly_Lost, and others for reporting.
Does destroying AI buildings with hacking incur the AIP increase that would come by shooting it?
Our wiki is of the opinion that it shouldn't be edited right now (some funny business with session tracking, it seems) so I'm keeping these here until that's sorted out.
Quote from: keith.lamothe on July 22, 2013, 02:36:51 pmOur wiki is of the opinion that it shouldn't be edited right now (some funny business with session tracking, it seems) so I'm keeping these here until that's sorted out.[dumb_suggestion]Um, have you tried rebooting it?[/dumb_suggestion]
Quote from: TechSY730 on July 22, 2013, 09:15:46 pmQuote from: keith.lamothe on July 22, 2013, 02:36:51 pmOur wiki is of the opinion that it shouldn't be edited right now (some funny business with session tracking, it seems) so I'm keeping these here until that's sorted out.[dumb_suggestion]Um, have you tried rebooting it?[/dumb_suggestion]"Hello, IT. Have you tried turning it off and on again?"
Quote from: Tridus on July 23, 2013, 07:45:26 amQuote from: TechSY730 on July 22, 2013, 09:15:46 pmQuote from: keith.lamothe on July 22, 2013, 02:36:51 pmOur wiki is of the opinion that it shouldn't be edited right now (some funny business with session tracking, it seems) so I'm keeping these here until that's sorted out.[dumb_suggestion]Um, have you tried rebooting it?[/dumb_suggestion]"Hello, IT. Have you tried turning it off and on again?"Have you checked to make sure it's plugged in?
Is there a glowing light on the big thing on the floor?