It's supposed to be a seal, was this an error or did 'pilot decide to do it as a rune?
Wait, why a seal?
It both seems like the kind of project a rune would be better at, one explosive seal isn't enough to fully destroy a rune(but is enough the destroy other ELF seals), and an explosive tag is easy to recognise and remove(while a rune is inscrutible and nearly immovable).
 
It would be really funny if a random ninja finds the speed up rune, briefly stays there because it's so cool, goes back to tell their friends, and then it's blown up and no longer working by the time they return.
Random ninja probably doesn't even notice the effect. Haven't you ever looked at the clock and been surprised at what time it was? The EN doesn't have pocketwatches so ninja are gonna tell their time by the sun, and there's no way they're gonna think the sun is telling time wrong. Odds are they'd feel like it was a particularly long day, they'd feel more sleepy than usual as night falls, and summarily brush it off as a coincidence.

Unless it's Ami. Ami would probably find a way to notice the discrepancy.
 
Well, we're working on the "die" part of scry and die, so how about the other?

Distant Mirror Rune (aka Scrying Rune; if you'd like to use the latter name in-character that's fine, I just thought I'd provide you an in-universe-compatible name too)

Projects an image as the landscape-equivalent of the clone technique (a hologram, in RL-terms) of a given volume of space up to [X] distance away as if an eyeball were at a spot, though it is not one, where X is whatever Hazou thinks is easiest, to start. The location of the sensor may be changed while the rune is active.

(As for how it is changed, and this is just a suggestion and does not in any way prescribe that other runes will be capable of being interacted with similarly: I was musing on it as being based on chakra repulsion against the surface of the rune. The closer to the "bottom" you start, the more fine grained the movement, the closer to the top, the faster and farther it'll go. A second concurrent chakra repulsion adjusts the viewing angle.)

Ideally, the sensor is invisible and intangible (can freely pass through walls), although these are stretch goals that may freely be dropped if Hazou thinks it renders it too difficult. Ideally, the sensor takes continuous video; if that is too difficult, to start, Hazou can instead choose to make one that creates a single still image.

Design priorities are, in order:

1: Hazou can research it and it gives veterancy toward the higher-numbered design priorities
2: It allows for visual viewing of a distant area
3: Range
4: Adjustment of location viewed while rune is active
5: Video view, as opposed to snapshot
6: Viewport is invisible/intangible

These are not strict; if Hazou thinks one of the lower ones would be really easy to add (a cost of like, +1 TN or some such) by all means add it.

On-research-finish questions that we will inevitably ask: Can Noburi detect it? Can anti-hyuuga seals block it?

Suggested answers: No (this provides no information as to whether other people can, but it doesn't appear as a chakra-based effect, being runic in nature), no (anti-hyuuga seals block the particular chakra effect the byakugan uses).
I'd like to posit this as another rune we should absolutely do a prep day on; if its full effects come back easy, then we can use it as an alternative to contacting Oro.
 
So, have we done the dead drop with Oro yet? I'm thinking we might want to give the scrying rune a shot before we do. Might as well see if we can get the info without risking contact with Oro.

Nevermind, I should've scrolled up. The answer is "We haven't done the dead drop yet but we'll do it soon".

"Hazō." Mari's tone was sharp. "He's a teenage boy who was starved, abused, and tortured for months before being used as fuel for a ritual we don't know the nature of. That would traumatize anyone even if done by normal means but, according to Orochimaru's dossier, the Sharingan has an ability that imposes torture beyond what is physically possible. If you think you could go through all that and not leak information when your torturer shows up to question you then you aren't as smart as I think you are. And you are far too demanding."
Thank you, Mari. Its about time that someone pointed this out.
 
He's a teenage boy who was starved, abused, and tortured for months before being used as fuel for a ritual we don't know the nature of. That would traumatize anyone even if done by normal means but, according to Orochimaru's dossier, the Sharingan has an ability that imposes torture beyond what is physically possible. If you think you could go through all that and not leak information when your torturer shows up to question you then you aren't as smart as I think you are.
Literal skill issue. Hazou would simply choose not to be traumatized.
 
Last edited:
We are still waiting on the ones we did 3 weeks ago, with absolutely no end in sight. I think 6 weeks is a reasonable estimate.
I'm willing to wait that long if that's what it takes; having Hazou make suboptimal decisions out of convenience ain't the way I like to do this.

e: Besides, we can vote it in conditionally. If (Scrying Rune is doable) then do it and don't contact Oro, if (Scraying Rune is not immediately doable) then contact Oro immediately.
 
But we've already asked them if they'd be okay with running interludes for a while while they catch up on backlog and they said yes [...]

Fwiw, I'm also willing to read interludes. To that effect...

[X] (Interlude) Snowflake's Perspective on the Goketsu Missing Nin Experience

[X] (Interlude) Meanwhile, Back in Leaf...

[X] (Interlude) Ino

[X] (Interlude) Leaf's Hunter Nin, Tracking Hazō an Co.
 
Speaking of research backlog: @eaglejarl @Paperclipped @Velorien , when can we expect the research rolls from this chapter? (Prep days would also be nice, but I'm aware those take time; but we did (or should have done) DotB tracks on Remote Explosive, Landmine, and possibly more, and knowing how far along we are with those is important for this voting cycle.) We can vote in interludes if you don't have time to do them now, but I think we really do need them if we want to write any research-containing plan.

Also, @eaglejarl @Paperclipped @Velorien (pinging separately to make it clear this is a distinct question): the plan said that we should leave the dead drop for Oro, if it was approved. It seems like it was; did that happen, or are we being given a chance to e.g. specify a more detailed approach to getting round the Arachnid oath problem?
 
[X] (Interlude) Meanwhile, Back in Leaf...

[X] (Interlude) Ino

[X] (Interlude) Leaf's Hunter Nin, Tracking Hazō an Co.
 
Also, @eaglejarl @Paperclipped @Velorien (pinging separately to make it clear this is a distinct question): the plan said that we should leave the dead drop for Oro, if it was approved. It seems like it was; did that happen, or are we being given a chance to e.g. specify a more detailed approach to getting round the Arachnid oath problem?
This plan said to do it so technically we should simply go ahead and do it. Granted, the plan also acknowledged a major problem with the idea and suggested only one way around that problem, a way that is going to cause huge problems for Hazō and, if executed literally, could destroy his relationship with Kumokōgõ.

...Yeah, let's say the dead drop hasn't happened and y'all can vote in a more specific implementation.
 
That's fine? But we've already asked them if they'd be okay with running interludes for a while while they catch up on backlog and they said yes, and you didn't seem opposed to it, then. What changed?
Nothing changed. If I felt it was worth delaying updates by 6 weeks to get this information I'd vote for it, I don't.

I don't think it's particularly likely to move the needle on the dead drop.
 
[X] Lore Update

As interesting as the other options are, not getting information about the state of Leaf is kind of important in this arc.
 
Back
Top