diff --git a/CHANGE LOG 1.0.6.2.txt b/CHANGE LOG 1.0.6.2.txt index 2dbe309b2..be25eddb7 100644 --- a/CHANGE LOG 1.0.6.2.txt +++ b/CHANGE LOG 1.0.6.2.txt @@ -61,12 +61,13 @@ [FIXED] Melee and tranquilizer bolt knockouts were usually instant or far shorter than the intended time of 20s-80s. [FIXED] Multiple dupe fixes - SERVER ADMINS, DO NOT IMPLEMENT SCRIPTS WHICH KICK PLAYERS TO THE LOBBY (ENDMISSION, FAILMISSION, etc.), YOU MUST KICK THEM ENTIRELY OUT OF THE SERVER! (EX: by BE restriction, but with the stock scripts.txt forceEnd, failmission, and endmission should kick the player anyway) [FIXED] Certain classes (i.e. Satchel Charge) which are both magazines and weapons were not retained through skin change #1981 @AirwavesMan +[FIXED] Blocked another A2OA script execution bug from improperly cleared eventhandlers. See dayz_code\system\antihack.sqf. Thanks to Dihan for reporting -[NOTE] Fixes below are included in the mission file and server pbo as part of server package 1.0.6.1A (March 10th 2017) +[NOTE] Fixes below were included in hotfix 1.0.6.1A (March 10th 2017) and are now in the default files. [FIXED] Fixed food and drink going down 10x faster from melee and other "working" actions. [FIXED] Glitch where group icons scaled very large momentarily while moving off screen. [NEW] Added temporary check for mission file overwrite exploit. This can be removed after Bohemia patches it. [INFO] HiveExt.dll has been updated to return character_data duration in the 101 call for the dayz_survived stat. Source is available at github.com/vbawol/DayZhiveEpoch/pull/13 @icomrade -[INFO] HiveExt.dll REQUIRES NEW PROCEDURE BE ADDED TO YOUR DATABASE, SEE 1.0.6.2_UPDATES.SQL! [REQUIRED BY IMPROVED VEHICLE/OBJECT SPAWNING LOGIC] +[INFO] HiveExt.dll REQUIRES A NEW PROCEDURE BE ADDED TO YOUR DATABASE, SEE 1.0.6.2_UPDATES.SQL! [REQUIRED BY IMPROVED VEHICLE/OBJECT SPAWNING LOGIC] [INFO] See Documents\CHANGE LOG 1.0.6.txt for the full list of 1.0.5.1 --> 1.0.6 changes. diff --git a/SQF/mod.cpp b/SQF/mod.cpp index 605b7582d..b677f80d5 100644 --- a/SQF/mod.cpp +++ b/SQF/mod.cpp @@ -1,5 +1,5 @@ dir = "@DayZ_Epoch"; -name = "DayZ Epoch 1.0.6.1"; +name = "DayZ Epoch 1.0.6.2"; picture = "z\addons\dayz_code\gui\loadingscreen.paa"; actionName = "Website"; action = "http://www.dayzepoch.com"; diff --git a/Server Files/Readme.md b/Server Files/Readme.md index 8629746ad..a390bde9e 100644 --- a/Server Files/Readme.md +++ b/Server Files/Readme.md @@ -2,22 +2,22 @@ Note: Both server and client should be updated to current A2OA stable 1.63.13112 ## Basic Install Guide -1. Install or update your [[Visual C++ Redistributable 2015 (x86 version)](https://www.microsoft.com/en-us/download/details.aspx?id=48145)]. You MUST install all previous Visual C++ Redistributables (x86 versions) [[found on this page](https://support.microsoft.com/en-us/kb/2977003)]. +1. Install or update [[Visual C++ Redistributable 2015 (x86 version)](https://www.microsoft.com/en-us/download/details.aspx?id=48145)] on the server. All previous Visual C++ Redistributables (x86 versions) [[found on this page](https://support.microsoft.com/en-us/kb/2977003)] must be installed. 2. [[Download](http://dayzepoch.com/a2dayzepoch.php)] both client and server files and extract to the root `Arma 2 Operation Arrowhead` folder. Example: `C:\Program Files (x86)\Steam\steamapps\common\Arma 2 Operation Arrowhead`. On some Windows systems you may need to "UnBlock" the dll files. Right-click the file, Properties and click "Unblock". 3. Install MySQL server and create a new MySQL database called `dayz_epoch`. Import the epoch.sql file. -4. Open HiveExt.ini and change your MySQL connection information. Open config.cfg in the same folder and change the admin password. +4. Open HiveExt.ini and adjust the MySQL settings. Open config.cfg in the same folder and change the admin password. 5. Launch the server with `-mod=@DayZ_Epoch;@DayZ_Epoch_Server;`. See the *.bat files in Config-Examples. -6. It may be necessary to forward [[these ports](https://community.bistudio.com/wiki/Arma_3_Dedicated_Server#Port_Forwarding)] in the server's software and hardware firewalls. +6. It may be necessary to forward [[these ports](https://community.bistudio.com/wiki/Arma_3_Dedicated_Server#Port_Forwarding)] in the server software and hardware firewalls. ## Basic Upgrading Guide -1. Perform steps #1 and #2 in the basic install guide, above. Be sure to update to the new MPMission, dayz_server, BattlEye filters and HiveExt.dll too. +1. Perform steps 1-2 in the basic install guide above. Be sure to update to the new MPMission, dayz_server, BattlEye filters and HiveExt.dll. -2. Connect to your MySQL server. Make a backup first to be safe, then run the x_Updates.sql file on your dayz_epoch database. Be sure to read the comments in the SQL field, especially at the bottom of the file if you are using single curreny or Precise Base Building 1.0.4 or older. +2. Connect to the MySQL server. Make a backup. Open the x_Updates.sql file and read the comments, especially at the bottom. Run the appropriate updates on the dayz_epoch database. -3. Inside the "Keys" folder on your server remove any previous day_epoch*.bikey keys. As of 1.0.6.1 our bikey is called dayz_epoch1061.bikey and we will use a new one for each release. +3. Inside the server "Keys" folder remove any DayZ_Epoch*.bikey files from previous versions. \ No newline at end of file diff --git a/Server Files/SQL/1.0.6.1_Updates.sql b/Server Files/SQL/1.0.6.1_Updates.sql deleted file mode 100644 index ede656693..000000000 --- a/Server Files/SQL/1.0.6.1_Updates.sql +++ /dev/null @@ -1,28 +0,0 @@ -/* - DayZ Epoch 1.0.6.1 Updates - - RUN THIS FILE IF UPDATING AN EXISTING 106 DATABASE TO 1061. - NEW DATABASES SHOULD USE EPOCH.SQL INSTEAD. - EXISTING 1051 DATABASES SHOULD RUN 1.0.6_UPDATES.SQL FIRST, THEN RUN THIS FILE. -*/ - --- ---------------------------- --- Fix M24 and DMR ammo prices so a profit can not be made by combining M24 rounds --- ---------------------------- -DELETE FROM `Traders_DATA` WHERE item = '["20Rnd_762x51_DMR"]'; -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 482, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 614, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 624, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 647, 'trade_items'); -DELETE FROM `Traders_DATA` WHERE item = '["5Rnd_762x51_M24"]'; -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 482, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 527, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 614, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 624, 'trade_items'); -INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 647, 'trade_items'); - --- ---------------------------- --- Add military flashlight attachments to DB traders --- ---------------------------- -INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_MFL",1]', 10, '[4,"ItemGoldBar",1]', '[2,"ItemGoldBar",1]', 0, 693, 'trade_items'); -INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_MFL_Pist",1]', 10, '[4,"ItemGoldBar",1]', '[2,"ItemGoldBar",1]', 0, 693, 'trade_items'); \ No newline at end of file diff --git a/Server Files/SQL/1.0.6.2_Updates.sql b/Server Files/SQL/1.0.6.2_Updates.sql index c50b13447..05a0a01d9 100644 --- a/Server Files/SQL/1.0.6.2_Updates.sql +++ b/Server Files/SQL/1.0.6.2_Updates.sql @@ -3,11 +3,11 @@ RUN THIS FILE IF UPDATING AN EXISTING 1061 DATABASE TO 1062. NEW DATABASES SHOULD USE EPOCH.SQL INSTEAD. - EXISTING 1051 DATABASES SHOULD RUN 1.0.6_UPDATES.SQL FIRST, 1.0.6.1_UPDATES.SQL SECOND, THEN RUN THIS FILE. + EXISTING 1051 DATABASES SHOULD RUN 1.0.6_UPDATES.SQL FIRST, THEN RUN THIS FILE. */ /* -THIS PROCEDURE IS REQUIRED FOR 1062 AND RETURNS THE OBJECT ID MUCH MORE EFFICENTLY THAN THE METHOD IN 1061 SQF +THIS PROCEDURE IS REQUIRED FOR 1062 AND RETURNS THE OBJECT ID MUCH MORE EFFICIENTLY THAN THE METHOD IN 1061 SQF */ DROP procedure IF EXISTS `retObjID`; diff --git a/Server Files/SQL/1.0.6_Updates.sql b/Server Files/SQL/1.0.6_Updates.sql index 591295658..472633072 100644 --- a/Server Files/SQL/1.0.6_Updates.sql +++ b/Server Files/SQL/1.0.6_Updates.sql @@ -146,6 +146,8 @@ INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_SCOPED",1]', 10, '[6,"Item INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_Sup9",1]', 10, '[4,"ItemGoldBar",1]', '[2,"ItemGoldBar",1]', 0, 693, 'trade_items'); INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_Sup545",1]', 10, '[6,"ItemGoldBar",1]', '[3,"ItemGoldBar",1]', 0, 693, 'trade_items'); INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_Sup556",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 693, 'trade_items'); +INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_MFL",1]', 10, '[4,"ItemGoldBar",1]', '[2,"ItemGoldBar",1]', 0, 693, 'trade_items'); +INSERT INTO `Traders_DATA` VALUES(null, '["Attachment_MFL_Pist",1]', 10, '[4,"ItemGoldBar",1]', '[2,"ItemGoldBar",1]', 0, 693, 'trade_items'); -- ---------------------------- -- ItemMatchbox_DZE was removed because it was identical to ItemMatchbox, use dayz_matchboxCount config variable for match stick count @@ -552,6 +554,20 @@ UPDATE character_data SET Backpack = REPLACE(Backpack, '"Winchester1866"', '"Win UPDATE character_data SET Inventory = REPLACE(Inventory, '"Winchester1866"', '"Winchester1866_DZ"') WHERE INSTR(Inventory, '"Winchester1866"') > 0; UPDATE object_data SET Inventory = REPLACE(Inventory, '"Winchester1866"', '"Winchester1866_DZ"') WHERE INSTR(Inventory, '"Winchester1866"') > 0; +-- ---------------------------- +-- Fix M24 and DMR ammo prices so a profit can not be made by combining M24 rounds +-- ---------------------------- +DELETE FROM `Traders_DATA` WHERE item = '["20Rnd_762x51_DMR"]'; +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 482, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 614, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 624, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["20Rnd_762x51_DMR",1]', 10, '[8,"ItemGoldBar",1]', '[4,"ItemGoldBar",1]', 0, 647, 'trade_items'); +DELETE FROM `Traders_DATA` WHERE item = '["5Rnd_762x51_M24"]'; +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 482, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 527, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 614, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 624, 'trade_items'); +INSERT IGNORE INTO `Traders_DATA` VALUES (NULL, '["5Rnd_762x51_M24",1]', 10, '[2,"ItemGoldBar",1]', '[1,"ItemGoldBar",1]', 0, 647, 'trade_items'); -- ---------------------------- diff --git a/Server Files/SQL/epoch.sql b/Server Files/SQL/epoch.sql index 422cea496..49b6de610 100644 --- a/Server Files/SQL/epoch.sql +++ b/Server Files/SQL/epoch.sql @@ -1,9 +1,9 @@ /* - DayZ Epoch 1.0.6.1 + DayZ Epoch 1.0.6.2 ONLY RUN THIS FILE IF CREATING A NEW DATABASE. - EXISTING 1051 DATABASES SHOULD USE 1.0.6_UPDATES.SQL INSTEAD AND THEN RUN 1.0.6.1_UPDATES.SQL. - EXISTING 106 DATABASES SHOULD USE 1.0.6.1_UPDATES.SQL INSTEAD. + EXISTING 1051 DATABASES SHOULD USE 1.0.6_UPDATES.SQL INSTEAD AND THEN RUN 1.0.6.2_UPDATES.SQL. + EXISTING 1061 DATABASES SHOULD USE 1.0.6.2_UPDATES.SQL INSTEAD. */ SET FOREIGN_KEY_CHECKS=0;