Server changes Options

[MonkeyFiend]

The patch is (hopefully) due out today.

1. I've added the procon updates to support the new patch, including the plugin that will automatically kill players who enter defined uncap zones. These uncap zones are essentially defined as circles on that player map, Players entering these zones will be warned then killed, essentially automatically enforcing our no-baserape rules

The zones can also be set to kill off snipers who perpetually camp in their own uncap

2. Additionally have added a stats plugin

Running the commands

"@bfbcs" - Gives a summary of the speaking player
"@bfbcs [playername]" - Gives a summary of another player
"@bfbcs [playername] [stat]" - Information about a weapon/vehicle/etc for a given player
"@bfbcs [player1] [vs] [player2]" - Compares player1 to player2.
"@bfbcs [player1] [vs] [player2] [stat]" - Compares player1 to player2 on a stat.

3. Will begin tracking stats e.g. kills, weapons usage specifically on the servers. This is due to populate the same database as the current events and bans list (am expecting this to be quite a hefty database and is still very much work in progress for getting usable info out)

4. The servers now automatically remove any player with the name Wonka or 187ci


Please don't edit the map uncap zones unless you know what you're doing e.g. accidentally adding an 'uncap' into the middle of the map would kill any enemy players entering it

Also some of these changes are partially working at the moment, will become fully functional once the patch is relased to the servers.

[Magik6]

Awesome, good work monkey. When comparing player etc with the command including [vs] do we enter it with brackets or without?

[MonkeyFiend]

Awesome, good work monkey. When comparing player etc with the command including [vs] do we enter it with brackets or without?

Pull general overview of yourself:

@bfbcs

>bfbcs.com (MonkeyFiend) > MonkeyFiend: 1021958 score, 260.50 elo, 15169 kills, 12670 deaths, 1.51 kdr,
>bfbcs.com (MonkeyFiend) > 4.00:16:12 days

Pull a stat (weapon, vehicle, pins etc etc) on yourself or another player
@bfbcs personname gol sniper

>bfbcs.com (personname) > GOL Sniper Magnum: 634 kills, 241 headshots, 4119 shots, 1522 hits, 37.0%
>bfbcs.com (personname) > accuracy, 10:44:38 hours

@bfbcs 1349 abram
>bfbcs.com (-1349-) > M1A2 Abrams: 82 kills, 1 roadkills, 19.96 km's, 01:41:23 hours

Compare one player to another on a stat
@bfbcs phogue vs 1349 gol sniper
>bfbcs.com (*Phogue vs -1349-) > GOL Sniper Magnum: +404 kills, +107 headshots, -249 shots, +209
>bfbcs.com (*Phogue vs -1349-) > hits, +7.8% accuracy, +07:59:15 hours

(not shown here but you can compare general results as well) i.e:
@bfbcs monkeyfiend vs magik6

@bfbcs cabletwitch gustav
should be used a lot to name and shame players

weapon names are the ones as defined on bfbcs. There's no autcomplete, so in the case of @bfbcs monkey vs magik it won't ask if I mean monkeyfiend, magik5 or magik6

NOTE: THE COMMAND IS @ TO SEND THE MESSAGE TO THE SERVER AND PRIVATELY BACK TO YOU. =SM= MEMBERS CAN ALSO USE ! INSTEAD OF @ TO YELL THE MESSAGE TO THE SERVER. PLEASE DON'T MAKE A HABIT OF THIS!!!

[K.]

ok so for example, we can change the uncap zones to also include the "high rock, next to the water fall on presa CQ" i doubt this area is meant to be accessable as you have to seriously go OOB to get to it?

and anyone trying to gain that spot would be autokilled after a period of time?

er how long is that period 1 , 2 , 5 mins?

is the period reset by merely leaving it and returning?

will the server recognise that someone is repeatedly going back to a "shifty" area? and deal with without warning?

[MonkeyFiend]

can probably tinker with various settings once the patch is relased and we can ,uck around with it thoroughily.

we can set:

instant kills or instant kick for entering an area or being outside an area and shooting someone whose in that area (in the latter case we can define how far outside the uncap area too if need be)

The area is defined mathmatically by a circle (size, coordinates), it should be possible to include multiple circles e.g. a big circle for the main uncap area and bolt on chains of smaller circles to catch up any bits not covered in the main circle - will have to test processing limitations on number of these

The uncap areas are defined by team e.g. a US uncap circle, will kill any Russian players entering it. We can set out of bounds areas (where people can sneak into, but they're not supposed to be, such as behind the waterfall on presa) by overlaying two identical sized uncap zone circles on top of each other - any players entering would be killed/kicked.

At the moment the logic is fairly black/white - someone enters a defined enemy uncap will be killed or kicked. To implement warnings prior to action we'll have to track players on the server and initialise a tally e.g. 2 warnings then kick. It's not in place at the moment, but is certainly an option for future development*

At the moment it'll be set up to kill anyone who enters an uncap area - like the uncap areas in rush. They can do this repeatdly but there's nothing to gain from it. Likewise someone going to an out of bounds area like the waterfull will be killed - so I'm not too concerned about them repeatedly trying it

As for snipey campers, it's currently based on the uncap zones, if a sniper stays within that defined friendly uncap zone for 5 minutes they will be kicked. (can change the amount of time). Currnetly the zones for this are the same as the general uncap zones, can maybe look into creating a different zones system for sniper camping (but again, future development work)


thx

Monkey

* get more complex if you add aging of infractions e.g. getting rid of infractions older than say 20 minutes or between rounds and also tracking players as they join/leave the server etc.,

p.s. at the moment the camping thing only accounts for solid amounts of time in an area e.g. a player could camp 4 minutes, run out the area and go straight back and camp some more.

Can probably balance this by writing culmulative time in uncap area minus time outside of area (so someone who camps, leaves/returns then camps some more will receive a punishment under culmulative time, e.g. with a 5 minute limit, someone who camps for 3 minutes in an uncap, goes elsewhere for 2 minutes will essentially have 1 minute of culmulative time, allowing them to return to camping for a further 4 minutes before being kicked.

Can adjust the ratio of this e.g. culmulative uncap time not directly proporsional to out of uncap time e.g. camping 3 minutes in an uncap takes 6 minutes out of uncap to clear culmulative effects.

The latter is probably the fairest way, but will require some ballbreaking coding to do.