Airwaves Man

Hello everyone,
 
Here is the public release of my Antihack / Admin tools. Both myself and Movinggun put a lot of work into this, so I hope you all can benefit. The culmination of my time spent on this game went into this, and I hope you all enjoy it just as much as I did.
Unfortunately due to time, I will not be able to actively add to this project, but I will always be around to approve pull requests. This project can easily live on through the community, and I hope you all the enjoy the complexity of everything involved with it.
 
The repository that contains install instructions can be found here:
https://github.com/BigEgg17/Epoch-Antihack-Admin-Tools
 
I will add source code for the DLL as soon as it is received from Movinggun, along with the source for the executable file.
I will also create an official release on the Github as soon as everything is successfully converted for compatibility with 1.0.7.
 
Best wishes to the community, I look forward to applying all changes desired, and to answering any questions members may have.
 
It's been a blast and I will never forget some of the memories and friends made on this game.
 
- BigEgg

Epoch 1.0.7 Pre-Release with signed pbos and the needed server key is ready. This will be in test until the 15th of April. If nothing bigger occurs we will release the final version on the same day.

Epoch 1.0.7 Pre-Release with signed pbos and the needed server key is ready. This will be in test until the 15th of April. If nothing bigger occurs we will release the final version on the same day.

Guys, RC4 is up and should be the last RC before the release. If everything goes as planned we should be ready in about 4 weeks.
https://github.com/EpochModTeam/DayZ-Epoch/issues/2117
 

Guys, RC4 is up and should be the last RC before the release. If everything goes as planned we should be ready in about 4 weeks.
https://github.com/EpochModTeam/DayZ-Epoch/issues/2117
 

RC2 released, mainpost updated.

Ladies and Gentlemen, this is the Epoch 1.0.7 Pre-Release with signed pbos and the needed server key. This will be in test until the 15th of April to make sure everything works correctly.
Joining with the DayZ Launcher
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Client Files from google drive: https://drive.google.com/drive/folders/1Xx0wq8QJFG4AqeXquxMQADm8y73FYeYO If you have finished the download, unpack the Epoch 1.0.7 Client Files. You need at least 7,4 GB of disk space. Go into the folder where you have installed all your of Arma 2 OA DayZ mods. It depends on where the DayZ Launcher has set the path. Once you found the folder with your mods rename @DayZ_Epoch to @DayZ_Epoch_old. Copy and paste the downloaded and unpacked folder from 3. into the mods folder where you have renamed the Epoch Mod. Keep in mind you need at least 7,4 GB of disk space. There should be a folder with the name @DayZ_Epoch_old and @DayZ_Epoch now. Click on @DayZ_Epoch and check if there is a sub folder called addons. @DayZ_Epoch\addons. If there is another folder called @DayZ_Epoch copy everything from this folder into the root folder called @DayZ_Epoch. So it looks like: that @DayZ_Epoch\addons and not: @DayZ_Epoch@DayZ_Epoch\addons. You are ready to join an Epoch 1.0.7 Server now. Open the DayZ Launcher and join 94.130.68.169 - Offical DayZ Epoch 1.0.7 Pre-Release Version You will get a message that Epoch needs validating/updating. Click ok and ignore it. You can join the Test Server now. If you want to join any other Epoch non 1.0.7 server, just rename @DayZ_Epoch_old back to @DayZ_Epoch For Server Admins: You have to update to the new server files that coming with this Pre-Release update.
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Server Files from google drive: https://drive.google.com/drive/folders/1gHNE4VBCeYXi0P_hosAI8k-49v15WNdr Take the DayZEpoch107.bikey from the Server Files keys folder and put them into your server keys folder. Also set verifySignatures = 2; in your config.cfg to activate the signatures check. How to test:
Do not use any third party scripts or tools. Do not use infistar as an admin tool. Use this testkit: https://github.com/worldwidesorrow/TestKit Enable -showscripterrors in the DayZ Launcher and never ever use -nologs for testing. If you have bugs and problems on testing always provide logs. Server(if you are the admin) and Client Logs. You can find the Client Logs under C:\Users\YourUsername\AppData\Local\ArmA 2 OA It is possbile that the folder is hidden in windows. You can make it visible: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10 Do not post the logs directly, use pastebin.com, google drive, or something like that and add the link. Report all bugs under this topic.

Yes you can use. Thats why I have add it here so everyone can take a look at it and can use if they want.

It is a very complicated way to realize this script. The main point why it is so hard, is because the item like the food and all magazines and weapons a player can take in-game are just items and no objects. So you cannot set a variable on a single object like you can do it on a building, a vechicle or a player. To work around you have to set a variable on the player which saves what the player does and when with the items. Plus you have to save the state of the variables to the database.
From my point of view it is not worth the effort and the performace impact that this script would have for only this small feature. You could add the backpack checking to the script above but the rest I would skip.

https://epochmod.com/forum/topic/47182-epoch-107-beta-rc1/

I like the idea of the script. You have asked why nobody else has made a script like that already, well it is because this is a way more complicated as you perhaps think at the moment. First of all you are new to coding so you can acutally not know most of the things so do not worry about it.
Your script has a few problems:
1. The script runs for the server too. It is not really a problem for the script itself but if you run things for clients only use.
if (!isDedicated) then { code }; 2. It only runs one time. A while loop would be required so the script can check the whole time the player is playing.
3. If one condition is true, lets say the first one, the script will wait 900s and will remove after that 'FoodBaconRaw'. But it does not check when the player got this item or the player even still have it. After removing the item it will add the biomeat no matter if the player really had the removed item. A few thoughts about that to make it more clear:
The player could have cooked the 'FoodBaconRaw' within the 900s. If the player gets a new 'FoodBaconRaw' within the 900s the script will remove it even it was in the player inventory only a few seconds. 4. The script will always remove only 1 item. If you have 2x 'FoodBaconRaw' only one gets removed.
5. If you relog everything gets resetted, the same if you died and you take back your gear. If you have died and took back your gear, it will only work after a relog because of the missing while loop.
6. Because of the high sleeps you are using the most parts of the script will never be checked. It just takes too long even if you would have added a while loop.
7. Some classnames are written wrong like FoodRawTuna is FishRawTuna.
To realize this script idea it will need a few variables and a complete different way to script it. I would call it expert level. Those are the key features you have to think about:
When has the player add the item to the inventory and how many items. How to handle the removal to the items if one or more got removed already by another action. How to handle if a new item of the same type got added within the time the other items will spoil. If a player relogs or getting killed. What about if the meat is inside the backpack. Do not use sleep with those high numbers. Use diag_tickTime instead. I've wrote a small script how it works better. But it still does not check the followong things:
Backpack Time when the player got the items Relog and death // Set the spoil time at the start of the script. local _spoilTickTime = diag_tickTime; // Nested array of items that spoil within the inventory. [Spoilt item, New item]. local _spoilItems = [["FoodBaconRaw","FoodBioMeat"],["FishRawTuna","FoodBioMeat"]]; // spoil time in mins local _spoilTime = 15; while {1==1} do { // Every default: 15mins the items spoil in the inventory. if ((diag_tickTime - _spoilTickTime) > (_spoilTime*60)) then { { local _item = _x select 0; // Make sure that the player has acutally the item that spoils in their inventroy. if (_item in magazines player) then { local _newItem = _x select 1; // Count the items that will spoil now to get them all. _qtyItems = {_x == _item} count magazines player; for "_i" from 1 to _qtyItems do { player removeMagazine _item; player addMagazine _newItem; }; // Get display text of the spoilt items and inform the player. _displayName = getText(configFile >> "CfgMagazines" >> _item >> "displayname"); systemchat format ["%1 %2 spoiled in your inventory.",_qtyItems,_displayName]; }; } foreach _spoilItems; // Reset the spoil time of the script. _spoilTickTime = diag_tickTime; }; uisleep 5; };  

Ladies and Gentlemen, this is the Epoch 1.0.7 Pre-Release with signed pbos and the needed server key. This will be in test until the 15th of April to make sure everything works correctly.
Joining with the DayZ Launcher
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Client Files from google drive: https://drive.google.com/drive/folders/1Xx0wq8QJFG4AqeXquxMQADm8y73FYeYO If you have finished the download, unpack the Epoch 1.0.7 Client Files. You need at least 7,4 GB of disk space. Go into the folder where you have installed all your of Arma 2 OA DayZ mods. It depends on where the DayZ Launcher has set the path. Once you found the folder with your mods rename @DayZ_Epoch to @DayZ_Epoch_old. Copy and paste the downloaded and unpacked folder from 3. into the mods folder where you have renamed the Epoch Mod. Keep in mind you need at least 7,4 GB of disk space. There should be a folder with the name @DayZ_Epoch_old and @DayZ_Epoch now. Click on @DayZ_Epoch and check if there is a sub folder called addons. @DayZ_Epoch\addons. If there is another folder called @DayZ_Epoch copy everything from this folder into the root folder called @DayZ_Epoch. So it looks like: that @DayZ_Epoch\addons and not: @DayZ_Epoch@DayZ_Epoch\addons. You are ready to join an Epoch 1.0.7 Server now. Open the DayZ Launcher and join 94.130.68.169 - Offical DayZ Epoch 1.0.7 Pre-Release Version You will get a message that Epoch needs validating/updating. Click ok and ignore it. You can join the Test Server now. If you want to join any other Epoch non 1.0.7 server, just rename @DayZ_Epoch_old back to @DayZ_Epoch For Server Admins: You have to update to the new server files that coming with this Pre-Release update.
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Server Files from google drive: https://drive.google.com/drive/folders/1gHNE4VBCeYXi0P_hosAI8k-49v15WNdr Take the DayZEpoch107.bikey from the Server Files keys folder and put them into your server keys folder. Also set verifySignatures = 2; in your config.cfg to activate the signatures check. How to test:
Do not use any third party scripts or tools. Do not use infistar as an admin tool. Use this testkit: https://github.com/worldwidesorrow/TestKit Enable -showscripterrors in the DayZ Launcher and never ever use -nologs for testing. If you have bugs and problems on testing always provide logs. Server(if you are the admin) and Client Logs. You can find the Client Logs under C:\Users\YourUsername\AppData\Local\ArmA 2 OA It is possbile that the folder is hidden in windows. You can make it visible: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10 Do not post the logs directly, use pastebin.com, google drive, or something like that and add the link. Report all bugs under this topic.

Ladies and Gentlemen, this is the Epoch 1.0.7 Pre-Release with signed pbos and the needed server key. This will be in test until the 15th of April to make sure everything works correctly.
Joining with the DayZ Launcher
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Client Files from google drive: https://drive.google.com/drive/folders/1Xx0wq8QJFG4AqeXquxMQADm8y73FYeYO If you have finished the download, unpack the Epoch 1.0.7 Client Files. You need at least 7,4 GB of disk space. Go into the folder where you have installed all your of Arma 2 OA DayZ mods. It depends on where the DayZ Launcher has set the path. Once you found the folder with your mods rename @DayZ_Epoch to @DayZ_Epoch_old. Copy and paste the downloaded and unpacked folder from 3. into the mods folder where you have renamed the Epoch Mod. Keep in mind you need at least 7,4 GB of disk space. There should be a folder with the name @DayZ_Epoch_old and @DayZ_Epoch now. Click on @DayZ_Epoch and check if there is a sub folder called addons. @DayZ_Epoch\addons. If there is another folder called @DayZ_Epoch copy everything from this folder into the root folder called @DayZ_Epoch. So it looks like: that @DayZ_Epoch\addons and not: @DayZ_Epoch@DayZ_Epoch\addons. You are ready to join an Epoch 1.0.7 Server now. Open the DayZ Launcher and join 94.130.68.169 - Offical DayZ Epoch 1.0.7 Pre-Release Version You will get a message that Epoch needs validating/updating. Click ok and ignore it. You can join the Test Server now. If you want to join any other Epoch non 1.0.7 server, just rename @DayZ_Epoch_old back to @DayZ_Epoch For Server Admins: You have to update to the new server files that coming with this Pre-Release update.
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Server Files from google drive: https://drive.google.com/drive/folders/1gHNE4VBCeYXi0P_hosAI8k-49v15WNdr Take the DayZEpoch107.bikey from the Server Files keys folder and put them into your server keys folder. Also set verifySignatures = 2; in your config.cfg to activate the signatures check. How to test:
Do not use any third party scripts or tools. Do not use infistar as an admin tool. Use this testkit: https://github.com/worldwidesorrow/TestKit Enable -showscripterrors in the DayZ Launcher and never ever use -nologs for testing. If you have bugs and problems on testing always provide logs. Server(if you are the admin) and Client Logs. You can find the Client Logs under C:\Users\YourUsername\AppData\Local\ArmA 2 OA It is possbile that the folder is hidden in windows. You can make it visible: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10 Do not post the logs directly, use pastebin.com, google drive, or something like that and add the link. Report all bugs under this topic.

Ladies and Gentlemen, this is the Epoch 1.0.7 Pre-Release with signed pbos and the needed server key. This will be in test until the 15th of April to make sure everything works correctly.
Joining with the DayZ Launcher
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Client Files from google drive: https://drive.google.com/drive/folders/1Xx0wq8QJFG4AqeXquxMQADm8y73FYeYO If you have finished the download, unpack the Epoch 1.0.7 Client Files. You need at least 7,4 GB of disk space. Go into the folder where you have installed all your of Arma 2 OA DayZ mods. It depends on where the DayZ Launcher has set the path. Once you found the folder with your mods rename @DayZ_Epoch to @DayZ_Epoch_old. Copy and paste the downloaded and unpacked folder from 3. into the mods folder where you have renamed the Epoch Mod. Keep in mind you need at least 7,4 GB of disk space. There should be a folder with the name @DayZ_Epoch_old and @DayZ_Epoch now. Click on @DayZ_Epoch and check if there is a sub folder called addons. @DayZ_Epoch\addons. If there is another folder called @DayZ_Epoch copy everything from this folder into the root folder called @DayZ_Epoch. So it looks like: that @DayZ_Epoch\addons and not: @DayZ_Epoch@DayZ_Epoch\addons. You are ready to join an Epoch 1.0.7 Server now. Open the DayZ Launcher and join 94.130.68.169 - Offical DayZ Epoch 1.0.7 Pre-Release Version You will get a message that Epoch needs validating/updating. Click ok and ignore it. You can join the Test Server now. If you want to join any other Epoch non 1.0.7 server, just rename @DayZ_Epoch_old back to @DayZ_Epoch For Server Admins: You have to update to the new server files that coming with this Pre-Release update.
Download and install 7-zip from this website: https://7-zip.de/download.html Download the Epoch 1.0.7 Server Files from google drive: https://drive.google.com/drive/folders/1gHNE4VBCeYXi0P_hosAI8k-49v15WNdr Take the DayZEpoch107.bikey from the Server Files keys folder and put them into your server keys folder. Also set verifySignatures = 2; in your config.cfg to activate the signatures check. How to test:
Do not use any third party scripts or tools. Do not use infistar as an admin tool. Use this testkit: https://github.com/worldwidesorrow/TestKit Enable -showscripterrors in the DayZ Launcher and never ever use -nologs for testing. If you have bugs and problems on testing always provide logs. Server(if you are the admin) and Client Logs. You can find the Client Logs under C:\Users\YourUsername\AppData\Local\ArmA 2 OA It is possbile that the folder is hidden in windows. You can make it visible: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10 Do not post the logs directly, use pastebin.com, google drive, or something like that and add the link. Report all bugs under this topic.

I like the idea of the script. You have asked why nobody else has made a script like that already, well it is because this is a way more complicated as you perhaps think at the moment. First of all you are new to coding so you can acutally not know most of the things so do not worry about it.
Your script has a few problems:
1. The script runs for the server too. It is not really a problem for the script itself but if you run things for clients only use.
if (!isDedicated) then { code }; 2. It only runs one time. A while loop would be required so the script can check the whole time the player is playing.
3. If one condition is true, lets say the first one, the script will wait 900s and will remove after that 'FoodBaconRaw'. But it does not check when the player got this item or the player even still have it. After removing the item it will add the biomeat no matter if the player really had the removed item. A few thoughts about that to make it more clear:
The player could have cooked the 'FoodBaconRaw' within the 900s. If the player gets a new 'FoodBaconRaw' within the 900s the script will remove it even it was in the player inventory only a few seconds. 4. The script will always remove only 1 item. If you have 2x 'FoodBaconRaw' only one gets removed.
5. If you relog everything gets resetted, the same if you died and you take back your gear. If you have died and took back your gear, it will only work after a relog because of the missing while loop.
6. Because of the high sleeps you are using the most parts of the script will never be checked. It just takes too long even if you would have added a while loop.
7. Some classnames are written wrong like FoodRawTuna is FishRawTuna.
To realize this script idea it will need a few variables and a complete different way to script it. I would call it expert level. Those are the key features you have to think about:
When has the player add the item to the inventory and how many items. How to handle the removal to the items if one or more got removed already by another action. How to handle if a new item of the same type got added within the time the other items will spoil. If a player relogs or getting killed. What about if the meat is inside the backpack. Do not use sleep with those high numbers. Use diag_tickTime instead. I've wrote a small script how it works better. But it still does not check the followong things:
Backpack Time when the player got the items Relog and death // Set the spoil time at the start of the script. local _spoilTickTime = diag_tickTime; // Nested array of items that spoil within the inventory. [Spoilt item, New item]. local _spoilItems = [["FoodBaconRaw","FoodBioMeat"],["FishRawTuna","FoodBioMeat"]]; // spoil time in mins local _spoilTime = 15; while {1==1} do { // Every default: 15mins the items spoil in the inventory. if ((diag_tickTime - _spoilTickTime) > (_spoilTime*60)) then { { local _item = _x select 0; // Make sure that the player has acutally the item that spoils in their inventroy. if (_item in magazines player) then { local _newItem = _x select 1; // Count the items that will spoil now to get them all. _qtyItems = {_x == _item} count magazines player; for "_i" from 1 to _qtyItems do { player removeMagazine _item; player addMagazine _newItem; }; // Get display text of the spoilt items and inform the player. _displayName = getText(configFile >> "CfgMagazines" >> _item >> "displayname"); systemchat format ["%1 %2 spoiled in your inventory.",_qtyItems,_displayName]; }; } foreach _spoilItems; // Reset the spoil time of the script. _spoilTickTime = diag_tickTime; }; uisleep 5; };  

It is a very complicated way to realize this script. The main point why it is so hard, is because the item like the food and all magazines and weapons a player can take in-game are just items and no objects. So you cannot set a variable on a single object like you can do it on a building, a vechicle or a player. To work around you have to set a variable on the player which saves what the player does and when with the items. Plus you have to save the state of the variables to the database.
From my point of view it is not worth the effort and the performace impact that this script would have for only this small feature. You could add the backpack checking to the script above but the rest I would skip.

I like the idea of the script. You have asked why nobody else has made a script like that already, well it is because this is a way more complicated as you perhaps think at the moment. First of all you are new to coding so you can acutally not know most of the things so do not worry about it.
Your script has a few problems:
1. The script runs for the server too. It is not really a problem for the script itself but if you run things for clients only use.
if (!isDedicated) then { code }; 2. It only runs one time. A while loop would be required so the script can check the whole time the player is playing.
3. If one condition is true, lets say the first one, the script will wait 900s and will remove after that 'FoodBaconRaw'. But it does not check when the player got this item or the player even still have it. After removing the item it will add the biomeat no matter if the player really had the removed item. A few thoughts about that to make it more clear:
The player could have cooked the 'FoodBaconRaw' within the 900s. If the player gets a new 'FoodBaconRaw' within the 900s the script will remove it even it was in the player inventory only a few seconds. 4. The script will always remove only 1 item. If you have 2x 'FoodBaconRaw' only one gets removed.
5. If you relog everything gets resetted, the same if you died and you take back your gear. If you have died and took back your gear, it will only work after a relog because of the missing while loop.
6. Because of the high sleeps you are using the most parts of the script will never be checked. It just takes too long even if you would have added a while loop.
7. Some classnames are written wrong like FoodRawTuna is FishRawTuna.
To realize this script idea it will need a few variables and a complete different way to script it. I would call it expert level. Those are the key features you have to think about:
When has the player add the item to the inventory and how many items. How to handle the removal to the items if one or more got removed already by another action. How to handle if a new item of the same type got added within the time the other items will spoil. If a player relogs or getting killed. What about if the meat is inside the backpack. Do not use sleep with those high numbers. Use diag_tickTime instead. I've wrote a small script how it works better. But it still does not check the followong things:
Backpack Time when the player got the items Relog and death // Set the spoil time at the start of the script. local _spoilTickTime = diag_tickTime; // Nested array of items that spoil within the inventory. [Spoilt item, New item]. local _spoilItems = [["FoodBaconRaw","FoodBioMeat"],["FishRawTuna","FoodBioMeat"]]; // spoil time in mins local _spoilTime = 15; while {1==1} do { // Every default: 15mins the items spoil in the inventory. if ((diag_tickTime - _spoilTickTime) > (_spoilTime*60)) then { { local _item = _x select 0; // Make sure that the player has acutally the item that spoils in their inventroy. if (_item in magazines player) then { local _newItem = _x select 1; // Count the items that will spoil now to get them all. _qtyItems = {_x == _item} count magazines player; for "_i" from 1 to _qtyItems do { player removeMagazine _item; player addMagazine _newItem; }; // Get display text of the spoilt items and inform the player. _displayName = getText(configFile >> "CfgMagazines" >> _item >> "displayname"); systemchat format ["%1 %2 spoiled in your inventory.",_qtyItems,_displayName]; }; } foreach _spoilItems; // Reset the spoil time of the script. _spoilTickTime = diag_tickTime; }; uisleep 5; };  

I wanted to send a big thank you to @A Man for all the hard work he's been putting into the new version. I've been following the githib commits for months and your code output is very impressive!

Also I wanted to ask if it would be possible for you to post the dayz_epoch_c content so I could test and try out this new version on my server.
Thanks!

And it looks like there another content file called dayz_epoch_w that is also required for 1.0.7.

Epoch 1.0.7 is no fake at all. We are working hard to get it out this year.

Epoch 1.0.7 is no fake at all. We are working hard to get it out this year.

Commet out in your anticheat.sqf the Command Menu lines.
https://github.com/worldwidesorrow/Epoch-Admin-Tools/blob/TestBranch/AdminTools/AntiCheat/antiCheat.sqf#L79

Epoch 1.0.7 is no fake at all. We are working hard to get it out this year.

@nova If you want to disable gems as currency just set the gemwortharray empty. Like this:
DZE_GemWorthArray = [];
It is in the configVariables.sqf. You can put it in your init.sqf after the configVariables.sqf call.

Schalldampfer is correct. An eventhandler cannot see from its sopce a private variable like this.
_motor addEventHandler ["getIn",{ _unit = _this select 2; _nil = [nil,_unit,"loc",rTITLETEXT,"\n\nThis vehicle will disappear on server restart!","PLAIN DOWN",5] call RE; _msg call dayz_rollingMessages; }]; If you still would like to fix it you have to hardcode it there. Like this:
_motor addEventHandler ["getIn",{ _unit = _this select 2; _nil = [nil,_unit,"loc",rTITLETEXT,"\n\nThis vehicle will disappear on server restart!","PLAIN DOWN",5] call RE; "This vehicle will disappear on server restart!" call dayz_rollingMessages; }]; But in this script it does not matter because it is called from the server. dayz_rollingMessages is a client only function which cannot be called from the server. Salival said this already.

Taking "full credit" for copy/pasting code?
 
https://github.com/MigSDev5/BankRobery