[HALP] me! (WORM quest)

The whole point of the plan is to safely purge the data. Since it's obviously a QA trap.
If we're going to try and save it, and get Gaea to optimize our Host to hold it, we can Research how to do it properly without me using my bonuses to autocrit. We'll have time.
Why are you so determined to save this virus set to hit us when Taylor Triggers?
If you want to keep the data, just vote against the plan. Although I don't know why we're keeping the data.
 
The whole point of the plan is to safely purge the data. Since it's obviously a QA trap.
If we're going to try and save it, and get Gaea to optimize our Host to hold it, we can Research how to do it properly without me using my bonuses to autocrit. We'll have time.
Why are you so determined to save this virus set to hit us when Taylor Triggers?
If you want to keep the data, just vote against the plan. Although I don't know why we're keeping the data.
I want the data out of Taylor's head, but I don't want to delete it entirely without figuring out what it is. My suggestion was that we transfer the data to a bud, removing it from Taylor's head in the process.
 
I want the data out of Taylor's head, but I don't want to delete it entirely without figuring out what it is.
It's reinstallQAoverus.exe
To the point that QA has a regular response to it of some sort.[snip]
Now, I know that you're… not Queenie, so to speak. This is… a recurring… phenomenon. [snip]
She tends to… stash… information… places.[snip]
You know, the way this brain tissue is configured, it could hold a ton of information.[snip]
I mean, there are some strong implications of what it is, and none of them are good.
I named the plan Red Flags, because that's all we've gotten about them.
 
Last edited:
I'd strongly prefer not to wipe that data yet. Even if it is something planted by the original QA with malicious intent, we still might get something useful out of it with sufficient Memetic Filtering - and we have no guarantee that that's the case.

After all, this almost certainly ties into the "Insane In The Membrane" quest, and the current step we're on in that quest is still "gather information".

Given that we can probably do this safely over time with a little patience, I'm really not feeling the desire to burn three (!!!) omake bonuses just to wipe the data clean right now.
 
Last edited:
We've begun to panic. It's like two party system. Some of us want to wait and see but the big parties are each pushing for trigger her now or wipe the data. We could vote to do nothing, but we'll only have enough votes thatvwre taking away from our second option.

I'm down for letting this go, doing research, and maybe Gaea will be able to tell us something.
 
Last edited:
Even if it is something planted by the original QA with malicious intent, we still might get something useful out of it with sufficient Memetic Filtering
Meme filtering can fail. And there's no guarantee that it will even block whatever is in the data chunk.

Keeping the data just doesn't pass a risk/reward comparison for me. If we want QA data/ memory we would be better off decoding what we already have in archeology.
 
[X] Plan Taylor Wait
Too little personal info on what's going on, but it seems there is a rush to wipe clean the black box sitting in Taylor's head.
Considering that this thing was discovered prematurely, I imagine the debuffs to rolls related to it are also high.
So for now, I'd rather not touch it.
 
I debated with myself over whether or not to vote for the plan, but then I realized that I could wait for an unknown amount of time to fix Taylor and fulfill the quest while hoping that the encoded data is not going to backfire on us, OR we could fulfill the quest now, get the rewards from doing so, fix Taylor, and get rid of a probable trap. The autocrits from the omake bonuses make this a much safer bet than many other plans I've seen.

The congress of yourselves plugging away at the Charge data all day pings you. It's done, although as you'd expected not everything could be recovered.

Well, first, there was a decent amount of Breaker Information, and, strangely, what looks like Brute Information buried in there.

Charge - Breaker Information (4): +56
Charge - Brute Information: +3
From what I understand, the (4) means that Charge is likely sense-sharing with another cape. @Gino, could you add the following question to Plan Data?:

-[ ] Ask whether Charge is sense-sharing, friends, or allies with any other Shards?

Before we deal with Charge, we might want to figure out who we're going to tick off by doing so.
 
I mean, there are some strong implications of what it is, and none of them are good.
I named the plan Red Flags, because that's all we've gotten about them.

Mmmm... given this I'm mostly worried about what would happen if we copy it to our shard. I mean, it could be a program that once uploaded to Administrator it reset it and restores a backup copy (QA) from Administrator's encoded memories. If this were the case uploading it and purging it would do nothing because althought that actions would be succesful, the data would have already fulfilled its mision.

Couldn't we achieve the same effect by simply uploading a copy of Taylor's mind to us and then make Gaea completly delete all the information in her brain (and the we put back the copy of her mind in the brai, that is.)

Or, simply, making Gaea delete all the encoded information without even trying to decode it.





On another completly unrelated note: A random idea for a power for Taylor or another Host (obviously Shard=us): Matter Manipulation

The Host interpretation:

The Host can control matter, organic and inorganic, around him as if it were parts of his body. Actually, the Host gets the sensation that the matter is part of his like if it were another arm or leg. In fact what the Host is doing is to transform the matter around him in his minions, each one the size of a speck of dust.

If the Host doesn't order the around then nothing happens, but if he, for example, transforms an iron beam in to a cloud of iron the size of specks of dust and then make it so they form and iron beam, it would fall apart the moment the Host leaves it outside his range because it wouldn't be an iron beam but a lot of little things of iron with the form of an iron beam without nothing to keep them together to one another except the Host power. Basically the user would be able to separate matter with extreme ease but unable to put it together.

The Host can not affect his own body with his power. By defeault the power works forcing his body to remain together and in the same form, trying to resist any and all typer of changes the user doesn't wish, compacting the matter in the body and hardening it as a result, althought it would not put back the matter in case this separated from the body. This grants the host enchanted strength and durability, althought not regeneration.

This power doesn't grants his Host any ablity to build/rebuild things with it intuitively. Moreover even in case the Host managed to build something with it, it would fall apart the moment the item left the range of effect of the power. And even if it were to be in the Host's range it wouln't work (in the case of something technological), this is because it wouldn't be the item built but mots of matter in the form of the object built.

The power doesn't grants clairvoyance around the area its affecting, althought the Host percibe all matter in the area.

The power doesn't works at an atomic scale. anything with a size lesser that a mote of dust is ignored and not registered as minion.


The Shard's implementation:

The Shard grants forcefields to any minion (to be considered a minion for the Shard the Host has to have ordered it to do something, aka tried to move it). This forcefield has the size of a speck of dust and surrounds the matter to manipulate, breaking its atomic links with the object/s it was linked to.

Then the Shard grants the Host the capacity to manipulate the forcefield, routing (the same way the limbs are) in his head its possibles movements, althought without explaining to its Hosts that it's in fact manipulating a forcefield instead of matter. This makes it so the Host can manipulate the minion with the same ease as a limb, which at the same time creates the mental illusion the minion is minion its part of himself, althought in fact it isn't true.

This forcefield doesn't grants any additional resistance to the minion it envelopes.

In the case of the body of the Host, the forcefields created are different from the others (this happens only with the Host, and not with other's bodies), and instead of breaking the atomic links when they are created what it does is make them shift of dimension so they aren't there when the Shard acts preventing changes in the Host's body, but at the same time are, avoiding damage to sensible body parts like the eyes (that would stop working if they were divided in thousands of pieces).

This last forcefield basically does the same as the first one only that without breaking the atomic links and at the same time preventing voluntary separation of the parst of the body of the Host as the atomic links are but not are broken at the same time.

Having not broken atomic links the Shard interprets the Host as only one minion, making it so it doesn't feel that anything weird is happening to his body (despite there beign thousands of forcefields), althought the same as all of his minions, the Shard routes in the brain of the Host the possibles movements his minion (his own body) can be moved as if it were a single inflexible and indivisible entity (the same as the rest of his minions). This is what grants the Host the capacity to fly (the Host ordering his minion (himself) to go up, what at the same time causes the rest of the forcefields in his body (and in consequence his body) to go up simultaneously, effectively flying).

If matter is separated from the body of the Host then that matter would get normal forcefields instead of the special ones, event if it is put back in the same place it was (unlessit goes back to form part of the body once again).
 
Last edited:
Given that we can probably do this safely over time with a little patience, I'm really not feeling the desire to burn three (!!!) omake bonuses just to wipe the data clean right now.
I just want to point out that the omake bonuses belong to The_GrandMage. If we don't vote for this plan, The_GrandMage decides an alternative way to use the bonuses, and we have no say in it unless it's another quest-affecting plan that needs voter consensus.

Mmmm... given this I'm mostly worried about what would happen if we copy it to our shard. I mean, it could be a program that once uploaded to Administrator it reset it and restores a backup copy (QA) from Administrator's encoded memories. If this were the case uploading it and purging it would do nothing because althought that actions would be succesful, the data would have already fulfilled its mision.

Couldn't we achieve the same effect by simply uploading a copy of Taylor's mind to us and then make Gaea completly delete all the information in her brain (and the we put back the copy of her mind in the brai, that is.)

Or, simply, making Gaea delete all the encoded information without even trying to decode it.
My understanding is that the plan DOESN'T have us copy over the data to Administrator but instead has us copy over only Taylor's brain and deleting the encoded data.
 
If this were the case uploading it and purging it would do nothing because althought that actions would be succesful, the data would have already fulfilled its mision.
That's why the plan is set up the way it is.
The plan doesn't involve uploading the data. We copy Taylor, only Taylor, and reformat the brainmeats to destroy the encrypted data entirely before plonking Taylor back in. We don't interact with the data in any way except for destroying it.
 
This is interesting, but does anyone know how Coil uses his simulations in canon? Does he even run them for a week at a time? Fanfiction has given me the impression that he'll run them for a day at a time with one instance having him go to work and the other having him be at home or in his base and then pick whichever day went better.
What we've seen of Coil in canon is that he runs them for 24+ hours on what appears to be a normal day. He wakes up, checks if he's fine overnight, and then collapses it into one timeline, before going to work/going to cape.

Coil's power is interesting because:
-Short simulations give him a lot of data, but very little safety. He can use it to effectively savescam a conversation or event.
-Long simulations give him a lot of safety, but he's stuck in reactive mode while doing so.

Its unlikely that he'd notice any cap higher than 30 hours(which incidentally, would also mean that any cap higher than 30 hours would not actually extend the shard's lifespan significantly)
Note that Cauldron does not offer aftercare. They don't know how Shards work either, and Eidolon himself is suffering unidentifiable power loss over time.

Wait a minute. Guys we're restricting Coil wrongly.
Cutting his simulation time doesn't do shit. Long simulations should not be any different computationally to multiple short simulations over the same period of time.
He's still simulating constantly.

A restriction should be cooldown. Otherwise Coil is still running his power literally every minute.

Like so:
[] Restrict Twin
-[] Twin's Host must spend a period of time between simulations equal to the length of the last simulation before he can start up a new simulation. If the Host attempts to simulate regardless during a cooldown, it is allowed, but a Thinker headache is imposed for the entire cooldown duration and the severity of the headache and duration of the next cooldown is doubled each time this occurs. The headache should be annoying on the first, impairing on the second and incapacitating on the third. Drugs should help with the first and second headaches, but not the third headache.

The drug bit is just to tempt him into slamming into the hard stop and spending a week writhing in agony kekeke
If trigger vote idea passes through I suspect voting will be organized. Also there is no limitation to power categories unlike some people (included me) suspected, so this is even better. I will possibly vote for Symbol(ism) Tinker or Monju as both are absurdly versatile power ideas. But as mentioned - if trigger vote doesn't go through, so be it.

Uh, I think you're reading too much into that statement. We explicitly know that Trigger Type matters. But we don't know how it matters because its blackboxed until we research that.

We can shove whatever data we want in, to create whatever power we want, but if we're giving Taylor the wrong kind of power for her trigger its going to have higher odds of deviating or mutating her in the process, as we've seen with Gallant/Valiant.

If we match it closely she might get more for the same data
 
Last edited:
I just want to point out that the omake bonuses belong to The_GrandMage. If we don't vote for this plan, The_GrandMage decides an alternative way to use the bonuses, and we have no say in it unless it's another quest-affecting plan that needs voter consensus.

Yeah, I'm aware?

It seems pretty unlikely to me that he'll choose to spend them all on the [Mad Kazoo Skillz] tree (or something similarly without use), so I'm fine with whatever alternative benefits he ends up choosing.
 
Last edited:
From what I understand, the (4) means that Charge is likely sense-sharing with another cape. @Gino, could you add the following question to Plan Data?:

-[ ] Ask whether Charge is sense-sharing, friends, or allies with any other Shards?

Before we deal with Charge, we might want to figure out who we're going to tick off by doing so.
That (4) is a note for me, the QM, so that I knew to roll four times instead of one to see how much Information, that is 4x1d20.

You can't know for sure, but given the state that Charge is currently in, the chance that it's sense-sharing hovers near zero.
 
[] Restrict Twin
-[] Twin's Host must spend a period of time between simulations equal to the length of the last simulation before he can start up a new simulation. If the Host attempts to simulate regardless during a cooldown, it is allowed, but a Thinker headache is imposed for the entire cooldown duration and the severity of the headache and duration of the next cooldown is doubled each time this occurs. The headache should be annoying on the first, impairing on the second and incapacitating on the third. Drugs should help with the first and second headaches, but not the third headache.
This is really good. I'm replacing my Negotiator vote with this.
 
It seems pretty unlikely to me that he'll choose to spend them all on the [Mad Kazoo Skillz] tree (or something similarly without use), so I'm fine with whatever alternative benefits he ends up choosing.
I bought the Continuous Research skill out of spite when the thread ignored me. I just might do this.
Kazoo skills? We don't even have lips.
I might bud off the Moon chunk from the Collective, though. Vive la révolution!
 
Research
[X] Plan Just Get Stuff Done Already
-[X] Continue Focused Research 1
-[X] Start Research Memetic Proxy Filtering 1
-[X] Start Basic Psionic Theory 1
-[X] Start Stabilize Trigger (Human)
-[X] Assign all excess research points after this round's rolls to Focused Research 1

[X] Charge Data Questions
-[X] What are the updated command codes that the original Administrator sent Charge?
-[X] Does Charge know the addresses for any other Shards that were contacted by the original Administrator when Eden died?

Shards
[X] Plan Restrict Frictionless
-[X] Send Frictionless the Standard Information Packet and the command codes so that it must listen to us.
-[X] Tell Frictionless to cap the size of objects that Ballistic can accelerate to only 5% bigger than the objects Ballistics currently uses.
-[X] Set up sense-sharing with Frictionless.

[X] Plan Restrict Fusion
-[X] Send Fusion the Standard Information Packet and the command codes so that it must listen to us.
-[X] Tell Fusion to cap the power output of suns such that it extends that maximum shard lifespan to normal parameters.
-[X] Set up sense-sharing with Fusion.

[X] Plan Senses
- [X] Set up sense-sharing with Audible, Swap, and Twin.
- [X] Take all Swap and Twin's data.

[X] Plan New Protocol with One-Way Option
- [X] When setting up the new sense-sharing connections, make them two-way, but create a new protocol that if the Shard senses aberrance in Administrator, it is to report this to Administrator and only Administrator.
--[X] If the Shard does not accept the new protocol, change the sense-sharing connection so that only Administrator gets the additional info.

[X] Restrict Twin
-[X] Twin's Host must spend a period of time between simulations equal to the length of the last simulation before he can start up a new simulation. If the Host attempts to simulate regardless during a cooldown, it is allowed, but a Thinker headache is imposed for the entire cooldown duration and the severity of the headache and duration of the next cooldown is doubled each time this occurs. The headache should be annoying on the first, impairing on the second and incapacitating on the third. Drugs should help with the first and second headaches, but not the third headache.

[X] Contact Singular & Surveillance
-[X] Get them to start sharing data with us.
--[X] Start spying on Bakuda as soon as she Triggers.

Hosts

[X] Do not Trigger Taylor

[X]Plan "Red Flags Over Brainmeats"
-[X] Transfer Taylor's Mind to us in her sleep.
--[X] Use Rune-Chan bonus 1 to autocrit on the attempt to not fuck this up.
-[X] Purge her Brainmeats of encrypted data everything else, just reformat it to empty.
--[X] Use PHO 2: Post Harder bonus to autocrit at this, getting rid of this probably dangerous chunk.
-[X] Transfer Taylor's Mind back into her new, enlarged Brainmeats she has more use of (Maybe with a slight program to make sure she feels proper levels of hunger to maintain it?)
--[X] Use Rune-Chan bonus 2 to autocrit at this, making sure we do it right.

[X] How did you know that name?
-[X] Think about the pros and cons of the various Brockton Bay teams while watching Lilac throughout the day, mulling over their members and resources and how well Lilac would fit in.
-[X] Have the portion of you doing this watch Lilac's Host data all day, record instances she seems to react to what you're thinking.
 
Last edited:
Back
Top