Epoch AH , bans.. any details on what for ??

[Chainsaw Squirrel]

I have quite a few people getting banned.. just sez banned in bans log for be.. is there a detailed log somewhere that sez what they were banned for >? 

Worried that more than normal are getting banned for no real reason.. I don't want to just log .. and not ban.. but also would like to get more traffic .. not hakerz or skipt kiddies .. but Im beginning to wonder.. dont have the cash right now for infrastr .. I have a a2 version lol .. dont think chris will let me switch fer free lol .. 

[Richie]

If you look inside the database with Redis Desktop Manager or something similar you'll see the ban reason, they're stored in 'AHB-log'

[Chainsaw Squirrel]

Ahh Thank you kind and brilliant one .. the meek humbly bow at your feet  .. need to add that kind of stuff to the server readme :)

 

[Chainsaw Squirrel]

If you look inside the database with Redis Desktop Manager or something similar you'll see the ban reason, they're stored in 'AHB-log'

Dont see a value for that in Redis Desktop manager .. do you happen to know what section its under .

Edited October 3, 2015 by Chainsaw Squirrel

[Ghostrider-GRG]

I have been getting these pretty often, about every 3 times I boot up a test server with vanilla Epoch 0.3.5.0, as well as modded files. Each time the Redis AH logs show:

Changed RscDisplayMainMap >> onLoad >> ["onLoad",_this,"RscDiary",'MpMarkDisplays'] call (uinamespace getvariable 'BIS_fnc_initDisplay')

My epochah.hpp:

antihack_Enabled = true; // built-in Anti-Hack
antihack_cfgPatchesCheck = false; // cfgPatches (AddOn Check)
antihack_PVSPrefix = "EPAH_"; // used to help whitelist pveh variables in BE without BEC and watchdog, leave blank to use no prefix.
antihack_cfgPatchesCfg[] = {1}; // 0 == BAN - 1 = LOG
antihack_ahInitAuthCfg[] = {1,180}; // 0 == BAN - 1 = LOG, 60 = ban or log if anti hack is not started in 90 seconds
antihack_whitelistedCfgPatches[] = {"...

//whitelisted cfgPatches for AiA TP
antihack_InvOpenCheck[] = {}; // blank array disables, enable with {6} distance in meters disallows gear access if another player is within this range also disables gear access in vehicles.
antihack_banReason = "EpochMod.com Autoban";
antihack_checkFiles[] = { //script check, leave it blank to disable it
    {"\x\addons\a3_epoch_code\compile\setup\EPOCH_clientInit.sqf", "EPOCH_clientInit"},
    {"\x\addons\a3_epoch_code\compile\EPOCH_onEachFrame.sqf", "EPOCH_onEachFrame"},
    {"\x\addons\a3_epoch_code\compile\setup\EPOCH_masterLoop.sqf", "EPOCH_masterLoop"},
    {"\x\addons\a3_epoch_code\compile\setup\EPOCH_client_rejectPlayer.sqf", "EPOCH_client_rejectPlayer"},
    {"\x\addons\a3_epoch_code\compile\setup\EPOCH_clientRespawn.sqf", "EPOCH_clientRespawn"},
    {"\x\addons\a3_epoch_code\compile\interface_event_handlers\EPOCH_KeyDown.sqf", "EPOCH_KeyDown"}
};
antihack_addActionCheck = false; // false to disable addAction checks
antihack_customVariablesCheck = false; // true enables variable scanning on missionNamespace
antihack_customVariables[] = {}; //Add global variables from custom scripts, example: {"MyOwnVar","CP_KK"} //Global Variables begin without "_" !!
antihack_customVariablesCheckMode = 0; // 0 = Ban, 1 = Log, 2 == learning mode (only enable with trusted players in a passwored server to profile your variables keep disabled for normal operation)

EDIT: RESOLVED

It appears I had not updated all files on my test server so that there was a minor missmatch between server and client. I presume this was the cause of the AH bans.

Edited November 24, 2015 by Ghostrider-DbD-
[RESOLVED]