>>14816024
Have Internbrate work with Cyberbrate to get some reactors, geothermal couplings, and the coolant systems back online on Dagobah.

Labbrate is to take a research team to the Aleman station/StarForge and find out what its purpose is.

Warbrate is to get ready to attack Dufay II.

Also, no Zerg Quest on the 25th, as I will be driving across the state to get tickets for a 6 am flight to Chicago.

Not looking forward to that part of the trip.

>>14816095
What? You can't get the tickets online and print them out yourself?

>>14816080
Despite pockets of resistance from androids still functioning underground, Internbrate is able to get troops into position near several of the power stations we saw before our orbital bombardment. It believes that reactivating these will allow Cyberbrate to activate the rest remotely. All it requires is that we give the word.

Labbrate takes control of a few units already on the station, and attempts to get it running again. Unfortunately, whenever power is restored to any portion of the ship, some of it is instantly rerouted to the surveillance cameras, and the entire station shuts down again. Without lights, power, or schematics, Labbrate can't tell us very much.

>>14816145
I'm not paying for them, and I don't have a printer. Getting past TSA with tickets you didn't purchase yourself is hard enough as-is. I don't want to complicate things and end up in Gitmo.

>>14816169
Restore power to Cyberbrate.

Have Labbrate continue searching through the Aleman station, and bring along a team of fingerlings/Infested Terrans with portable floodlights and some portable power generators.

While we're at it, quick update from Toaster on the progress of Nuke World and projects for when we can start slinging nukes around like Kingston: Soon, Gimme a Few Months, Maybe Next Year, HAHAHA...Oh wait, you're serious, let me laugh harder!

Also, from Accountantbrate and Citybrate, how is our production of new units: we're still on a war footing since VoidGate hasn't been knocked out of the fight yet.

Does our Dropserver over Brullant detect any radio transmission? Can it intercept and decrypt them?

>>14816198
The floodlights help Labbrate's team survey the station. It can safely say that the station is equipped to produce a wide range of materials, not just the large plating it was building when we arrived. It is a very versatile tool, that Labbrate considers very impressive. Still, without access to the plans and schematics of what it was constructing, that doesn't narrow the field. Hooking independent power sources into the systems doesn't help. Consoles and systems that cannot actively shut down simply lock up.

Internbrate activates the power stations. Several units report sickening grinding noises coming from parts of the machinery, and the indicator lights across the under-scape are substantially less consistent than we'd like. Cyberbrate's mind is a torrent of data that we can't fully follow. After a few minutes, it announces that the planet is operating at approximately 45% efficiency, with massive hardware failure and data corruption...but still operating, and seemingly stable.

>>14816287
Toaster indicates that Kingston's nuclear arsenal was the result of a 250-year military buildup, and is likely exhausted. It does have 20 nuclear missiles ready for our use, with more on the way.

While production is frantic, our harsh military campaigns have severely depleted our active forces, and we have very little reserve troops left.

We detect only the standard VoidGate background signals, which we still cannot decipher.

>>14816294
Well, have Labbrate continue analyzing the station. Maybe if he can find the central control systems, he can gain control of the StarForge.

As for Cyberbrate, have it begin repairs of its systems. See if it now has control of the VoidGate units that were left on the planet.

Any word from Warbrate on how soon it can send a strike force to capture Dufay II?

Also, have Cyberbrate and Internbrate attempt to decipher VoidGate's transmissions. Now that Cyberbrate has integrated with the leftover VoidGate hardware, it might be able to get something useful, such as a cipher or encryption algorithm.

Also, status update from Colonylord, please.

>>14816294
Quickly, let's make a bad decision.

>>14816400
Aw c'mon. Class gets cancelled and I can finally get here at the beginning of Zerg Quest to keep stupid decisions down, and you're already clamoring for them?

>>14816419
It was mild sarcasm, because I can't think of any new ideas to add only support already stated ideas like looking for voidgates codes.

>>14816474
The other thing we can do is begin production of more Dropservers to send throughout Protoss and Confederacy space.
Sure they're bigger than the Protoss Observers, but they're almost as good.

"Welcome to Crazy Anon's Dropserver Emporium! You need observer? Why not get dropserver, only mildly used! Is just as good and only half the price!"

>>14816474
Besides searching for those codes, you know what else Cyberbrate should look for?
That Protoss schematic database that VoidGate stole!

First:
www.obviouswinner.com/obvwin/2011/2/9/disgruntled-copywriter-i-do-anything-craigslist-ad.html

Why does this remind me so strongly of my resume?

>>14816397
There are surprisingly (or, after a moment's thought, Labbrate considers unsurprisingly) few interface devices at all. In fact, large portions of the station aren't even designed for use by anything larger than the small, automated repair drones. Labbrate doubts there is any sort of Central Control Console at all.

Cyberbrate has no means to enact repairs. The data corruption is likely irreversible, and the physical damage will require replacement parts that will need to be manufactured off-planet (as VoidGate harvested most of the planet's resources).

Warbrate estimates that a strike force could be planetside at Dufay in approximately 2 hours.

Cyberbrate declares that the communications protocols for decryption are intact, but that its security protocols are corrupted. It doubts that we will be able to send any convincing messages, though we could listen in.

Colonylord is harried, as it has been attempting to support Accountantbrate in managing our resource gathering/expenditure to keep units in production.

>>14816561
Have Labbrate look for a communications array.
Also begin analysis. It will take much longer than if the station was online, but we might be able to gain SOME information from the station.

Have Internbrate assist Cyberbrate in the manufacture of replacement components. Use the fabrication facilities on Yoshus.

Have Cyberbrate begin decoding VoidGate's transmissions. If we can learn what it's doing, then that should be helpful.

Warbrate is to prepare a strike force to attack and take over Dufay II. Give him 3 hours to prepare appropriately.

Also, any word on the stolen Protoss unit schematic database, or how much of the Protoss Science Archives that VoidGate was able to leach away?

>>14816541
We decided on making more last thread.
>>14816556
I blame not having ZQ last week for that forgetery.

>>14816664
Totally not my fault. I had the whole first post typed up and ready to go, but 4chan was broken. I whined profusely, but it wouldn't listen.

>>14816661
Labbrate would like to clarify: we have NO systems access. Everything is still strictly under AI control on the station, and even if we had access to the computer cores to wipe VoidGate, we have no way of knowing which drives store VoidGate's code, and which store the schematics we want. It can attempt to locate major drives, and gain physical access to them, and we can decide which ones to wipe, but we won't know if we've wiped the right ones unless...well, unless we've wiped the right ones.

Internbrate points out that refitting a planetary-core-size computer will require halting construction of Protoss and Terran ships for some time.

We begin decrypting messages from Brullant, the only system actively producing comm chatter. After sifting through hundreds of thousands of base-line individual unit commands, we stumble upon a schematic of one of the things under construction on the surface: a massive plasma cannon, fully capable of destroying an orbiting carrier with a single blast.

Warbrate claims to be ready now. As ready as it can be, anyway.

Cyberbrate tells us that fragmented logfiles indicate that VoidGate was unable to obtain the Protoss Science Database before our attack. Roughly 82% of Protoss unit schematics are available in its databanks.

>>14816812
I wasn't blaming you, I saw that the last new post came from 3 hours earlier.

So a giant photon cannon that can one shot a carrier. I don't like it, I think this job calls for nukes. Nukes and violence, mayhapse fisticuffs as well?

>>14816812
Please list what Protoss units we can now produce.

Have Labbrate continue searching for those computer cores. If nothing else, we can wipe all of the cores, set up a communications array, and have Cyberbrate take control of the StarForge.
But once the cores have been identified, I'd like to have Cyberbrate attempt to tell them apart by using whatever design scheme that still remains in the Dagobah computer logs on how VoidGate would have set up or designed the station's computer systems.

I also think that getting Cyberbrate up and fully operational is going to be important. Bring the Xenta shipyards off-line to produce the necessary components; if it has to be Yoshus, however, so be it. Switch the production from ships to computer parts.

Can the information from Brullant give us an estimated time of completion for the plasma cannon? We will need to attack before they can finish it, if possible.

Finally, order Warbrate to attack Dufay II and capture it, for the glory of the Swarm!

Can we hunt down the registry files?

>>14816900
Probe
Dragoon (requires immolated Protoss)
Zealot (requires really excitable non-immolated Protoss)
Carrier
Corsair (development notes indicate lack of sufficient battlefield testing)
Observer
Reaver (Scarab designs unavailable)
Scout
Shuttle (unit computer programming unavailable)
Arbiter (requires multidimensional base materials)
Multiple designs for Templar robes and MASSIVE PAULDRONS available, but likely useless.

Labbrate identifies the four largest drives, where mission-critical information and VoidGate's primary code would likely be stored. However, they are virtually identical. We can wipe any or all of them at any time.

(1 vote to quit producing non-Zerg units and focus on repairing Dagobah. Need 3 for that, what with the whole war-footing production thing)

Cyberbrate is sorting through an entire planet's-worth of comm on the fly, but it seems to indicate that at least two are under construction at the moment, and at least one of the two is "critically near completion," though exactly what that means is unclear.

Warbrate delays the attack briefly, giving us the psionic equivalent of a sly wink. As our forces arrive, the planet's cloaking field finally loses power and collapses, revealing the world to our troops. The planet is woefully underdefended, and all combat-ready hostiles are destroyed after half an hour, with minimal casualties (Accountantbrate still complains, as it will take nearly two hours to recoup those losses). The processing centers are still operational, and Warbrate isn't sure what we want to do with them.

>>14816926
(Error: the file you wish to access is in use. Please restart your computer and try again.)

>>14817083
I say we holdoff on fixing Dagoba until voidgate is dead. And what processing centers? If they're on Bulfry then destroy them. Also, MASSIVE TEMPLAR PAULDRONS ARE ALWAYS USEFUL! WE SHALL DRESS OUR DORSAL RIDGE SCRATCHIER IN AS A HIGH TEMPLAR!

>>14817083
Have Saberhagen, Wormface, and Toaster look over the Protoss Probe designs to see if they can be helpful in their construction queues. They won't help with Zerg structures, but being machines they might help in the manufacture of our Terran and Protoss-based units.

Since I was the one to want to switch production to computer parts, my vote is still there.
If we can't get enough support to stop ship production, have the next resource rich planet that Colonylord finds be slated to be a computer part foundry world.

Have Internbrate look over the manufacturing systems that are on Dufay II. It may be useful as another manufacturing center. Warbrate is to secure the planet. Cyberbrate, check any communications being sent from Dufay II. Make sure that there are no nuclear self-destructs on-board.

>>14817165
No, the assemblies aren't on Brullant, they're on Dufay II which we just captured.

Also, I'm voting for Cyberbrate to take a look at the computer cores on the StarForge/Aleman Station to see if there's any way to tell them apart.

If not, I say start wiping them one at a time, attempting to restore power each time to see if we got VoidGate.

>>14817165
We are overcome with a desire to garb our buxom ridge scratcher in the mighty pauldrons of the Templar. Wearing nothing else, they curly menacingly past her head. This won't actually DO anything, but damned if she won't be stylish for an otherwise nude human.

>>14817188
Toaster studies the trickier parts of carrier construction, and we can tell it feels very stupid for not being able to streamline the process of production sooner. However, integrating any of this into Terran designs, or improving upon it, would definitely be something it would defer to Labbrate.

(Still 1 vote)

Very few manufacturing facilities are present. In fact, they all seem to be in mothballs, ready for an extremely long period of downtime. The comm center (there is only one) released a quick burst of high-density signal once our victory became inevitable, and then went silent. Cyberbrate is trying to decrypt, but tells us that the decryption algorithm seems to be modified, so not all of the information makes sense. The gist of what it has is a situation report, and a counter that repeats the number 1 many times. While nuclear batteries and the materials for nuclear missiles are present, there are no obvious self-destruct devices on the planet.

>>14816812

An odd thought just occurred to me.

There are hints that Dufay is some sort of escape pod for Voidgate. However, this doesn't make sense because:

1. Dufay is SLOW when you look at distances it would need to travel to be an escape pod (I think there was mention of it taking tens of thousands of years to leave the sector).

2. Voidgate doesn't NEED a planet in order to escape. However it got to our sector, it wasn't by flying on a multi-trillion tonne rock.

3. It does not have the fuel to both remain cloaked indefinitely or accelerate for more than a few hours.

What we have here is a cloaked-multi-trillion-tonne rock. Two possibilities:

1. The entire planet is a huge lump of raw resources for some sort of gargantuan mining operation and is being sent somewhere for processing and refining.

2. Voidgate is chucking a (cloaked) rock at something. Presumably us.

Regardless of whether or not I am correct, the first priority is to gain immediately control of the steering mechanism or to tamper with the navigation system of this damn planet.

The second priority is to find out WHERE THE DAMN ROCK IS AIMED AT.

If it's aimed at one of our planets, evacuate or try to divert the planet.

If it's aimed at 'the middle of nowhere' send overlords there ASAP to investigate.

We don't want too many zerg forces (and certainly not a cerebrate) to be stuck on a rock headed to armaggedon.

>>14817313
Have Internbrate direct a team of thumblings to see if schematics for VoidGate's infantry plasma weapons and its androids are on Dufay II.

I'm voting to have Labbrate randomly pick one core and wipe it, then try turning the power back on. If this doesn't clear out VoidGate from the Aleman Station, proceed to wipe the next drive in line, until we have the station cleaned out.

>>14817214
Cyberbrate indicates that files concerning the Aleman station appear to have been deliberately deleted prior to the planet's deactivation. Partial recovery identifies one of the drives as containing a VoidGate backup for immediate activation in the case that the primary drive is disabled, but information on the other two drives is unavailable. We will either have to erase both, or pick one (So, you know, vote on that. 1, 2, or both. I promise I won't cheat, no matter how much giving you the mission-critical data has the potential to make you gods among...men? Worms? Whatever).

>>14817349
Inasmuch as the planet burned away most of its core before our attack and is running entirely on momentum, the navigation is locked. Nevertheless, we set Labbrate to calculate its trajectory.

After a few minutes of advanced gravitational computation, calculation of stellar drift, and logarithms, Labbrate states that after approximately 24,200 years, the planet will become a captured body in the Lutrious system, an unexplored star system (that, for narrative purposes, is outside of the Koprulu Sector, even though the planet is traveling at sublight speeds, and thus shouldn't get anywhere that far in a LONG time).

A unit using Warp techniques could likely reach the system in a matter of weeks.

>>14817434
(You, sir, have the chance to re-vote! See above)

While there are interface devices on Dufay, none of them respond to our units. They all display the same message:

>Mission Failed.
>Planet Lost.
>_

>>14817482
I say hold off on wiping drives for a bit, After all where did Voidgate send that transmission?

>>14817553
For the sake of moving things along...Please vote.

Jolly, candylike button, can you resist, etc.

>>14817482
I vote to delete both VoidGate AI cores.

>>14817571
Fine let's wipe both just to be sure.

>>14817629
Wait, VoidGate might have put in a fail-safe to have the station self-destruct if both AI cores get wiped.
But then again, if we delete the primary and allow the secondary VoidGate copy to come online, it might decide to self-destruct the station anyway, to prevent it from falling into our claws.
But if we do nothing, then the station is as good as destroyed since we can't use it.

Great, Cerebrate Anon, now you're making me second-guess my vote to wipe both AI's.

>>14817482

Is there any way to open channels of communication with Void Gate again? I'm assuming that 'dense package of data' that escaped was either aimed at Void Gate or was Void Gate itself so we can locate him relatively easily.

I propose that we offer to return possession of Dufay back to him in return for a non-aggression pact, a promise to abandon the sector and the keys, codes and locations to all Void Gate assets in the sector.

Depending on its answer we'll have a better idea of whether or not he's REALLY leaving for good or just planning a counter-attack at some stage.

Also, since its 'escape pod' is so ludicrously slow, there's little chance on it trying to cheat us by self-destructing all Void Gate assets after we say goodbye.

No, no, no. I assumed you were going to delete the backup VoidGate just because...you know, what's the point of hitting the primary if you leave the backup? That's silly.

The question is which of the remaining drives (one of which holds the primary VoidGate code, and the other holds the plans for what the station was building) you're wiping. If you pick the right one to leave, then you get the plans for whatever super-construction VoidGate was making.

>>14817726
OH! That's what you meant.
So 3 of the 4 drives contains VoidGate code, and only 1 has the schematics we want?

Well, if that's the case, why not wipe the 2 drives we know have VoidGate on them, and then have Cyberbrate send dummy data to the two remaining drives to see how they respond, and getter a better gut-feeling for which one is the VoidGate and which one has the schematics.

rolled 2 = 2

>>14817726

>>14817771
Is that a vote for two, or just flipping a 1d2 to determine which drive to wipe?

>>14817769
(Huh. I did originally say there were 4, didn't I? How silly of me. Whatever. Yes. You are picking from 2 drives, one of which will be awesome for you, and the other not so awesome. I'm going to go ahead and say outright that trying your plan will immediately alert VoidGate, and it will react. Just pick 1, 2, or both)

>>14817771
Ok, so one vote for wiping drive 2.

>>14817726
I vote "wait".

We only have a 1 in 4 chance of getting it right and there's no reason to rush at the moment.

If we can I'd like to see if we could blackmail Void Gate into telling us the correct answer.

>>14817821
Voting for 1 drive, then.

>>14817813
yes

>>14817826
>If we can I'd like to see if we could blackmail Void Gate into telling us the correct answer.
What? VoidGate is an AI that has shown that it doesn't a give a shit about its copies as long as they serve their purpose. Why would it turn over the operation of the Aleman Station to us, when it can just build another one once it has its primary base secured?

>>14817826
See
>>14817571
(If you wait, this shit goes undone for another week)

>>14817836
1: 1
2: 1
Both: 0

Awaiting the tiebreaker Gotham deserves,

>>14817844
Damnit TUCAMP, you're standing in the way of potential progress. What reason do you have to wiping both drives, when we could still get away with one?

Why could this not be earlier so I could join. Oh well, WOO ZERG QUEST.

>>14817968
... I'm currently the vote for drive #2... so calm down.

>>14817975
Uh...no.
See >>14817821
Your vote is being counted to wipe both drives.
If that's not correct, then say so.

>>14817985
Uh yes it is see
>>14817930
and reread
>>14817821

Somebody vote for something, damnit!

>>14818014
Alright. I concede that your vote was for Drive #2.

Which I still think is the wrong choice, but in the interest of getting this moving again, I'll change my vote from Drive #1 to Drive #2.

If this turns out to be wrong, I will never let it go and hound you every chance I get, TUCAMP.

>>14817930
Just wipe drive 2...
Unless we could make a backup from both drives, and then wipe the original drives; of course this is irrelevant if we could just isolate the original drives from the station.

>>14818072
I take no responsibility, it was the tg dice, but last time I used them I was able to land an overlord on a cloaked planet.

>>14818107
You still rolled the dice. It's still your fault.

>>14818072
>>14818076
Well, the good news is that I don't have to decide whether to jerk you guys around on the timetable for building a Dyson Sphere, because you just erased the plans for it.

The bad news is, you just erased the plans for VoidGate's totally awesome Dyson Sphere.

On the plus side, despite alarm klaxons sounding and doors sealing shut, there doesn't appear to be any sort of self-destruct mechanism going off.

>>14818120
Well, if it's only a Dyson Sphere then nothing of value was lost.

>>14818120
God-fucking-damnit.

Wipe the other drive free of VoidGate. Maybe we can still use the Aleman Station as a manufacturing center.

Cerebrate Anon, can we use the Aleman Station as another shipyard?

>>14818132
I repeat: a Totally Awesome Dyson Sphere. None of that "habitable inner side" shit. All "computer that needs ships, nukes, and computing power"-oriented. It would have been pretty glorious.

>>14818139
After a bit of chasing around from drive to drive, Labbrate manages to wipe out the last of VoidGate's code in the station's systems. The station's systems are now responding. If we can figure out how to work them, we can use them as we will.

>>14818172
and I think that the timeframe to build it would be similar to out terran breeding program, longer then the quest will run... maybe

>>14818216
Well, the timeframe is "never" now, so whatever.

Anyway, so...

Brullant remains a threat. Dufay has been pacified, but VoidGate remains operational within the computer systems of the planet, which is careening very slowly toward the Lutrious system, a distant, unexplored star system.

Go.

>>14818172
Bring Labbrate back, and have him work on using our newly acquired Protoss probe, carrier, and observer schematics to help improve our Terran technologies.

I'm looking at probes to assist in automated construction, carriers shielding systems integrated into battlecruisers, and the Observer's sensor package to upgrade the ones on our dropservers.

Internbrate is to be given Aleman Station as his project. His final goal is to turn it into a manufacturing facility that can truly be called a StarForge.

Warbrate is to begin planning an assault on Brullant. We will have a week to replenish our depleted forces.

>>14818245
Remove VoidGate from the Dufay computer systems.
Prepare a dropserver and observer pair to be sent to the Lutrious System, along with a squadron of Mutalisks and a cloak Overlord carrying several drones to be launched as soon as they roll off the assembly lines.

>>14818245
Check out Lutrious, poke the starforge with a stick until it works, double check for any other traces of voidgate, check in on artisanlord.zergTV

>>14818288
Warbrate pleads with us not to send combat troops. Its forces are severely depleted, and it knows we're contemplating an attack on Brullant, which, from all the comm chatter, is obviously crawling with hostiles.

>>14818262
Labbrate wishes to know just what we want from this mesh of Terran and Protoss tech. We already have Protoss shielding technology, and the complex Protoss machinery requires more time and resources to complete. The observer sensor suite is essentially too sensitive to function on a much larger vessel. What is the goal?

Internbrate sets to work. It may take time to reprogram the systems and work out the oddities of VoidGate's designs, though.

>>14818296
We are somewhat concerned about Artisanlord. It has evolved hair follicles, and grown large bangs that hang over its eyes, and ZergTV has a lot more teen Drone dramas than we remember...

Surely, it's just a phase.

>>14818348
I think what's wanted is to slap the dragoon cannon onto stuff, but I'd say we should build some corsairs for testing.

>>14818363
Clearly what's needed is competitive cooking shows, obstacle courses, and Larva & Order marathons

>>14818348
Build a few Corsairs to try them out.

Acquiesce to Warbrate's advice, and send only the Dropserver-Observer pair to Lutrious.

As for what I want from meshing Protoss and Terran tech further, I'd like to see if the Protoss probes can be used alongside our SVC's to cut down construction time on Terran and Protoss units.
I want to see if Dragoon photon cannons can be used on Wraiths and if the gausslisks could mount the Dragoon weaponry.

>>14818442
Why not put the scouts antimatter missiles into wraiths? Which begs the question of why we haven't done that? Also, cane we figure out how the carrier beam works.

>>14818434
Artisanlord's dark mood breaks almost instantly after we propose Larva and Order. It immediately changes its hair to a very distinctive salt-and-pepper color...

>>14818442
>>14818378
Toaster diverts a bit of its time from Nuke World to begin construction of corsairs. The Protoss seem to have begun developing them more than a century ago, but still consider them "too new and unproven."

An observer and one of our dropservers begins the long trek to Lutrious.

Unfortunately, the bulky dragoon cannon is incompatible with our gausslisks, short of a chest-mounted version, which would hinder all other gausslisk functions.

The cannon could be added to a wraith in place of its standard weapon, but would increase build times for wraiths.

>>14818499
>The cannon could be added to a wraith in place of its standard weapon, but would increase build times for wraiths.
Begin construction of an experimental squadron of Wraiths equipped with the Dragoon cannons. Allow Warbrate to test them out, and return to us with a report as to their effectiveness. Does he believe that the increased damage potential is worth the increased time and resource investment?
Might as well put his experience to use.

>>14818518
Warbrate considers this for a while, and concludes that at this point, anything that keeps our forces from being rebuilt as soon and as cheaply as possible is a mistake. Accountantbrate, if it had eyes, would tear up at the sentiment.

>>14818545
Quick, glue a pair of googly eyes to accountbrate.

>>14818567
I wish Zerg Quest had more drawfags.

>>14818545
Very well.
Table the up-gunned Wraith design for now. We will revisit it when we have more resources to spare.
Our current priority should be replenishing our forces in preparation for an invasion of the Brullant system.

>>14818499
Although the real question is, will Larva and Order run as long as Brate-anza did?

>>14818585
I don't know. It doesn't have to run against the Dukes of Korhol, so it might not be a fair comparison.

>>14818573
Done lazily, I think making them asymmetric is funnier

So, I take it we're more or less wrapping up for the night, then?

>>14818619
Current plan seems to be to replenish our forces,check Lutrious, test corsairs, and fiddle with the starforge.

>>14818619
Replenish our forces and build up our nuclear stockpile for a massive nuclear strike on Brullant when we attack.
Test the corsairs.
Have Internbrate examine the Aleman Station.
Cyberbrate to use it's knowledge of VoidGate's communication frequencies to come up with an ECM drone which will interfere with VoidGate's communications.
If the Terrans built a Psi Disruptor, it's only fair that we build an ECM system to counter VoidGate's communications.

Waiting on word from our Lutrious expedition.

Nothing cures emo overlords better then larva and order.

>>14818659
Takes a while, takes a while, takes a while, and takes a while.

Alright...well, then, we'll have a TIME JUMP next week.

Perhaps as time passes in reality, it will ALSO pass in Zerg Quest!

Almost like it's happening in REALTIME!

Only not, because that's preposterous.

Anyway, http://suptg.thisisnotatrueending.com/archive/14816024/

I'm still amazed, by the way, that you guys haven't picked up on VoidGate's Terminator-based weakness. Every week. Pic completely unrelated, though.

>>14818721
OMG A GIANT ELECTROMAGNET! Why didn't I think of this before.

>>14818721
>Terminator-based weakness
What, we find a Terran boy named John Connor, and watch as VoidGate drops everything as it tries to eliminate the boy from the timestream?

>>14818737

>>14818707
I totally started out by saying Lutrious was a 24,000 year journey at sublight, or weeks of travel in warp. You're not just going to pop out, because SC warp travel isn't foldspace so much as hyperspace. It's never really a big point, but it's mentioned.

Theoretically, all of the main characters are hopping in and out of Cold Sleep Chambers between battles for the weeks or months it takes to get to the next one. This is mentioned briefly in Brood War (I hope you found your Cold Sleep Chamber...accommodating?), and explicitly stated in the manual.

I don't know why I'm going over this, though. Did I have a point?

>>14818762
We could attack enemy forces in cold-sleep somehow, and annihilate them while they can't retaliate?

Terminator-related weakness... no psionic potential? Something like how Necrons are extra weak against psykers?

>>14818794
There's not really any precedent for pulling somebody OUT of warp. I'm going to assume it's not possible for simplicity's sake, since I'm already derping the travel times down to nothing for the same reason.

This is yet another reason that Blizzard's official timeline makes no sense, but another reason that neither does Zerg Quest's, so I can't claim to have the high ground.

>>14818794
>>14818739
>>14818737
Nope, nope, and nope, btw.

Anyway. Bedtime, before one of you starts marathoning the movies looking for a weakness.