Wintersdark, on 11 May 2015 - 06:07 PM, said:
1) TT battlevalue's would be worthless here, not even good as a starting point, because really mech geometry is probably one of the most prominent factors in mech power.. Particular when coupled with the correct hardpoints. Thus, you'd need to design a totally new BV system, and adapt it every time game mechanics changed. Not impossible, but a tremendous amount of Dev time to create, balance and maintain. BV is much easier in a largely static dice based game.
2) how do you determine what BV is allowed per team? What about pugs, pugs of teams, 12 mans... Vs combinations of the same? Do you give each player a BV limit? You could use an arbitrary value, and then with a fixed 4 mechs as that seems a UI requirement..
But ultimately, that's all pretty much functionally identical to tonnage, particularly given how poorly balanced the BV ratings will be (and thus how open to exploitation).
BV sounds awesome, and is great for TT. In theory - with free devtime to develops and maintain - it could be here too. But the reality is that its not worth the cost andrisk that it wouldn't be balanced and thus be tremendously exploitable.
People lobbying for BattleValue would probably do themselves a great service if they stopped calling it BattleValue. What they are really after is assigning a scalar number to a Mech and its pilot. It would have no relation whatsoever to the TT BattleValue formula. Of course there is much hand-waving about how that scalar would actually be calculated. But that's just details.
You said a BattleValue (for lack of a better term) system wouldn't be any better than tonnage, but I'm not sure that's entirely correct. If the really good Mechs had a much bigger number than the crappy Mechs, we could make sure that 4 of whatever the best Mech is doesn't fit within the maximum threshold.
I'm not really campaigning for a BattleValue system, but I'd prefer if you'd focus exclusively on pointing out that the actual scalar number would be incredibly difficult to calculate and that's why we can't have it, rather than saying it wouldn't be any better than a tonnage system because tonnage accounts even less for the very things you mentioned like geometry and hardpoint locations.
Edit:
And I do realize you did mostly focus on the complexity, but it's like guilt by association. Because you also said it would be no better than tonnage, your other valid arguments are likely to get dismissed.
Edited by Domenoth, 11 May 2015 - 06:54 PM.


























