I feel like this happens less than it appears to happen. That is, if someone presents an idea and someone spots an obvious problem with it and voices it, that doesn't have to be 'this is a bad idea and we shouldn't do it'. It can just as easily be them pointing out the first roadblock in accomplishing the idea, in an attempt to prompt discussion of how to work past the problems and actually accomplish it.
I've noticed, some situations more than others, that people often get defensive at posts like this, as if pointing out flaws in the as-stated implementation of the idea is a denouncement of the entire idea instead of a call for a more nuanced implementation.
While it is good practice to try and give ideas for solving a problem when you raise it, I don't think we should demand that of people as a prerequisite to contributing to a conversation. It's much better for both sides, I think, to assume if someone points out a problem with your plan that they're asking for you or someone else to suggest nuanced additions to the plan instead of attacking the very concept of the plan in the first place.
This would be kosher with me if people were able to differentiate "Spitballing on potential future plots." and "Things that need to be put into an action plan, like right now."
It's unreasonable to expect spitballing to be entirely error free.
Less of "The problem with this is X." and more of "I think this could maybe work, modulo X or Y being resolved in a way that doesn't cause problems."
I am not opposed to the idea of a heist itself.
Don't let me get in the way of you walking back your past statements, but I find this hard to reconcile with said past statements.
Your responses when you noticed this idea being bandied about were roughly along the lines of
"Why the fuck are we talking about this?"
"There's no analysis done on what we stand to gain, NO NO NO NO!"
"At this stage, it's an automatic veto."
"Yes, I shot the heist idea down."
"We have no reason to do a heist. Therefore, my vote will be no. I categorically refuse to do a heist until then. "
Furthermore, in this very response you state:
It's too specific of an idea at this stage, and ruining a merchant strikes me as immoral at first impression, and it's not the only way to ruin a merchant. Before we commit to a single plan for ruining a merchant, we should first ask ourselves whether that accomplish our goal and concerns of ethic/morality, benefit and cost analysis.
When/if a mission come up that really required a heist, only then I will support it.
We haven't even done the unsexy part, such as setting up merchant spy network, talking to people, etc.
The above checks off the following from my Bullshit Sensors(which is not to say that you were bullshitting me, of course):
- Claimed that idea was too specific simultaneously with using the specific example as representative of the overall idea class.
- Moralizing
- Vaguely stated criteria for approval.
- Implication that this needs to be gatekeeped behind scenario specific details (merchant spy network, talking to people, etc.)
You could instead have just said "I don't want to do this." or "Maybe later but I don't really see the value now." or "I don't see why this is helpful, can someone enlighten me?" or a number of things and stopped posting further objections. Instead, it seems like you feel the need to actively shout this down for some reason, and the only objective that that accomplished was to raise the noise quotient.
Someone responded to you with a very thoughtful post more or less outlining that its highly possible that , whatever your goals may be, this could in some way be implemented in such a way as to help them, and pointed out that it is rarely the case that there is
no reason to do something. Your
immediate response was to double down on your position that "There is no reason to do Thing." and ignore anything they actually said.
As a general rule of thumb(for me personally) this sort of behavior does not convince me that I should grant heavy weight to your opinions on the matter in question. Similarly, it doesn't really make me want to spend that much effort discussing this point with you, since you don't appear to be very open to changing your mind on things you already have an opinion on and I have finite time to spend.
So, let's think constructively on how we might achieve some of these ambitious goals. I'll take the merchant spy network. Questions I can think of, that we're going to need to answer in order to make this work:
- Recruitment and vetting. How do we find the right people and how do we ensure they can be trusted (and how much)?
- Incentives. What reason do they have to work for us? Are we paying in ryo? Favors and contacts? Ideological satisfaction?
- Levels of involvement and trust. Are we looking for full-time dedicated agents? Or just normal merchants willing to keep an ear out and sell information? Something in between?
- Structure and infosec practices. Solo operatives or cells? Do we want regional coordinators? How do we make them not single points of failure?
- How big of a central organization in Leaf are we envisioning? Do we plan for Hazou do just run it on his own like Jiraiya did? If not, who is going to do it and how do we convince them to do so?
- How do we build out? We currently have nothing, what are the steps to get from this state to the organization we're envisioning?
Anyone want to do something similar for scrolls? We have some leads there, so a good question to answer would be, say, how to find Grandmaster F and what to offer them for their scroll.
See, this is productive discussion and a great way to address potential issues!
I will vote for your plan(s) for a voting cycle of your choosing in return for being an exemplar of
jolly cooperation!