Nex nerfing poll -proper

[Mirio]

Leave the Nex as it is.
Nexuiz is a simple. old school FPS with heavy weapons and intensive gameplay. The Nex is one of the basics of this. Hitscan, deadly brutal, and needs "some" skill to use it (not more then the mortar, RL, or omg the gaygun crylink)... Kinda reminds me.. oh wait, what do I hear... RAILGUN FROM QUAKE SERIES?!

Come on, this thread makes me sick!

I didn't want to offend you anyway with this frag alpha.

[Alien]

New poll what?

For rocket launcher. This is for nex only.

[ai]

Rocket Launcher doesn't need a poll. It's perfect the way it is, exactly as Nex is perfect the way it is. People should stop changing stuff that doesn't need changing. The weapon balance is the one thing that's been the great about Nexuiz ever since 1.5!
Seriously, stop this nonsense!

[Alien]

Rocket Launcher doesn't need a poll.

Argue about this with kojak and tzork. I don't have an opinion about rl.

[mungtor]

I registered just to post in this thread and ask another question. I've been playing Nexuiz for about a year and maintaining a server on a private LAN for a few friends.

While I'm not going to say the Nex _must_ be a certain way, how hard would it be to incorporate a change where the damage and refire in zoom mode is different than non-zoom? Some variables like g_balance_nex_zoom_damage and g_balance_nex_zoom_refire would go a long way to giving people the flexibility to find a good balance.

Since the problem with the Nex, as I see it, is that it's underpowered for a sniper weapon (which is is since it's the only weapon with a zoom mode on secondary) and overpowered for just running around with. That's why there are so many balance questions/problems with it and very few with other weapons it seems.

[GreEn`mArine]

The problem now is that zooming is done entirely on the clientside. Some players have already been doing it this way by having their own scripts that set their FOV (field of view, the "fov" variable in the console) to a low value.

Such variables like g_balance_nex_zoom_damage are serverside variables and indicate, or well, assume, that the server does have entirely control over this.

Of course the clientside-code has some threshold of a FOV value where it thinks that the player is in zooming state atm - and it could send this information to the server. But this is unreliable imo and the info that a player did the shot while zooming might not reach the server. This makes the concept void that a server is always right about the decision how much damage to deal.

[mungtor]

The problem now is that zooming is done entirely on the clientside. Some players have already been doing it this way by having their own scripts that set their FOV (field of view, the "fov" variable in the console) to a low value.

Ahhh... I didn't know that would work that way. I guess it makes sense because the engine scales the FOV over the entire screen.

Such variables like g_balance_nex_zoom_damage are serverside variables and indicate, or well, assume, that the server does have entirely control over this.

Of course the clientside-code has some threshold of a FOV value where it thinks that the player is in zooming state atm - and it could send this information to the server. But this is unreliable imo and the info that a player did the shot while zooming might not reach the server. This makes the concept void that a server is always right about the decision how much damage to deal.

Actually, it seems more likely that people would want to report to the server that they were zoomed when they weren't, leading back to the original problem of too much damage when not zoomed. If that's the way it's handled, it's just broken and probably needs to be redesigned as two separate weapons. I wonder how Valve did it for the Half-Life crossbow, since that's pretty much the behavior that would be appropriate.

[esteel]

Such a think would require code changes.. also pressing mouse2 the nex zoom and mouse4 (the all guns zoom) is not difference. There just was no idea for a nex secondary fire mode