ProconRulz V44j1 - weapon limits and other event-triggered admin actions

[ImportBot]

Originally Posted by Bl1ndy*:

 

That's the complete rule!

Code:

On Kill;Weapon M26Mass;PlayerCount 2;yell <Message>;Kick
On Kill;Weapon M26Mass;PlayerCount 1;Say <Message>;Kill
On Kill;Weapon M26Mass;PlayerCount 0;Say <Message>;Kill

Shamrock, but what does it make when i delete PlayerCount 0 ...

The player is killed and then the server thinks it was a suicide :/

It's not possible, current version reads killed by admin as a suicide. Maybe bambam can add a On Adminkill next release cause R21 now shows KILLED BY ADMIN but i don't know if the procon event changed to killed by admin aswell.

[ImportBot]

Originally Posted by ty_ger07*:

 

Thanks Shamrock

 

# SNIPER RULZ

Kit Recon 1;PlayerSay >>%p%

# TEAMKILL RULZ

On TeamKill;Weapon DEFIB;Say >>%p%

On Teamkill;Count 3;Say >>%p%

On Teamkill;Damage SniperRifle;Say >>%p%

On Teamkill;Say >>%p%

 

I need only 1 rule: "1 sniper for Team", if 2 snipers the player is killed.

is it allright_?

Are these rules for BF3, or BC2?

 

In BF3, Kit Recon doesn't mean anything since BF3 game server doesn't tell PRoCon which kits player spawn with. So, won't work for BF3 even if you add On Spawn as a trigger. All you can do is enforce a punishment after the player kills with a sniper rifle.

[ImportBot]

Originally Posted by ty_ger07*:

 

ok i have this defib rule which works great

On Kill;weapon defib; Yell 5 %p% Just Fried %v% with the %w%

but when i include this rule

On Kill;Damage Melee;yell 5 %p% just took %v%'s TAGS!

 

both messages come up

As bambam just said, DAMAGE Melee is for kills from knife, melee, repair tool, or defib. WEAPON Melee is what you should use if you want Melee in your rule to only mean grabbing dog tags.

 

Please look at the plugin's damage and weapon keys and you will see what I mean.

[ImportBot]

Originally Posted by bambam*:

 

I have got a lil prob :x

 

On a friends server there are two rules

Code:

On Kill;Weapon <Weapon>;PlayerCount 0;Say <Message>;Kill
On Suicide;Say <Message>

But when he is killed for using then the Suicide message appears

 

Is there any chance to avoid this ?

Eh? That would mean BF3 has changed the rcon protocol in some recent release and it's more likely your friend has cocked up something else on the server, but this should still be checked (hey, everything is possible).

 

Point 1: "PlayerCount 0" is EXACTLY equivalent to not having that condition at all (read the documentation description of the PlayerCount condition). The rule is triggered, and then the condition checks "has this rule been triggered more than zero times" well of course it has...

 

Point 2: this analysis depends on a new "feature" of a BF3 server that an admin 'kill' of a player will trigger the "On Suicide" condition of ProconRulz -hey it's possible but that never used to happen and I'd have to provide an updated plugin to fix that.

 

I'm not at home to test this -- can you add log actions to the rulz as below and paste here a few lines from the chat log that shows the On Kill.. On Suicide sequence?

 

On Kill;Weapon ;Log %p% killed %v% with %w% and will be slayed;Say ;Kill

On Suicide;Log %p% suicided with %w%;Say

[ImportBot]

Originally Posted by bambam*:

 

Hi guys,

 

Firstly bambam, thanks for the great plugin.

 

My first question is the following: is it possible to successfully change the name of the server with a rule? The idea is to append " - Admins Online" when an admin joins, and change it back when the admin leaves. I've tried:

 

The exec commands work through the console - however when ProconRulz executes it, it splits the string into seperate parameters at every space, thus making the command invalid, such as:

 

 

My second question is: is there any way to say the name of the next map in the maplist in chat? I've tried a number of things here which haven't worked.

 

Thanks for any help anyone can give.

Yeah I'm sorry about this I know it's a complete pain in the ass - the format for the command to be executed in Procon has each element of the command broken up into separate parameters of the function call but there's no consistency about how the parameters should be divided (e.g. PunkBuster commands have all the parameters combined into one argument) and I've gradually extended ProconRulz to support the various cases but "parameters with spaces" are still generally mis-handled.

 

Give me a couple of days and I'll provide an improvement.

[ImportBot]

Originally Posted by _ddonut_*:

 

Don't work :x

[ImportBot]

Originally Posted by ThisGeek*:

 

Fwiw on BF3 R21 server:

 

Code:

On Kill;Weapon Melee,Weapons/Knife/Knife;Yell %p% KNIFED %v%

triggers on dog tags AND on slash kill.

[ImportBot]

Originally Posted by _ddonut_*:

 

Code:

On Spawn;PlayerOnce;PlayerYell <Message>

Is there any chance to don't log this?

Because they are too full if every join will be logged! :x

[ImportBot]

Originally Posted by ty_ger07*:

 

Fwiw on BF3 R21 server:

 

Code:

On Kill;Weapon Melee,Weapons/Knife/Knife;Yell %p% KNIFED %v%

triggers on dog tags AND on slash kill.

Well, duh!

 

Weapon Melee is the dog tag kill.

Weapon Weapons/Knife/Knife is the slash kill.

 

Of course it would trigger for both since you included both.

 

On Kill;Weapon Melee,Weapons/Knife/Knife;Yell %p% KNIFED %v% would trigger or a slash kill or dog tag kill.

On Kill;Weapon Melee;Yell %p% KNIFED %v% would only trigger if someone got someone's dog tags.

On Kill;Weapon Weapons/Knife/Knife;Yell %p% KNIFED %v% would only trigger for a slash kill.

On Kill;Damage Melee;Yell %p% KNIFED %v% would trigger for a slash kill, dog tag kill, repair tool kill, and defibrillator kill.

[ImportBot]

Originally Posted by gedankenleser22*:

 

So here is the Turorial of my Tool.

Read the description for more Info.

Link: http://www.youtube.com/watch_v=3DXvt5x1EJM

[ImportBot]

Originally Posted by gedankenleser22*:

 

So here is the Turorial of my Tool.

Read the description for more Info.

Link: youtube.com/watch_v=3DXvt5x1EJM

[ImportBot]

Originally Posted by Shamrock*:

 

Thanks bambam!

[ImportBot]

Originally Posted by bambam*:

 

So here is the Turorial of my Tool.

Read the description for more Info.

Link: youtube.com/watch_v=3DXvt5x1EJM

hey mate I wish you luck but you could be a bit more up front with the fact you're asking 5 Euro for your tool.

 

The tool is a neat idea but the rulz it produces are a bit hit-and-miss - we'd get more progress if you dropped the charging and collaborated.

[ImportBot]

Originally Posted by gedankenleser22*:

 

hey mate I wish you luck but you could be a bit more up front with the fact you're asking 5 Euro for your tool.

 

The tool is a neat idea but the rulz it produces are a bit hit-and-miss - we'd get more progress if you dropped the charging and collaborated.

this is only for the beta I didn't won't that all people can use it now evey week will more tester give a license, you can see this 5€ now like a spend

 

I would be happy if you can test it and give me feedback

I will give you an full license key if you wan't bambam

[ImportBot]

Originally Posted by ThisGeek*:

 

Well, duh!

 

Weapon Melee is the dog tag kill.

Weapon Weapons/Knife/Knife is the slash kill.

 

Of course it would trigger for both since you included both.

 

On Kill;Weapon Melee,Weapons/Knife/Knife;Yell %p% KNIFED %v% would trigger or a slash kill or dog tag kill.

On Kill;Weapon Melee;Yell %p% KNIFED %v% would only trigger if someone got someone's dog tags.

On Kill;Weapon Weapons/Knife/Knife;Yell %p% KNIFED %v% would only trigger for a slash kill.

On Kill;Damage Melee;Yell %p% KNIFED %v% would trigger for a slash kill, dog tag kill, repair tool kill, and defibrillator kill.

AH! Explains a lot. Was wondering why it did not want to work properly.

[ImportBot]

Originally Posted by badlizz*:

 

Hello BamBam, thanks for the great tool.

 

Was wondering if you could help me with a quick question.

I would like to restrict vehicles when teams are small, but only on the infantry style maps, such as Terahan highway, siene, bazaar etc.

 

Is there a way to string all the maps together into one rule? I have read through the PDF and everything refers only to having one map in each rule, so wasn't sure if that was a limitation.

 

I thought I saw something like you could separate them with a ,

And also can I just use the MP_001

 

ie. Can I do this: On Kill;Map MP_001,MP_003;Weapon Death;Teamsize 3;

[ImportBot]

Originally Posted by Leitwolf*:

 

Hello out there,

 

i got an question to Rulez with PlayerYell like these:

 

Well, duh!

 

Weapon Melee is the dog tag kill.

Weapon Weapons/Knife/Knife is the slash kill.

 

Of course it would trigger for both since you included both.

 

On Kill;Weapon Melee,Weapons/Knife/Knife;Yell %p% KNIFED %v% would trigger or a slash kill or dog tag kill.

On Kill;Weapon Melee;Yell %p% KNIFED %v% would only trigger if someone got someone's dog tags.

On Kill;Weapon Weapons/Knife/Knife;Yell %p% KNIFED %v% would only trigger for a slash kill.

On Kill;Damage Melee;Yell %p% KNIFED %v% would trigger for a slash kill, dog tag kill, repair tool kill, and defibrillator kill.

including Yelled Welcome Messages.

 

if i Yell a Message, the Message is shown untill the next Message should be displayed and so on.... What´s wrong?

 

Please help me

[ImportBot]

Originally Posted by aduh*:

 

I'm looking for code to spam 1 "YELL message" every 10 minutes. Thank you.

[ImportBot]

Originally Posted by ty_ger07*:

 

Hello out there,

 

i got an question to Rulez with PlayerYell like these:

 

 

 

including Yelled Welcome Messages.

 

if i Yell a Message, the Message is shown untill the next Message should be displayed and so on.... What´s wrong?

 

Please help me

Update PRoConRulz to the latest version. You must be using an old version of this plugin.

[ImportBot]

Originally Posted by ty_ger07*:

 

I'm looking for code to spam 1 "YELL message" every 10 minutes. Thank you.

The easiest method is to create a scheduled task in your game server's PBSV.cfg file.

 

Example:

 

pb_sv_task 200 600 admin.yell "Check rules: !rules" 4

 

If you added that command at the bottom of your pbsv.cfg file and restarted your game server, it would create a task to yell "Check rules: !rules" for 4 seconds after 200 seconds of the server being restarted and then every 600 seconds thereafter. In other words, the server would yell the message for 4 seconds every 10 minutes.

 

Let me explain the command: pb_sv_task 200 600 admin.yell "Check rules: !rules" 4

pb_sv_task means to create a new task.

200 means to start the task 200 seconds after the server is started.

600 means to repeat the task every 600 seconds.

admin.yell means to "yell" the message to the server (display the message at the bottom center of the player's screen). You may substitute admin.yell for admin.say to "say" the message in the chat box instead (what you are trying not to do).

"Check rules: !rules" is the message which will be yelled. The message must be within quotation marks if the message is longer than 1 word (has any spaces).

4 is how long the rule is yelled on the screen before disappearing.

[ImportBot]

Originally Posted by aduh*:

 

thank you !

[ImportBot]

Originally Posted by Shamrock*:

 

Either that or use the pre-bundled spambot plugin, which I believe has the option to yell the command rather than saying it.

[ImportBot]

Originally Posted by Shamrock*:

 

Hello out there,

 

i got an question to Rulez with PlayerYell like these:

 

including Yelled Welcome Messages.

 

if i Yell a Message, the Message is shown untill the next Message should be displayed and so on.... What´s wrong?

 

Please help me

The problem is in the proconrulz config file, where the yell delay is by default set to 5000 seconds or something crazy like that. If you update to the latest version of the plugin you can set how long you'd like it to display by typing something like

Code:

On Kill;Yell 5 Your message here

...where 5 is the number of seconds it'll be displayed for.

[ImportBot]

Originally Posted by Athlon*:

 

The problem is in the proconrulz config file, where the yell delay is by default set to 5000 seconds or something crazy like that. If you update to the latest version of the plugin you can set how long you'd like it to display by typing something like

Code:

On Kill;Yell 5 Your message here

...where 5 is the number of seconds it'll be displayed for.

That issue was corrected in the latest version of this plugin.

[ImportBot]

Originally Posted by _ddonut_*:

 

Code:

On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 0;yell [message];Kill
On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 1;yell [message];Kill
On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 2;yell [message];Kill

On a server hosted by a friend there are these rules.

But there is something wrong, because they will be killed after this ServerCount too and the message appears too!

[ImportBot]

Originally Posted by ty_ger07*:

 

Code:

On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 0;yell [message];Kill
On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 1;yell [message];Kill
On Kill;Map MP_001;ServerCount 10;Weapon Death;PlayerCount 2;yell [message];Kill

On a server hosted by a friend there are these rules.

But there is something wrong, because they will be killed after this ServerCount too and the message appears too!

TeamCount might not be what you want to use. I don't know what yiu are trying to do, but if you are trying to count the number of players in the server ServerCount is not the command to use. ServerCount counts the number of times everyone has triggered the rule.

 

To count players in the server, use TeamSize. TeamSize is usually about half of server size; so for counting 10 players in the server, use TeamSize 5.

 

Trigger;TeamSize 5;Action

[ImportBot]

Originally Posted by _ddonut_*:

 

TeamCount might not be what you want to use. I don't know what yiu are trying to do, but if you are trying to count the number of players in the server ServerCount is not the command to use. ServerCount counts the number of times everyone has triggered the rule.

 

To count players in the server, use TeamSize. TeamSize is usually about half of server size; so for counting 10 players in the server, use TeamSize 5.

 

Trigger;TeamSize 5;Action

Hmm i read the online documentation after my post

 

Code:

On Kill;Map MP_001,MP_011;Weapon Death;Teamsize 5;
PlayerCount 5;Yell %p% banned für keine Panzer unter 5 vs 5;Log %p% banned für keine Panzer unter 5 vs 5;TempBan 172800 Du bist gebannt für 48h, Keine Panzer unter 5 vs 5
PlayerCount 3;Yell %p% kicked für keine Panzer unter 5 vs 5;Log %p% kicked für keine Panzer unter 5 vs 5;Kick Keine Panzer unter 5 vs 5
PlayerCount 1;Yell %p% - Warnung %c% von 3! Keine Panzer unter 5 vs 5;Kill

I hope this should work

[ImportBot]

Originally Posted by Tomgun*:

 

[22:40:41] ShaybusPL is ripping people to bits with his M27 IAR !!!

[22:40:51] Killing Spree! ShaybusPL 5-KILL STREAK

[22:40:51] ShaybusPL is ripping people to bits with his M27 IAR !!!

[22:40:51] saffranspannkaka ENDED ShaybusPL's 5-KILL STREAK with M16A4 Assault Rifle

[22:40:55] Killing Spree! imArkAngel 5-KILL STREAK

[22:41:03] (PlayerSay smoothywounds1) smoothywounds1 has 2 Team Kills!!

[22:41:04] (PlayerSay smoothywounds1) lNiNjA: !forgive or !punish

[22:41:04] smoothywounds1's TEAMKILL ENDED lNiNjA's 7-KILL STREAK with Type88 Maschine Gun

 

note the word machine gun is spelt wrong in various weapons and other its spelt right, can this be sorted please

[ImportBot]

Originally Posted by ty_ger07*:

 

[22:40:41] ShaybusPL is ripping people to bits with his M27 IAR !!!

[22:40:51] Killing Spree! ShaybusPL 5-KILL STREAK

[22:40:51] ShaybusPL is ripping people to bits with his M27 IAR !!!

[22:40:51] saffranspannkaka ENDED ShaybusPL's 5-KILL STREAK with M16A4 Assault Rifle

[22:40:55] Killing Spree! imArkAngel 5-KILL STREAK

[22:41:03] (PlayerSay smoothywounds1) smoothywounds1 has 2 Team Kills!!

[22:41:04] (PlayerSay smoothywounds1) lNiNjA: !forgive or !punish

[22:41:04] smoothywounds1's TEAMKILL ENDED lNiNjA's 7-KILL STREAK with Type88 Maschine Gun

 

note the word machine gun is spelt wrong in various weapons and other its spelt right, can this be sorted please

This isn't BamBam's fault. It isn't PRoConRulz plugin which is spelling it wrong. DICE is the one who spelled it wrong. Just like 'Grenade Luncher'.

[ImportBot]

Originally Posted by Leitwolf*:

 

Thanks for the Help, you were right my Version was to old.

 

I got an other question for you. Yesterday i found these lines for Country based Welcomemessages:

 

ProconRulz is a general-purpose Procon plugin that allows admin actions to be taken based on events and triggers. The most common usage is for weapon limits, e.g. "On Kill;Weapon SMAW;Kill" (which will limit the SMAW rockets by killing any player that kills with that weapon). Or you can limit players NOT using certain weapons, e.g. for a pistols-only server "On Kill;Not Damage Handgun;Kill" (which will kill any player that kills with anything NOT a pistol).

 

Rulz for many example requirements are given at the end of this thread

 

If you are new to ProconRulz, and look at the documentation, the fact that ProconRulz is now capable of enabling you to write sets of rulz that behave as killstreak announcers or in-game admin or rude-word-responders will appear scary at first, so don't forget ProconRulz was designed from the beginning to allow simple rulz to implement weapon limits, so it's easy to start with a single rule e.g. limiting nades with On Kill;Weapon M67;PlayerCount 3;Say Too many nade kills for %p%;Kill.

 

ONLINE DOCUMENTATION HERE

 

See below in this thread for sample rulz and an explanation of BF3 limitations so you don't ask the same "how do I block mortars" question as everyone else...

 

ProconRulz has a very flexible range of conditions and actions that can be applied, so as your rulz get fancy you are in effect creating a custom plugin. But everyone begins thinking they "just" want a simple weapon limit.

 

NEWS 2-May-2012: Download updated to version 39d.1. Minor update: new substitution variable %team_score% which holds the number of tickets left for each team, updated about every 30 seconds. See ProconRulz online docs (link above) for details,

NEWS 24-Apr-2012: Download updated to version 39b.2. Minor update: all yell actions now have an optional integer first parameter for the number of seconds it should remain on screen, e.g. "PlayerYell 10 Change your kit %p%!!! Sniper Limit". If the text immediately following the action name (e.g. "Yell") isn't a number, then the default yell time from your plugin settings is used. (And that is set to 5 seconds unless you change that...). Also I've updated the online docs

NEWS 16-Apr-2012: Download updated to version 39a.4. Full set of Say/Yell actions provided for BF3 now that BF3 R20 supports those. I.e. Say, PlayerSay, SquadSay, TeamSay, Yell, PlayerYell, SquadYell, TeamYell. Also 'player country' substitution variables added %pcountry%, %pcountrykey%, %vcountry%, %vcountrykey% for player and victim country (e.g. Germany) and country 'key' (e.g. DE) respectively.

NEWS 07-Apr-2012: Cambridge win the Boat Race. ProconRulz Sniper Limit (by tarreltje) added as Example 13.

NEWS 02-Apr-2012: Minor update 38e.1 for BF3 R20 - Yell and PlayerSay actions now work.

NEWS 26-Jan-2012: A new documentation PDF is available

NEWS 18-Jan-2012: ProconRulz update to version 38d2. It is recommended all users update to this version which significantly extends the flexibility with which rulz can be written and fixes an issue with executing punkBuster commands. ProconRulz remains upwards-compatible with rulz from prior versions. It is expected the core processing logic of ProconRulz will be stable now for a while (with bug fixes as needed), with development limited to new conditions, actions, or perhaps substitution variables if they're needed. Basically 38d2 is like a VERSION upgrade, while the next few upgrades can be considered incremental releases. With 38d2, conditions (e.g. "Weapon SMAW") and actions (e.g. "Kick") can now be freely intermixed in any rule in any order, with processing proceeding from left-to-right through the rule until a condition fails. This won't mean much to you unless you've tried it but it removes a constraint from prior versions that was unexpected to some users. Variable names can now be nested in a completely general way, e.g. a count of weapon use by each player could be stored in %server_weapon_use[%w%][%p%]%.

Older news click to expand:

 

 

NEWS 11-Jan-2012: New example added (Example 8) of simple kill-rate anti-hacker rulz.

NEWS 09-Jan-2012: It's been noted the Procon Configs/BF3.def file does not have an entry for the Jackhammer MK3A1 shotgun. If you want to add the weapon without waiting for a Procon update, add the following line to the Configs\BF3.def file near the other similar entries:

procon.protected.weapons.add None "jackhammer" Primary Shotgun

NEWS 04-Jan-2012: Minor bugfix v37g3 (fixes minor PBBan message error). Also adds a new "If %var% word " condition that matches words (e.g. say text) not just a string anywhere as 'Text' condition.

NEWS 28-Dec-2011: Minor bugfix v37e3 upload, corrects the display of the %c% variable (now counts from 1, not 0), and the 'Text' condition for single-word player say values.

NEWS 27-Dec-2011: ProconRulz major update to v37 - This has a significant update to the rules processing engine, plus a few useful things that have been asked for:

* NEW PBKick and PBBan actions added (kicking, banning via PunkBuster using PB GUID)

* NEW substitution variables %ea_guid%, %pb_guid%, %ip%

* A small change has been made to the way ProconRulz steps through the rulz: ProconRulz will CONTINUE rulz processing for a single event until a KILL/KICK/BAN event is fired.. This means multiple Log/Say actions can fire for a single event. A new action "End" can be placed after any Log/Say action to return the behaviour of the prior versions.

* NEW Continue and End actions that force rulz processing to continue or end respectively, overriding the default behaviour of continuing unless the action was Kill/Kick/Ban.

* NEW User-writeable Rulz %Variables%. Supported with new conditions Set, Incr, Decr, and If. This provides much greater flexibility in rulz writing, e.g. to keep track of kill streaks, or for a QuakeCounter-style plugin.

NEWS 29-Nov-2011: ProconRulz minor update to v34 - 'Protection' of admins from kicks/bans now optional.

NEWS 28-Nov-2011: An updated Procon 1.1.2.0 is available, so ProconRulz modified BF3.def is no longer needed or included in the zip.

 

 

 

 

ProconRulz has been extensively used on BFBC2 servers (for BFBC2 see this thread*). That thread now has hundreds of entries so for BF3 I've started this new one.

 

ProconRulz has relatively comprehensive documentation on its 'Details' tab, so please refer to that. For info, if you haven't downloaded the plugin yet, you can check out an cached version of the details info online here. Of course for the most up-to-date version of the documentation, check the plugin 'Details'.

 

ProconRulz allows rulz of the format "Trigger;Conditions...;Actions..." with a wide choice of triggers, conditions and actions. The most trivial forms of weapon limits can be implemented with a single rule, e.g. to kill players using the M320 underslung rifle nade, use the single rule given as an example at the top of this post. However, with a bit of thought, it is possible to provide rulz with a more complex behaviour, e.g. warn on the first kill, kill on the third, kick on the fifth.

 

ProconRulz installs with half-a-dozen default simple rulz that provide a template for your rulz if that helps.

 

Some current limitations of BF3 to be aware of

 

1) not all weapon keys are available. All kills by mortar, MAV, tanks, choppers, humvee are just weapon 'Death'. This means Damage VehicleXXX conditions cannot be used in BF3.

2) weapon keys are currently given on 'kill' events but not on 'spawn' events.

3) player kit (i.e. assault, recon etc) is not available

4) player specializations/accessories are not availabe

5) 'say' messages are to server/team/squad only. I.e. no 'PlayerSay' which makes in-game admin awkward

6) A rocket attack on a tank, killing the player inside, cannot be distinguished from a soldier that gets hit by a rocket in the face. Both show the killer killing the victim with a rocket. This means no plugin can detect RPG's used on infantry as opposed to tanks.

7) there are no events triggered when a player enters or leaves any vehicle

8) Nade launchers slung under assault rifles are reported by BF3 as a kill BY THE ASSAULT RIFLE. This is an absolute bug in BF3, IMHO. It means you CANNOT tell in any plugin whether the kill was by a bullet from an M416 rifle, or an M320 nade from a launcher that happened to be attached to the M416 rifle.

9) BF3 R16 is not reporting the map coordinates of the killer or victim in a kill event. This means the ProconRulz 'Range' condition and %r% variable are non-functioning for BF3.

 

Specifically, these kinds of limits are not possible, even though many people ask:

* no mortar limits (see 1. Mortars are one of the weapons with key DEATH, as well as all vehicles). On an infantry-only server, you can use a Weapon Death condition to block mortars because you are not worried about vehicle kills being affected by the same rule.

* no server limit for numbers of players spawned with a particular kit/spec/weapon (see 2). See also Example 13 (by tarreltje), with a workaround by checking for snipers a kill time.

* no 'max 2 snipers per team' type rule at spawn time (I just explained that in the line above ^^)

* no 'max 2 mortars per team' type rule (ditto)

* no kill or spawn limit for players with MAV (aka Weapon Roadkill - similar issues to mortar comment above) except on non-vehicle maps like Metro where blocking all roadkill works

* no rule to kill m26 users (Dart/Mass) BF3 not reporting underslung weapons

 

For all this, you can still prevent the use of the 55 weapons that *do* have a weapon key (and hence also a damage-type), by having a rule that kills any player that kills with one. E.g. my favorite rule:

On Kill;Map Subway;Damage ProjectileExplosive;Kill

This makes RPG kills on Operation Metro suicidal. Right now you probably have no idea what this rule does or how it works, but when you've installed ProconRulz and tried a few simple rulz you'll get the idea, so congratulations...

 

So I've tried to explain the BF3 limitations, but still get questions like this:

 

Answer: No BF3 admin tool can do this at spawn time. Read the BF3 limitations above, especially #2. Instead all you can do is limit the number of kills by sniper weapons, or with rulz you can track the counts of players with sniper rifles at kill time (see Example 13).

 

Some sample rulz

 

KEEP the default logging On Kill rule at the end of all your rulz. This has a 'Log' action which is very helpful when your rulz don't pick up the condition you expected... (e.g. Log %pt% %k% %p% killed %v% with %w% (%wk%), damage %d%). You don't need to understand this now, just leave it in.

 

Example 1. Limit a single weapon (usage suicidal, kick on 4th kill, ban on 6th kill):

Click to expand:

 

 

On Kill;Weapon Siaga20k;PlayerCount 5;Log %p% banned for Saiga;Ban %p% Saiga shotgun use

On Kill;Weapon Siaga20k;PlayerCount 3;Log %p% kicked for Saiga;Kick %p% Saiga shotgun use

On Kill;Weapon Siaga20k;PlayerSay %p% no Saiga shotgun;Kill 100

 

 

 

 

 

Example 2. Limit a weapon category via Damage condition (usage suicidal, kick on 4th kill, ban on 6th kill):

Click to expand:

 

 

On Kill;Damage Shotgun;PlayerCount 5;Log %p% banned for Shotgun;Ban %p% shotgun use

On Kill;Damage Shotgun;PlayerCount 3;Log %p% kicked for Shotgun;Kick %p% shotgun use

On Kill;Damage Shotgun;PlayerSay %p% no Shotgun;Kill 100

 

Above rule can be used with Damage ProjectileExplosive, or Damage SniperRifle (instead of Damage Shotgun) to block rockets or snipers respectively.

 

 

 

 

 

Example 3. For a sniper/pistol server (usage of other weapons is suicidal, kick on 4th kill, ban on 6th kill):

Click to expand:

 

 

 

On Kill;Not Damage SniperRifle;Not Damage Handgun;PlayerCount 5;Log %p%banned (snipers / pistols only);Ban %p% snipers only

On Kill;Not Damage SniperRifle;Not Damage Handgun;PlayerCount 3;Log %p% kicked (snipers / pistols only);Kick %p% snipers only

On Kill;Not Damage SniperRifle;Not Damage Handgun;PlayerSay %p% snipers/pistols only;Kill 100

 

 

 

 

 

Example 4. Make teamkills suicidal

Click to expand:

 

 

The simplest idea is just have a rule:

On TeamKill;Say %p% teamkilled %v%;Kill 100;

If you want !forgive/!punish

See this dedicated thread*

 

 

 

 

 

Example 5. Stop use of rockets on map Operation Metro:

Click to expand:

 

 

 

On Kill;Map Subway;Damage ProjectileExplosive;PlayerCount 5;Log %p% banned for rockets on Metro;Ban %p% Metro rockets

On Kill;Map Subway;Damage ProjectileExplosive;PlayerCount 3;Log %p% kicked for rockets on Metro;Kick %p% Metro rockets

On Kill;Map Subway;Damage ProjectileExplosive;PlayerSay %p% no rockets on Metro;Kill 100

 

For reference, the other map filenames / map names (use substring of either in Map condition) are:

MP_001 (Grand Bazaar)

MP_003 (Teheran Highway)

MP_007 (Caspian Border)

MP_011 (Seine Crossing)

MP_012 (Operation Firestorm)

MP_013 (Damavand Peak)

MP_017 (Noshashar Canals)

MP_018 (Kharg Island)

MP_Subway (Operation Metro)

 

there are more filesnames for more maps (e.g. Karkand), but go find them on the interweb. If you post the new mapnames here I'll update this list.

 

Be careful !! These are not the definitive spellings of the full map names. It is possible a map name could include non-english characters, e.g. "Operation Métro" or something like that. If in doubt use a safe subset of the map name, or map filename e.g. "Map 011" or "Map Canal"

 

 

 

 

 

Example 6. If you want to reduce the frequency of a weapon use

e.g. limit players to max 2 nade kills per minute:

Click to expand:

 

 

 

On Kill;Damage Explosive;Rate 2 60;Say %p% excessive nade spam;Kill

 

 

 

 

 

Example 7. Kill Streak Announcer

 

by ty_ger07.

 

Please see this dedicated thread*

 

Example 8. Basic Cheater Detector

Click to expand:

 

 

 

by ty_ger07.

 

These rulz use the 'Rate' condition to QUICKLY ban likely hackers, i.e. the kiddies that appear on the server and don't even pretend to play the game.

 

You can adjust the thresholds and messages (in fact it's a good idea if you do). Note that you do NOT have to tell the player you banned WHY you banned them (why tell the hacker you specifically detected their knife hack_) but it is helpful to have unique info in the ban message so YOU know which rule banned them. You cannot have these kinds of rulz without risking false positives, in particular BF3 players can get long-term high kill rates in vehicles (Weapon Death...) and short-term high kills rates with explosives/rockets.

 

Micovery's Insane Limiter plugin provides more comprehensive support for this capability (by also checking BattleLog stats) and can be used in addition to ProconRulz.

 

# Cheater Detector by ty_ger07

On Kill;Damage Melee;Rate 8 30;Say %p%: banned - kill rate;Ban %p% Auto-banned - hacking status 5

On Kill;Weapon Death;Rate 10 30;Say %p%: banned - nuke;Ban %p% Auto-banned - hacking status 6

On Kill;Not Damage Explosive;Not Damage ProjectileExplosive;Rate 20 50;Say %p%: banned - kill rate 1;Ban %p% Auto-banned - hacking status 1

On Kill;Not Damage Explosive;Not Damage ProjectileExplosive;Rate 40 200;Say %p%: banned - kill rate;Ban %p% Auto-banned - hacking status 2

On Kill;Headshot;Rate 6 15;Say %p%: banned - aimbot;Ban %p% Auto-banned - hacking status 3

On Kill;Headshot;Rate 8 25;Say %p%: banned - aimbot;Ban %p% Auto-banned - hacking status 4

 

 

 

 

 

Example 9. Limit vehicle use when teams are small

Click to expand:

 

 

 

All BF3 vehicle kills are currently reported as "Weapon Death", and FYI Mortars are reported as "Weapon Death" also, so you cannot tell those kills apart. But if you want to limit all vehicles AND mortars when teams are small, then you can use these rulz for BF3 (For BFBC2 there is full support for vehicle kills, e.g. with Damage VehicleHeavy, VehicleAir etc. so you can use similar rulz but be more specific).

 

The Teamsize condition in these rulz makes vehicle kills suicidal if the smallest team is 4 or smaller. On a balanced server this means vehicle kills will be suicidal until 10 players total are in-game...

 

The PlayerCount conditions control the kill count thresholds for warn (vehicle kill 1,2,3), kill (vehicle kill 4,5), kick (vehicle kills >5)

On Kill;Weapon Death;Teamsize 4;

PlayerCount 5;Say %p% kicked for vehicle kills;Kick kicked for vehicle kills with small teams

PlayerCount 3;Say %p% slayed for vehicle kill %c%/5;Kill 100

Say %p% - no vehicle kills with small teams (#%c%/5)

 

 

 

 

 

Example 10. Easy in-game admin

Click to expand:

 

 

 

Using the TargetPlayer condition simplifies matching player names - any string subset of the name will do, and ProconRulz will only match the name if ONLY ONE match is found so you're unlikely to kick the wrong player and no "confirm..." step is needed.

 

You can type ANY SUBSTRING of the player name and the command will be applied if that is found in a SINGLE player name (upper/lower case still match). If there is no match, or the string is found in multiple names, the command does nothing.

 

E.g. to kick player "l33t_h4x0r_^^_" just say "!kick h4x" (or "!kick 33", or any other substring of the player name that gives a unique match).

 

On Say;Admin;Text !kill;TargetPlayer;Say Player %t% killed;TargetAction Kill 100

On Say;Admin;Text !kick;TargetPlayer;Say Player %t% kicked;TargetAction Kick Kicked by Admin

 

 

 

 

 

Example 11. No MAV's on Metro

Click to expand:

 

 

Credit: Rouven

 

MAV's kill with weapon 'Roadkill', so you can only trap this if there are no vehicles on your server that could do this as well. E.g. you can use these rulz on Metro or on an infantry-only server.

On Kill;Map Subway;Weapon Roadkill;PlayerCount 5;Log %p% banned for MAV;Ban %p% MAV use

On Kill;Map Subway;Weapon Roadkill;PlayerCount 3;Log %p% kicked for MAV;Kick %p% MAV use

On Kill;Map Subway;Weapon Roadkill;PlayerSay %p% no MAV;Kill 100

 

 

 

 

 

Example 12. Unreal Tournament Multi Kills Announcer by Bl1ndy

 

Please see this dedicated thread*

 

 

Example 13. Sniper Limit V2!!! (credit tarreltje)

Click to expand:

 

 

These rulz are damn clever, thanks to tarreltje ...

 

These rulz set the max number of snipers per team to 2. If you want a different limit, edit the On Round.. rule that currently has "Set %server_sniperlimit% 2" to another number.

 

Most BF3 admins know by now that the game server doesn't inform the plugins what weapons a player has chosen at spawn time, so limiting snipers is tricky. What these rulz do is keep track of the players that have sniper rifles when a kill occurs, so the plugin can detect when more than two players are trying to kill with sniper rifles (get it_). So where with BFBC2 you could say "max two players can spawn with sniper rifles" (i.e. the third spawning sniper gets admin-slayed), these rulz do the same thing at kill-time. The first two players to kill with sniper rifles are ok, the third player to kill with a sniper rifle will get admin-slayed.

 

#sniper limit by tarreltje V2.1

 

# SET THE MAX # OF SNIPERS HERE:

On Round;Set %server_sniperlimit% 2

 

# sniper limit rulz

On Spawn;if %beingsniper% == 1;Decr %beingsniper%;Decr %team_recontotal%;log we have %team_recontotal% snipers on team %pt%

On Spawn;Set %beingsniper% 0

 

On kill;Damage sniperRifle;

if %team_recontotal% == %server_sniperlimit%;if %beingsniper% == 0;Say Sniper Limit max %server_sniperlimit% snipers each team !!!;Kill

if %beingsniper% == 1;End;log %p% is still a sniper, %team_recontotal% snipers on team %pt%

incr %team_recontotal%;set %beingsniper% 1;log %p% is a sniper, %team_recontotal% snipers on team %pt%

On kill;Not Damage sniperRifle;if %beingsniper% == 1;decr %beingsniper%;decr %team_recontotal%;log %p% is no sniper anymore, %team_recontotal% snipers on team %pt%

On Leave;if %beingsniper% == 1;Decr %team_recontotal%

 

 

 

 

 

Example 14. Multi-language 'join' welcome messages (credit Angry_AGAIN)

Click to expand:

 

 

Here is our first version for country based welcome.

Hope its usefull for somebody

PS: DEACTIVATE vars.serverMessage if you use this welcome.

 

#Country Base Welcome

#BASETEXT: Welcome - YOUR TEXT - Please follow our rules

#Countrykeys only in small letters based on ISO3166

# Only latin letters works propper

 

On Spawn;PlayerOnce;If %pcountrykey% == de;Yell 10 WILLKOMMEN %p% - RED EYES ONLY @ AMSTERDAM 420 SERVER - BITTE BEACHTE UNSERE REGELN

On Spawn;PlayerOnce;If %pcountrykey% == nl;Yell 10 Welkom %p% - RED EYES ONLY @ AMSTERDAM 420 SERVERS - check ff onze huisregels,enjoy

On Spawn;PlayerOnce;If %pcountrykey% == fr;Yell 10 BONJOUR %p% -YOUR SERVER TEXT HERE - VEUILLEZ SUIVRE NOS RÈGLES

On Spawn;PlayerOnce;If %pcountrykey% == uk;Yell 10 WELCOME %p% -YOUR SERVER TEXT HERE - PLEASE FOLLOW OUR RULES

On Spawn;PlayerOnce;If %pcountrykey% == us;Yell 10 WELCOME %p% -YOUR SERVER TEXT HERE - PLEASE FOLLOW OUR RULES

On Spawn;PlayerOnce;If %pcountrykey% == ru;Yell 10 Dobro pozhalovat %p% -YOUR SERVER TEXT HERE - pozhaluysta sleduy nashim pravilam

On Spawn;PlayerOnce;If %pcountrykey% == pt;Yell 10 Sangrado %p% -YOUR SERVER TEXT HERE - Por favor anote nosso Regimento

On Spawn;PlayerOnce;If %pcountrykey% == dk;Yell 10 Velkommen %p% -YOUR SERVER TEXT HERE - følg vores regler

On Spawn;PlayerOnce;If %pcountrykey% == it;Yell 10 Benvenuti %p% -YOUR SERVER TEXT HERE - SI PREGA DI SEGUIRE LE NOSTRE REGOLE

On Spawn;PlayerOnce;If %pcountrykey% == no;Yell 10 Velkommen %p% -YOUR SERVER TEXT HERE - KAN DU FØLGE VÅRE REGLER

On Spawn;PlayerOnce;If %pcountrykey% == se;Yell 10 Välkommen %p% -YOUR SERVER TEXT HERE - följ VÅRA REGLER

On Spawn;PlayerOnce;If %pcountrykey% == es;Yell 10 Bienvenido %p% -YOUR SERVER TEXT HERE - por favor siga nuestro reglamento

On Spawn;PlayerOnce;If %pcountrykey% == fi;Yell 10 Suhtaudun myönteisesti %p% -YOUR SERVER TEXT HERE - huomaa työjärjestyksemme

On Spawn;PlayerOnce;If %pcountrykey% == pl;Yell 10 Mile widziane %p% -YOUR SERVER TEXT HERE - PROSIMY O PRZESTRZEGANIE NASZYCH ZASAD

 

 

 

 

New section: Servers using ProconRulz.

 

OFcGaming.com HC|FF - the home of Bambam (and the OFc clan)...

bfcom.org - 1000 Tickets Metro only 24/7 NO ROCKETS/M320! - the home of MorpheusX...

Crzy88s-Metro-Sein-Crossing-1000-Tickets-1p-to-start - from TiDisintegro...

E-A-C-Koksnutten-DE-Hardcore-ngz-server-de/ - home of NARF! ...

KillZone-01-No-Explosives-Operation-Metro-1000-Tickets/ - thanks RadicalMode...

KillZone-07-No-Explosives-Operation-Metro-1000-Tickets-HC/ - RadicalMode #2 thanks...

Hattinger-Hauptbahnhof-24-7-Metro-Server-Rules-by-ngz-server-de/ - home of Friegide ...

TTT-TheTacTeam-Standard-HC-SQ-Rush-16-UK - ty_ger kickin ass on this one ...

TTT-TheTacTeam-B2K-HC-SQ-Rush-16-UK/ - and this one...

Hated-HC-Infantry-Only-MAP-VOTE - from FOLLOW3R

SKK-Skurup-killers-HC-Squad-server-Old-and-new-maps - from Rodex

Damaged Frontlines - 24/7 Canals TDM. No Clays/bolt-action. - thanks to OstrichPolicy

FR-GiFr-RUSH-www-gifr-fr - home of C-4-N

FR-GiFr-METRO-NO-EXPLOSIF-CLAYMORE-RPG-M320-www-gifr-fr - home of C-4-N

FR-GiFr-INFANTRY-www-gifr-fr - home of C-4-N

FR-GiFr-CONQUEST-www-gifr-fr - home of C-4-N

H-Operation-Metro-1000-Tickets-No-M320-RPG-7-SMAW/ - home of ChaB

GF-gfclan-org-Conquest-Rush-Deathmatch/ - home of lupri ...

TGONE-TDM-HardCore-500-TICKETS/ - home of AJ Toft and his clan...

Multiplay-Conquest-300-tickets-read-rules-Faithclan-su/ - home of Phantomik87 and Faith clan...

Knife Only Metro / Shotgun Only Noshars 2 rounds cycle - home of NL_Henkenator68 and the Dutch Armed Forces clan...

[OFF]Club | HC | ONLY Bolt Action Sniper Rifle and Knife - home of Small_d and the OFF clan...

NL-DUTCH-COWBOYS-SQDM-TDM-24-7-10-maps - home of tarreltje and the Dutch Cowboys...

KoX-24-7-CITYMAPS-NORPG-GCC-by-ngz-server-de - home of tobi13...FTB-02-SUBWAY-1000-TICKETS-FAST-RESPAW-24-7/ - home of guapoloko and the =FTB= FORÇA TÁTICA BRASILEIRA clan (in Brazil)...

FTB-10-SUBWAY-RUSH-FAST-RESPAWN-24-7/ - another server from guapoloko (in Brazil)...

Bl1ndy-s-Bolt-Action-Sniper-Only-CANALS-GGC-Stream - home of Bl1ndy

i3D-net-NCe-Next-Century-eu-1-Fast-Vehicle-750Tick-2PS - home of Helldon and Next-Century eSports

i3D-net-NCe-Next-Century-eu-2-Infantry-TeamPlay-2PS - home of Helldon and Next-Century eSports

i3D-net-NCe-Next-Century-eu-3-Infantry-SquadPlay-2PS - home of Helldon and Next-Century eSports

[P]arental[A]dvisory | 24/7 RUSH ONLY | Votemap | Rules - home of _ddonut? and his Parental Advisory Gaming Clan

F-Re-Fighting-Rebels-DE-MAPVOTE-150p-TICKETS-1P-START/ home of Hand of Shadow, in Germany

 

How to enter your rulz

click here to expand this section:

 

 

Click the elements 1..5 as per the screenshot below.

When the [...] button is clicked on the 'Rules' plugin setting (#5 in image) a pop-up edit window wll appear and you cut-and-paste your rulz into that window and save.

 

 

 

 

 

Versions summary:

 

v39 (Apr 12 2012): Yell added (with BF3 R20). Yell/Say can now be to all, Player, Squad, Team (e.g. SquadYell). Player/Victim country codes available (e.g. %pcountry% see online docs). Tickets remaining now in %team_score%.

v38 (Jan 18 2012): any order now permitted for intermixing actions and conditions. server, team, squad, player variables now more easily mixable, Exec can now run PunkBuster commands in addition to the v37 PBBan & PBTempBan, TargetPlayer condition enhanced for ease of use in rulz.

v37: PunkBuster Kicks/bans, new rulz processing flow, rulz variables

v34: Players 'protected' from kicks, kills, bans by ProconRulz now Admins, Admins+Reserved_Slots, Neither, plus Player and Clan whitelist.

v33: BF3 compatibility

v1..32 (see ProconRulz BFBC2 thread)

 

Downloads: 9603 + count on this version:

the Question i got to this: Is it possible to edit the Lines so only the "fresh" joined Player gets the Yell Message at the moment all active Players get the Message.

 

Thank you!