extDB2 New Rcon Features

extDB2 New Rcon Features

« posted: May 17, 2015, 10:26 PM »
Just aheads up for those more comfortable with scripting.

Once extDB2 Rcon has been started i.e 9:START_RCON  (you don't need RCon Protocol).

extDB2 has the ability to kick players for bad playernames
Configurable based on extdb-conf.ini settings, char/string/regex match

extDB2 also has whitelisting / reserved slots
Whitelisted BEGuids are either set in extdb-conf.ini or you can configure a setting to run SQL Query that returns 1 or 0.
  • Offline LouD
  • Silent but deadly ;)
  • Moderator
  • Veteran
  • ******
  • Posts: 1415

Re: extDB2 New Rcon Features

« Reply #1 posted: May 18, 2015, 07:13 AM »
Cool, nice features! How would the reserved slots work? Same like BEC? Players get kicked if normal slots are filled?

Re: extDB2 New Rcon Features

« Reply #2 posted: May 18, 2015, 07:40 AM »
This is great news for Linux server admins.

Re: extDB2 New Rcon Features

« Reply #3 posted: May 18, 2015, 01:22 PM »
Btw i have never used BEC  ???

----------

It should work very similar


If server player count > public open slots.
If player joins != whitelisted, player will be kicked from server with a custom kick message.


Note will be small update later today to fix a small issue.

It was counting
Non-Whitelisted Players > public open slots
Instead of
Total players > public open slots

---------------
  • Offline LouD
  • Silent but deadly ;)
  • Moderator
  • Veteran
  • ******
  • Posts: 1415

Re: extDB2 New Rcon Features

« Reply #4 posted: May 18, 2015, 02:50 PM »
Imho kicking someone from your server when public slots are reached is the most player unfriendly thing you can do. It's the main reason why I never used it in BEC. I was hoping extDB did it in a 'nicer' way like giving a popup saying public slot limit reached when clicking on the server in the browser. But that probably isn't even possible.
  • Offline CREAMPIE
  • Armaholic
  • Veteran
  • ******
  • Posts: 1085
  • ^_^;;

Re: extDB2 New Rcon Features

« Reply #5 posted: May 18, 2015, 03:34 PM »
Imho kicking someone from your server when public slots are reached is the most player unfriendly thing you can do. It's the main reason why I never used it in BEC. I was hoping extDB did it in a 'nicer' way like giving a popup saying public slot limit reached when clicking on the server in the browser. But that probably isn't even possible.


you could always just whitelist 2 slots on each team for admins using GUIDs ?

- from the grassy knoll -
  • Offline LouD
  • Silent but deadly ;)
  • Moderator
  • Veteran
  • ******
  • Posts: 1415

Re: extDB2 New Rcon Features

« Reply #6 posted: May 18, 2015, 03:40 PM »

you could always just whitelist 2 slots on each team for admins using GUIDs ?
Still doesn't help if your server is full :)
  • Offline CREAMPIE
  • Armaholic
  • Veteran
  • ******
  • Posts: 1085
  • ^_^;;

Re: extDB2 New Rcon Features

« Reply #7 posted: May 18, 2015, 03:46 PM »
Still doesn't help if your server is full :)

Well the whitelisted slots will help , as only the players allowed to join those slots can join on them :P

So you keep 64 player server , have 6 free (whitelisted slots ) for yourself or admins only.

easy to do ^_^

- from the grassy knoll -
  • Offline LouD
  • Silent but deadly ;)
  • Moderator
  • Veteran
  • ******
  • Posts: 1415

Re: extDB2 New Rcon Features

« Reply #8 posted: May 18, 2015, 03:48 PM »
Well the whitelisted slots will help , as only the players allowed to join those slots can join on them :P

So you keep 64 player server , have 6 free (whitelisted slots ) for yourself or admins only.

easy to do ^_^
Which means you have to modify the standard amount of player slots :)

Re: extDB2 New Rcon Features

« Reply #9 posted: May 18, 2015, 04:26 PM »
@Loud
No idea what you expect.
extDB2 is limited to Rcon Protocol, if you want proper reserved slots all nice + user friendly.
Bug BIS to implement it into the game engine, assuming they can implement since they are using Steam Server Listings.

------------------------------

The nicest way currently todo Whitelisting in Arma currently is

Custom Dialogs + Rcon code serverside to kick the player off the server after a set amount of time (to prevent hackers getting around the Custom Dialogs).
This has been possible to implement since start of Feb.


------------------------------

Lastly
Quote
popup saying public slot limit reached when clicking on the server in the browser

extDB2 is serverside extension only, it has zero control over the client.
Like i said bug BIS

Re: extDB2 New Rcon Features

« Reply #10 posted: Jul 05, 2015, 03:31 PM »
Where should I put the code "9:START_RCON" to enable the RCON feature?

Re: extDB2 New Rcon Features

« Reply #11 posted: Jul 07, 2015, 06:54 PM »
Thanks Rev for adding support to this feature in v1.2_beta.

@torndeco: Could you tell what exactly do I need to edit in extdb-conf.ini in order to put the bad player name and reserved slots features into practical use? The comments provided in the file is a bit vague.

For example, I want to kick player with blank names and keep 4 reserved slots out of 80 total slots. How should config those settings?
  • Offline AgentRev
  • Developer
  • Veteran
  • ******
  • Posts: 2593

Re: extDB2 New Rcon Features

« Reply #12 posted: Jul 07, 2015, 07:30 PM »
Thanks Rev for adding support to this feature in v1.2_beta.

torndeco did, not me

Re: extDB2 New Rcon Features

« Reply #13 posted: Jul 07, 2015, 07:35 PM »
Oops, my bad then. I just fetched and merged. Didn't checked every commit.