I don't think it's threadjacking - the topic is NTBB2.0 and we're talking about things that it is meant to address. Now, that said, there's never going to be a compromise on the concept of anecdote as data... at least as far as I'm concerned. There's a reason that no serious discipline in the entire world favours anecdote over data. It also doesn't matter how trivial the application is.. from games to sports to medicine.. there's NO REASON not to do things the smart, right way.Hitonagashi wrote:Regardless, we are thread-jacking again. I would like to hammer out our differences, because you are clearly intelligent (and most of the time, correct), but this thread is not the time or place for it. I'm also pretty sure that even offering to discuss will be met out of hand with a scornful insult, probably comparing talking to me to negotiating with a terrorist, but hey, I offered.
I'm flattered you think my postings take a long time to craft. They don't - I'm just verbose, eloquent, handsome, and charming.Hitonagashi wrote:I (and I imagine Garion) don't spend hours carefully crafting the ideal retort/response.
Maybe yes, maybe no. Long term outcomes are based on skill access. Looking into the utility of skills in each of the skill categories and trying to balance the categories to have some semblance of equal utility... would help a ton. The same is true of giving different skills different values in terms of TV.Hitonagashi wrote:If you are only looking at short term, cool! You could be right about CRP+ being a long term boost which negates the short term nerf. The games I mostly care about are high (1600+) TV, so the team charts look different at that size. I'd like to see NTBB attempt to narrow the tiers at all ranges, rather than just short term, but that's a much harder proposition.
The fact that will make everyone cringe is that bash teams don't win very much compared to agility teams which means that balancing the games around TV levels and win% would involve boosting bash or nerfing agility. Certainly in Box type environments people would scream about that being the opposite of what is needed... which suggests that trying to balance things to work in all environments would require some form of robustness balance as well... so that bash teams win more, but agility teams get wrecked less.