Jump to content

Photo

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

BF4 BF3 BC2 MOH

  • Please log in to reply
6070 replies to this topic

#1
ColColonCleaner

ColColonCleaner

    AdKats Developer

  • Plugin Developer
  • PipPipPip
  • 55 posts

Donator

Original post by bambam.

MAJOR UPDATE TO V44. BF4 SUPPORT, PLUS SUPPORT FOR EXTERNAL PROCONRULZ SCRIPT FILES


Summary

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


How to enter your rulz

Spoiler

 

See below in this thread for sample rulz and an explanation of BF3/BF4 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 25-Dec-2013: version 44j1 uploaded. Rulz .txt files now reloaded on plugin enable (useful for layer-server users).
NEWS 17-Dec-2013: version 44h6 uploaded. New On RoundOver trigger that fired on end-of-round (useful for BF4). !knife rulz added.
NEWS 9-Dec-2013: version 44g3 uploaded. BUGFIX version for new "On Init" trigger with BF3/4. Users who downloaded 44g.2 should replace with this version if they want to use the new On Init trigger (also used in snipersquad rulz set).
NEWS 6-Dec-2013: version 44g2 uploaded. Sniper Squad limiter rulz added. Added Linux support for %ini_..% vars file. New 'On Init' trigger that can be used for simple startup values for rules.
NEWS 2-Dec-2013: version 44f1 uploaded. Support for Linux external .txt rulz files. Updated sniper limit with additional !setsniper command (e.g. !setsniper bam) for admin to guarantee sniper slot to a player.
NEWS 26-Nov-2013: version 44e2 uploaded. Support for BF4 with four weeks of testing (thanks D1bble, Tarreltje). Now rulz can be held in an external file and loaded by the plugin making it easier to share rulz sets e.g. for weapon limits, teamkill limits, announcers, etc.

Spoiler

 

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.

Currently included rulz sets

Sniper Limit (proconrulz_sniperlimit.txt) - limits the number of snipers on each team to a maximum set at the top of the rulz. A sniper slot is reserved when the player kills with a sniper rifle. The sniper slot is released when the round ends, the player leaves, or the player kills with some other weapon and an announcement is issued to team. All players have the !snipers command which tells them the current snipers on their team. Also included is proconrulz_sniperdmrlimit.txt which is the same but limits both sniper rifles and DMR's. CREDIT tarreltje and see thread here

Sniper Squad Limit (proconrulz_snipersquad.txt) - only permits sniper kills if you are in a particular squad (default Echo). Also supports a !snipers command that tells users what's going on. (As above, also with proconrulz_sniperdmrsquad.txt for snipers andDMR's). CREDIT staazvaind.

Announcer (proconrulz_announcer.txt) - gives a few kill messages (Fred knifed Barney) for you to modify.

Multi-kills (proconrulz_multikill.txt) - keeps track of short-term multi-kill streaks and makes Quake-like announcements. Credit Bl1ndy and Panther.

Rules (proconrulz_rules.txt) - simple rulz that display messages when any player types !rules - for you to modify for your server.

Punish (proconrulz_punish.txt) Support of !punish / !p and !forgive / !f for teamkills. CREDIT ty_ger07 and russel5

Killstreak (proconrulz_killstreak.txt) Announces kill streaks at 5/10/15 kills etc, and when ended. Credit ty_ger07

Best 3 Players (proconrulz_best3players.txt) Particularly for TDM announces current highest kill player & each time that changes. CREDIT tarreltje.

************************************************** ************************************************
Plus, you can still edit additional rulz directly into the Plugin settings with these as examples for ideas below
************************************************** ************************************************


BF3 Map names and modes

In case you need them in Map or MapMode conditions, BF3/BF4 names and modes are collected into this post.

ProconRulz doesn't really care what keys you use - it's up to you to check your conditions match whatever your server is sending. This is collected documentation for BF3 that you can find on the internet.

Some current limitations of BF3/BF4 to be aware of

Spoiler

 

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):

Spoiler

 

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

Spoiler

 

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

Spoiler

 

Example 4. Make teamkills suicidal

Spoiler

 

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

Spoiler

 

Example 6. If you want to reduce the frequency of a weapon use
e.g. limit players to max 2 nade kills per minute:

Spoiler


Example 8. Basic Cheater Detector

Spoiler

 

Example 9. Limit vehicle use when teams are small

Spoiler
 
Example 10. Easy in-game admin

Spoiler

 

Example 11. No MAV's on Metro

Spoiler

 

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

Spoiler

 

Example 15. Knife/Defib/Repair Tool Kill YELL Announcer
This plugin will put a Yell message on the screen each knife or other melee weaon kill

Spoiler

 

Example 17. Country filter by L2Devlier
Here's an interesting concept, illustrating the global villiage we live (game) in. It's possible you live in a small country, adjacent to a large country (e.g. China), and you're trying to build a local community, but end up with the server being dominated by large numbers of gamers texting in the foreign language from the large-country-next-door, what can you do. L2Devlier came up with this solution in in a long PM to me emphasized this is not about being racist, just trying to compensate for limitations in the EA queueing system if you're trying to build a local community. For other-country-applicability you'll need to read the rulz, understand what they do, and tweak the country-codes as appropriate.

 

Spoiler

Example 21. !votekick - ingame command for players to vote to kick another player

Spoiler


Example 23. Simple Aimbot headshot detector
credit russel5

These rulz count headshots and if it's more than 60% after 30 kills (these params in line 5) and it's not a sniper rifle, player is banned.

Spoiler

 

Versions summary:

v44 (Nov 26 2013): Support for BF4, plus the support for separate rulz .txt files (incl Linux from 44f.1 credit FritzE).On RoundOver trigger.
v43 (Aug 21 2012): Arithmetic in Set/If statements, permanent 'ini' vars, rounding, new date/time and teamsize variables, logging options. New player %score% variable, '+' as 1st character on line allows multi-line rulz.
v41 (Jun 29 2012): More flexible support for in-game admin commands e.g. !kick <player> <reason>
v40 (May 15 2012): Quoted strings can be used in rulz e.g. Set %server_message% "Get ready for next round"
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)


Please note: There is an unsupported version below ProconRulz_NL.zip which allows new lines in messages.

Example new line:

Code:
On Say;Text /show;PlayerYell \nHello %p%\nThis is your first visit, please type !rules

It should look like this on the player screen:

[ADMIN]
Hello DarthVader
This is your first visit, please type !rules

 

DOWNLOADS

ProconRulz Main
ProconRulz(Unsupported newline version)

 



#2
lakaelo

lakaelo

    Newbie

  • Members
  • Pip
  • 2 posts
just got something in my mind and would know it its possible....
 
in the got old bf2 time we had the "nofly" server. helis and jets are only for transport and no kills from them are allowed.
 
guess it must be possible to setup a equal rule into proconrulez and just found this example from the "no vehicle kill while low population.
 
 
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)
 
i am not really that crack in this things so i would have to know if it is possible to change weapon to helis and jets ( do they have there own or are they also only death? ) to a simple rules that everyone got killed when he is killing from a jet or heli?
 
something like that:
On Kill;Weapon Heli and Jet;
Say %p% killed for vehicle kills;Kick kicked for heli or jet kill

Edited by Prophet731, 20 July 2019 - 02:40 PM.
Changed quote blocks to code blocks


#3
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

Donations: none needed - ProconRulz is 100% free software. Please acknowledge any support by clicking the Rate this thread link just above this post, and sharing the rulz you come up with. Thank You.

MAJOR UPDATE TO V44. BF4 SUPPORT, PLUS SUPPORT FOR EXTERNAL PROCONRULZ SCRIPT FILES

Summary

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


How to enter your rulz
click here to expand this section:
Spoiler



See below in this thread for sample rulz and an explanation of BF3/BF4 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 25-Dec-2013: version 44j1 uploaded. Rulz .txt files now reloaded on plugin enable (useful for layer-server users).
NEWS 17-Dec-2013: version 44h6 uploaded. New On RoundOver trigger that fired on end-of-round (useful for BF4). !knife rulz added.
NEWS 9-Dec-2013: version 44g3 uploaded. BUGFIX version for new "On Init" trigger with BF3/4. Users who downloaded 44g.2 should replace with this version if they want to use the new On Init trigger (also used in snipersquad rulz set).
NEWS 6-Dec-2013: version 44g2 uploaded. Sniper Squad limiter rulz added. Added Linux support for %ini_..% vars file. New 'On Init' trigger that can be used for simple startup values for rules.
NEWS 2-Dec-2013: version 44f1 uploaded. Support for Linux external .txt rulz files. Updated sniper limit with additional !setsniper command (e.g. !setsniper bam) for admin to guarantee sniper slot to a player.
NEWS 26-Nov-2013: version 44e2 uploaded. Support for BF4 with four weeks of testing (thanks D1bble, Tarreltje). Now rulz can be held in an external file and loaded by the plugin making it easier to share rulz sets e.g. for weapon limits, teamkill limits, announcers, etc.
Older news click to expand:
Spoiler


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.

Currently included rulz sets

Sniper Limit (proconrulz_sniperlimit.txt) - limits the number of snipers on each team to a maximum set at the top of the rulz. A sniper slot is reserved when the player kills with a sniper rifle. The sniper slot is released when the round ends, the player leaves, or the player kills with some other weapon and an announcement is issued to team. All players have the !snipers command which tells them the current snipers on their team. Also included is proconrulz_sniperdmrlimit.txt which is the same but limits both sniper rifles and DMR's. CREDIT tarreltje and see thread here*

Sniper Squad Limit (proconrulz_snipersquad.txt) - only permits sniper kills if you are in a particular squad (default Echo). Also supports a !snipers command that tells users what's going on. (As above, also with proconrulz_sniperdmrsquad.txt for snipers andDMR's). CREDIT staazvaind.

Announcer (proconrulz_announcer.txt) - gives a few kill messages (Fred knifed Barney) for you to modify.

Multi-kills (proconrulz_multikill.txt) - keeps track of short-term multi-kill streaks and makes Quake-like announcements. Credit Bl1ndy and Panther.

Rules (proconrulz_rules.txt) - simple rulz that display messages when any player types !rules - for you to modify for your server.

Punish (proconrulz_punish.txt) Support of !punish / !p and !forgive / !f for teamkills. CREDIT ty_ger07 and russel5

Killstreak (proconrulz_killstreak.txt) Announces kill streaks at 5/10/15 kills etc, and when ended. Credit ty_ger07

Best 3 Players (proconrulz_best3players.txt) Particularly for TDM announces current highest kill player & each time that changes. CREDIT tarreltje.

************************************************** ************************************************
Plus, you can still edit additional rulz directly into the Plugin settings with these as examples for ideas below
************************************************** ************************************************


BF3 Map names and modes

In case you need them in Map or MapMode conditions, BF3/BF4 names and modes are collected into this post*.

ProconRulz doesn't really care what keys you use - it's up to you to check your conditions match whatever your server is sending. This is collected documentation for BF3 that you can find on the internet.

Some current limitations of BF3/BF4 to be aware of

click to expand:
Spoiler


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:
Spoiler



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



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



Example 4. Make teamkills suicidal
Click to expand:
Spoiler



Example 5. Stop use of rockets on map Operation Metro:
Click to expand:
Spoiler



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:
Spoiler



Example 7. Kill Streak Announcer

by ty_ger07.

Please see this dedicated thread*

Example 8. Basic Cheater Detector
Click to expand:
Spoiler



Example 9. Limit vehicle use when teams are small
Click to expand:
Spoiler



Example 10. Easy in-game admin
Click to expand:
Spoiler



Example 11. No MAV's on Metro
Click to expand:
Spoiler



Example 12. Unreal Tournament Multi Kills Announcer by Bl1ndy

Please see this dedicated thread*


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

Please see this dedicated thread*

Click to expand for a bit of explanation of how these rulz work in BF3:
Spoiler



Example 14. Multi-language 'join' welcome messages (credit Angry_AGAIN)
Click to expand:
Spoiler



Example 15. Knife/Defib/Repair Tool Kill YELL Announcer
This plugin will put a Yell message on the screen each knife or other melee weaon kill
Click to expand:
Spoiler



Example 16. End of Round Stats Announcer by tarreltje

These rules give the 'most kills', 'most knife kills', 'most headshots' playernames and kill counts during and near the end of the round. As with all ProconRulz rulz you can tweak the rulz for different stats or timings as you want.

Please see this dedicated thread*

Example 17. Country filter by L2Devlier
Here's an interesting concept, illustrating the global villiage we live (game) in. It's possible you live in a small country, adjacent to a large country (e.g. China), and you're trying to build a local community, but end up with the server being dominated by large numbers of gamers texting in the foreign language from the large-country-next-door, what can you do. L2Devlier came up with this solution in in a long PM to me emphasized this is not about being racist, just trying to compensate for limitations in the EA queueing system if you're trying to build a local community. For other-country-applicability you'll need to read the rulz, understand what they do, and tweak the country-codes as appropriate.

Click to expand the rulz:
Spoiler



Example 18. BEST 3 PLAYERS Announcer by tarreltje

Every 100 tickets, these rulz announce the top 3 players based on kills, e.g.:
BEST 3 PLAYERS :

1st Tarreltje 1000 kills
2nd Gaga 580 kills
3rd Noob 30 kills

Please see this dedicated thread*

Example 19. SERVER STATS by tarreltje

On the first kill of each round, server will announce the player names with the highest kill counts, e.g.

DUTCH COWBOYS SERVER STATS
1st RINUSS 1000 kills
2nd BAMBAM 500 kills
3th GAGA 200 kills
Most Knives: RINUSS 3000 knives

Please see this dedicated thread*

Example 20. !punish and other TeamKill protection rulz by ty_ger

The !punish, !forgive commands you've probably seen on a variety of servers, plus optional rulz so you can automatically punish teamkillers if you prefer that for your server.

Please see this dedicated thread*

Example 21. !votekick - ingame command for players to vote to kick another player

Click to expand:
Spoiler



Example 22. Adaptive SPAMBOT by tarreltje

Easy to modify, these rulz 'chat' different messages according to the map 'Mode' that is currently running, i.e. you can have message for TeamDeathMatch, and different messages for Conquest. The same rulz could be tweaked if you want messages based on Map, rather than MapMode (i.e. some messages for Caspian, different messages for Seine Crossing...)

Please see this dedicated thread*

Example 23. Simple Aimbot headshot detector
credit russel5

These rulz count headshots and if it's more than 60% after 30 kills (these params in line 5) and it's not a sniper rifle, player is banned.
click here for rulz:
Spoiler



Versions summary:

v44 (Nov 26 2013): Support for BF4, plus the support for separate rulz .txt files (incl Linux from 44f.1 credit FritzE).On RoundOver trigger.
v43 (Aug 21 2012): Arithmetic in Set/If statements, permanent 'ini' vars, rounding, new date/time and teamsize variables, logging options. New player %score% variable, '+' as 1st character on line allows multi-line rulz.
v41 (Jun 29 2012): More flexible support for in-game admin commands e.g. !kick
v40 (May 15 2012): Quoted strings can be used in rulz e.g. Set %server_message% "Get ready for next round"
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: 15,811 + count on this version:


Please note: There is an unsupported version below ProconRulz_NL.zip which allows new lines in messages.
Example new line:
Code:
On Say;Text /show;PlayerYell \nHello %p%\nThis is your first visit, please type !rules
It should look like this on the player screen:


[ADMIN]
Hello DarthVader
This is your first visit, please type !rules

Attached Files:

* Restored post. It could be that the author is no longer active.

#4
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by RadicalMode*:

wow! good news!

it's working like a charm.
* Restored post. It could be that the author is no longer active.

#5
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by Legate*:

Good Job bambam :-)
* Restored post. It could be that the author is no longer active.

#6
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by Clay52*:

Thank you very much bambam, interesting the reference to the M320 :ohmy:

Now do we backup the BF3.def and just copy this one in or wait for the next update as referenced above? BTW I sent you a PM.

For rule writing help, if anyone knows how to write a rule for banning use of M320, though I do allow for smoke but don't think that is currently an option, and controlling spamming of RPG/SMAW I'd be grateful for your assistance, thank you.
* Restored post. It could be that the author is no longer active.

#7
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by itBurnsPatton*:

Thank You, Thank You, Thank You ! ! !
* Restored post. It could be that the author is no longer active.

#8
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

the BF3.def I included is a superset of the one shipped with Procon 1.1.1.1 so you can copy it over that one. Basically it includes a list of all the BF3 R8 weapon definitions - the key work was done by Phil (and me) and will be included in the next 'prod' release of Procon.

So install this BF3.def in your Config folder, and when the next Procon update comes along (soon) it'll get updated again and that's fine. The BF3.def is needed if you want to use 'Damage' conditions (e.g. Damage ProjectileExplosive, or Damage SniperRifle, or Damage Handgun) as opposed to single weapon conditions, and also will give weapon display names in the subst variable %w%.

If you *don't* install this BF3.def, ProconRulz will still work, but all the weapon damages will be "None" and all the weapon display names will be the same as the weapon key, as per the BF3.def shipped with Procon 1.1.1.1.
* Restored post. It could be that the author is no longer active.

#9
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

Update for ProconRulz noobies:

ProconRulz can do lots of stuff, and will become more powerful as soon as EA ship a version of BF3 that enables more weapon keys and more admin events as were in BFBC2, particularly when a player spawns. But the most common usage is for weapon limits and here's a rulz template, using SniperRifle as an example (say you want to reduce sniper use to 5 sniper kills / player):


On Kill;Damage SniperRifle;Count 7;Kick %p% ignoring sniper limit
On Kill;Damage SniperRifle;Count 5;Say %p% sniper limit;Kill 100
On Kill;Damage SniperRifle;Count 3;Say %p% sniper limit warning #%c%


The plugin will display say-text warnings above 3 sniper kills, player will get auto-killed above 5 sniper kills, and will get auto-kicked above 7 sniper kills.

If you didn't know - weapon limits in BFx are traditionally applied at SPAWN time (i.e. if you limit snipers, you kill players that SPAWN with a sniper rifle if a certain number have already spawned with one on that team). ProconRulz is designed to support this as well as the On Kill rulz, but BF3 R8 is limiting the functionality to Kill-only at the moment, hence the limited example above.
* Restored post. It could be that the author is no longer active.

#10
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by YouPilA*:

hello
I've no EA rules to read when we join our server?
Can you help me please?
* Restored post. It could be that the author is no longer active.

#11
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by MorpheusX(AUT)*:

What do EA rules (_) have to do with this plugin?
* Restored post. It could be that the author is no longer active.

#12
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by YouPilA*:

Yes there is this option
"EA Rules of conduct read and accepted" Yes/No
* Restored post. It could be that the author is no longer active.

#13
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by Clay52*:

Thanks bambam, can we have as many rules as we like, any limit? Do we necessarily want to remove any of the default rules or just add to them?
* Restored post. It could be that the author is no longer active.

#14
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

The idea is you find some EA rules of conduct on the interweb, and when you've read and digested those thoroughly, discussed them with your rabbi, and written a considered article on the relative merits of your rules with respect to the worthy guidelines in the EA conduct guidelines, then you should feel comfortable changing the checkbox in the plugin to "Yes, I've read the EA conduct guidelines". Apparently some people just change it to "Yes" without such considered reflection, but hey.

Bambam

*Edit* Clay52 the default rulz are just there as a guideline to help you write yours. Keep or discard them as you see fit. E.g. the 'say protected' rule is worth keeping so you can check a clan-members Procon admin rights, and the catch-all On Spawn and On Kill rulz do put useful logging data into your chat log which will help as you first write your rulz - just make sure YOUR rulz are higher up the list of rulz than these defaults, and they'll always take effect if their conditions trigger.

personally I'd recommend you KEEP the default teamkill limit, because BF3 has poor punishment for TK's at the moment so players are TKing just to get in a vehicle. The default rulz make 3+ teamkills suicidal. But it is completely up to you - all of the default rulz can be kept or deleted and ProconRulz works the same.

*Edit Edit* no limit on the # of rulz that I know of - our clan had 70+ with BFBC2 and the Procon cpu use was still <1%. But just take it a step at a time and be careful - use LOG actions at first. In the beginning you could create a rule that empties the server, e.g.

On Kill;Kill

For clarity, I do NOT recommend you use the On Kill;Kill rule I just wrote... ok ?
* Restored post. It could be that the author is no longer active.

#15
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by lethak*:

Hello, I get this error:

[18:30:45 33] Compiling ProconRulz.cs... Errors or Warnings
[18:30:45 33] ProconRulz.cs (Line: 2054, C: 30) CS0115: 'PRoConEvents.ProconRulz.OnLevelLoaded(string, string, int, int)'



EDIT: I had to remove the keyword "override" at line 2054, may be related to the .NET Framework used on my computer
* Restored post. It could be that the author is no longer active.

#16
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by Clay52*:

The idea is you find some EA rules of conduct on the interweb, and when you've read and digested those thoroughly, discussed them with your rabbi, and written a considered article on the relative merits of your rules with respect to the worthy guidelines in the EA conduct guidelines, then you should feel comfortable changing the checkbox in the plugin to "Yes, I've read the EA conduct guidelines". Apparently some people just change it to "Yes" without such considered reflection, but hey.

Bambam

*Edit* Clay52 the default rulz are just there as a guideline to help you write yours. Keep or discard them as you see fit. E.g. the 'say protected' rule is worth keeping so you can check a clan-members Procon admin rights, and the catch-all On Spawn and On Kill rulz do put useful logging data into your chat log which will help as you first write your rulz - just make sure YOUR rulz are higher up the list of rulz than these defaults, and they'll always take effect if their conditions trigger.

Much appreciated my friend, I'll report back my experiences.
* Restored post. It could be that the author is no longer active.

#17
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by itBurnsPatton*:

This plugin seems to keep crashing our server.

On Kill;Weapon M320;PlayerCount 1;Kick
On Kill;Weapon M320;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon RPG-7;PlayerCount 1;Kick
On Kill;Weapon RPG-7;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon SMAW;PlayerCount 1;Kick
On Kill;Weapon SMAW;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon Siaga20k;PlayerCount 1;Kick
On Kill;Weapon Siaga20k;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon USAS-12;PlayerCount 1;Kick
On Kill;Weapon USAS-12;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon DAO-12;PlayerCount 1;Kick
On Kill;Weapon DAO-12;Say %p%, %w% Not Permitted;Kill 100
On Kill;Weapon M1014;PlayerCount 1;Kick
On Kill;Weapon M1014;Say %p%, %w% Not Permitted;Kill

We have now tested it with the M320. It kills the person. Then if they do it again, it will kick them. However, on some occassions, it is also crashing the entire server when it kicks them. (It has crashed the server 3/5 times we've tried it)

UPDATE:
Tried the RPG and SMAW .. server didn't crash .. then tried the M320 a few more times, and server didn't crash.

Very strange!
* Restored post. It could be that the author is no longer active.

#18
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by Rapidorg*:

Damn lucky me.. gonna test this tonight on SQDM and TDM

Thanks again
* Restored post. It could be that the author is no longer active.

#19
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by MorpheusX(AUT)*:

Oh. This is just a check to get responsibility from bambam in case your server gets banned from EA. Depending on your settings, you could break EA's rules of conduct, and your server could get banned (although I've never seen that happen).
* Restored post. It could be that the author is no longer active.

#20
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by AJToft*:

I have some questions:

1. Is this the ruls to use if i want max 4 snipers on each team "On Spawn;Team Attack;Teamsize 12;Kit Recon 4;Say >>%p%<< Max 4 Snipers!!;Kill"?
2. The rules i want to use, do i just have to enter them in "Rules" in "Plugin Settings" as on the picProconRULZ.JPG?
* Restored post. It could be that the author is no longer active.

#21
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

@itBurnsPatton - the BF3 kick and kill commands are unchanged from BFBC2, and that bit of ProconRulz is unchanged also - the plugin sends the "admin.kill playername" command via Procon. There might be a new vulnerability in BF3 that we'll have to workaround, but I haven't seen it in the testing on our server over the past few weeks. If there's something in a log that helps, let me know. Re your rulz, be aware a player could kill TWO (or more) other players with a single SMAW rocket, so your rules will immediately kick them without them seeing the warning - you could set the 'kick' action with PlayerCount 3 maybe. Technically the rulz are 100% correct.

@AJToft - sorry the rule you want depends on BF3 sending the player KIT at spawn time, and as of BF3 R8 only the playername and team are sent during the SPAWN event so you can't have your rule. You're right that that is the kind of rule that most people will want, but BF3 won't support it. ProconRulz *will* support your rule as soon as BF3 delivers the data. Your screenshot is exactly right - click on row where it says 'Rules', a [...] button will appear on the right end of the same row, click that and the rulz will appear in an edit box. ONLY edit the rules by clicking on the [...] button and then saving.
* Restored post. It could be that the author is no longer active.

#22
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by lethak*:

The config keeps erazing to default each time the plugin is enabled/disabled,
do you have an idea ?

(seems to affect array string only)
* Restored post. It could be that the author is no longer active.

#23
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

plugin parameters are stored in the Procon\Configs\.cfg

it sounds like your PC is having problems writing to that file. Try settings for other plugins, or just try the 'EA Rules of Conduct' Yes/No setting in ProconRulz, and see if that gets saved, and we'll narrow down your issue.

edit: if your Procon install is in your 'Program Files' folder, maybe move it out of there, in case user access control is kicking in.

edit edit: if it's just the array string, make sure you oNLY click the [...] button that appears on the 'Rules' row when you click on that row, then edit the rulz within the pop-up window, and save.

Bambam
* Restored post. It could be that the author is no longer active.

#24
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by lethak*:

- I am running Procon as admin
- Not installed in Program Files, not even C:
- Boolean values are stored
- Strings are reset
* Restored post. It could be that the author is no longer active.

#25
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

are you clicking on the [...] button to edit the string array? (Don't hit the [+] and try and edit the item on the expanded list directly) see attached

Attached Files:

* Restored post. It could be that the author is no longer active.

#26
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by lethak*:

It is working using this way, I am sorry, first time using pluggin options :ohmy:

Thx for your help (and the time you spent on this plugin)
* Restored post. It could be that the author is no longer active.

#27
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

cool - I'm pleased you fixed it. The Plugin UI for string array edits IS confusing IMHO...

Bambam
* Restored post. It could be that the author is no longer active.

#28
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by AJToft*:

I cant get this rule to work: On Kill;Damage ProjectileExplosive;Say No Rocket vs infantry;Kick
* Restored post. It could be that the author is no longer active.

#29
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by bambam*:

You're not clear whether you see the 'Say' messages, so you know the rule is working (but the kick isn't) or whether you don't see the Say message, which would mean the rule isn't firing when you expect it to.

if you don't see the 'Say' messages, change it to

On Kill;Damage ProjectileExplosive;Log Rocket nade kill !! %p% killed %v% with %w%, damage %d%
On Kill;Log %p% killed %v% with %w%, damage %d%

and look in the Procon chat window as the log messages come by and see what it says.

Note that 'protected' players will not be kicked (i.e. admins)
* Restored post. It could be that the author is no longer active.

#30
ImportBot

ImportBot

    Advanced Member

  • Friendly Neighborhood Bot
  • 52428 posts
Originally Posted by AJToft*:

You're not clear whether you see the 'Say' messages, so you know the rule is working (but the kick isn't) or whether you don't see the Say message, which would mean the rule isn't firing when you expect it to.

if you don't see the 'Say' messages, change it to

On Kill;Damage ProjectileExplosive;Log Rocket nade kill !! %p% killed %v% with %w%, damage %d%
On Kill;Log %p% killed %v% with %w%, damage %d%

and look in the Procon chat window as the log messages come by and see what it says.

Note that 'protected' players will not be kicked (i.e. admins)

Still not working :sad:
* Restored post. It could be that the author is no longer active.



Also tagged with one or more of these keywords: BF4, BF3, BC2, MOH

5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users