Deathlike, on 21 March 2017 - 07:56 AM, said:
You have to consider that you only deal with putting up that kind of tree with as many characters as you'd want to run (which isn't that many, unless you create 1 character per day or something). In MWO, you'd have to do this with as many mechs as you'd want to apply it to, so those with super-large pokemech collectors... this would be a chore. Then again, you won't expect Spider-5Vs getting a full tree (it would be a waste of time to even consider in the first place) because it wouldn't be worth it.
People really need to think this through before spouting out "it would've been fine"... because it wouldn't have been.
So yeah, it's going to take a little more effort to level up ONE 'mech now, because you're actually only having to it for the ONE 'mech. You'd no longer be required to level up what will probably end up being 'throw away' 'mechs just to get the full benefit.
PGI's new skill tree was NOTHING like PoE, that's the point I was trying to make. The new tree comparatively simple, shallow even, compared to PoE.
As much as we play the 'mechs we like I seriously don't see this being an issue. All the 'mechs I like playing have hundreds, millions, even tens of millions of unused exp just because I've played them so frequently.
And ultimately for the majority of us, I think it would cover all the 'mechs we've been regularly playing over the last few years.
Any "new" 'mechs post new skill tree implementation, it will require reasonable effort and expense to level up, BUT again, you're only having to do it for the ONE you really want to play anyway. To me it seems win/win...
The new cBill sink version is there for a reason, to help drive revenue. Continuous revenue ensures we have a game to play. I'm not totally against this. Some have suggested making the skills that would be equivalent to what we have in our current skill tree, and that are equivalent to modules "exp only", and that seems like a 'reasonable' compromise.
There'd still be plenty of nodes on the tree to sink cBills into, but it wouldn't be overly burdensome to those folks who didn't buy lots of modules.
As far as 'compensating for time'... Really? That's just silly...




























