JasonTM

You need to have the string table on the root of your mission file. https://github.com/oiad/communityLocalizations

ExecVM format["\z\addons\dayz_server\WAI\static\%1.sqf",(["sector","sector2","sector3"] call BIS_fnc_selectRandom)];

I don't think those particle definitions work in Arma 2. A2 uses the universal particle effects. The way to accomplish a moving tornado would be to spawn an AI with the invisible skin and attach your particle source to the AI. Have the AI move through the list of waypoints. You would need a fail-safe like a timer in case the AI's movement was blocked by something.

If you comment out the line then you are disabling that feature of the anticheat. I put that in there on purpose because Epoch Admin Tools is based on commanding menus. You need to read what the kicks say. The kicks are for additional commanding menus on that mod. Add them to the array like the other one. Like this: #define MENUS ["","RscTeam","RscMainMenu","RscGroupRootMenu"] Look through the files for that mod and see if there are any other commanding menus to white list. Testing should not be done on a live server if possible.

What does the server rpt say?

I just changed the file so you can whitelist commanding menus. Download the new antiCheat.sqf and add your commanding menu to the array here: https://github.com/worldwidesorrow/Epoch-Admin-Tools/blob/TestBranch/AdminTools/AntiCheat/antiCheat.sqf#L3 So your line should look like this: #define MENUS ["","RscTeam"]

Are you referring to the status icons in the lower right of the screen? The admin tools shouldn't disable those. They can be toggled off and on with the F3 key in game.

The debug monitors are in the same folder: https://github.com/worldwidesorrow/Epoch-Admin-Tools/tree/TestBranch/AdminTools/DebugMonitors You just have to modify the line so that it references the other file. So instead of: #include "\z\addons\dayz_server\adminTools\DebugMonitors\debugMonitor2.sqf" you have: #include "\z\addons\dayz_server\adminTools\DebugMonitors\debugMonitor.sqf"

For regular players, the debug is loaded at the bottom of the anticheat here: https://github.com/worldwidesorrow/Epoch-Admin-Tools/blob/TestBranch/AdminTools/AntiCheat/antiCheat.sqf#L99 For admins/mods it is loaded near the bottom of the activate.sqf file here: https://github.com/worldwidesorrow/Epoch-Admin-Tools/blob/TestBranch/AdminTools/Admin/activate.sqf#L51 You can comment out the lines to disable the debug or change the file name to use the old style debug monitor.

The mission file is defined here: https://github.com/EpochModTeam/DayZ-Epoch/blob/master/Server Files/DZE_Server_Config/11_chernarus.cfg#L36 It doesn't sound like the server is set up correctly. At the top of your server rpt, there should be an entry like this. It will show you what is being loaded. == C:\path\arma2oaserver.exe -port=2302 "-config=C:\DZE_Server_Config\2_chernarus_winter.cfg" "-cfg=C:\DZE_Server_Config\basic.cfg" "-profiles=C:\DZE_Server_Config" -name=server "[email protected]_Epoch;@DayZ_Epoch_Server;"

Those mod names don't sound correct. Check the names of the mods you have in your Arma 2 OA directory. It should be more like @panthera; @DayzOverwatch; @DayZ_Epoch; By default, I think that DayZ Launcher sets the directory as the my documents folder but that should be changed in settings and the files moved to the Arma 2 OA directory.

The missing addon name is in your rpt. There should be an entry like "cannot play this mission due to missing addon..."

Turn this parameter to true: https://github.com/worldwidesorrow/WICKED-AI/blob/master/WAI/missions/MISSION_EXAMPLE.sqf#L126

Public Variable PVDZE_obj_Publish no longer exists in DayZ Epoch. What version of DayZ Epoch are you using? Did you place that metal floor with the admin tools or the Epoch build system? What version of admin tools are you using?

That error message means you have a bad weapon classname. You don't need to add the Overwatch weapons. They are already loaded from this file. https://github.com/worldwidesorrow/WICKED-AI/blob/master/WAI/configs/overwatch.sqf