>>14662402
Clyde

>>14662402
Also, lets send dropserves to the three other planets to check.

(Minecraft has ACHIEVEMENTS now? I don't stand a chance of leaving the house tomorrow, now.)

>>14662439
(You want to name the newest cerebrate of the Swarm, destined to interface with a planet-sized computer...Clyde?)

>>14662531
You have a problem with the Cerabrate Logrithmic Yodeling Database Emulator?

I can't spell my own name today

>>14662590
(Logarithmic Yodeling? I don't know. Bernie might feel jealous of the audacity)

Seconding sending dropservers to suspected VoidGate-held worlds, also suggesting Cipher as the name for our new cerebrate.

>>14662614
I was having trouble think of Y words. Though I do like the acronym idea.

Zergputer. Easy.

>>14662653
How about Ivan, Integrated Vernticles And Neurons

We continue pondering names.

Odd thoughts cross our mind, such as Clyde. More traditional computer-themed names like Cipher or Daemon filter through, as well. Zerg-centric ones occur to us. Cyberbrate. Robobrate. Digibrate. That sort of thing.

>>14662701
Infested Video And Networks

Maybe Boris, Big Original Registry Infestation Service

>>14662759
Mental Operator Of Stupendous Non-Standard QUasi-Infinite Reckoning Laptop?

Obviously the new cerabrate is named Robobrate.

>>14662712
I second the first option that is not an acronym of any kind.

>>14662653
I am supporting Cypher as the name of this new cerebrate.

>>14662853
Moosnsquirl?

>>14662884
>>14662895
(Sudden windfall of votes for Cipher?)

>>14662905
Yes, as long as it's not an acronym for anything.

>>14662901
Jes, Natasha. Vee get moosnsquirl.

In hindsight... 100% in support of Cyberbrate.

>>14662402

We are NOT the Overmind, though we are creating pseudo/semi-cerebrates.

Ask it what it thinks its name should be. It will be a test of its sapience and we might be able to get a rough feel for its personality. Also it might placate nargil a bit.

>>14662905

Obviously is must be named CAVE

Cerebrate and virtual emulator.

He must speak with a 50's american accent.

>>14662884
>>14662895
But Cipher is a dull name,

>>14662895
Sure, let's go with that.

>>14662916
The name will be Captain Wrong-Way Peachfuzz!
>>14662921
That works too. But, adding "and Infested Networks" would make it "CAVE IN." Take that VoidGate.

In the interest of this entire thread not being an acronym contest, can we decisively vote on one of the names put forward so far?

Clyde, Boris, Zergputer, Ivan, Boris, Robobrate, or Cyberbrate?

I live!
Seriously, its been a long time since I have used this name.

So Cypher for the new Cerabrate?
works for me.

>>14662971
You did not include Cypher as one of the choices, even though it's currently leading in votes.

Cyberbrate.

>>14662971
Boris

>>14663022
Whoa. My bad. I must have seen Clyde and thought it was Cipher.

>>14662971
Clyde.

>>14663045
I am in support of whatever is NOT an acronym.

>>14663051
That would be Cipher, or any of the ones that end in 'brate.

>>14663085

Cipherbrate, then.

>>14662971
Cyberbrate.

>>14662971
Cyberbrate

In the interest of compromise, how about we go with Unnameable as the name of the cerebrate.

>>14663120
No. I cannot support that decision.
My vote is still to Cipher.

>>14663152
I thought it was clever due to the Lovecraft reference.

>>14663167
Yeah, I saw the reference, but no. It's not a good name for something that is not a Bernie abomination.

We're plopping a cerebrate onto a planet sized computer in the hopes of learning all of voidgate's stuff, if this goes wrong we will have made a horrible abomination, Nargil certainly thinks we've made one already.

>>14663099
>>14663116
>>14663032
(HA!)

Cyberbrate takes a moment to acclimatize itself with the world, then asks us what we wish of it.

A dropserver arrives over what was once a Terran arsenal world, Brullant VI. This world's people and industry manufactured, stored, marketed, and sold a wide range of weapons for both the civilian and government markets. When it dropped off the grid, Fear gripped the Confederacy. It is obvious from our initial scans that VoidGate is here. The debris and slight nuclear fallout littering the star system are telltale signs by this point. Detector satellites are in orbit, so a close approach is inadvisable, but first reports indicated a LOT of movement on the surface.

Conversely, Dufay II, the inhabited world in the Dufay Majora system, is missing entirely. The fallout and debris are there. The first planet is there. The planet...is not.

>>14663256
go and like get all in that computer mainframe and integrate technology with our consciousness, bro. Shit will be awesome

>>14663256
Well, at least it's what we all agreed to call it in the last thread. Let's check the last potential voidgate world, then air the dropserver footage of Brullant VI and the other one if voidgate is there. No reason to let kingston keep those nukes.

>>14663256
Project where the 2nd planet in Dufay Majora would be from navigational charts and past movement data. It's obviously still there, just cloaked.

Brullant VI should be filmed on ZergTV and Kingston'd.

>>14663256
Cyberbrate is to be transported to Dagobah and integrated into the VoidGate computer system under the watchful ministrations of Labbrate and Internbrate.

As for the Dufay Majora system, continue sweeping it and analyzing it to see what happened to Dufay II.

What is the progress of Nuke World?

>>14663324
>>14663326
>>14663300
Labbrate arranges for a Creep coverage to precede Cyberbrate, allowing it to take root over the processing center of Dagobah. It begins intertwining with the circuitry.

Footage of Brullant is a little more vague than that of Olayhus was, since we can't get close, but one can tell that the world is no longer Terran, and the continents are still recognizable enough to confirm the location. If we decide to send this information to Kingston, we will need another story, though. We only goaded him into attacking before by claiming that the fleet in orbit was preparing to invade. There is no fleet, here.

After some quick number crunching, Internbrate determines where Dufay II ought to be. As the dropserver pulls closer, the instruments suddenly indicate a massive cloaking field, and a gravity well. The ship turns sharply to avoid a fatal descent into an invisible atmosphere.

>>14663370
Toaster is happy to announce that we have 22 nuclear missiles ready to fire, with infrastructure laid for another 20 by the day's end.

>>14663431
Pull the Dropserver back from Dufay II, and send in a Cloaked Overlord in its place. We need to see just how VoidGate is able to generate such a massive cloak, and what it's doing.

Also, we need a status on Nuke World and on our military production and resource stores.

>>14663451
Tell Toaster that it has done well. Continue non-stop production of nukes.

>>14663431
Can we get a dropserver to the third potential planet?

>>14663510
We...never actually built a third one.

Which planet do you want to quit watching?

>>14663517
Well, let's build another Dropserver, then!

>>14663517
Dufay II, and SpAWN MOR DROPSERVERS.

>>14663517
Pull the Dropserver from Dufay II, and send it to the third VoidGate candidate world.
Have a cloaked Overlord take up duties on Dufay II, and attempt to penetrate the cloaking field.

And construct more dropservers.

How expensive is a dropserver? We should try to have 8, so build an extra 6, if they're not extremely expensive.

>>14663522
It takes a few hours, but we churn out another of our bastardized machines.

Aleman Beta, a former governmentally-unaffiliated colony (read: major pirate haven), was, militarily and fiscally, nearly as powerful as Umoja...before contact was lost. Despite the fear caused by such a powerful entity seemingly falling off the face of the galaxy, most of the Confederate citizenry was alright with the nuisance of this "pirate empire" being gone.

Our first impression of the planet is that it is smaller than we expected. We confirm this to be caused by the four unique craft that appear to be tearing parts of the crust away from the planet and carrying it to a large facility orbiting the sun. We don't read any detector satellites.

>>14663618
Move the dropserver closer to one of those unique ships, and begin passive scanning. I want Labbrate to analyze the footage later.
Follow the ship to the processing plant and see what's being constructed. Once we've collected all the useful passive data, begin active scanning.

>>14663618
We must investigate this facility near the star.

>>14663618
Okay, so one planet is Massively Cloaked, one has Cloaked Detectors (or no detectors), and the other has Cloaked Detectors (or no detectors).
Either their fleets are cloaked, or not present.

I'd say, we need to orbital bombard the everloving shite out of one of the planets. I'd go for:
Brullant VI first, since it's obviously already active
Then Dufay II, since it's cloaked and we're not sure. The unknown is usualy not good
Finally, Aleman Beta, since it'll take a long time for their sun facility to get up and running.

>>14663639
>>14663640
The craft are massive, but simple. They gather broad swathes of the planet's surface, break free of its gravity, and deliver their cargo to the satellite.

The satellite is similarly massive, but appears incredibly complex. We aren't even sure exactly what it is doing, though it appears to have just recently begun operation. There are several massive panels nearby, being dragged into heliocentric orbits by what appear to be modified VoidGate combat craft.

Labbrate feels awestruck.

>>14663666
Our production should focus on Space power - Orbital ships with the power to bombard a planet, and smaller ships that can defend the Big guns while in orbit. This seems to be where Google is weak.

>>14663666
(In case you missed it, Brullant has a fully functional detector satellite grid in place)

>>14663690
I do not like Voidgate trying to reconstruct itself by rebuilding a planet.

>>14663666
No. Your plan is flawed and a waste of resources.

Cerebrate, have the Dropserver in the Brullant system begin patrolling the system to see if there are any cloaked fleets.
We need the cloaked Overlord in the Dufay system to penetrate Dufay II's cloaking field to see what's going on.
Finally we need to see what the ships and orbital facility are in the Aleman Beta system.
Since Aleman Beta is still under construction, it should be our first priority to attack its weak defenses and attempt to capture the facility.

>>14663714
Balls.
>>14663723
Right, that makes sense. Alemann Beta first, and after we see through the cloaking field, we can choose which target to go after next.

>>14663690
VoidGate is trying to build a StarForge. We must not allow that to happen, and we must also capture it and take it for ourselves.

>>14663691
Why do you keep on spouting terrible ideas and plans? Why don't you just shut up.

>>14663723
>>14663666
Plans so far:
Attack Brullant: 1
Attack Aleman: 1
Try to get Kingston to attack Brullant: 1

Am I missing anything?

>>14663743
These so-called "terrible" ideas and plans seem pretty good!
Why are you so mad?

>>14663747
You need to put up the recon plans for Brullant and Dufay.

>>14663739
I'm sure we can send a dozen cloaked overlord into the cloaked planet to see what's going on, no need to be particularly careful with cloaked overlords.

>>14663767
No one supports your ideas That should be an indication of whether your ideas are good ones or not.

I've seen this trend in all of the quests that you post in; your ideas are generally considered ill-thought out and wasteful.
You contribute nothing of value.

>>14663747
Attack Aleman

>>14663747
>>14663768
Attack Brullant: 0
Attack Aleman: 2
Try to get Kingston to attack Brullant: 1
Fly all around Brullant to check for cloaked ships: 1
Get closer to Dufay to see what's going on: 1

>your ideas are generally considered ill-thought out and wasteful
By you, maybe. :P

>>14663791
Attack Aleman
Fly around Brullant to find any cloaked fleets.
Send in cloaked overlords to find out what's going on with Dufay.

>>14663788
Zerg Quest has a long and storied history of bad plans and bad decisions!

He'll fit right in!

>>14663791
What would it take to convince Kingston to attack another planet? What did we do last time? Can it be redone, or are there differences between then and now? If so, what's different? Should be possible, with some thought.

>>14663819
Seems wise. Build 1 more Dropserver in case our current one gets picked off.

>>14663821
What, in your opinion, was the biggest messup plan thus far this quest?

>Fly all around Brullant to check for cloaked ships
>Get closer to Dufay to see what's going on
Cloaked overlords everywhere.

>>14663833
There was a gigantic fleet over that world that we didn't want to deal with. We broadcast to all of the remaining Confederates that it was an invasion force aimed at them (even though it wasn't) and that we were too busy striking at key staging points to devote resources to the battle (we weren't).

There's no fleet, here. It's just a world with a serious amount of stuff going down on the surface that we can't quite make out because of the intense detection grid.

>>14663790
>>14663819
Attack Aleman: 4 (Ok, then)
Try to get Kingston to attack Brullant: 1
Fly all around Brullant to check for cloaked ships: 2
Get closer to Dufay to see what's going on: 2

Should we go, or do you want simultaneous ops, here?

>>14663879
I want simultaneous ops. The attack on Aleman may provoke a response from the other planets and I want cloaked Overlords and dropservers ready to record everything.

>>14663879
Focus on one at a time, as long as we aren't pulling trump cards or surprise tactics. Better to concentrate our forces on one target at a time - it may give Voidgate more time to prepare, but while you can prepare for new technology or trickery, you can't exactly 'prepare' for SEVERAL FLEETS' WORTH OF RAW JOULES OF EXPLOSIVE AND LASER-RELATED ENERGY.

>>14663860
1) Letting Kingston escape the Magellan
2) Picking to wrong Void Seeker.
3) Telling VoidGate the time

>>14663879
I'm in favor of simultaneous ops and sending cloaked overlords at the other 2 planets, cloaked overlords everywhere.

>>14663860
>What was our biggest mistake?

Not killing Kingston back when he was just an elusive sciency guy on a science vessel? I spent 45 minutes talking about something happening above the docking bay...

>>14663912
The Void Ship wasn't your fault, really. You guys tried.

Waking up VoidGate was pretty stupid...

Anyway, brief lull in conversation while I type up the next message.

Multitudes of overlords arrive over Bullant and begin searching the system for cloaked ships. We cast a wide net, but find nothing nearby the planet. We slowly move further out, but still fail to find any aircraft of any kind.

Just as our overlords begin to arrive near Dufay, we lose contact with the dropserver entirely. The overlords detect no ships, but are sensitive enough to notice severe changes in the gravitation of the system.

Finally, our mutalisks and scourge arrive at Aleman. Screaming into combat fully cloaked, they begin disabling the planet-scooping craft moments before nuclear detonations begin. None of the explosions are close enough to the craft to damage them, but we lose a substantial number of forces in seconds. The dropserver traces the exhaust trails of the missiles back to empty space outside of sensor range.

>>14664062
VoidGate, you are no friend, computer.

>>14664062
Drops a cloaked Overlord sensor net into the Aleman system to find those launchers. We need to take that StarForge offline.
Prepare 3 nukes to launch and target the VoidGate nuke launcher as soon as we detect it.

As for the Overlords in Dufay, see if they can examine the cloaked planet.

>>14664062
>we lose contact with the dropserver entirely
Build a spare, but don't send it in, use cloaked overlords only.
>>14664062
Right, so it seems they've put up a DECOY base, and have cloaked their real one.
Perhaps the cloaked missile ship is a DOUBLE DECOY, and their REAL REAL one is still cloaked.

We need to invent something that:
Can detect cloaked objects at a long distance, in a narrow beam
Can rotate, like a radar, to scan the entire systems for cloaked shit.
Come to think of it, scan the previous 3 systems we were in - Dagobah and whatever the other ones were - for more cloak shenanigans. There may be more ships there.

So, tl;dr: GET SHIT THAT DETECTS WHETHER THERE ARE ENTIRE STARBASES THAT ARE CLOAKED, MAKE SHIT-TONS OF THEM AND SEND THEM NEAR ANYTHING VOIDGATE RELATED.

Cerebrate, can we just go along with this >>14664111
It's been 10 minutes without another valid suggestion for action.

We cease attacks, the units that remain huddling near the courier craft as they move from planet to station and back again. The overlords that arrive in the Aleman system near the launch point of the missiles detect one VoidGate ship flying out of their detection range. As they attempt to follow the faster ship, another comes from behind, on a similar path. On a hunch, we spread our overlords out and, after a few minutes, we determine that there are approximately two dozen of the craft, cloaked and flying in a large helical formation around the path of the other craft.

The overlords in the Dufay system continue to detect large shifts in gravitation. Labbrate snaps out of its awe of the Aleman station to inform us, again with awe, that it has seen similar readings before: when we moved Zerg World.

>>14664111
Alright I'll second
>>14664234
and I think yours counts as a third.

>>14664244
First things first: Send cloaked Mutalisk squadrons to hunt down and destroy those nuke launchers in the Aleman system. Have their attacks synchronized to occur all at once. Our assault will continue once they have been dealt with. The Overlord sensor net is to stay in place to aid us in our attack.

In the Dufay system, attempt to get at least one cloaked Overlord onto the Dufay II surface if it can as the planet Warps out. We want to at least find out where VoidGate is taking VoidWorld.

How goes Cyberbrate's integration with the computer system?

>>14664244
Ask Warbrate on the likelihood of attacking Aleman Station, given what we know about its force composition.
We obviously need to start building more detection, too.

>>14664244
That infuriating AI, it keeps stealing our ideas... and makes them better... bastard...

>>14664297
Sounds like a plan, seconded.

>>14664297
>>14664299
Warbrate is not a contented cerebrate. Those nuclear blasts took out a large portion of our already-depleted forces. It thanks the Overmind that we didn't send in our Protoss or Terran forces. It reminds us that we are still rebuilding basic defenses of our own colonies, after our total commitment attacks on Ash'Arak and Dagobah, which were right on the heels of our losses at Tyrador. It thinks we can destroy VoidGate's forces here, but we may not have any Zerg units left to attack anything for some time afterward.

(Heh. About Zerg World...that was a long time ago, and the Quest was different back then. There wasn't any Warp engine. It was all old-fashioned kinetic pushing and pulling. It didn't make a lot of sense, which is part of why I made it so absurdly bulky. Same here, really. Which is why...)

After a few tries, we notice that any overlords we send to where Dufay ought to be are incinerated completely.

hay guyz wats goin on in this thred?

>>14664362
Okay. So we NEED to convince the Terrans and the Protoss to help us in this attack.
I suck at diplomacy, someone else do it. :P

>>14664362
Are any of the Overlords able to penetrate the cloaking field surrounding Dufay II? Also, according to the gravimetric readings, is Dufay II moving along on a set vector? If so, attempt one more time to send in an Overlord, this time at a perpendicular angle to VoidWorld's course.

Assure Warbrate that we will scale back attacks once we have this massive facility secured.
Did we detect any changes in the Brullant system?

>>14664062

Spread out the swarm: 1 scrouge every 50 metres ought to do it. Fly the swarm towards where we suspect the cloaked attackers are.

We'll detects the bastards by crashing into them if we need to.

In the mean-time, fill our transport-worms full of lurkers and ready them for warping. The lurker's orders are to burrow into the first non-zerg substrate they encounter, then burrow their way to the largest source of energy/movement/heat that they can.

Place some of the nukes we have into overlords to be warped INTO whatever we locate if the target is too large for the lurkers to subdue.

I don't know whether the cloaked attackers is the main Void-gate fleet or a some sort of super construct and it doesn't really matter.

Void-gate is going to need to literally tear itself to pieces to dislodge the lurkers and he won't be able to cloak or warp away when there are living zerg still on board to give away his location/be beacons for further warp jumps.

>>14664397
i will do it

my skills at diplomacy are unmatched

>>14664397
We might be able to get Kingston to go after VoidWorld if we pitch it as a new protoss super weapon. Just done as a documentary mind you. At this point I think Kingston understands that we only point him at things when there is actually benefit towards him, and he used it as an opportunity to make us afraid of his new toys.

>>14664420
You're late; our Overlord sensor net in Aleman has already detected the nuke launchers.

>>14664412
So far, all of our attempts to see the planet have ended in a Zerg roast. Labbrate and Internbrate do some estimation and have an overlord jump to what they hope will be the path of the planet to wait. After a few minutes, the edge of the cloaking field ripples across the overlord, which is now attempting to enter the atmosphere without proper orientation points.

Best of the first two replies with a 1d100 sees if it can keep itself alive during atmospheric entry to an invisible planet. DC 65.

Aside from continuing readings of lots and lots of movement on the surface, no change in the Bullant system.

rolled 100 = 100

>>14664466
I don't like this computer.

rolled 66 = 66

>>14664466
Come on, little Overlord! You can do it!

rolled 71 = 71

>>14664466
>>14664491
surprising

>>14664422

Question 1: Is there a way to DIGITIZE Bernie into something that can be transmitted electronically?

Question 2: If would we be able to fit the digitized essence of Bernie into the data-storage of a Protoss Carrier?

Question 3: Did we sucessfully prevent Void-gate from downloading all Protoss technology last time?

Question 4: How is Cyberbrate holding up?

>>14664491
You son of a bitch.

>>14664495
>>14664491
>100
>66
Bwahahaha!

>>14664504
I love you too.
>>14664503
I think voidgate got all the protoss unit designs.

>>14664528

I thought we managed to stop his ships from relaying the information.

Come to think of it this reminds me of that time I suggested we have Kingston attack Shakurass.

>>14664568
Voidgate was in the process of downloading the Protoss Science Archive or some such, unless I'm misremembering.
>proverbs erbsti

>>14664594
>Protoss unit design download complete.
>Accessing Protoss Science directory.
Hurray for the archives.

>>14664568
No, we were only able to prevent VoidGate from downloading the Protoss Science Archives.
It's more important than it sounds: if VoidGate had gotten the Archives, not only would it be able to produce more Arbiters, but it would actually understand the time dilation theory that goes into their construction, and it would have been able to build such systems into its factories.

>>14664503
1 - No.
2 - Extra no.
3 - You'll know if Cyberbrate can access the Dagobah data cores, but that's probably going to be next week's opener.
4 - See #3. There's nuclear devastation and an interstellar planet going on. Let him work in peace.

(I can't imagine another situation where "interstellar planet" is actually a phrase you can use)

>>14664491
The overlord pushes its piloting to the limit, flying right along the razor's edge of destruction. We will the unit not to look down, knowing that if it does, it will be finished. As wind shear bears down on it, we respond by dangerously throttling wide open, like a proverbial bat out of Hell. The cloaking field parts around the overlord as it crashes through the planet's atmosphere. We push the overlord to its limit (LIMIIIIIT!).

And it survives. It survives, takes no damage, finds an equilibrium for continued flight, and even manages to maintain its cloak (which, considering that it is inside of another cloaking field, is approximately a one in a million coincidence).

The planet below is little more than a series of large computing facilities attached to almost 2/3 of a planet's-worth of massive engines. Internbrate cautiously estimates that VoidGate has actually utilized the planet's molten core as fuel. Labbrate informs us that with this data, it can calculate that the planet will break free of the star system, slingshot into deep space, and then likely float, lost, for thousands or even millions of years without encountering another major celestial body.

>>14664649
This must be VoidGate's final fallback, it's last line of defense.
I'm torn between nuking it, and taking it and going "U MAD" at VoidGate.

>>14664649
So, Voidgate is ensuring its survival, not surprising. Let's capture the starforge then.

(Oh, StumbleUpon. You make my day, sometimes)

http://earslap.com/projectslab/otomata/?q=1o2h1a3j3k4a0h5o

>>14664649
Does the Overlord see any defenses or weapon emplacements? With this Overlord acting as a beacon, would Labbrate be able to land science teams on VoidWorld to disable it?

>>14664703
Plop down a couple hatcheries more like it.

>>14664695
You're right. We now have a beacon on VoidWorld, one that VoidGate is unaware of. We can attack it at our leisure.
But for right now, the StarForge awaits!

Cerebrate, are the cloaked mutalisk squadrons prepared to destroy the nuke launching ships in a simultaneous attack?

>>14664703
The overlord is one of our standard overlords, different from the Overmind's old ones only in that this one has a cloaking harness with small shield capabilities, and the ability to use a psi-lash attack for small damage.

The cloak will keep the overlord undetected for another 14 minutes. If we deactivate the overlord's shields, we can probably up that to around 30 minutes.

The nature of our psionic link is such that, so long as a unit remains on this world, we will know its location.

Some defensive weaponry is evident on the planet, but not a lot. We could easily disable them with a dedicated raid.

>>14664767
Deactivate the overlord's shields and have it look for a place to hide when its cloak runs out. While that's going on we capture the starforge.

>>14664767
Deactivate its shield. Use the extra time where it can find some place on the planet surface that does not appear to be scanned or under surveillance, and sit tight until we can put together a force to take this world.

Warbrate, how big of a force would you estimate would be required to subdue VoidWorld. If the answer is enough that it would cause the StarForge operation to fail, then we will wait for the StarForge to be ours and our numbers replenished.

SO:

Deactivate shields, attack Aleman: 1
Screw that, attack Dufay now: 0

Vote on that, and if you pick Aleman, come up with and/or vote on a strategy.

>>14664802
>>14664790
We are in accord! Let's take that starforge!

>>14664802
Deactivate shields, attack Aleman: 2
Screw that, attack Dufay now: 0

Warbrate can't say. If we choose a decent strategy and losses at Aleman are low, we could probably take Dufay. If things go badly, we may not even take Aleman.

>>14664817
It's 2 for Aleman, but let's resweep the system to make sure we're tracking all of voidgate's cloaked assets, then destroy them all with zerg forces simultaneously, then we storm the starforge.

>>14664817
Deactivate Shields, Attack Aleman.

A coordinated, synchronized assault on all VoidGate nuke launching ships by cloaked mutalisk squadrons. Have them bring the nuke defenses down in a single assault.

As soon as the defenses are down, attack the StarForge and its attendant ships with a massive assault. Attack in waves, taking into account that VoidGate may have defensive nuke launchers aboard the StarForge. Board them and attempt to take them intact as possible. Search out and disable self-destruct devices.

>>14664850
Seconding on expanding our cloaked Overlord sensor net in the Aleman system. We found its patrolling nuke launchers; let's see if it has any cloaked detector satellites as well.

>>14664857
Aleman wins.

Are you all alright with this mutalisk strategy?

>>14664871
After another sweep of the system yes, bring in more overlords to get it done faster.

>>14664871
Yes, but only after we bring in more cloaked Overlords for a comprehensive sweep of the system to avoid other nasty surprises.

After assembling a pretty impressive number of overlords, we become sure that we have in fact found all of VoidGate's ships in the Aleman system.

Our mutalisks swarm away from their safe haven near the other ships, while our scourge idle, unused. The mutalisks gather in the paths of the ships and simultaneously attack. The ships immediately turn, sidewinding away from our detection net and their unseen attackers. All but two are destroyed, but we lose track of those two just before missiles fire out from it to the locations of four of the destroyed craft. Our losses are heavy in those areas, but we blanket the areas where the missiles came from with glave wurms until the overlords catch up. We quickly dispatch the ships.

The system is ours, though VoidGate's ships continue their task around the sun.

The battle was quick, but even fast warfare is lengthy. Our overlord on Dufay has a mere 8 minutes of power left in its cloaking harness, and no shields once its cloak drops.

>>14664960
...why do I keep forgetting about scourge? Alright lets assemble an assault force to take the starforge, and find a hiding place for that overlord, and if we cant find one well just warp in a replacement.

>>14664960
Was the Overlord in Dufay able to find a safe hiding place? It needs to find one as quickly as possible, perhaps landing on the surface somewhere.

In the Aleman system, send the Scourge and Overlords towards the StarForge as Zerg troops are readied to board the station and capture it.
The Scourge will hopefully be attacked by the station's defenses, which will highlight them for follow-up destruction by our surviving Mutalisks.

In the case of the Overlord on Dufay II not being able to find a hiding place, have Warbrate prepare a raiding party in force using a mix of Zerg, Protoss, and Terran units to make up for our depleted Zerg forces. All communications systems are to be shutdown to prevent hacking.

>>14664985
Where would it hide on a computer complex/giant flaming engine world?

Are you intending to destroy the station, or attempting to capture it?

>>14664960
How long will it take to get more forces to Dufay?
Also, can we even GET forces onto the planet's surface? We can't get even cloaked overlords in, so won't everything else just vaporise?

We should clear Aleman of Voidgate forces.

What's the status on Brullant VI? I'm inclined to kill the entire planet with Orbital Bombardment if it doesn't have an airforce. Send only 2 or 3 ships to start, to check if it's a trap.

>>14665004
Presumably it could stay close to a structure, like an auxiliary computing facility and stay below the radar.
Otherwise, have a Dropserver pulled from the Brullant system and have it park on VoidWorld, using the Overlord already on the planet to help guide it in using psychic coordination.

As for the StarForge, we want to take it intact. Or at least, intact as can be expected.

>>14665004
On a heatsink? Or is the entire planet in flames?

>>14664960

We need to warp something in whilst the overlord's location is still hidden, be it a single lurker or a zergling.

After that, we can try to open up communications with Void-gate. Let's see if we can either bluff it into submission/surrender or get a few concessions from it in exchange for free passage from the sector.

I'm hoping to get at least 75% of it's nuke stock-pile (if it's running into deep-space, it won't need nukes) the protoss unit schematics and some way to hack into the data-bases of other races like Void-gate did with the protoss.

If Void-gate IS leaving and promising not to return, give Artisan-lord the task of thinking of some sort of 'no hard feelings' gift.

>>14665014
Also, would the Protoss or the Terrans find any threat in Voidgate stealing an entire f*cking planet? At the very least we should ZergTV that:
(to terrans) Sentient malevolent AIs are STEALING ENTIRE TERRAN COLONY WORLDS.
(to protoss) Sentient malevolent AIs that can hijack all of their technology are GETTING AWAY WITH AN ENTIRE FUCKING PLANET.

At the very least we can throw someone ELSE into the grinder other than ourselves.

>>14665040
>>14665041
Combine these. If -we- make a peace treaty with it, that doesn't stop someone ELSE from blowing it up.

Then again, Voidgate doesn't really go for peace. Doesn't hurt to try, though.

>>14665014
(Once again, Blizzard-like fudging will allow time to dilate such that you can send in troops right now, because I, like Blizzard, didn't quite think this part through. Oops. Maybe I shouldn't be so hard on them about that...)

Internbrate chimes in that having a line of sight from within the cloaking field will allow us to enter the atmosphere properly, as we will see where we are going (which would be much more difficult for a species that could not be in two places at once in this way).

So far, Brullant is still quiet. No aircraft of any kind, aside from the detection satellites.

>>14665056
If that's the case, have the Dropserver from Brullant pull out and get to VoidWorld. Once the Dropserver is secure on the world and we have a psionic presence on it, we can have the Overlord break atmosphere and Warp out.
We will attack VoidWorld when we have finished conquering the StarForge.

>>14665056
Send 2 Cloaked Overlords in, unshielded, having 1 to act as a backup in case the first dies or something.
Once these two are in orbit on Grand Theft Planet, crash the first overlord into the boiling molten surface before its cloak runs out (and gives away the location of its brothers).

We can presumably buy time this way with minimal forces. Even the noobiest zerg can macro 2 overlords every 25 minutes.

>So far, Brullant is still quiet.
This makes me worried.

>>14665056
Then lets send a dropserver or 2 to wait on the planet until we decide what we're doing with it. I'd like to take the starforge first, and would prefer to find out what's happening on the other planet.

>>14665073
Goddamnit you stupid fuck! Overlord cloaking harnesses have a limited battery life; dropservers can maintain their cloak indefinitely!
Why are you sending in Overlords whose cloaking fields will run out well before we can ready an invasion force?

Quick vote:
Cloaked overlords:
Dropservers:

Think carefully. One has an obvious benefit, but a less obvious drawback. The other has an obvious drawback, but a less obvious benefit.

>>14665092
Because they are less expensive than Dropservers, and they have a much lower chance of resulting in Voidgate stealing Dropserver technology.

Also, quit getting mad at traditional games.

>>14665104
Obviously an endless stream of cloaked overlords in my opinion. No point risking a Dropserver on that.

>>14665104
The dropserver has a weaker psionic connection with us? Ask labrate how long it will be before the planet leaves the sector.

>>14665104
We are using fingerlings to pilot our dropservers, so we should be able to maintain a psychic sense of where it is and control it, regardless of ECM. If we also shut down its communication systems and active scanners, it should be pretty much invisible.
The only possible drawback I can think of, is if the metals on the dropserver get picked up by VoidWorld magnetic scanners.

>>14665105
Do you even know what the dropserver is? It's all off-the-shelf technology from existing units. There's nothing new about it, except that we stuffed a second reactor in a dropship's cargo bay to power the cloaking field generator.

>>14665109
Cloaked overlords: 1
Dropservers: 0

VOTE OR DIE

>>14665116
The...Koprulu Sector? Quite some time. Say, 200 years?

>>14665136
Dropservers. TUCAMP and I have been voting for that for quite a while now.

>>14665141
Cloaked overlords: 1
Dropservers: 1

>>14665141
Actually since >>14665104 I've been trying to figure out what the drawback to the dropserver is and haven't actually made up my mind.

>>14665160
VoidGate could potentially have ferro-magnetic sensors, and the dropship would appear on those. There's also the chance that it could pick up any electronic signals from the dropserver's computer systems, but that's what putting everything on passive is supposed to do.
There's also the point about it possibly needing to land, while the Overlord is capable of indefinite flight, however, with the extra energy of the dropserver's second reactor, it should need to land for quite a while.

>>14665160
Well, never mind that part, then. Vote, and I'll be generous. It's late-ish.

Clearly we wont do anything regarding Voidworld until next week, so I'm actually going to have to er on the side of caution and vote for what we already know works, perpetual stream of overlords.

>>14665136
Question:
If Voidgate can cloak an entire planet, and use its BURNING MOLTEN CORE to power its shit, can we detect its infra-red emissions (heat) once it gets far enough away from its star to get it out of the background noise?
If not, where is that heat going? Is it Heat-sinking the ENTIRE PLANET'S MOLTEN FURY and warping the CONCENTRATED MOLTEN FURY elsewhere?

>>14665216
or perhaps the infra-red emissions of an ENTIRE PLANET are being lensed and focused into a narrow beam - thus making it A. harder to see, and B. Incredibly destructive to anything in its path.
Like a Giant Death Ray, but instead of a Giant Death Ray being built on a planet, THE ENTIRE PLANET IS A GIANT DEATH RAY?

In any case, I think I have two ideas on what to do with some spare planets.

>>14665251
If we build some orbital telescopes we could track it by the gravitation distortions it will cause, but that's a future problem.

>>14665182
(Awesome! A choice is made!)

We guide a second overlord into the atmosphere of Dufay as the first overlord makes its way to the massive engines moving the planet. Just before its cloak runs out, it burns up without a trace. Just as planned. As long as we don't screw anything up, we can keep this up indefinitely (despite Accountantbrate's protests, "THE EXPENSE!" is not all that bad).

Meanwhile, in the Aleman system, our scourge disable the engines of the courier ships, leaving them dead in space while we storm the space station. Despite our massive aerospace losses, Warbrate is confident with our remaining ground forces. We swarm into the structure, slaughtering every cyborg and android we come across. The process is long and arduous, but after merely a few hours (and eight overlords), the station is ours. As soon as the last combat machine falls, VoidGate's background communication signal amplifies substantially for a few moments, and the station goes quiet. The power shuts off. All the screens go blank. All the lights go black.

(NEXT WEEK, find out whether Cyberbrate can do the job we created it for, or if we sent an innocent cerebrate to its death! Deal with Dufay, VoidGate's runaway planet! Contemplate Brullant, the final stronghold in the malicious AI's inventory! Maybe get some kind of door prize for 40 threads or something!)

>>14665275
Just a question, what would have happened -if- we used a Dropserver?

I just hope that the idea of using a constant stream of Overlords doesn't come back to bite us in the ass like so many of our other plans have.

>>14665275
You do know for 40 threads we get a free shawarma.

http://suptg.thisisnotatrueending.com/archive/14662402/

Archived. Personally, I'm pretty happy with all the crazy shit that's been happening the past few threads.

>>14665216
I'm resisting the urge to work out the specifics behind actually strapping engines to a goddamn planet and driving it around. Pretty hard. Logistically, the core wouldn't provide enough fuel for that, the heat of the engines would melt anything on the surface, the destabilized orbit would likely crash the planet INTO the sun instead of get it free, etc etc etc.

Just repeat to yourself, "it's just a show. I should really just relax."

>>14665269
Galileo refuses to assist the vile xenomorphic threat!

>>14665310
Sh...awar...what? I'm afraid to Google that...

>>14665353
It's another name for gyro.
It's merely a food item.
http://en.wikipedia.org/wiki/Shawarma

>>14665344
True. It was total bullshit how in System Shock 2, a pod you Jettisoned in Jupiter's orbit lands on Tau Ceti.

It escaped Jupiter's gravity well
It escaped the SUN's gravity well
And its propulsion was ... like, fuck all, it's a botany pod, it has no thrusters.

I was like "What?"

>>14665275
>despite Accountantbrate's protests, "THE EXPENSE!"

Pic Related

>>14665376
Quit clicking the tornado button you chucklefuck

If you could repeatedly click on the Simcity 2000 Roads advisor, what would its pissed.wav sounds be?

>>14665394
WAAAAAAAAAAAAAAGH!

>>14665376
That's the most accurate picture of Accountantbrate to date.

>>14665450
Your welcome, this OC was inspired by your comment.

>>14663431
>(dagobah

holy shit the zerg are invading star wars in this quest?)

>>14665534
Looks like you missed a thread.

CA gave us a choice of planets and a few rolls to choose a unique encounter. We had the chance to encounter Yoda, some parasitic species, the Terminators, or something else. We rolled terminators.