As I said I would, I did some work on
the wiki.
Cool, thank you.
Also, small questions: can we rename Kekkai Genkai to Bloodlines, and refer to Hidden Villages by their common names, like Mist and Leaf?
It would certainly make my life easier. I can never remember the Japanese for any of them besides Konoha.
No they...ohhh, that was metaphor. nm
I think we're ignoring the elephant in the room here, so let me spit it out:
We're between two flames here because even though I would were much like plans like this we're getting punished for them because of wordcount limits.
If we don't elaborate so much there could be dozens of small mistakes that we ignore and set aside, making them as 'this should be common sense'. But if it is just implied that Hazou should do something, but not explicitly stated, QMs can mess with Hazou however they want, which they sometimes do. Yes, often it is our plan that specificly firces Hazou act stupid, but that not always the case.
Result: we get punished by being very explicit (less XP) and we get punished by being ambiguous (IC stupidity that we didn't expected)
I understand that its easier for QMs to work with short plans, but we're really stuck here. And, guys, please, don't take it personally. You're great People that pooled together a fantastic story and I really appreciate the amount of time you've put in it.
However, the thing everyone are saying right now is 'Hazou should start acting smarter by default' in dozen different flavours.
What hivemind is missing here, from my perspective, is that we need to establish an agreement with QMs on what they should treat as default reactiin from Hazou. Until it is aquired, all IC we're proposing is going to work one-two chapters and then get erasied again.
Whether the reactions would be developed or receive as a reward for doing something perfectly, trained or aquired for doing things properly for set amount of in-game time is not as important as receiving recognition that we can change Hazou's default reactions and, probably, some sort of manual on how to do this. Because I haven't found any unambiguous way of achieving this in mechanics. Othervise things'll just continue to go downhill...
Ah, look, this is an even-numbered month, time for the QMs to be accused of being unfair and acting in bad faith. </humor>
But then, he spills beans about Akane's EM when SHOULD HAVE LEARNED BETTER. Its the things that would be reasonable for him to remember, but every time we don't specify them explicitly, Hazou just f*cks up.
My recollection is that during voting it was acknowledged that the plan involved compromising one of her techniques and it was decided that that was acceptable given the circumstances.
So, is there a way in mechanics to justify learning things so that they would stick. Is there a skill 'mind your damn OPSEC'
Unfortunately, no. The mechanics are descriptive, not normative.
It is reasonable for him to remember such things, especially when he already was hit hard by doing other way around.
Once something gets promoted to your attention there's a tendency to notice things that are related to it. If you read an interesting book about high-frequency trading then you'll suddenly start noticing things in the news related to HFT, or to ancillary things that were mentioned in the book. I'm sure there's a technical term for this, but I don't know what it is. It isn't confirmation bias -- I'm talking about what you notice, not about how you interpret it. It isn't cherry-picking, because this isn't a question of deliberately choosing examples that reinforce your position. It's not apophenia because there
are actual connections. Anyone know? Eh, I'll just call it zubble until I know what the right word is.
The problem with zubble is that it's easier to notice things that are exceptions instead of defaults -- it's the curse of the sysadmin and the sewage technician: no one thinks about you until something goes wrong.
@TarzanNn, you're angry because Hazō has OPSEC failures, but you aren't considering them in balance with his OPSEC successes because the latter don't get promoted to your attention.
Three quick examples, the first ones that came to mind:
- Chapter 186: Hazō needs to tell N&K about Jiraiya's directions re: Team Bloodrage. He takes them to an isolated rooftop.
- Chapter 214: Hana, his mother and the person who Hazō loves and misses the most out of everyone in the world, whom he has been desperate to reconnect with for two years, shows up on his doorstep. He has a long conversation with her, telling her all about his travels...while keeping OPSEC in the forefront of his mind and not leaking anything at all.
- Chapter 218: Hazō needs to tell Noburi and Keiko about Mari-sensei selecting them for the swamp mission. He does not do it in the middle of the street, or even in the well-warded Gōketsu residence. He takes them outside the city and puts domes over them.
Again, these were just the first three examples that popped to mind; I could easily find more if I actually looked. In none of these cases did the plan say anything about OPSEC; Hazō's success was completely down to the QMs recognizing that he's improving and implementing his behavior in that light.
As to us "messing with Hazō however we want"...that's not a thing we do. In point of fact, there have been times when we went out of our way to fix something or smooth something over -- a recent example was
Chapter 232, where the plan specified that the kids should go out gambling together, without taking into account that it had been specifically called out how terrified Keiko was of crowds and how she was unwilling even to walk down the street; she either went across the roofs or she sent the boys to buy stuff for her. I knew that the players had been wanting for quite a while to see some gambling, so I went out of my way to fix the plan. That is not the act of someone who operates in bad faith.
So, yes. I understand that it's frustrating to watch Hazō stumble sometimes. Keep in mind that he's 14, and a child soldier who spent almost two years with a social circle of 3, then 4, then 5 people. If he's not the smoothest operator on the planet...give him time. He is improving.
Okay, that ended up longer than intended, but hopefully it will allay your concerns.
I really appreciate all the work you do, so I'm Sorry if that post came out as rude.