Ive of the firm belief if more than 50% of the population is using a type of skill, weapon, special, spell, consumable, etc.... It needs looked in to for balance.
There is about a 75% chance that the "object" being used is way more powerful than the other choices, hence balance needs to be restored.
Archery, why dont people use an Elven Composite bow? Terrible specials and damage/speed. Why do people use "insert stronger bow type name here" ?? Because it is faster/stronger and has better specials.
Do we nerf the strong bows or buff the weak ones?
This works for every skill/class/weapon...
Everything won't be balanced. I understand that, but we can make a better effort.
Now, when it comes to something EVERYONE IS USING it is too strong. (Alchemy for instance)
Actually, EP + Alchemy bonus isnt calculated right, but no one wants to believe it, when the tests clearly show more than a 30% increase when stacked with 50% EP.
So everyone gets used to using the over powered nature of it, and dont want to ADAPT or have it changed. Hence, the problems we are running in to where more people cry about it and it doesnt get changed. And we wonder why our templates have no diversity.
If I'm using alchemy/EP for 80% (actually more but we will pretend the formula isn't screwed up) extra damage on Novas, you have to use alchemy/EP for 80% extra heals on your heal pot.
Notice how this is a never ending cycle?
Change is a good thing, and I get very annoyed at testing things, showing proper data, putting down a collective thought process (In proper -EASY ON THE EYES TO READ- English), to be ignored by answers like...
Omg its been like that for years.
Its not strong. Stfu newb.
Adapt and get it yourself.
Not my fault your suit sucks.
Only 1 option is useful.
It takes 100 skill points to be worth while.
Seriously? Those are the arguments that are keeping this skill (And EP in general) untouched and unnerfed?
Now, take out the word alchemy, and insert archery, and you have almost identical arguments.
Did I prove my point yet? Just saying.
@Bleak