cRPG: status and plans

[Zlisch_The_Butcher]

Like RON Paul RULES! accidentally the whole sheet?

Agreed.

[Jarlek]

Why would we stop working on the mod but keep posting on the boards?
That said, there will be big changes somewhere in August (unless something goes very wrong).

Yay!

If you need testers, you know where to find me!

[Butan]

Why would we stop working on the mod but keep posting on the boards?
That said, there will be big changes somewhere in August (unless something goes very wrong).

One post can change everything; yours did

[Adam_Bomb]

Therefore, we'll change the system to something that rewards personal skill and risk more. It will be, among other factors, proximity based, as we had in the early versions of cRPG. It will definately not be purely kill based, we don't want to reward fraghunters over teamplayers. It will also not reward proximity leechers. You can expect this change soon.

Sorry if this has been addressed, didnt have the time to read 17 pages.. So does "proximity based" mean that someone who makes the majority of their kills from long range (arby user) will be screwed when it comes to XP gain?

[Dooz]

Big changes in August scares me. Change is scary. Or dolla dolla bills ya'll for me.

[Micah]

... we'll hold them back for the sequel ...

+

... there will be big changes somewhere in August ...

=

(click to show/hide)

visitors can't see pics , please register or login

[Turkhammer]

Therefore, we'll change the system to something that rewards personal skill and risk more. It will be, among other factors, proximity based, as we had in the early versions of cRPG. It will definately not be purely kill based, we don't want to reward fraghunters over teamplayers. It will also not reward proximity leechers. You can expect this change soon.

All great points chadz but hopefully you will reward players providing "assists" or giving damage to the other team.  As a hopilite I distract, weaken and sometimes kill opponents while giving a chance for my heavier hitting team mates to finish them off.  Also support players give good service for unhorsing cavalry.  If xp is to be based on performance, these types of actions should be accounted for also.

[Oberyn]

Killing horses should definitely give some type of reward. Perhaps only if they are killed when someone is riding them, I can imagine the frenzy to kill a riderless horse otherwise.

[Shub]

I would be happy to see System msges ,reports of dmg dealth , headshots and crit -just like  it was done in singleplayer . I miss that a lot.
Its like mini achivment -to see u  have dealt 9999 dmg to some thing . \o/

[Zlisch_The_Butcher]

Killing horses should definitely give some type of reward. Perhaps only if they are killed when someone is riding them, I can imagine the frenzy to kill a riderless horse otherwise.

People who aim for your horse and not you are dickless cowards and deserve no reward, people who kill random running horses (fuck I've even been TK'd by a guy who tried to kill the fucking horse I was mounting several times) deserve to have a multi taken away from them.

[Jarlek]

People who aim for your horse and not you are dickless cowards and deserve no reward, people who kill random running horses (fuck I've even been TK'd by a guy who tried to kill the fucking horse I was mounting several times) deserve to have a multi taken away from them.

[Murmillus_Prime]

At fifteen, I had the will to  learn ; at thirty, I could stand ; at forty, I had no  doubts ; at fifty, I understood the heavenly Bidding ;  at sixty, my ears were opened ; at seventy, I could  do as my heart lusted without trespassing from the  square.!

[BD_Baby_Wolf]

I don't think this is good idea. You should put a cap on wpf, somewhere around 160 imho but you should also further decrease effects armor weight has on wpf. Making builds with 200 or more wpf in single proficiency possible isn't the best way to balance things.

This is coming from someone who currently has 176 wpf in 2H and has more than 170 wpf for almost a year. Buff hybrids instead, allow people with 8 WM to have 150 wpf in 3 different weapon proficiencies (with higher WM allow them to reach cap in 3 or more categories).

Basically what I'm suggesting is to buff those with high WM skill the most, and to scale wpp gain for lower WM levels like this:

7 WM - 3 x 130 wpp, 2 x 150 wpp
6 WM - 3 x 100 wpp, 2 x 140 wpp
5 WM - 3 x 75 wpp, 2 x 120 wpp, 1 x 160 wpp
4 WM - 3 x 50 wpp, 2 x 100 wpp, 1 x 140 wpp
3 WM - 2 x 75 wpp, 1 x 120 wpp
2 WM - 1 x 100 wpp
1 WM - 1 x 75 wpp
0 WM - 0 wpp

Bring back variety into combat, don't support extreme builds. Don't nerf moderate to semi-extreme str builds, totally nerf extreme str builds (those with 3 agi and no wm), buff high agi builds so they are more versatile in combat but don't give them more damage.

+1 here.

[Visconti]

I don't think this is good idea. You should put a cap on wpf, somewhere around 160 imho but you should also further decrease effects armor weight has on wpf. Making builds with 200 or more wpf in single proficiency possible isn't the best way to balance things.

This is coming from someone who currently has 176 wpf in 2H and has more than 170 wpf for almost a year. Buff hybrids instead, allow people with 8 WM to have 150 wpf in 3 different weapon proficiencies (with higher WM allow them to reach cap in 3 or more categories).

Basically what I'm suggesting is to buff those with high WM skill the most, and to scale wpp gain for lower WM levels like this:

7 WM - 3 x 130 wpp, 2 x 150 wpp
6 WM - 3 x 100 wpp, 2 x 140 wpp
5 WM - 3 x 75 wpp, 2 x 120 wpp, 1 x 160 wpp
4 WM - 3 x 50 wpp, 2 x 100 wpp, 1 x 140 wpp
3 WM - 2 x 75 wpp, 1 x 120 wpp
2 WM - 1 x 100 wpp
1 WM - 1 x 75 wpp
0 WM - 0 wpp

Bring back variety into combat, don't support extreme builds. Don't nerf moderate to semi-extreme str builds, totally nerf extreme str builds (those with 3 agi and no wm), buff high agi builds so they are more versatile in combat but don't give them more damage.

Best idea in thread, +1

[Elindor]

I agree, I hope that more than speeding up those with high WPF, that this new curve actually SLOWS DOWN those who invest little to nothing in WPF (and WM to that matter).