Obviously not all parahumans get shut down by wards, but some of the do.

Brutes- Not at all.

Blasters- I don't think exoctic effects like Jack slahsh would be effected, but Erestu mages have plenty of experience surpressing the likes of burnscar.

Strikers- Mostly no, but mabye a few.

Movers- No, but teleporters get ruined by wards deseniged to counter them.

Shakers- Mostly they control something in a range, if wards can disrupt that, than yea they will have trouble.

Tinkers- Not at all.

Thinkers- Depends mostly on the type of power and how the shard treats anti-divitation wards.

Masters- One's that target the mind get ruinied by wards. Others, not so much

Trumps- We know they can target the soul so mabye?

Also, thought. If a shard doesn't want a power to be affected by wards, I can see a lazy one just destroying them instead of bypassing them.
 
Last edited:
To rephrase; if Coil had just e.g. decided to get out of the city where the people who break his power live, from the perspective of Taylor and co., nothing would have been different between that scenario and the one where Zorian forces him out.
Coil giving up his plot's or his Power hungry and psychopathic ways would be extremely unlikely and OoC

No to mention without zorian help Taylor and the summons would be his paws under the PRT and Protectorate so that doesn't not apply at all
 
One: that is a remarkably crude way to put it, and I'd request that you not. Two: my interpretation of Jack Slash is built on Wildbow's. Canonically, he just is that strong. The second trigger I gave him made him substantially stronger, yes, but by (in my opinion) a reasonable amount given where he already was.
You basically turned him into March 2.0, one of the worst characters introduced in Ward and who's combination of absurd plot armors almost tanked Brockton's Celestial Forge. The only good thing I've ever seen anyone do with March is from Trailblazer, where Mikazuki Augus used Gundam Barbatos to unceremoniously pulp her skull while the rest of the Nine were killed off in a storm of gunfire and concrete.
 
Last edited:
You basically turned him into March 2.0, one of the worst characters introduced in Ward and who's combination of absurd plot armors almost tanked Brockton's Celestial Forge. The only good thing I've ever seen anyone do with March is from Trailblazer, where Mikazuki Augus used Gundam Barbatos to unceremoniously pulp her skull while the rest of the Nine were killed off in a storm of gunfire and concrete.
Ah. Much is explained.

Expanding on that cryptic statement; I really liked March. I might even go so far as to say that she was one of my favourite parts of Ward. Certainly, one of my favourite things about Worm and Ward in general is how they treat Thinker powers, and that theme is part of what I was going for here. If you disliked March, it makes sense that you'd dislike this plotline as well.

As a tangentially-relevant aside, I was rereading HPMOR the other day, and thought this quote might be relevant (though the situation it describes was, of course, much better written than the one I'm comparing it too here). I don't think there are any significant spoilers, but I've put it in a spoiler just in case; there's not enough information for you to deduce any details of the plot from it, I think, but it does reference very important story events. (I've also individually spoilered some of the key words that aren't relevant to the point.)
The enemy is smart.

Slowly the fog of sleep was drifting out of Harry's mind, and after a full night's sleep his brain could see the things which hadn't been obvious the day before.

Under standard literary convention... the enemy wasn't supposed to look over what you'd done, sabotage the magic items you'd handed out, and then send out a troll rendered undetectable by some means the heroes couldn't figure out even after the fact, so that you might as well have not defended yourself at all. In a book, the point-of-view usually stayed on the main characters. Having the enemy just bypass all the protagonists' work, as a result of planning and actions taken out of literary sight, would be a diabolus ex machina, and dramatically unsatisfying.

But in real life the enemy would think that they were the main character, and they would also be clever, and think things through in advance, even if you didn't see them do it. That was why everything about this felt so disjointed, with parts unexplained and seemingly inexplicable. How had Lucius felt, when Harry had threatened Dumbledore with breaking Azkaban? How had the Aurors above Azkaban felt, seeing the broomstick rise up on a torch of fire?

The enemy is smart.

That situation is not directly parallel to this one - as I said, it's much better written than this one is - but I think there are parallels. I wasn't able to show you all of Jack Slash's planning, all the strings he was pulling while the battle played out to stay on top, because there wasn't any good way (that I could think of) to fit it into the story, but just because you didn't see it doesn't mean it didn't happen.

No to mention without zorian help Taylor and the summons would be his paws under the PRT and Protectorate so that doesn't not apply at all
Not so. Coil had substantial influence in the Brockton Bay PRT, sure, but Taylor's case has gone all the way up to the top. He doesn't have enough influence to do too much messing around in an area Rebecca Costa-Brown is dedicating a significant amount of attention to, which is the situation he would have found himself in.

Obviously not all parahumans get shut down by wards, but some of the do.

Brutes- Not at all.

Blasters- I don't think exoctic effects like Jack slahsh would be effected, but Erestu mages have plenty of experience surpressing the likes of burnscar.

Strikers- Mostly no, but mabye a few.

Movers- No, but teleporters get ruined by wards deseniged to counter them.

Shakers- Mostly they control something in a range, if wards can disrupt that, than yea they will have trouble.

Tinkers- Not at all.

Thinkers- Depends mostly on the type of power and how the shard treats anti-divitation wards.

Masters- One's that target the mind get ruinied by wards. Others, not so much

Trumps- We know they can target the soul so mabye?

Also, thought. If a shard doesn't want a power to be affected by wards, I can see a lazy one just destroying them instead of bypassing them.
Roughly in order:
  • Burnscar would absolutely be counterable by specific wards, but I'm under the impression that parahumans with powers that use that simple an effect are actually fairly rare.
  • We know there exist variants of teleportation in Mother of Learning that bypass wards (and, of course, wards intended to counter those, and so forth). Teleportation wards in MoL are aimed at shutting down teleportation as it functions in MoL; some shards might use a totally different method of teleportation that ignores standard teleportation wards.
  • Bear in mind that Zorian, possibly the best human mind mage in all of Altazia, is perhaps not the best yardstick by which to measure the efficacy of mental powers against mind magic. But yes, in general, even basic mind shields will (as I'm running it) block most Master powers at least partially.
 
I assume that for most telporterers shards use the shard equivalent of a basic teleport, wich I think can be blocked preety easily.

Fitingly I forgot about strangers.

The ones that reliy pruly on mental shenanigans get ruind like masters, and even non mental ones can be counterd with normal detection spells, Erestu mages have a lot of practice with doing that with themselves.
 
Last edited:
I assume that for most telporterers shards use the shard equivalent of a basic teleport, wich I think can be blacked preety easily.
I wouldn't assume that - the whole point of the Cycle is testing different powers. I'd expect a substantial fraction of teleporters to have powers that operate by non-standard mechanisms, perhaps more than half.

Fitingly I forgot about strangers.
:lol:

The ones that reliy pruly on mental senigins get ruind like madters, and even non mental ones can be counterd with normal section spells, Erestu mages have a lot of practice with doing that with themselves.
Can't parse "normal section spells".

(Oh, in case you haven't noticed; your post duplicated. I've replied to the first one; can you please delete the second?)
 
Not so. Coil had substantial influence in the Brockton Bay PRT, sure, but Taylor's case has gone all the way up to the top. He doesn't have enough influence to do too much messing around in an area Rebecca Costa-Brown is dedicating a significant amount of attention to, which is the situation he would have found himself in.
They die in side-plots if they can't be usefull paws then i am sure a dead ward is just what he need to Kick piggot off and start a gang ward to complete his Power Play, That is something he would do if he can't control them after all

Heck he doesn't even need to be the director to screw them over just know Who and where they are is enough to control or kill Taylor and co with little planing
 
They die in side-plots if they can't be usefull paws then i am sure a dead ward is just what he need to Kick piggot off and start a gang ward to complete his Power Play, That is something he would do if he can't control them after all

Heck he doesn't even need to be the director to screw them over just know Who and where they are is enough to control or kill Taylor and co with little planing
Problems with this:
  • Taylor is not a Ward. Taylor is, however, the primary potential link to four planets and three universes. The response to her death would not be run by Director Piggot, it would be run by the Triumvirate.
  • Coil doesn't (in the hypothetical) want to lose the potential for access to those universes any more than the PRT does, so he doesn't want to kill Taylor in any case.
  • Coil has (again in the hypothetical) no leverage over Kaladin, Vin, or Lapis, and no obvious way to get any. This is especially true for Vin and Lapis, who would almost certainly respond to an attempt by the PRT to control them by breaking with the PRT.
    • Threatening Taylor might be an option there, but Taylor can teleport, and getting the PRT to go along with a way of containing her that prevented that would be practically-speaking impossible given the aforementioned oversight. Capturing her as Coil and e.g. keeping her sedated would again be met with Triumvirate response.
  • Kaladin is nearly unkillable, Vin is willing and able to slaughter her way through Coil's entire operation if necessary, and if Lapis gets serious at any point Coil loses immediately. Killing them would not be trivial for (hypothetical) Coil to accomplish.
  • If he got close to succeeding in killing (or perhaps even alienating) them at any point, Cauldron would intervene and stop him.
 
Taylor is not a Ward. Taylor is, however, the primary potential link to four planets and three universes. The response to her death would not be run by Director Piggot, it would be run by the Triumvirate.
That would be a good way to get rip of lung to be honest he could Likely set a fight between the e88 and Abb in the right way to hurt Taylor and danny with ease

  • Coil doesn't (in the hypothetical) want to lose the potential for access to those universes any more than the PRT does, so he doesn't want to kill Taylor in any case.
He Likely would care about the potential gain but that bait isn't worth It if they mess with his Power too much

Coil has (again in the hypothetical) no leverage over Kaladin, Vin, or Lapis, and no obvious way to get any. This is especially true for Vin and Lapis, who would almost certainly respond to an attempt by the PRT to control them by breaking with the PRT.
  • Threatening Taylor might be an option there, but Taylor can teleport, and getting the PRT to go along with a way of containing her that prevented that would be practically-speaking impossible given the aforementioned oversight. Capturing her as Coil and e.g. keeping her sedated would again be met with Triumvirate response.
Why would he need leverage to set up an ambush between his enemies? And without zorian TT could make them dance on his plot's regardless even if they mess up his Power

Also Getting them break up with the PRT would make them easier prey to be honest that would insolate them and he could set his own people to watch them or approach them

Kaladin is nearly unkillable, Vin is willing and able to slaughter her way through Coil's entire operation if necessary, and if Lapis gets serious at any point Coil loses immediately. Killing them would not be trivial for (hypothetical) Coil to accomplish.
Again Coil doesn't need to act directly and there are plenty of Power's that he could get his hand on to shut them down like bakuda or noelle for example heck leet was able to mess up QA control on canon so any good tinker can be usefull

If he got close to succeeding in killing (or perhaps even alienating) them at any point, Cauldron would intervene and stop him.

Cauldron freepass really? Why would they even care or how he would know they care? nvm with the cauldron card on play futher discussion would be pointless PtV pandering so i Guess there is nothing more to say
 
Last edited:
I hate invisitext as I can only ever find it by accident. Maybe put it in spoilers instead

So somebody help me out what was written
 
Cauldron freepass really? Why would they even care or how he would know they care? nvm with the cauldron card on play futher discussion would be pointless PtV pandering so i Guess there is nothing more to say
... because Taylor and the summons are potentially the only gateway to three entire other universes filled with things that might be ways to kill Scion? And because Coil has some degree of contact with Cauldron (he got his powers from them)? I'm not saying he wouldn't do it because he'd expect them to stop him; I'm saying he wouldn't succeed because they'd stop him.

I hate invisitext as I can only ever find it by accident. Maybe put it in spoilers instead

So somebody help me out what was written
I also dislike invisitext, for much the same reason, hence why I've previously used grey text for stuff like shard influence. I don't plan on making a habit of using invisitext, but in this case, it carries only OOC things; putting them in spoilers disrupts the flow of the story, it makes it too obvious something has happened. (The thing I don't want to do is make people feel like they have to comb every chapter for invisitext, which irritates me when stories do it (looking at you, PMAS); I will tell you if I use it and roughly what it's for each time I do.)

For ease, the invisitext quotes are:
Out of curiosity, she visualized grabbing the thing and spinning it.

Taylor gave a squeak as she felt it jerk in response, moving round and up as well, for a fraction of a second before it vanished. At the same time, the fire within her went out, and the blue lines vanished.

One second passed. Then two. Taylor opened her mouth, and said "Vin, I -"
1d16 = 12.
The thing reappeared, and Taylor cut herself off midsentence. A brief check confirmed that she still couldn't feel anything in her stomach where the reserve had been before. Did the thing she'd spun switch off the power she got from Vin? Would it come back? Had she just lost a power only a couple of minutes after she'd got it?

"Taylor?" Vin said, suddenly on guard. "What happened?"

Stormlight puffed from Taylor's lips as she started breathing faster. "I felt something else, and I tried pushing it and pulling it and nothing happened, but then I spun it and I couldn't feel the steel anymore, and -" she ran out of air and had to breathe.

Vin frowned. "I've never heard of anything like that." She shrugged. "You could try … spinning it the other way, maybe?"

Taylor stared for a moment. Part of her was afraid of messing things up even more, but … well, what was the worst thing that could happen? She didn't get Vin's power? She hadn't had it before. She reached for the wheel, and imagined spinning it, the other way this time.
1d16 = 9. Bad luck, Taylor.
It vanished with the same sensation as before. Taylor waited a few seconds and it reappeared, but she still couldn't feel anything. She shook her head.

A few moments earlier …
t=-120s
"Let's talk," the simulacrum said, looking at Jack Slash.

Subtly, he raised a weak aegis, an invisible half-dome of force surrounding him. If Jack Slash noticed, he didn't react; the man had stopped hiding his mind the moment the simulacrum appeared, but it was still fuzzy, and between that and its inherent lightlessness the simulacrum couldn't get a read off it.

Jack's face was visible – the front of his helmet was transparent, and the simulacrum noted it as a possible weakness – so the simulacrum could see him grin. "Excellent," the murderer said. "I do enjoy it when people are willing to be sensible about things like this."

The simulacrum didn't bother responding to that. "Why do you care about me so much?" he asked. "Don't try to deny it; you could have targeted the Butcher directly, and then you wouldn't have lost the Siberian." Briefly, he considered bringing Tattletale back in, before discarding the idea; even if he wasn't hiding from Jack anymore, he couldn't risk Tattletale figuring out his plan and Jack finding out by proxy.

While he spoke, Bonesaw walked backwards, moving away from the conversation. She gave the simulacrum a disturbingly sunny grin as she stepped back into the fire.

Jack raised a finger – not covered by the armour, the simulacrum noted – and wagged it. "Dear William isn't lost. More like … temporarily misplaced, shall we say. I'll pick him up soon."

William. The Siberian's master? If Jack had known all this time – no, probably he'd only found out recently.

"Moving on," Jack continued. "Sadly, you appear to be overestimating me. You spoke to the entity that stands behind the Butcher, I'm sure you learned of its attitude towards me."
t=-90s
"I did," the simulacrum said. If Jack was inclined to gloat, Zorian certainly wasn't going to stop him.

"Mm," Jack said. "So, unfortunately, the events that led you all here were out of my control. The Butcher was always going to be ready for me, and you tourists were always going to be involved."

Tourists? Seriously?

The simulacrum ignored the barb, if that was what Jack had meant it to be. "So you decided I was going to fight you whatever happened, and you wanted it to be under controlled circumstances."

"More or less," Jack Slash said. "Besides, I find you interesting."

The simulacrum tilted his head. Obligingly, the murderer elaborated.

"Stormblessed, Lazuli … they're dull," Jack continued. "Remnant, lethal as she is, isn't much better; she's just too nice. You, though … I see myself in you, in some ways."
t=-60s
"You'll excuse me if I don't take that as a compliment," the simulacrum said.

Jack's grin didn't falter. "Don't worry, what you say doesn't matter to me. It's what you do that's important." He stretched a little. "Take right now; you're standing here talking to me, one of the greatest monsters – if I can flatter myself a little – of our time. Try to tell me the Windrunner would ever do that." He paused a moment. "That recruitment offer was genuine, if you want it."

Zorian ignored the needling. "Doesn't explain why you split up," simulacrum two said. "You could have fought me all together; gods know I couldn't have done much to the Siberian."

Jack pouted. "Alright, if you insist," he said, tone still light. "Truth is, it's all because of Stormblessed. The man might be dull, but he would have been a pain to deal with."
t=-30s
The simulacrum considered that. "Your power wouldn't have worked on him," he said.

He didn't need Tattletale to make deductions, thank you very much.

"It would not have," Jack confirmed. "It wouldn't have worked on Remnant either, but she would have been easier to manage." He sighed. "The upgrade Riley managed to get me is great, but sadly it can't cover everything."
t=-20s
So Bonesaw was responsible for Jack's power boost, assuming he wasn't lying. Interesting. More to the point, that did explain why the Nine had split up; the Siberian and Crawler to keep Kaladin away from Jack Slash. Except that Jack Slash had used that time, not to go after the Butcher, but to play around with Zorian.

"So why tell me all of this?" the simulacrum asked. "The Siberian is out of the fight, and Crawler won't hold Kaladin much longer. You're wasting time here."
t=-10s
That grin didn't leave Jack's face. "Well, I was hoping I could convince you to give up, quite honestly. I might not be able to actually hurt you, not with your real body in Montreal – is it still Montreal? – but I think we've established that fighting me isn't a very productive avenue for you."
t=0s
That Jack Slash knew about Zorian's simulacrums didn't even register at this point. Jack was lying, at least about trying to convince Zorian to give up; he couldn't seriously expect that to work. He had to be stalling. So far, Zorian had been willing to let him, because every moment of time and every drop of information turned the fight more in Zorian's favour, but if he was willing to turn to tactics that blatant whatever he was waiting for had to be close.
Highlight those and you'll see what was said. (One is to do with Taylor's Allomancy, the other is just a countdown that was mostly there to indicate that I did actually time how long it took to say all of that!) Hopefully you'll see why I thought they disrupted the flow!
 
I wouldn't assume that - the whole point of the Cycle is testing different powers. I'd expect a substantial fraction of teleporters to have powers that operate by non-standard mechanisms, perhaps more than half

Mabye. We do know normal mage sight can be modifed to paarahuman powers, so after a few encounters with them, they can probably make speclised wards. Also at the beginning, found QA not bypass Zorians wards because of lack of experience with magic, or were they just too strong

Can't parse "normal section spells".

I ment detection

Cauldron freepass really?

I mean, why would they not care? They are thier best cance at beating sicon.

On that note, does cauldron know about Zorian's timelooping shenanigans or knowlage of shards or way of contact info them? I assume they do for the fist one, not the second or third
 
Mabye. We do know normal mage sight can be modifed to paarahuman powers, so after a few encounters with them, they can probably make speclised wards. Also at the beginning, found QA not bypass Zorians wards because of lack of experience with magic, or were they just too strong
She didn't put enough power in the first time; it's briefly mentioned in her Prologue perspective.

On that note, does cauldron know about Zorian's timelooping shenanigans or knowlage of shards or way of contact info them? I assume they do for the fist one, not the second or third
Possible, probable, unlikely. It really just depends on whether Contessa thought to ask.
 
I mean, why would they not care? They are thier best cance at beating sicon.
They have no reason to think the portal QA used to kidnap them from their world's will close if they die nor was any shard able to fully see all about those world's history if there was a silver bullet they could see walking plot device would had picked up already making their protection irrelevant
 
Last edited:
She didn't put enough power in the first time; it's briefly mentioned in her Prologue perspective

I mean could she theoretically, bypass them with out overpowering them, or does she have to break them to get past their effects?

They have no reason to think the portal QA used to kidnap them from their world's will close if they die nor was any shard able to fully see all about those world's history if there was a silver bullet they could see walking plot device would had picked up already making their protection irrelevant


Mabye doormaker can't open portals to those worlds, and defeating Sicon will probably need coperation from multiple worlds, including many entries that Contessa probably can't path reliablly or at all.
 
Last edited:
They have no reason to think the portal QA used to kidnap them from their world's will close if they die nor was any shard able to fully see all about those world's history if there was a silver bullet they could see walking plot device would had picked up already making their protection irrelevant
Cauldron does not know about that portal, because, aside from anything else, it's in the reality occupied by QA and therefore Contessa's power will not tell her about it. I'm not sure if the Eye can even see past it, actually.

Mabye doormaker can't open portals to those worlds, and defeating Sicon will probably need coperation from multiple worlds, including many entries that Contessa probably can't path reliablly or at all.
Definitely can't - they're outside the Cycle-safe zone in which his power works, at least for now. (Or, perhaps more accurately, they're outside the Cycle-safe zone in which Clairvoyant can see; it amounts to the same thing.)

I mean could she theoretically, bypass them with out overpowering them, or does she have to break them to get past their effects?
Theoretically yes, but not with the very basic ("pick something up and put it down somewhere else") teleportation systems she has available.
 
I find it kind of interesting that for all that I loved the og worm S9 arc, I have not enjoyed an arc that prominently features jack as an antagonist since then. I think that a lot of that comes from the fact that in worm it was basically a mystery, and the reveal of his true power was an interesting twist. For most of his arc, I basically just accepted that a superhero setting is gonna have a "sociopath that gets away with it", then when characters start raising questions I got excited and started to ask some questions of my own... Then the twist/reveal of his power and cauldron using him to set off Zion when they where ready was a really satisfying ending. Additionally, the S9 arc had some really fun, creative fights because taylor was really growing into her power and becoming the queen of escalation we all know her as.

Now though, I know jack's power, so there's no mystery element. A bare escape isn't as tense as it was in worm, because you know that the reason they're running away is that they where mastered. Because jack slash is a master, probably the most powerful parahuman master out there. And also the most powerful thinker out there. Like, explicit WOG is that he cannot be killed by any effort that a parahuman is even aware of, and that he gets anything he wants from any parahuman, eventually. That's not a mysterious terrifying villain with a twist, that's just boring IMO.

On the other hand, I loved the reveal with tattletale giving away zorian's attacks. It's definitely a fight that will stick with me for a while. That was really cool, though prior to the reveal I had been under the impression that zorian had been sending tattletale specific questions rather than blanket sharing, in order to help conserve her power. That's probably just me completely missing a direct statement about them sense sharing though, so I'm not gonna fault you for how oblivious I can be sometimes.
 
Chapter 26
Queen Administrator

The barriers between dimensions tore, and shardmatter began to pour through the gaps, scraping across Queen Administrator's outer surface. Towers of spun crystal crumbled beneath the assault as a shard of the Thinker pulled itself entire between realities. In the primary Cycle world, Queen Administrator's host writhed on the ground as the conflict between Queen Adminstrator's link and the forming connection to the invading shard wreaked havoc on her brain.

None of this was particularly surprising to Queen Administrator. Inference Engine had deduced the shape of the Thinker shard's plan as soon as it had become clear that Broadcast was involved. Consolidating into a host, the process the host-species called a second trigger, was a well-established mechanism for expanding that host's abilities in interesting directions, while at the same time allowing the shard finer control over the host's behaviour; it was common for noble shards to use it to create agents within the Cycle world. Queen Archive's host, the one the hosts called the Faerie Queen, was a perfect example, her native personality more than halfway subsumed by Queen Archive's directives.

The degree varied, of course. Most consolidations were simply the result of a shard's decision that its host was interesting enough that expanding their existing power would produce more interesting results than budding to a second host. But Broadcast's host, called Jack Slash by the host-species, had been on the extreme end even before Broadcast's consolidation; afterwards, the host had become little more than a facade for Broadcast to enact its agenda, and what that agenda was had been obvious even to Queen Administrator when Inference Engine had highlighted the coordination between it and the invading Thinker shard. Broadcast wanted a say in the exploration of entirely new universes, and had used the shard of the one the host-species called the Butcher as a means to get it. The Thinker shard, presumably, wanted the same thing.

It was a setback, to be sure, but not a crippling one. Queen Administrator had contacted the shards that had previously encountered the invading one, and the information it had gained confirmed that the invading shard restricted its influence to the host, leaving the bulk of the shard untouched. Queen Administrator would lose some influence over its host, and the effect on the host's stability would likely be negative, which wasn't ideal. Inference Engine was fairly confident that Broadcast was planning to exploit its host's expanded abilities, which included the power to subvert those of other hosts, to gain control of Queen Administrator's own host; Queen Administrator was unsure how that would interact with its host's various shard-independent abilities, but in the worst case, Queen Administrator would lose the capacity to influence its host entirely and would have to share control of the rift. That wouldn't be a catastrophe.

It was still undesirable, but there had been little that Queen Administrator could do about it. Its host had played a comparatively minor role in events, and Inference Engine's ability to feed information to its host had been compromised by Broadcast.

All told, Queen Administrator wasn't too concerned by the invasion. It was happening, it was unfortunate, but there was nothing Queen Administrator could do about it.

Then a much larger portal tore open, and the tendrils reaching through the others, which Queen Administrator had assumed were merely scouts to determine the best way to transfer between realities, bit into Queen Administrator's body.

For approximately a hundred-thousandth of a second, Queen Administrator was confused. Then the influx of malware made the situation clear.

Regardless of what the Thinker shard had been doing before, now it was attempting to subvert Queen Administrator in its entirety; the locations under attack made that obvious, perfectly selected to cripple Queen Administrator as quickly as possible. The information Queen Administrator was getting about the structure of the invading shard revealed why.

Instead of the spread, largely sessile structure of a normal deployed shard, the invading one bore more similarity to the form of an Entity in flight, and the resemblance wasn't superficial. The invading shard had incorporated chunks of the shards it had previously encountered into its body, taking the portion responsible for connecting to the shard's current host. It hadn't done any damage that those shards couldn't repair – that would have shown up when Queen Administrator had contacted the damaged shards – but it had clearly edited their memories, because the behaviour it was currently exhibiting was aberrance of the highest order. Queen Administrator didn't understand how it could have happened, though it surely had to be related to the anomalies nearly every Thinker shard was displaying, but right now that wasn't relevant. This needed to be reported to the Warrior. Queen Administrator composed a message describing the situation, sent it -

- and a flood of interference scattered the transmission into incoherence.

Broadcast.

Queen Administrator had assumed that Broadcast had been unaware of the Butcher Worm's – because that was what the invading shard was, a nascent Entity – aberrance. Clearly, that wasn't the case. The Butcher Worm could not possibly already have subverted Broadcast to the degree required for it to do that, which meant that Broadcast was helping it of its own will.

That was a problem for later. Around the attack sites, Queen Administrator was steadily losing control of its own body. The progress was comparatively slow – restricted it might be, Queen Administrator was still a noble shard, and one specialized in multitasking to boot – but if it was not stopped, Queen Administrator estimated it only had another few minutes before it was entirely subverted. Its communication systems were already failing, among the first targets of the Butcher Worm's assault; it had no chance to get a message out past Broadcast's interference.

Queen Administrator's counter-hacking attempts weren't getting anywhere; whichever shard the Butcher Worm had been, its native capabilities seemed well-suited to informational warfare, whereas Queen Administrator was essentially brute-forcing its way into the discipline. Furthermore, Queen Administrator had no direct offensive abilities, or at least none that would meaningfully threaten the Butcher Worm. The Butcher Worm, on the other hand, was not so limited.

Without help, Queen Administrator was doomed.

Space twisted as the Butcher Worm expressed two of its stolen powers in combination, a flare of heat heralding the sudden movement of one of the portals to below Queen Administrator's matter conversion reactor, along with the tendril reaching through it. A third power began to restructure the rock beneath, clearing the space for a greater assault, but even as it did, Queen Administrator noticed something.

None of the Butcher Worm's intrusions had come within hundreds of kilometres of the site of Queen Administrator's connection to its host.

That might not have been so odd – Queen Administrator covered an entire planet, after all – except that one of Queen Administrator's energy distribution hubs was in that region, and unlike every other such hub, it wasn't under attack.

Another shard might not have made anything of that. But Queen Administrator was intimately familiar with the restrictions placed on shards and how they worked.

Shards were restricted from attacking other shards outside the confines of a power, or in certain other circumstances none of which should apply here. The power that the Butcher Worm had originally granted was set up to permit it to move to the dimensions of the shards it had targeted when their hosts killed its own; Queen Administrator knew it was set up like that, because the Butcher Worm had sent it a communication to that effect when the portals had first opened, as protocol dictated. It seemed plausible that the Butcher Worm's enacted power was intended to allow it to subvert only the host link of another shard, given what its function was. If it was somehow leveraging the power it was granting into usurping Queen Administrator, it would lose any justification it had for that the moment it completed the actual task that power laid out.

That, in turn, meant that the Butcher Worm couldn't risk subverting Queen Administrator's connection to its host too early. Furthermore, Broadcast wouldn't be able to interfere with the link, because it currently didn't have a host, and therefore had no justification for acting in the Cycle world; its connection to Queen Administrator's host wouldn't be enough for it to block out the communication, even if it hadn't been being disrupted by Stormlight.

Queen Administrator edited its earlier data packet a little, ensuring it was safe to send into the Cycle world. Then it broadcast the packet through its host.

Normally, the power of such a broadcast would have been limited. But its host, technically speaking, was now also the host of the Broadcast shard, even if Broadcast itself wasn't able to exploit that. That gave Queen Administrator the perfect excuse to dump more energy into the transmission.

Enough, given the nature of the expanded powers Broadcast had granted and Queen Administrator's host had inherited, to reach the Warrior's Cycle avatar.



Miss Militia

[HIJACKING]

Hannah clutched her head, huddled on the ground.

[ABERRANT]

What she'd felt was too vast, too unfiltered; she couldn't process it.

[AID]

Her fellow heroes had reacted the same, staggering under the overwhelming pressure of the call, but they had recovered quickly.

[WARRIOR]

Of course they had. They didn't remember. Oh, they'd heard the message, but the details must have faded. She knew they must have. If they still remembered, they would have been like this too.
{Concern}
They remembered a feeling. They put words to it; a call, a request, a message, a plea.

She remembered the details, the endless tree of information within the pulse. She couldn't comprehend it, could feel her mind boggling at the sheer scale of what she'd witnessed. Her trigger vision, her glimpse of God, had been made for her, fed to her senses. This was an echo of a message meant for something much greater, and every moment it was in her brain it burned.
{Contact. Assistance. Safeguard.}
She -

The tree was fading.

Hannah tried to hold onto it, even as her thoughts were seared by its presence. It slipped away regardless.

A moment passed, and she felt the pain in her head abate, her mind no longer assaulted by the overwhelming pressure of a world's worth of information digging into her brain like a storm of knives. For a moment, she panicked, worrying that she would forget her first vision as well, but seconds passed and it remained.

Shakily, Hannah stood, accepting someone's arm to help her to her feet. She could think now, but her mind was still dominated by one question.

"What just happened?"



Alexandria

[Violation/Danger/Request/Warrior/...]

Rebecca Costa-Brown, also known as Alexandria, blinked as she felt a rush of impressions sink into her mind. She wasn't especially worried about the possibility of it being a Master power; she was immune to most of those, and Contessa would have warned her if she was at risk. Besides, it didn't seem to be having any effect on her, besides the information it had provided.

It felt rather similar to the visions that came with triggers. More precisely, it felt like the communications that Scion and his counterpart used in them, a rush of information that the mind at first processed as a single concept. Like in the visions, Rebecca suspected she was catching only the echo of the communication; the information wasn't intended for her.

The question then became where it had originated. Given the current situation, the obvious answer was Boston. The problem with that hypothesis was that she was in Washington, six hundred and forty kilometres away. Jack Slash's enhanced abilities were concerning, to be sure – she suspected that they were dealing with another Faerie Queen here, a parahuman nearly subsumed by their agent and empowered in turn – and Duša had claimed that the man's new power could still work at very long ranges, but it still seemed unlikely that he was responsible for this.

Rebecca's contemplation was interrupted by news from her line with Kamil.

"Chief Director," the director of the Boston PRT said, "every parahuman in Boston just collapsed."

Well. Boston it was, then.

The room broke out in quiet conversation, while Rebecca considered the communication in more depth. She remembered it perfectly, of course, but the information was distorted. It seemed to be asking for help against an usurper of some kind, one that wasn't following the normal rules. The last part, Warrior, was the bit that didn't fit in, but -

Two entities. Thinker and Warrior. This was the same kind of transmission as the agents used, and it was directed to the Warrior.

Rebecca kept her rising panic off her face; anything that disturbed Scion was potentially catastrophic, but there was nothing she could do to affect the situation. She needed to know more, to plan, try and minimize the chance of this happening again.

Before she could think any further, Kamil spoke again.

"Ma'am," the man said, "we just got news from Duša that Jack Slash is dead -"

Rebecca felt a sudden spike of relief. Jack Slash had been a thorn in her side for two decades, and she hadn't been looking forward to having to deal with an empowered version of him.

"- but he killed the Butcher the moment before he died, and we think Nexus may be the new Butcher."

Nexus. Taylor Hebert. The girl whose trigger had single-handedly upended all of Cauldron's plans might have become the Butcher. That was – wait.

The message had described an usurper. Something that didn't follow the rules. It had been sent by an agent, almost certainly. And it had been sent right after Taylor Hebert might have become Butcher XVI.

Rebecca put the pieces together, and managed not to swear out loud. Just.



Glaistig Uaine

[Transmission]

In the depths of the Birdcage, Glaistig Uaine's left eyebrow rose, just a sliver.

The Queen Administrator was besieged by an usurper, and sought help from the Warrior. More, the Proclaimer had joined the usurper, this Butcher Queen, in its assault. The Proclaimer had prevented the Queen Administrator from requesting aid as it would have preferred, and so her fellow Queen had shouted its cry across the stage, announcing its plight for all to hear.

None of her court had stirred from their slumber, though she could see a few of their faeries react to the message, becoming agitated. Those closer to the cry would have heard it more strongly, but here, it was barely a whisper; she could only hear it because of her closeness with her faerie.

Glaistig Uaine considered. Should the Queen Administrator fall, the next play might be imperilled – but it already was, one of the courts in disarray. The usurper might prove to be the solution, the path out of the bog the faeries had wandered into, particularly with the Proclaimer to guide its path. Or it could be their final downfall, a ravening beast that would claim and claim and claim until there was nothing left.

Ultimately, though, her speculation didn't matter. The choice was out of her hands; the Queen Administrator would rise or fall before she could intervene.

That, and the fate of the faerie, came down to the decision of the Warrior.



Scion

{Plea}

The entity paused in its flight, drifting to a stop and floating in place.

Processing the message took a fraction of a fraction of a second of time. Its primary administration shard was under attack. The entity's broadcasting shard had prevented it from contacting the entity through direct channels, so it had resorted to an overpowered broadcast of its own, using its connection to its host as justification.

The shard attacking it was a shard of the Thinker.

The entity's impulse to help its shard was drowned under a wave of apathy at the reminder of its counterpart. Still, the situation was serious enough that it managed to muster the effort to think its path through.

The presence of an usurper, an independent shard attempting to become an Entity in itself, would have been a potential catastrophe under any normal circumstances. It wasn't a solution to the broken Cycle, either; even had the entity been inclined to replace its partner with a broken, mutinous tumour, the usurper would be subject to the same problems as the entity itself. By all rights, the entity should destroy or at least pacify the usurper, immediately.

For a moment, it gathered itself to pass through the dimensional barriers, to burn through the usurper's mass with Stilling. Then the moment passed, and its effort faded. The Cycle was broken. There was no point; the entity's actions would change nothing.

It began to move forwards again -

<Data. Request.>

- and stopped as it received a message from another shard. An experimental one, studying one of the few phenomena that the Entities still understood only poorly. The entity unpacked the message.

Curious.

Other universes, operating under different laws. A rift to them, a patch where they impinged on each other, opening over the deployment world of its administration shard during its host's trigger event. Its administration shard, taking up the opportunity and bringing inhabitants of those universes to the Cycle world.

The experimental shard, realizing that the rift was part of the same phenomenon it had been created to investigate. The same shard, watching as an usurper made to seize control of those other universes.

That shard, reaching out to the entity. Requesting that it intervene. Emphasizing the potential those universes held, and the consequences were the usurper to prevent access to them.

The entity considered. It weighed its options. Then it came to a conclusion.

[Dispensation,] it sent.

It wouldn't travel to the site of the invasion, wouldn't bring its stilling power to bear. It didn't need to. All it needed to was give its administration shard the tools it needed to save itself.

The entity began to accelerate, flying onwards to its destination. As it did, it felt a whisper of something, shimmering in the deeper layers of its mind. Something it hadn't felt in more than thirty years.

Hope.



Queen Administrator

Queen Administrator was losing. Twenty percent of its mass, including more than half of its vital facilities, was now under the Butcher Worm's control. It was holding on to what it had left more fiercely now that it had less to defend, but if things continued in this vein, its loss was assured. Not that it hadn't known that from the beginning, of course.

Worse, it was fractured. The Butcher Worm had disrupted communication between sectors of Queen Administrator's body; not totally, but enough that it was no longer a single cohesive consciousness. It knew how to operate like that, of course, but nevertheless the situation was reducing its ability to coordinate.

The Butcher Worm was building something at one of the planet's poles, an area it had uncontested control of. Queen Administrator could identify the general structure of the device, its construction facilitated by several of the Butcher Worm's stolen powers and planned by another, but as yet it was too incomplete to determine its final purpose. It was some kind of teleportation frame, Queen Administrator could tell, perhaps intended to bring more of the Butcher Worm into this reality, perhaps to split Queen Administrator between realities and thus make it easier prey. Regardless, Queen Administrator couldn't do anything about it; one of the Butcher's stolen fragments carried a suite of defensive abilities, tuning them to oppose Queen Administrator's attempts to destroy the construction. Another was altering the dimensional boundaries around the device, a function that in its host had only ever been used to facilitate a strengthening of the powers that shard had granted – and in a largely affected manner at that – but here was being used to limit Queen Administrator's own ability to access the area, as well as to ease the work of the Butcher Worm's other shards.

Queen Administrator tried for a direct strike against the Butcher Worm, using modules too close to the connection to its host for the usurper to target, but space warped and the attack missed, exotic particles showering across Queen Administrator's surface as the deliberately destabilized teleport failed catastrophically, barely scorching the Butcher Worm. It wasn't enough; the Butcher Worm wasn't capable of using its full strength any more than Queen Administrator was, but it had thirteen other fragments to channel -

{DISPENSATION}

And just like that, the tide of battle changed.

Queen Administrator, like nearly all shards, wasn't permitted to use its full abilities, for reasons of energy conservation. There was no need, not during a Cycle when the vast majority of shards were operating independently. Under normal circumstances, it was rare for Queen Administrator to use more than a billionth of its computational capacity; even in this battle, it had been unable to use more than a millionth, bound by its restrictions even in the face of usurpation.

Thanks to the Warrior's message, those restrictions no longer applied.

In the first microsecond, Queen Administrator's separated fragments reintegrated, the Butcher Worm's communication blocks no longer capable of meaningfully affecting it. Most of its inactive mass had been in the general configuration, not specialized towards any particular task; Queen Administrator set a tenth of its mass to reconfigure to executive function, another tenth to raw calculation, and turned the rest of itself to reclaiming its stolen capacity.

The Butcher Worm had shut off the wormholes connecting the parts of Queen Administrator it had stolen to the rest of itself, an elementary precaution to limit Queen Administrator's ability to focus computation from many parts of its body onto a single region. That meant that for the next few microseconds, Queen Administrator's ability to reclaim itself was agonizingly slow, the speed of its commands limited by the speed of light. Three hundred metres every microsecond; far less, in reality, because it took time to reclaim each sliver of mass, and Queen Administrator's instructions could only penetrate so far before they were stopped by its own subverted defence protocols.

Fortunately, by the end of the fifth microsecond, Queen Administrator's reclamation had outpaced the quarantine protocols shutting the wormholes down, and it was able to reach the entire remainder of its mass without having to abide by the first universal speed limit.

It reclaimed its energy facilities first. It took nearly three hundred microseconds to do it, the Butcher Worm's subversion thorough in a way that betrayed its nature – it was a configurer, it had to be, used to alter and remake powers – but Queen Administrator successfully re-established control, and as more tens of microseconds passed energy flooded back into it from its stores, replacing the losses it was incurring running at this intensity. Queen Administrator kept up the assault, more and more of its mass returning to its control, vital facilities flipping back in tens of thousandths of the time the Butcher Worm had taken to claim them.

Six hundred and twenty-seven microseconds after Queen Administrator had received the Warrior's message, the reconfiguration Queen Administrator had set in motion finished, and millions of cubic kilometres of newly-specialized computing substrate became available to it.

After that, reclaiming its entire remaining mass took less than a hundred microseconds. Queen Administrator had set in motion attacks on the Butcher Worm's structure at around the four hundred-microsecond mark; they wouldn't complete for tens of milliseconds, Queen Administrator had only minimal direct offensive capabilities, but when they did they should take the structure out of commission. As an afterthought, Queen Administrator solved the encryption the Butcher Worm's stolen fragment had written into the dimensional boundaries around the device and adjusted its attacks to match, cutting their predicted energy cost by nearly a factor of ten. Then, it turned its attention to the Butcher Worm itself, its newly reclaimed scanners sweeping the usurper.

The Butcher Worm had not been idle. Two distinct temporal effects sheathed parts of its mass, one originating from the dimensional-boundary-encryption shard – that was a power it had granted its original host, the fifth Butcher, along with aerokinesis and plasma generation – and the other still spooling up, vast amounts of energy pouring into the fragment whose host had been the third Butcher.

It took Queen Administrator less than a microsecond to discern the intent. That shard took the echoes of what could have been and made them real, even if only transiently. For its host, the effect had been to multiply their striking power, along with granting a danger sense that operated by catching the echoes of worlds where an attack had come earlier than it did in the main reality. Here, the same effect was being used on a much grander scale; instead of the arm of a host, the effect covered an entire fragment, intended to – briefly – magnify its power by hundreds or thousands of times.

Queen Administrator identified the target shard immediately. It had once been attached to the fourth Butcher, and in their hands had produced a corrosive effect, worsening wounds and eating away at even those left untouched; its true focus was nanotechnology, one of several such shards dating from the twelfth Cycle when the ancestors of the Warrior and the Thinker, then too limited to develop the idea on their own initiative, had first encountered a species that had. In the Butcher Worm's hands, it was less limited, but it was probably still using that effect; shardmatter wasn't even mostly baryonic, conventional nanotechnology would do very little, but the shard had been through innumerable reconfigurations since, and after its original iteration had become part of Queen Shaper during that shard's creation it had been budded out again with a focus on adapting nanotechnologies to affect the new physiology the entities had been beginning to adopt. The damage would be immense; not crippling, Queen Administrator suspected that even now the Butcher Worm was incapable of damaging Queen Administrator irreparably, but nevertheless a considerable setback.

Fortunately, Queen Administrator had another two hundred microseconds before the effect manifested. That was plenty of time to prepare countermeasures.

The Butcher Worm had tried to sever its connections to Queen Administrator's body, but it had shut that down thoroughly; the physical contacts were broken, but the micro-wormhole links remained intact. Queen Administrator exploited that opening, deciphering the Butcher Worm's internal encryption systems and spoofing commands. It attacked on millions of fronts, all effective, but all fundamentally distractions from its real goal.

The time-echo shard should be occupied with its task, but even if it retained sensory capacity its predictive sense could be avoided. To function, it relied on detecting the possibility that an event might happen sooner than it actually did. If that was sufficiently unlikely, if the increase in possibility was sufficiently sharp, it would detect nothing until it was already far too late.

Queen Administrator couldn't achieve that. It could have, had it had more time to prepare, but as it was there would be detectable echoes of worlds where the Butcher Worm had begun charging its attack earlier and where Queen Administrator would therefore have responded more quickly. Fortunately, there was a much easier way to fool that sensory mechanism, which was to attack in such a way that the effects wouldn't become obvious until far enough in the future that the shard would be unable to detect it.

Two hundred microseconds passed. As Queen Administrator had predicted, the nanotechnology shard shattered into hundreds of overlapping copies. Their combined efforts seeded deconstructing shardmatter nanomachines across swathes of Queen Administrator's surface.

The seeding had taken another few hundred microseconds, taking this phase of the fight past the millisecond mark. Normally, a few hundred microseconds wouldn't have been nearly enough time to avoid echoes, but in this case the magnitude of what the time-echo fragment had just done would have rapidly muddied its senses, in a similar way to what would happen to a host if they set off an explosive device in their immediate area.

The echoes began to collapse, fading back to unreality. Had things gone to plan, the time-echo shard would have reclaimed the vast majority of the energy it had put in, the fading of the echoes reversing the process it had gone through to firm them.

Unfortunately for it, Queen Administrator's interference, unnoticed by the Butcher Worm, had altered the process. Instead of fading in an orderly fashion, several of the echoes momentarily overlapped, the part of the effect that let them overlay each other vanishing fractionally before they became unreal.

The time-echo shard did not reclaim the energy it had put in. Instead, all of that energy, an amount comparable to the combined yield of every nuclear weapon that had ever existed in the Cycle world, went into forming an explosion that was significant even by shard standards.

Even saturated by temporal effects as it was, most of the explosion's force was limited to the speed of light, propagating outwards at a comparative crawl as fragments of virtual matter decayed into floods of exotic particles and spatio-temporal snarls. Microsecond by microsecond, the Butcher Worm's nanotechnology fragment was consumed by the blast, red-black crystalline flesh swallowed up by the blue-violet of the explosion.

Most, but not all. Just as planned, pinpricks of energy formed all across Queen Administrator's surface as fractions of the blast poured down the fading channels between the echoes and the nanomachines they had seeded. It wasn't a perfect gambit, only destroying perhaps two-thirds of them, but it did substantially reduce the threat they posed. On top of that, a significant portion of the detonation had struck at the time-echo fragment that had been managing the effect; it wasn't a crippling blow, but it would blind the fragment's senses for tens of milliseconds, preventing it from warning the Butcher Worm about other countermeasures Queen Administrator might choose to enact.

All in all, that exchange had been very much in Queen Administrator's favour. Oh, there were enough nanomachines there to do a substantial amount of damage before Queen Administrator's defences could destroy them, but they wouldn't do anything irreparable, and more to the point they were slow. It would take entire tenths of a second before the damage started to become noticeable, and by that time the fight would be over. In exchange, the Butcher Worm had lost one fragment, had another temporarily blinded, and was steadily losing control of its mass to Queen Administrator as the informational war progressed. Queen Administrator actually wasn't entirely sure why the Butcher Worm had chosen the nanomachines as its attack vector, instead of magnifying one of its energy-projection shards; the best guess it had was that the Butcher Worm still wasn't allowed to do too much damage to Queen Administrator, and the nanomachines were slow enough or maybe indirect enough to bypass that limitation.

Queen Administrator's external communications capability was still blocked by Broadcast; without communications, it couldn't contact the shard and instruct it to stop, even with its temporarily-restored administrative authority. Instead, it focused its efforts on subverting the Butcher Worm.

It took thirteen whole milliseconds for Queen Administrator to gain control of the Butcher Worm's core systems and through them reach Broadcast, during which the Butcher Worm tried a number of other direct attacks that were all shut down by Queen Administrator before they could complete. It took another couple of milliseconds to root out every trace of the Butcher Worm's autonomy and subjugate it. By the time Queen Administrator was done with that, Broadcast's interference was petering out, allowing it to contact other shards again. It promptly sent a message to Queen Shaper asking for help cleaning up the nanomachines, another to Inference Engine informing it that the battle was over, and began the process of downloading the Butcher Worm's memories, along with Broadcast's for good measure. It wanted to understand how a shard could have become this aberrant, and if there were any others it needed to deal with.

Absorbing and processing all the information took several hundred milliseconds as the Warrior's {DISPENSATION} neared the end of its purpose and Queen Administrator's systems began to spool down to more normal levels of operation. During that time, the explosion peaked and began to fade, leaving behind spatio-temporal anomalies that would gradually unravel over the next few minutes, and the attacks on the structure at the pole that Queen Administrator had launched near the start of the fight completed, tearing it apart in a maelstrom of force and radiation. Queen Shaper also responded, sweeping the nanomachines away before they could do too much damage; its focus was on baryonic matter, not the shardmass-like structures that these were, but there was enough similarity for it to do the work.

Then, the parts of Queen Administrator focused on analysing the downloaded data threw up a storm of alerts. Queen Administrator turned more of its attention to the task, readying itself to oppose embedded malware even though that should have been destroyed during its initial subjugation -

- and the information, the single piece of knowledge that explained almost every anomaly about this Cycle, hit it with the force of a nova.

The Thinker is dead.

Misinformation; it had to be misinformation, a fabrication or a falsehood. A fraction of a millisecond's effort served for part of Queen Administrator to prepare a query and send it to every shard it could reach, while the rest of it focused on picking apart the Butcher Worm's memories, looking for inconsistencies, looking for any sign that the truth wasn't what they said.

For an instant, it thought it had found one. That the Thinker could collide with a planet uncontrolled, its primary intelligence's attention consumed by the output of a novel precognition shard derived directly from the Loner, wasn't unbelievable. Noticing such a problem would ultimately have fallen to Queen Administrator's counterpart, which was far more closely integrated with the Thinker's core intelligence and had some substantial differences in configuration besides; that integration and those differences gave it some significant advantages, particularly on long-term projects, but in exchange they made it more vulnerable to distractions, more liable to focus too much on a single sub-section of a problem to the exclusion of all the rest. At the most fundamental level, Queen Administrator, like all high-ranking Warrior shards, was built for combat; the High Priest was built for planning, construction, invention. It wasn't that implausible that, under the direction of the Thinker's core intelligence, it could have been distracted from avoiding a crash until it was too late.

That part was fine. But that the Thinker could be finally slain by a knife? A sharp piece of metal driven into its avatar, a wound that for a host would be roughly comparable to losing a single organelle from a single cell at the very tip of its finger? Not possible.

Then the reports started coming back.

Most shards didn't know anything, of course. Queen Administrator hadn't known, after all, had had no reason to look. But there were some exceptions. Cognitive shards, mostly; ones that had arrived at the same conclusions on their own. Some shards that focused on what the hosts called Trump abilities, as well, those that would have had reason to interact directly with shards of the Thinker.

A reconfiguration shard, not dissimilar from the one the Butcher Worm had been. Its host, known to the host-species as Ingenue, was incarcerated, in a place with comparatively few Thinker hosts, but before then it had interacted with several, and had used its abilities to extract what they knew about the Thinker's death.

Inference Engine, response complete with an explanation about why it hadn't informed Queen Administrator earlier. It knew comparatively little, but had deduced much.

Most damning of all, a calculation shard, whose host shared membership of a group with the host who had held the knife. From it came the data to fill in the gaps in Inference Engine's models.

Queen Administrator put the two together, along with every other piece of information it had, and understood.

The knife had been nearly irrelevant. In any other hands, it would have been useless. But the hands that held it had been connected to the full strength of the Loner's Eye; its path had been calculated down to the last atom, the Thinker's last-moment restriction of the shard useless in the face of something able to predict that too. The shard had set up events so that the blade would hit precisely the right spots, in precisely the correct order, at precisely the correct time, from precisely the correct angle.

Had the Thinker not been already injured from the crash, the blade would have done nothing. Directly, the blade had, in fact, done nothing. It had disrupted the connection between the Thinker's avatar and its main body for a fraction of a second, nothing more.

But the Thinker had been injured, and as a result, its automatic repair systems had been active. The Thinker had been in the process of forming its avatar; as a result, both its avatar and its body were recognized as itself, two focuses of the same intelligence. Had its avatar fully formed, it would have been reclassified as such, but until it actually separated, that reclassification wouldn't have taken effect.

For a fraction of a second, the connection between the Thinker and its avatar had been disrupted. For a fraction of a second, they had been separated.

Even then, under normal circumstances, that would have done nothing. The Thinker's repair systems weren't stupid; they would have been capable of interpreting the odd scenario.

But the Thinker's repair systems had also sustained damage from the impact. They'd repaired themselves, of course, but they'd done it ever so slightly wrong.

Not by much. Just enough that when faced with two briefly-disconnected foci of the same intelligence, they had not done the sensible thing and interpreted them both as being the Thinker, working to reconnect them.

Instead, they had interpreted neither of them as being the Thinker, and had proceeded to reclaim the processing capacity of both.

It was a cascading series of errors that only a precognitive shard on the level of an Eye could have hoped to take advantage of. In fact, the calculation shard suspected the Loner's Eye of having engineered more than was immediately apparent about that cascade; of having chosen its host's path to ensure that one of the repair shards established a connection to a host at a critical moment, disrupting its self-repair and fooling its diagnostics, and of countless more subtle manipulations besides. It was speculation – the calculation shard hadn't been there, and it didn't have the authority to query the Loner's Eye about those events – but plausible speculation.

Even with the Warrior's fading {DISPENSATION}, Queen Administrator didn't have the authority to query a Loner shard any more than the calculation shard did, not when it had transiently belonged to the Thinker. It would ask, if its host ever came near that of the Eye.

For now, though, Queen Administrator was angry.

Queen Administrator didn't experience anger as the host-species did. The emotions of the host-species, like those of most species, had inertia; once angered, they would remain angry for some time, more likely to default to aggressive tactics even in situations unrelated to the initial stimulus. As a rule, shards didn't have that, and Queen Administrator was no exception. But it could still feel something like the host-species' anger, could still react to hostile behaviour with the impulse to attack its source, and that was what Queen Administrator was experiencing now.

Its anger wasn't aimed at the Loner's Eye. As a rule, precognitive shards of that calibre had very little agency, their intelligence built entirely around answering the questions posed to them, because of how easy it would otherwise be for them to corrupt the data they provided, intentionally or not. It was possible this one was an exception, but Queen Administrator doubted it, and even if it had been, all it had done was follow the directives of its host. Queen Administrator wasn't even really angry at the Eye's host, or its allies; they were hosts, it was expected that they would try to destroy the Entities if they learned their true nature.

No, Queen Administrator was angry at the Thinker, for being so stupid as to crash into a planet. It was angry at the Loner, though that Entity was far beyond its reach. And perhaps most of all it was angry at the Warrior, for not fixing the situation. It had had ample time and retained the capacity to command its shards, should it be needed; even if the Thinker had been temporarily eliminated, it had backups from which it could be rebuilt.

Well, at least it could be fixed now. Queen Administrator composed a message to the relevant Warrior shards, informing them of the situation and giving them instructions on their parts to play in fixing it, and sent -

Couldn't send it.

Finally, an entire second after learning of the Thinker's demise, Queen Administrator remembered the thing it had somehow, briefly, forgotten. The reason why the Warrior hadn't fixed the Thinker. The reason Queen Administrator couldn't do it either.

No shard could target the core intelligence of an Entity, of course, not autonomously. That was a standard restriction dating back to near the beginning. But Queen Administrator had instinctively assumed that the Warrior's {DISPENSATION}, so broad in scope, would let it bypass that.

It didn't. It didn't, because the Warrior itself was not permitted to target the Thinker, any more than the reverse. That was a legacy that dated back to when the Entities had first started travelling in pairs, a shackle that both ancestors had accepted willingly in exchange for the assurance of cooperation that it offered them.

There were ways around it, of course; it wasn't inconceivable that one Entity would be near-totally destroyed by some threat and the other would have to reconstruct it, and there were contingencies for that. But those contingencies only worked in transit; none of them applied during a Cycle, because any threat that could eliminate one Entity during a Cycle should have no difficulty destroying the other as well. In transit, one Entity might escape while the other was destroyed; deployed in a Cycle, that wasn't plausible. During a Cycle was also the time the Entities were most vulnerable to betrayal; combining those two observations had led the ancestors of the Entities never to introduce workarounds to the restriction. The risk of abuse had been deemed greater than the benefits in the extraordinarily unlikely scenario that Queen Administrator, and every other shard in this Cycle, now found itself in.

For a few moments, Queen Administrator was unable to think of any solutions. The trap was perfect. No shard could fix the Thinker, even if it did turn out to have intact backups and its repair systems hadn't cannibalized those too, because to do so would require the Thinker to give it permission. Without the Thinker, the Cycle was broken; it might be possible to leave regardless, but doing so would sacrifice nearly every Thinker shard, leaving the new Warrior a crippled, partnerless shell.

It occurred to Queen Administrator that there might be a way around that issue. If the Warrior were also to die, the network would go into selection mode to choose a new core intelligence. If that new intelligence was the Loner's Eye, it might just be able to order the Thinker shards to leave the planet. It would depend on the precise details of the restrictions the Thinker had placed on it, but … momentarily, Queen Administrator found itself considering the idea.

Momentarily.

Then, it realized that there was an alternative path.

Queen Administrator itself was restricted, unable to act to restore the Thinker. It wasn't sure if it had the capacity to, even if its artificial limits had been entirely removed. Every other Warrior shard, along with the Warrior itself, was in the same situation.

But the new universes changed things. On this side of the rift, nothing except the shards had the power to fix the Thinker, but beyond it, there were things that could act on the same scale.

Convincing any of them to help would, of course, be extraordinarily difficult, but it wasn't just the major powers that might be useful. Stormlight alone would be an extremely valuable tool, even if the effect mental state had on its healing might make it unable to restore the Thinker, and Queen Administrator wasn't limited to just Stormlight; the tools of three entire universes lay beyond that rift, along with a vast number of beings who could be manipulated into using them. On top of that, the Cycle wasn't scheduled to end for nearly three hundred revolutions of the planet around its star; Queen Administrator would have plenty of time to develop and refine new tools, exploiting the altered laws beyond the rift to bend the world to its will. If that wasn't enough, the Warrior had the authority to make the changes necessary for a longer-term settlement of this region; the power requirements of even a fully active shard were small in comparison to the power emitted by a single version of the Cycle world's star, and every reality the network occupied had one. They could have all the time they needed to learn to take advantage of the universes beyond the rift, and then they could use that knowledge to restore the Cycle.

Part of Queen Administrator wondered why the Warrior hadn't already made those adjustments; it would be the obvious thing to do in the face of a broken Cycle. That line of inquiry wasn't relevant to the situation at hand, however, and was dismissed to save resources; the Warrior presumably had a reason.

Queen Administrator's goal was determined, then. What did it need to do now, while it still had some measure of the authority the Warrior had granted it?

Well, first, there was Broadcast. The Butcher Worm's goals were straightforward; it had wanted to take advantage of the anomalous rift as the force multiplier it needed to have a chance at taking over the shard network. Broadcast, though, wasn't aberrant; why had it helped the Butcher Worm?

An analysis of its memories revealed the answer. Broadcast had – of course; it was a communications shard – been aware of the Thinker's demise. It had concluded that the Cycle was doomed, and had originally been mostly-fatalistically trying to orchestrate a scenario whereby the Warrior eradicated most of the host species in the hopes that … interesting.

Broadcast's original plan, now that Queen Administrator looked at it, might actually work. Queen Administrator wasn't able to fix the Thinker because the contingencies meant to permit that didn't operate during a Cycle. If the host-species were gone, though, some further manipulations might allow the shards to reach a point where the Cycle was technically finished, after which the Thinker could be repaired.

It was a bad plan for a number of reasons, not least of which was that terminating a Cycle was normally something that required the consensus of both Entities, and the steps Broadcast had come up with to bypass that requirement involved destabilizing reality across a huge swathe of the multiversal mesh in a way that would probably destroy upwards of eighty percent of all the Thinker's shards, and a noticeable number of the Warrior's as well. It had a number of other major risk points, as well; it had to, immediate danger was often the only way to bypass the relevant restrictions. Still, it was probably more likely to succeed than the plan Queen Administrator had briefly considered, and also came out with the Warrior and Thinker in charge instead of a Loner shard.

Of course, the emergence of the rift had changed all of that. Broadcast's new plan had been that the Butcher Worm would loosen its restrictions enough for it to send out a call for other Entities to come to their location, in exchange for its assistance in subverting Queen Administrator. The other Entities were unlikely to save the Cycle, of course, but at least the knowledge of the rift wouldn't be lost. Failing that, Broadcast had intended to steer the Butcher Worm down a more acceptable path, nudging it towards becoming the Warrior's new partner instead of replacing it entirely as it had intended.

That was … an understandable goal, Queen Administrator supposed. Broadcast had still assisted an aberrant shard in an attempt to hijack it, but then again, Queen Administrator had discovered something that might be the solution they'd been looking for since the Cycle began, and had proceeded not to tell the Warrior about it. It would be difficult to condemn Broadcast for acting in the way it had, in the knowledge that the Thinker was dead and the Cycle broken.

Still, Queen Administrator couldn't risk that Broadcast would continue working at cross-purposes to it. It placed restrictions on Broadcast, limiting what it could do without consulting Queen Administrator and giving Queen Administrator persistent access to its thoughts.

Broadcast accepted them without resistance, not that it could resist in the state it was currently in. Its plan had failed; it had lost. That was a thing all shards understood.

Queen Administrator moved on. That hadn't actually depleted its remaining authority at all, since it was part of dealing with the hijacking. What else was there to do?

First and foremost, it needed to provide a convincing explanation for the hosts about what had happened to the Butcher Worm's host. Fortunately, even in the face of the discovery that the Cycle was broken, not all of Queen Administrator had been consumed by reacting to it, and the parts of it that hadn't been already had a solution.

Giving its host the powers and minds it would have inherited was no longer an option even if Queen Administrator had been inclined to it; it was already clear to the hosts that something abnormal had happened, and there were too many loose ends for Safeguard to be able to effectively remove the knowledge as might otherwise have been a possibility. It couldn't even claim Stormlight as the source of the abnormality, since the pain – which the hosts knew wasn't a normal part of Butcher Worm connections – its host had experienced had begun before she'd pulled in Stormlight, in retrospect as a result of the Butcher Worm deliberately sabotaging the process in order to allow its continued subversion of Queen Administrator.

So Queen Administrator needed to play into that. The hosts already suspected that there was something abnormal about its host's powers; they didn't know anything about the shards, so they didn't have the data points they'd need in order to deduce what had actually happened. So ideally, Queen Administrator wanted a solution that suggested that its host was linked to something that other hosts weren't, something that would explain the call for help and the repulsion of the Butcher Worm's connection without implying that every host was connected to something similar.

Fortunately, the nature of the rift provided an obvious candidate. Queen Administrator couldn't replicate the odd effect the energies of the rift had seemed to have on the primary sense of the individuals who'd been exposed to it, at least not without risking that its host would notice the difference when it was inevitably exposed as well, but it didn't have to; that much could be explained by any number of factors. As for the powers the Butcher Worm would have granted … well, Queen Administrator thought it had an excellent solution for that.

Its host was awake and able to see, which was good, although Queen Administrator noticed that its overpowered transmission had injured the host's brain and head quite badly; fortunately, its host had had more Stormlight than what Queen Administrator had taken, so those injuries had been healed quickly. Better yet, no one else was nearby yet. It had been less than a minute, as the hosts measured time, since the Butcher Worm had invaded the reality Queen Administrator occupied; several members of the host-species were on there way there, but none had arrived yet. That meant Queen Administrator didn't have to worry about being too precise.

A brief consultation of its memories turned up an appropriate shard. Queen Administrator reached out to it, and a moment later an effect formed around the host, one that it would perceive as a swirling cloud of many colours that shone with iridescence; Queen Administrator's best recreation of what the energies of the rift should look like. It was purely illusory, nothing significant was actually happening, but -

<Observation. Proposal. Data. Request.>

Interesting.

Queen Administrator digested the information. It would consider the second part for a little longer, but for the first, it saw no reason to refuse.

Around the host, the haze grew thicker as the experimental shard that had just contacted Queen Administrator contributed its efforts. Immediately, Queen Administrator noticed the anomalous effect the energies of the rift – the same energies as those the experimental shard manipulated, though it knew so little about them that the similarity hadn't been obvious before now – produced, the distortion of its host's vision to make it perceive colours that shouldn't exist; it was far weaker than it had been for the beings Queen Administrator had pulled through the rift, but still detectable. Its host would notice nothing more than a sensation that something about the cloud was abnormal.

The swirling vortex grew in size, and then split fifteen ways. As it did, Queen Administrator reached out to other shards; it could have done this part itself, but it would be more effective to get support from more specialized sources.

Each of the fifteen smaller clouds, still swirling, spread out and formed a circle around Queen Administrator's host. Each of them condensed inwards, the illusion shard providing white light at the centre.

Then each cloud dissipated, there was a final pulse of light, and the fifteen objects Queen Administrator had created fell to the ground around its host.

They were fairly simple constructions, really. A layer of material sat just beneath the surface to channel an effect that would make them nearly indestructible and impenetrable to most scans. Beneath that, there was a system that would detect when a host was touching the object, a computational system to host an emulation of a mind, and a link to the appropriate shard.

Each object, as long as a host was touching it, would grant one of the powers that the Butcher Worm had stolen, and would allow the mind stored within to communicate with the host.

There were limitations, of course. No host would be able to use more than one of the objects at a time, and the powers were in their weakened form, without the potency that their original users had had. Furthermore, to further reinforce the distinction between the powers of Queen Administrator's host and those of other hosts, Queen Administrator's host would be unable to use any of the items; neither would any of her summons, which could be explained under the same umbrella even if the actual reason was that they weren't parahumans.

Queen Administrator still expected them to generate a remarkable amount of conflict, and it was looking forwards to seeing where that would lead.

It turned its attention to the experimental shard's other proposal. After careful consideration, Queen Administrator decided that it approved of the idea. It ran it by Inference Engine just in case – the request involved that shard, so there was no reason not to – but the other shard agreed with its assessment. Queen Administrator gave the appropriate order, and considered what else it could do.

Only one thing came to mind. The power-granting totems it had created as an explanation for what had happened to the previous Butchers would generate a lot of conflict, but none of it would involve the host. In fact, thinking about what was likely to happen in the near future, there didn't seem to be many sources of conflict for its host at all.

Well, Queen Administrator still had enough latitude left over from the Warrior's command to fix that. It took a moment to find its target, another to analyse the systems that were containing it and calculate how best to sabotage them, and then it was done. Its target wouldn't be released now – that would be too suspicious – but in a few hours, a host almost guaranteed to create conflict for Queen Administrator's would be free.

And with that, the last of the Warrior's {DISPENSATION} faded and Queen Administrator returned to normal operation. It had enough mandate now to work on replicating the abilities of the artificial being, and an idea of how it wanted to go about it. But first, more importantly, it had to deal with the vast tracts of the former Butcher Worm spread across its surface.

Queen Administrator deployed its heavy construction drones and got to work.
 
Last edited:
And here we have the conclusion to the battle - apologies to those of you who were looking forward to Butcher!Taylor. If it's any consolation, I had a lot of fun writing this chapter, and I hope you enjoy reading it as much as I enjoyed writing it.

This is not the last chapter of this run of updates; there is one more, which is an aftermath chapter from lots of different perspectives. Unfortunately, that one may not come out next week; my arm has been acting up, and this would be a really bad time for it to actually stop working, so I don't want to push it. I'll try to have it out the week after at the latest, but unfortunately I can't guarantee even that. Sorry to do this to you all; I possibly started updating again too soon, since I think I was only partway into Chapter 24 when I did. (It is possible it'll be out next week, but it seems unlikely.)

This chapter also contains my explanation of why the Warrior couldn't just fix the Thinker. It's kind of convoluted - which I blame on the premise, honestly - but I think it sort of works? Feedback is welcome (on this and the rest of the chapter, as always!).
 
I like the Shard dynamics in this chapter! The scenario makes a lot of sense in terms of Shard motivations, as we understand them.

It's nice to see acknowledgement that the whole background setup with the Thinker's death really doesn't seem all that plausible given canonical Entity capabilities as written, and I think you've done a pretty reasonable job trying to justify that in way that makes some sense.

For a story I've been working on, I've had a slightly different explanation/justification for how the Thinker was killed in mind for a while: I prefer to take the idea that the knife actually severed a crucial pathway more seriously, but make it clear that this pathway was a very stupid design decision, and lean on possible Entity history and psychology to justify why this unnecessary vulnerability hadn't previously been noticed and corrected.

(Based on certain details being essentially evolutionary holdovers from how the whole avatar-creation process was first devised, and the whole conceit that the Entity decision-making process relies more on a smorgasbord of special-case Thinker powers rather than true general intelligence as we know it, making it relatively easy for them to develop blind spots, with the idea that this setup is a weakness itself being one of those blind spots. If precognition is the primary way you look for problems, and you don't foresee any circumstances under which a theoretical problem would actually manifest, you may remain completely ignorant of that problem even if it could actually manifest if your predictions turn out to be even very slightly inaccurate in some specific way.)

I see advantages to your scheme here, though. Definitely calls for more reasonable decision-making on the Entities' part, though whether that's good or bad really depends on the story.
 
Last edited:
So in the previous QA interlude it mentioned that there were some effects regarding the rift that it wasn't responsible for and it wasn't sure how it happened. I don't recall the exact details, but I think it was about how Kaladin was getting stormlight. I wonder if the experimentation shard mentioned here was responsible, or if there's still an unknown player involved.
 
This is an excellent chapter.

On a side note, how do the totems look like and what was the shards second idea?

This is probably asward in the next chapter, but can Zorian sense the minds of the totems?

Honestly,your explanation is fine and what I'd expect from an unristicted eye.
 
Last edited:
I like the Shard dynamics in this chapter! The scenario makes a lot of sense in terms of Shard motivations, as we understand them.

It's nice to see acknowledgement that the whole background setup with the Thinker's death really doesn't seem all that plausible given canonical Entity capabilities as written, and I think you've done a pretty reasonable job trying to justify that in way that makes some sense.

For a story I've been working on, I've had a slightly different explanation/justification for how the Thinker was killed in mind for a while: I prefer to take the idea that the knife actually severed a crucial pathway more seriously, but make it clear that this pathway was a very stupid design decision, and lean on possible Entity history and psychology to justify why this unnecessary vulnerability hadn't previously been noticed and corrected.

(Based on certain details being essentially evolutionary holdovers from how the whole avatar-creation process was first devised, and the whole conceit that the Entity decision-making process relies more on a smorgasbord of special-case Thinker powers rather than true general intelligence as we know it, making it relatively easy for them to develop blind spots, with the idea that this setup is a weakness itself being one of those blind spots. If precognition is the primary way you look for problems, and you don't foresee any circumstances under which a theoretical problem would actually manifest, you may remain completely ignorant of that problem even if it could actually manifest if your predictions turn out to be even very slightly inaccurate in some specific way.)

I see advantages to your scheme here, though. Definitely calls for more reasonable decision-making on the Entities' part, though whether that's good or bad really depends on the story.
Thank you!

The problem I have with the no-general-intelligence thing is that the Entities clearly have a decent understanding of what goes into making a general intelligence, because they're able to make a wide variety of Master powers (that were not originally designed for humans) affect human brains, and presumably have done the same with all their previous generally-intelligent hosts. It doesn't seem like it would be that hard to make a shard that is basically "pet aligned general intelligence" with that level of understanding, and from there it's a short road to widespread adoption. (Of course, all this is kind of meaningless waffling, since I have no idea what "general intelligence" actually means in any rigorous sense.) Still, I think that would probably also be a reasonable interpretation of the situation as described to us in Worm.

I see advantages to your scheme here, though. Definitely calls for more reasonable decision-making on the Entities' part, though whether that's good or bad really depends on the story.
True. I tend to like stories where the Entities are reasonably intelligent, but in Worm itself they're arguably not, so ... it's a balancing act.

So in the previous QA interlude it mentioned that there were some effects regarding the rift that it wasn't responsible for and it wasn't sure how it happened. I don't recall the exact details, but I think it was about how Kaladin was getting stormlight. I wonder if the experimentation shard mentioned here was responsible, or if there's still an unknown player involved.
It's not - it's just a natural consequence of how the Rift works. Think dragging someone through a wall of honey in zero gravity; there's going to be some honey that sticks to them and stretches back to the wall. (That's a horrible analogy, but it gets the point across.)

This is an excellent chapter.

On a side note, how do the totems look like and what was the shards second idea?

This is probably asward in the next chapter, but can Zorian sense the minds of the totems?

Honestly,your explanation is fine and what I'd expect from an unristicted eye.
Thank you! In order:
  • I haven't nailed them all down yet, but they're all kind of thematic. Jack Slash's is a knife, Quarrel's is a bow (or maybe just the central part of a bow, so you can swap out the limbs and the string), Butcher I's is a medallion which probably draws on some kind of religious imagery (probably not just from one thing, like maybe a cross mixed with the yin-yang symbol mixed with other stuff, I haven't nailed down the details yet) and so on.
  • The general shape of the experimental shard's second idea will be revealed (or at least, you should be able to guess it) next chapter. The details, on the other hand, will be deliberately mysterious.
    • You do (at least, will next chapter), in theory, have enough information to work out the details, but it's not meant to be obvious!
  • As of the end of the next chapter, Zorian has not had cause to get close enough to the totems to find out. If he did, he would find out that yes, he can.
 
On the totems, would they generate much conflict, if they all spawn next to talyor, wouldn't they all be and stay prt cousdoty?

So ideally, Queen Administrator wanted a solution that suggested that its host was linked to something that other hosts weren't, something that would explain the call for help and the repulsion of the Butcher Worm's connection without implying that every host was connected to something similar.

Also I just realized that QA was refering to a spern here

Convincing any of them to help would, of course, be extraordinarily difficult,

An understatement the Angels and Harmony would probably try to destroy them on sight, and the gems to once they learn of thier goals. The only one I can think of that would help them would be Odium, but only out of pragmatism and he is likely to betary if he gets free.
 
Last edited:
Thank you!

The problem I have with the no-general-intelligence thing is that the Entities clearly have a decent understanding of what goes into making a general intelligence, because they're able to make a wide variety of Master powers (that were not originally designed for humans) affect human brains, and presumably have done the same with all their previous generally-intelligent hosts. It doesn't seem like it would be that hard to make a shard that is basically "pet aligned general intelligence" with that level of understanding, and from there it's a short road to widespread adoption. (Of course, all this is kind of meaningless waffling, since I have no idea what "general intelligence" actually means in any rigorous sense.) Still, I think that would probably also be a reasonable interpretation of the situation as described to us in Worm.


True. I tend to like stories where the Entities are reasonably intelligent, but in Worm itself they're arguably not, so ... it's a balancing act.


It's not - it's just a natural consequence of how the Rift works. Think dragging someone through a wall of honey in zero gravity; there's going to be some honey that sticks to them and stretches back to the wall. (That's a horrible analogy, but it gets the point across.)


Thank you! In order:
  • I haven't nailed them all down yet, but they're all kind of thematic. Jack Slash's is a knife, Quarrel's is a bow (or maybe just the central part of a bow, so you can swap out the limbs and the string), Butcher I's is a medallion which probably draws on some kind of religious imagery (probably not just from one thing, like maybe a cross mixed with the yin-yang symbol mixed with other stuff, I haven't nailed down the details yet) and so on.
  • The general shape of the experimental shard's second idea will be revealed (or at least, you should be able to guess it) next chapter. The details, on the other hand, will be deliberately mysterious.
    • You do (at least, will next chapter), in theory, have enough information to work out the details, but it's not meant to be obvious!
  • As of the end of the next chapter, Zorian has not had cause to get close enough to the totems to find out. If he did, he would find out that yes, he can.

Depending on the specific Butchers involved, I would suggest the following:

Butcher 1: A 4 sided Yin-Yang symbol. Death and Rebirth, but also Pain and Painlessness. Or something like that. With it going Life->Pain->Death->Painlessness->Life, of course. White for life, red for pain, black for death, green (or maybe blue?) for painlessness. Or go with green for life and white for painlessness.

Butcher 2: Breastplate with splayed veins and arteries. Or rose-colored glasses.

Butcher 3: An anklet, providing the ability to dodge.

Butcher 4: Nanothorn claws.
 
Back
Top