Should I split my WPF?

[Kirbies]

So im thinking about getting 9 WM eventually on my main, and I was thinking about splitting the proficiency 145 - 145 2h/polearm so I dont get bored.
But how much of a difference does it make between 145 wpf split and 198 wpf if I go pure?

[Switchtense]

If you plan to play both 2h and polearm then splitting is the better option.

If you do not plan on playing either 2h or polearm often then I guess it is better not to split.

The difference is not that huge, at least for polearms. I could not feel a great difference between 170 and 100 so I guess 190 -> 145 won't be that big either.

No idea about 2h though, since I never played it for a long time.

[_Tak_]

Ill suggest not to split,with 100 WPF you won't be able to spam. with 198 you can people people to death if you know how to spam.

[Killer]

On my polearm/2h build that will have 9 wm i am splitting it to 180 pole and 92 2h. So with the melee bonus i get 190 pole and 120 something in 2h but ill be using 2h as a sidearm

[Macropus]

If you split your weapon points between 2h and polearm evenly, then you get 167 in one and 168 in another.
To me it seems like a much better choice than having 198 wpf in single weapon class.

[Tojo]

Split it or do what Agweber says in the post below. You won't feel the difference unless you wear heavy armor. Also, to make your true wpf go higher you can wear light armor for the extra speed.                                           

[agweber]

Use a STF and play with the WPF at the WM level you're planning. I made a X/27 with 9 WM and came up with these

1/147/146, effective 44/168/167 (379 total, 335 2h/pole)
1/148/145, effective 44/169/167 (380 total, 336 2h/pole)
1/150/143, effective 44/171/165 (380 total, 336 2h/pole)
1/165/123, effective 43/181/148 (372 total, 329 2h/pole)
1/198/1,     effective 33/198/33   (264 total, 231 2h/pole)

You can maximize your total wpf by playing with it for some odd reason.

So if you go 198, you go 198, however, you can get 181 in 2h and 148 in pole if you attribute in the effective wpf stuff. (Which might I add sounds way better than 145/145 vs 190 comparison)

[Rico]

splitting the proficiency 145 - 145 2h/polearm so I dont get bored.

If you use mainly light armor, a wpf split is no problem at all. You will still have a lot of wpf even after the split if there is no or only a small armor penalty. If you like to play in plate, I would not recommend the split.

You can maximize your total wpf by playing with it for some odd reason.

Can you explain this?

[Umbra]

If you just want to have fun sure, split wpf. Might i suggest something a bit different than 2h/pole. I mean, both 2h and pole playstyles are pretty similar, try something unorthodox like xbow/2h or throwing/pole. Actually you could roleplay a "roman/greek" like char, with shield/spear/throwing lances. I was gonna do something like that myself but i decided to go for a throwing axes/shield/warhammer build, its pretty fun. If you are a min/maxing tryhard then its not a good idea to split wpf

[Nordwolf]

Just realised you can do this with 9 wm :O
(effective wpf)
One Handed:153
Two Handed:152
Polearm:152
Weapon Master:9

Hybrid is a thing with 9 wm 

[Rico]

Just realised you can do this with 9 wm :O
(effective wpf)
One Handed:153
Two Handed:152
Polearm:152
Weapon Master:9

Hybrid is a thing with 9 wm 

I got wpf in 4 categories, it is viable with the right build and if you know how to use it. As a rule of thumb, the more broad instead of focused your build is, the lighter armor you should wear.

[agweber]

Can you explain this?

I don't know the specifics of it.. I'll go look.

(click to show/hide)

Code: [Select]

function getEffectiveWpf(wpfStat)
{
switch (wpfStat.name)
{
case 'wpfOneHanded':
return Math.floor((Math.max(stats.wpfTwoHanded.current*0.7-30, 0) + Math.max(stats.wpfPolearm.current*0.7-30, 0)) * 0.3 + stats.wpfOneHanded.current);

case 'wpfTwoHanded':
return Math.floor((Math.max(stats.wpfOneHanded.current*0.7-30, 0) + Math.max(stats.wpfPolearm.current*0.7-30, 0)) * 0.3 + stats.wpfTwoHanded.current);

case 'wpfPolearm':
return Math.floor((Math.max(stats.wpfOneHanded.current*0.7-30, 0) + Math.max(stats.wpfTwoHanded.current*0.7-30, 0)) * 0.3 + stats.wpfPolearm.current);

default:
return -1;
}
}

So the effective wpf is calculated by

Code: [Select]

base+(X*0.7-30)+(Y*0.7-30)and it's then rounded down. The funkiness is due to the rounding math.