Jump to content

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


ColColonCleaner

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

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

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:

  Reveal hidden contents

 

 

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:

  Reveal hidden contents

 

 

 

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

Click to expand:

  Reveal hidden contents

 

 

 

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

Click to expand:

  Reveal hidden contents

 

 

 

Example 4. Make teamkills suicidal

Click to expand:

  Reveal hidden contents

 

 

 

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

Click to expand:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

Example 7. Kill Streak Announcer

 

by ty_ger07.

 

Please see this dedicated thread*

 

Example 8. Basic Cheater Detector

Click to expand:

  Reveal hidden contents

 

 

 

Example 9. Limit vehicle use when teams are small

Click to expand:

  Reveal hidden contents

 

 

 

Example 10. Easy in-game admin

Click to expand:

  Reveal hidden contents

 

 

 

Example 11. No MAV's on Metro

Click to expand:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

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

Click to expand:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

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:

  Reveal hidden contents

 

 

 

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:

proconrulz_documentation.pdfFetching info...

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

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.
Link to comment

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.
Link to comment

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.
Link to comment

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

 

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.
Link to comment

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.
Link to comment

Originally Posted by Clay52*:

 

  bambam* said:

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.
Link to comment

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.
Link to comment

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.
Link to comment

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.
Link to comment

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.
Link to comment

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.
Link to comment

Originally Posted by AJToft*:

 

  bambam* said:

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.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




  • Our picks

    • Game Server Hosting:

      We're happy to announce that EZRCON will branch out into the game server provider scene. This is a big step for us so please having patience if something doesn't go right in this area. Now, what makes us different compared to other providers? Well, we're going with the idea of having a scaleable server hosting and providing more control in how you set up your server. For example, in Minecraft, you have the ability to control how many CPU cores you wish your server to have access to, how much RAM you want to use, how much disk space you want to use. This type of control can't be offered in a single service package so you're able to configure a custom package the way you want it.

      You can see all the available games here. Currently, we have the following games available.

      Valheim (From $1.50 USD)


      Rust (From $3.20 USD)


      Minecraft (Basic) (From $4.00 USD)


      Call of Duty 4X (From $7.00 USD)


      OpenTTD (From $4.00 USD)


      Squad (From $9.00 USD)


      Insurgency: Sandstorm (From $6.40 USD)


      Changes to US-East:

      Starting in January 2022, we will be moving to a different provider that has better support, better infrastructure, and better connectivity. We've noticed that the connection/routes to this location are not ideal and it's been hard getting support to correct this. Our contract for our two servers ends in March/April respectively. If you currently have servers in this location you will be migrated over to the new provider. We'll have more details when the time comes closer to January. The new location for this change will be based out of Atlanta, GA. If you have any questions/concerns please open a ticket and we'll do our best to answer them.
      • 5 replies
    • Hello All,

      I wanted to give an update to how EZRCON is doing. As of today we have 56 active customers using the services offered. I'm glad its doing so well and it hasn't been 1 year yet. To those that have services with EZRCON, I hope the service is doing well and if not please let us know so that we can improve it where possible. We've done quite a few changes behind the scenes to improve the performance hopefully. 

      We'll be launching a new location for hosting procon layers in either Los Angeles, USA or Chicago, IL. Still being decided on where the placement should be but these two locations are not set in stone yet. We would like to get feedback on where we should have a new location for hosting the Procon Layers, which you can do by replying to this topic. A poll will be created where people can vote on which location they would like to see.

      We're also looking for some suggestions on what else you would like to see for hosting provider options. So please let us know your thoughts on this matter.
      • 4 replies
    • Added ability to disable the new API check for player country info


      Updated GeoIP database file


      Removed usage sending stats


      Added EZRCON ad banner



      If you are upgrading then you may need to add these two lines to your existing installation in the file procon.cfg. To enable these options just change False to True.

      procon.private.options.UseGeoIpFileOnly False
      procon.private.options.BlockRssFeedNews False



       
      • 2 replies
    • I wanted I let you know that I am starting to build out the foundation for the hosting services that I talked about here. The pricing model I was originally going for wasn't going to be suitable for how I want to build it. So instead I decided to offer each service as it's own product instead of a package deal. In the future, hopefully, I will be able to do this and offer discounts to those that choose it.

      Here is how the pricing is laid out for each service as well as information about each. This is as of 7/12/2020.

      Single MySQL database (up to 30 GB) is $10 USD per month.



      If you go over the 30 GB usage for the database then each additional gigabyte is charged at $0.10 USD each billing cycle. If you're under 30GB you don't need to worry about this.


      Databases are replicated across 3 zones (regions) for redundancy. One (1) on the east coast of the USA, One (1) in Frankfurt, and One (1) in Singapore. Depending on the demand, this would grow to more regions.


      Databases will also be backed up daily and retained for 7 days.




      Procon Layer will be $2 USD per month.


      Each layer will only allow one (1) game server connection. The reason behind this is for performance.


      Each layer will also come with all available plugins installed by default. This is to help facilitate faster deployments and get you up and running quickly.


      Each layer will automatically restart if Procon crashes. 


      Each layer will also automatically restart daily at midnight to make sure it stays in tip-top shape.


      Custom plugins can be installed by submitting a support ticket.




      Battlefield Admin Control Panel (BFACP) will be $5 USD per month


      As I am still working on building version 3 of the software, I will be installing the last version I did. Once I complete version 3 it will automatically be upgraded for you.





      All these services will be managed by me so you don't have to worry about the technical side of things to get up and going.

      If you would like to see how much it would cost for the services, I made a calculator that you can use. It can be found here https://ezrcon.com/calculator.html

       
      • 11 replies
    • I have pushed out a new minor release which updates the geodata pull (flags in the playerlisting). This should be way more accurate now. As always, please let me know if any problems show up.

       
      • 9 replies
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.