We will stop checking after 3 days or when the native ban would have expired on its own. If a BattleMetrics permanent ban is removed or a BattleMetrics temporary ban is removed before it expires, we will check every 3 hours to ensure the native ban is removed. Only Arma and Rust provide the information necessary for this check. When a connection from a player is rejected.When the associated BattleMetrics ban is updated or removed.
We'll also check on the following events:
#Arma 3 sync more than 10 max connections update
The regular update interval will choose the nearest time based on the conditions below. We only reissue a native ban if a banned player attempts to join again and our internal database kicks them. However, we do not blindly reissue bans that should be added. If we are unable to check if a ban is currently in the server's ban list then we will issue removal commands multiple times.
If the game supports the ability to view bans we will verify that bans that should be present are present and bans that should be removed have been removed. The system will check the above criteria at regular intervals as well as on certain triggering events. The Ban Sync system is designed to ensure that bans we have issued are: This is a common problem with ArmA servers. Setting a max duration decreases the chance that a ban could become "stuck" in a game's ban system if we are unable to remove it. If the game does not support temporary bans then this setting will have no effect. After a native ban expires we will add it again if the ban is still valid, and the TTL has not been exceeded. Native Max Duration allows you to set the maximum duration/expiration that we will use when adding native bans. If a player rejoins the server after the native ban has been removed, we will kick them based on the ban in our internal database and issue a native ban again, restarting the TTL counter. Once the TTL is exceeded we will remove the ban from the native ban list. We recommend that you keep the TTL value under 30 days. Many games have issues with large native ban lists. Time To Live (TTL) is the maximum amount of time a ban is allowed to stay on a native ban list. We add bans to all servers in case the player attempts to join another one of your servers. When the ban is added to our system orĪ native ban is added to all servers that the ban applies to.If you do not have BattleMetrics bans on a ban list you may use the "Import" option when editing a ban list, which will move bans that are not already on a list to that list. Bans added to a list will use the list's default setting unless you specifically enable or disable it on the ban. You may also set "enabled" or "disabled" as a default setting for a given ban list. A large ban list can cause issues when attempting to add, remove, and verify bans.īan Sync can be enabled or disabled for an individual ban. We recommend that you clear your server's native ban list before using Ban Sync. A few seconds after adding a ban we will recheck that it was successfully added and in the correct state whenever possible.
If you enable Ban Sync then we will also add a native ban after kicking them. The normal BattleMetrics ban system will continue to kick players that are on your ban list. It only keeps bans issued through the BattleMetrics ban system synchronized.
#Arma 3 sync more than 10 max connections full
This allows you to utilize our full feature set even if the game's ban system is limited.īan Sync does not import bans that have already been added to the server's native ban list. Ban Sync is designed to augment the BattleMetrics ban system, not replace it. It will automatically handle adding, removing, and updating bans. Ban Sync pushes your BattleMetrics bans to your server's native (game-level) ban system.
0 kommentar(er)
