Voting is open for the next 1 day, 18 hours
Random other references: Nobby the smol whiny boy and Hazou the smug machine

I think you nail Nobby. I am not so sure about Hazou.

Clearly we need to start a quest revolving around our real world personas in our attempts to influence the course of events in Marked for Death.

So Hazou is going to have to explain to sensei the nature of his tactical geniuses which consisted of talking heads communicating to him extra-dimensionally with lot of ideas, some good, and some bad, and you expect sensei to go along with it? Maybe she'll accept it as some kind of newfanged bloodline.

Also, don't forget the wiki looooooove has been lacking.
 
Keiko is not pleased with me and keeps not wanting to look cute at all. But she is anyway.

Keiko Line Work
Kawaiiii! Where can I sign up to get one?

Well, Hazou is a man of humble origins, driven by a collective consciousness, out to fix the world whether the world wants it or not, his actions often have disastrous unintended consequences, and we can't even imagine the unintended consequences of his long-term plans.

His theme is obviously The Internationale.
It gets even better when you factor in all the plans to uplift the commoners and rebel against the privileged ninja regime that dominates them while living off their labour.

Correct Horse Battery Staple
@eaglejarl, you were supposed to also change the password on the pangolin special elements doc!
 
Ninja Operation Manual page is created, along copy and pasted Hot Spring Failure Analysis.

Feel free to edit and extend those wikipages. I am trying to systematize our approach to making plans and avoiding costly mistakes in the future. The analogy I am using here is aircraft crashes and how every aircraft checklist are paid for in blood. We'll make a ninja checklist paid for in mishaps and blood as well.

Anyway, I know there's a dearth of people contributing to the wiki or keeping things up to date. But I must keep trying!
 
Last edited:
Ninja Operation Manual page is created, along copy and pasted Hot Spring Failure Analysis.

Feel free to edit and extend those wikipages. I am trying to systematize our approach to making plans and avoiding costly mistakes in the future. The analogy I am using here is aircraft crashes and how every aircraft checklist are paid for in blood. We'll make a ninja checklist paid for in mishaps and blood as well.

Anyway, I know there's a dearth of people contributing to the wiki or keeping things up to date. But I must keep trying!
I'm on mobile and new at this, so I didn't put links but did add the SOPs we need to put there that I could think of (maybe should add one for "how to write a good plan" as well, which is somewhere in the knowledge doc).

HISSS is linked in someone's signature, lemme go look...

E: it was in @Jello_Raptor's, here
 
Last edited:
I think I can be properly motivated to write a mission statement and start the brainstorm on how we should move forward to complete that goal. Military style documentation on what our group is about and how we should go about our business of correcting the faults of the ninja world. We really should think about expanding out from our cell into an actual organization to enact real change on the world. There is only so much that we as a group of 6 can do against the whole of the rest of the ninja world. We have to talk with leaders of all types, industry, agriculture, military. A force strong enough to be taken seriously will be needed to do that.
 
I think I can be properly motivated to write a mission statement and start the brainstorm on how we should move forward to complete that goal. Military style documentation on what our group is about and how we should go about our business of correcting the faults of the ninja world. We really should think about expanding out from our cell into an actual organization to enact real change on the world. There is only so much that we as a group of 6 can do against the whole of the rest of the ninja world. We have to talk with leaders of all types, industry, agriculture, military. A force strong enough to be taken seriously will be needed to do that.
Sounds like we need to subvert Jiraiya's organization :D

(Also, we're now <600 replies from being the 8th most replied quest on SV! That's only, like, two days' worth of frantic panicking for us, no biggie! :p)
 
Last edited:
I'm on mobile and new at this, so I didn't put links but did add the SOPs we need to put there that I could think of (maybe should add one for "how to write a good plan" as well, which is somewhere in the knowledge doc).

HISSS is linked in someone's signature, lemme go look...

E: it was in @Jello_Raptor's, here

Are these really necessary, especially if the details are happily taken care by our QMs? In-story, Kagome would be the one advising us not to get screwed over by experimentation.

I want to focus on plan checklist, because that where the players can most affect the survival of our group and our goal.

SOP could be useful if we could keep our QMs from forgetting that Nobby have a barrel that we should be using and that we have X and Y anti-pursuit tools in our arsenal, and the like. It could also prevent us from tediously writing plans. Instead we could refer to our "anti-pursuit" SOP and modify as needed.
 
Last edited:
especially if the details are happily taken care by our QMs?
They aren't happily taken care of, though. The fact that we didn't chakra boost away from hot springs was a big deal a couple chapters back, and part of that was that our running away procedure was insufficiently specific. Hence, write out an SOP for it (which @Velorien specifically recommended at the time, I believe) and just reference it in the future.

In-story, Hazou does have a list of sealing safety procedures that got looked over by Kagome. That's what HISSS is.

It could also prevent us from tediously writing plans. Instead we could refer to our "anti-pursuit" SOP.
Yes, exactly this.
 
SOPs are macros that should have enough flexibility to be modified with a few lines during a planning session. What those few modifications are will be what we debate and generate ideas for that specific situation.
 
They aren't happily taken care of, though. The fact that we didn't chakra boost away from hot springs was a big deal a couple chapters back, and part of that was that our running away procedure was insufficiently specific. Hence, write out an SOP for it (which @Velorien specifically recommended at the time, I believe) and just reference it in the future.

It's a double edged sword, what the GM forgets about the opposition may stack against our favor, or maybe not. if the GM forgot about the Iwa-nin, we would be able to get out of Hot Spring with ease.

I think I am in favor of SOP. It will decrease uncertainty, and with great SOPs, we will also decrease risk.
 
SOPs are macros that should have enough flexibility to be modified with a few lines during a planning session. What those few modifications are will be what we debate and generate ideas for that specific situation.
I look forward to the day when our plans are just code to be executed by the QMs :D

Code:
flee('HotSpring', 'Fire', 'Iron', 'rivers'=True, 'boost'=True);
camp('MEW'=True, 'KagomeSec'=True);
debrief('Hugs');
if training_time(CURR_UPDATE):
       rest_recuperate(medic='Nobby');
       research_hazou('PMYF2');
       research_noburi('VD');
       training_keiko('Contracts');
       training_akane('PunchStuff');
else
       rest_recuperate(medic='Nobby');
 
Last edited:
Code:
flee('HotSpring', 'Fire', 'Iron', 'rivers'=True, 'boost'=True);

Is it bad that I see this and my first reaction is about how bad an API it is?

I mean 'HotSpring', 'Fire', 'Iron' is a list of locations we have to traverse in order, and shouldn't be a set of independent parameters. Not to mention 'HotSpring' is the supposed current location and should be implied by the state of the system.

It really should be something closer to:

Code:
flee(['Fire', 'Iron'], 'rivers'=True, 'boost'=True);

Also, flee should probably a monad rather than a function, but that's more debatable.
 
Last edited:
Is it bad that I see this and my first reaction is about how bad an API it is?

I mean 'HotSpring', 'Fire', 'Iron' is a list of locations we have to traverse, and shouldn't be a set of independent parameters. Not to mention 'HotSpring' is the supposed current location and should be implied by the state of the system.

It really should be something closer to:

Code:
flee(['Fire', 'Iron'], 'rivers'=True, 'boost'=True);

Also, flee should probably a monad rather than a function, but that's more debatable.
Everyone's a critic :p

He placed four dozen tags on the wall they intended to destroy, activated them on a five-minute countdown
She armed it on a one minute timer,
@eaglejarl @Velorien found some stuff indicating explosives can be armed for longer periods of time than 5 seconds - was this an oversight/has it been overruled?
 
@eaglejarl, you were supposed to also change the password on the pangolin special elements doc!

I did! These tricksy players must have broken the encryption! Next time I'll rot13-encode it twice for extra safety.

@eaglejarl @Velorien found some stuff indicating explosives can be armed for longer periods of time than 5 seconds - was this an oversight/has it been overruled?

Yeah, that was before we'd nailed down the limits on timers.
 
By the way @Kiba I appreciate your efforts to get people to update the wiki -- it's been quite helpful to us as a centralized place to put information.

e: It's kind of too bad SV doesn't support thread headers/footers on every page. It'd be neat to have Wiki/chat/etc. there.
 
Last edited:
Voting is open for the next 1 day, 18 hours
Back
Top