FreeGameDev

(originally from the bug tracker but was removed, since this is a feature request)

This would allow server admins to enforce certain variables on clients to make games more fair.

Some ideas about this variable:

/fairgame 0
- no variables enforced

/fairgame 1
- sets texreduce to 2 maximum (values above 2 are reduced to 2)
- caps fullbright model value to 50 (the default one)
- don't allow "showboundingbox"
- don't allow disabling "waterenvmap" (makes players easier to see underwater, as the water doesn't reflect at all)
- basic zoom script prevention (prevent changing fov while playing, fov changes only applied once you die)
- don't allow showing player names on radar (some var does that)
- force enabling gun model (and don't allow changing other gunmodel-related variables such as transparency, etc)
- force colors to the default ones (don't allow overtone/undertone changes)
- don't allow changing "blobmargin" (changes blob shadows size, makes players easier to see, especially through walls)
- players that are using modified maps are automatically put in spectator and cannot unspectate

/fairgame 2
- same as 1, additional stuff:
- enforce first person
- enforce fov to default fov
- enforce default crosshair
- enforce default HUD display (don't allow showing impulse in percentages, background of health/weapon icons must be kept, etc...)

It seems to be like 'Tournament' mode or smth.
Remember that RE is more FFA game, not real tournament

These variables are mostly aimed at "beginner" servers (so that more advanced players can't exploit some variables to have advantage over beginners) and competitive/clan war servers.

In QL i can change all that i want . And if a person played in game with his settings, and someone enable him unfamiliar Settings, how he must play with this? lol . in all games i use fov 120 and you want say that i must play with fov 100 for example ? Also if player don't have a good pc (i have but i usually play on intel video card because i have a high temperature with invidia) and must use texreduce 10 ?

I think the better way would be here, to expose the "important" variables in a more comfortable way to new players. For example, fullbrightmodels could be accessable via the graphic options menu; or at least have them better documented, maybe collected in a "important vars for new players" section.

riidom {l Wrote}:I think the better way would be here, to expose the "important" variables in a more comfortable way to new players. For example, fullbrightmodels could be accessable via the graphic options menu; or at least have them better documented, maybe collected in a "important vars for new players" section.

I agree
I think is better way that adding all to menus . In profile for example . For ex. here can be a weapons cfg's (croshair) , fullbright option ect .