Voting is open for the next 22 hours, 7 minutes
Short of somehow abolishing sealing and getting rid of all knowledge of it, the only way to minimize shifts is to ensure that nobody causes sealing failures deliberately, and apparently there's already a secret organization doing that.

Assuming the shifts are being caused by sealing failures, anyway. Do we know that for sure yet?
Clearly ascending to godhood is the optimal solution here.

-suddenly solid clones cease to exist-
Come now, "It still doesnt work." is too simple a cop out to resort to retcons :p
You know, this is probably why you can't put chakra inside normal storage seals. The space inside the seal shouldn't be accessible to normal users and therefore doesn't have chakra mechanics defined. Result is some kind of exception that crashes the process.
That does make a lot of sense.

How do Jinchuuriki work then?:o
 
Hey programmers: If you make a program that produces an arbitrarily large number of crashes (for any reason) would the computer ever shut down?
 
Hey programmers: If you make a program that produces an arbitrarily large number of crashes (for any reason) would the computer ever shut down?

Programs shouldn't be capable of crashing a well-designed operating system. It's standard practice for them to execute in isolation and only access resources through well-defined interfaces.

In practice, it's surprisingly difficult for an operating system to protect itself from a denial of service attack by a program, so I'd think more along those lines. Try to request tons of different resources in rapid succession and see if anything gives.
 
Please don't try to crash chakra.

You look away for five minutes...​ :p

Don't worry. If it were me designing this system, there'd be a separate group of daemons assigned to each volume of space, so at most you'd be able to disable chakra in a given area for a moment.

... actually, that sounds really useful. And likely very achievable with a seal. Hm.
 
I support Hazou remembering Henge and other shifts that took place since his extradimensional sealing failure. Given how Kagome remembers them, it feels like a reasonable and interesting development of his identity as a sealmaster. As the first major shift for Hazou to remember, I feel like it would be reasonable for it to take him a while to remember it (more importantly, this would make currently-written chapters where he doesn't remember it still consistent), showing up in his dreams recollecting past events or causing him to brainfart as he plans because he almost thought for a moment that ninja could just disguise themselves as anything.

Once Hazou figures out what happened one way or another, it puts him one step further on the mad sealmaster route, but he's already knee deep in that and it doesn't seem to have impaired his socials (any more than usual, that is) so I don't mind advancing his character in that way.
 
I support Hazou remembering Henge and other shifts that took place since his extradimensional sealing failure. Given how Kagome remembers them, it feels like a reasonable and interesting development of his identity as a sealmaster. As the first major shift for Hazou to remember, I feel like it would be reasonable for it to take him a while to remember it (more importantly, this would make currently-written chapters where he doesn't remember it still consistent), showing up in his dreams recollecting past events or causing him to brainfart as he plans because he almost thought for a moment that ninja could just disguise themselves as anything.

Once Hazou figures out what happened one way or another, it puts him one step further on the mad sealmaster route, but he's already knee deep in that and it doesn't seem to have impaired his socials (any more than usual, that is) so I don't mind advancing his character in that way.
I don't. I don't want this to become MetaQuest.
 
Blend Wild Sorcery from DnD with FATAL's ridiculous outcome tables and throw it into the "Sealing Failure" outcome possibilities
 
Hey programmers: If you make a program that produces an arbitrarily large number of crashes (for any reason) would the computer ever shut down?
Broadly speaking, there are two kinds of errors. Handled errors, and unhandled errors.

Handled errors come with a plan for what the computer is supposed to do if it gets the error. 'Try to read file X; if file X doesn't exist, try file Y instead'. That sort of thing. Handled errors mean the program can keep running.

Unhandled errors don't come with a plan B. Maybe the programmer didn't bother to make one, or more often the programmer didn't foresee the error occurring. This results in a crash to desktop because the program's only instructions are something it can't follow, like trying to read a file that doesn't exist. Or if it's the OS that gets the unhandled error, then you've got a BSOD.
 
Last edited:
Voting is open for the next 22 hours, 7 minutes
Back
Top