PSA: I'm working through the plan and just got to the section on LBF. For two reasons, I'm going to leave it out of the update and assume that Hazō prioritized other things:
1) I don't understand what you're talking about with straight sticks and how this is supposed to work.

2) LBF is not a reusable seal. I can't tell but I think your experiment is predicated on that.
I wasn't really there for discussion but I think the plan was to have LBF in the rods, and have some opening to trigger the seals to activate. This would allow LBF to activate adjacent seals such that civilian merchants could use seals.
 
isn't it essentially a death sentence for civilians to travel on there own? If that's true wouldn't civilian usable storage scrolls be redundant since a ninja will always be around
 
So what kind of birthday party should we throw for Mari? What kind of theme should we try and make for her. We could have it retirement themed and give a joke gift first before the actual gift, such as a walker or dentures and the like. An over the hill party that we can teasingly throw before switching to the actual festivities.
 
We could also sell them explosive tags. Which would be a lot more effective at defense than the shit civilians use to fight.
It shouldn't actually be that difficult to make grenades for civilians.
Imagine something like a thin square box. In the interior there are a pair of tripwire seals and an explosion seal. The hole is sealed except for a small slot at one end where you poke something in to prime the explosive. (We should develop a modified version of the tripwire seal so that we can make a better version where you pull the pin out.)
Obviously we should test the trigger and safety thouroughly using other seals before we stick explosives in it. We should also be able to use the technique to create civilian usable versions of other seals such as the Air Dome.
 
Hey all, we're looking for definitive QM quotes on whether LBF tags *automatically* reset their tripwire, or if they need to do so manually, because we've found some conflicting and unclear quotes. Help a brother out?
 
Yes, the tripwires (LBFs) are persistent as long as the tags on either end remain intact. That means that if you connect them to an explosive or anything else destructive then the tripwire is destroyed too, but if you attach it to (e.g.) a storage seal then the tripwire sticks around.

To eliminate ambiguity, a tripwire is a physical object (a piece of wire), but an LBF (Lesser Barrier Formation, which I've been referring to as a 'tripwire seal') is an invisible sensor beam between two seals. Damaging or moving either seal will cause the sensor beam to fail.
 
Yes, the tripwires (LBFs) are persistent as long as the tags on either end remain intact. That means that if you connect them to an explosive or anything else destructive then the tripwire is destroyed too, but if you attach it to (e.g.) a storage seal then the tripwire sticks around.

To eliminate ambiguity, a tripwire is a physical object (a piece of wire), but an LBF (Lesser Barrier Formation, which I've been referring to as a 'tripwire seal') is an invisible sensor beam between two seals. Damaging or moving either seal will cause the sensor beam to fail.
Note that most seals are one use. Storage scrolls are persistent, Force Wall seals can't be shut down (they expire after a time) or restarted. "Is reusable" is a special property that needs to be set at creation time.
This implies creating a reusable tripwire seal is at least as easy as a single-use one. (Otherwise Kagome would use the easier less risky version for his traps). I'd like clarification on how hard making seals reusable is in general and whether this is a special case.

It may be that making a reusable seal is not really difficult compared to a single-use seal and the primary cost is that reusable seals are more inefficient and wear out faster. For tripwire seals this doesn't matter because they are so chakra efficient and you can always make the seals a little larger if you need to.
 
Hey all, we're looking for definitive QM quotes on whether LBF tags *automatically* reset their tripwire, or if they need to do so manually, because we've found some conflicting and unclear quotes. Help a brother out?
Here are some conflicting and clear quotes
Are Kagome's tripwires persistent as long as they don't get blown up or would they need to be refreshed by a ninja after each use?
Yes, the tripwires (LBFs) are persistent as long as the tags on either end remain intact. That means that if you connect them to an explosive or anything else destructive then the tripwire is destroyed too, but if you attach it to (e.g.) a storage seal then the tripwire sticks around.
To eliminate ambiguity, a tripwire is a physical object (a piece of wire), but an LBF (Lesser Barrier Formation, which I've been referring to as a 'tripwire seal') is an invisible sensor beam between two seals. Damaging or moving either seal will cause the sensor beam to fail.
2) LBF is not a reusable seal. I can't tell but I think your experiment is predicated on that.
 
Hm. Is there any system that would be easier than google docs for keeping track of rulings (which is what I believe the QMs have used in the past)? Preferably something tabulated and easy to browse/edit.
 
Hm. Is there any system that would be easier than google docs for keeping track of rulings (which is what I believe the QMs have used in the past)? Preferably something tabulated and easy to browse/edit.

There was a time I tried to get qm-rulings migrated to the wiki, but that would've taken way more effort than I was prepared to put in myself.

There's also the issue of coordination with QMs, because sometimes rulings conflict and they're already putting in lots and lots of time. I suspect that once the infrastructure is set up, it's effort-saving in the long-run because a single complex system is a lot simpler than the set of plausible complex systems, but it's one hell of an initial investment.

A possible first step in the right direction is a mechanics-focused QM. Sadly, the one player who was actively pursuing that position left after the QMs accurately simulated Frozen Skein and I'm certainly not volunteering since I'm not able to make that sort of time commitment.

I have another idea kicking around in the back of my head that addresses this and a few other concerns but it would be premature to say anything more right now.
 
There was a time I tried to get qm-rulings migrated to the wiki, but that would've taken way more effort than I was prepared to put in myself.

There's also the issue of coordination with QMs, because sometimes rulings conflict and they're already putting in lots and lots of time. I suspect that once the infrastructure is set up, it's effort-saving in the long-run because a single complex system is a lot simpler than the set of plausible complex systems, but it's one hell of an initial investment.

A possible first step in the right direction is a mechanics-focused QM. Sadly, the one player who was actively pursuing that position left after the QMs accurately simulated Frozen Skein and I'm certainly not volunteering since I'm not able to make that sort of time commitment.

I have another idea kicking around in the back of my head that addresses this and a few other concerns but it would be premature to say anything more right now.

I have the next 3 days free so was planning on updating the wiki as much as possible. Should be able to get a large portion of the non contradictory QM rulings migrated over there
 
All this LBF back and forth is making me feel conflicted about whether to bounce with anticipation or brace for the worst. I'm starting to sympathize somewhat with faflec here.

However, I don't like posts in a sleepy time without substantiative discussion, so how should we aim to use Ino like she is undoubtedly using us?

I think we should counter fish for information and her viewpoint, being as subtle or brazen as we feel is right for the situation, as she is undoubtedly doing to us.
 
I am really thinking that we should throw an Over the Hill themed party for Mari before going into the actual festivities. Everyone from the team should get her a second gift that fits the theme before they present their actual gift. It will be great and very funny to see it written.
 
All this LBF back and forth is making me feel conflicted about whether to bounce with anticipation or brace for the worst. I'm starting to sympathize somewhat with faflec here.

However, I don't like posts in a sleepy time without substantiative discussion, so how should we aim to use Ino like she is undoubtedly using us?

I think we should counter fish for information and her viewpoint, being as subtle or brazen as we feel is right for the situation, as she is undoubtedly doing to us.
I feel that our time might be best used for other things -- I don't think that Ino's plotting is as great of a concern to us as, say, other clan leaders'.

...That said, if we can force a gift of seals onto Ino to get rid of our debt to her, that would be ideal.

Also... @OliWhail @eaglejarl @Velorien What seals that Hazou knows has he infused enough times to be relatively secure in doing? For instance, can he infuse Air Domes himself without issue?

e: Oh, also, does researching related seals lower the TN to infuse as well as research?
 
Last edited:
I feel that our time might be best used for other things -- I don't think that Ino's plotting is as great of a concern to us as, say, other clan leaders'.

...That said, if we can force a gift of seals onto Ino to get rid of our debt to her, that would be ideal.
I consider Ino to be a high threat vector because she seems so harmless, but nevertheless I digress.

How do we plan on countering the political machinations of our clan head's opponents then?
 
I consider Ino to be a high threat vector because she seems so harmless, but nevertheless I digress.

How do we plan on countering the political machinations of our clan head's opponents then?
By staying out of the public spotlight and let Jiraiya and/or Mari-sensei deal with this.

Side note: Is Mari's last name Goketsu now? Because hAH.
 
Back
Top