yea, i think i got it now...
the point is: the include command will look for a "ZSC" folder IN "gui", which is wrong.
try this:
#include "..\ZSC\config\ZSChud.hpp"
};
#include "..\ZSC\config\ZSCdefines.hpp"
#include "..\ZSC\config\ZSCdialogs.hpp"
the double dot (..) should make it go one folder up, and then its fine.
EDIT: actually even that wouldnt work, as you can see here:
http://forums.bistudio.com/showthread.php?132476-include-statement-for-file-in-parent-folder
that is pretty weak, if you ask me.
so the easiest way to get around this is moving the 3 files into your "gui" folder, and call them like this instead:
#include "ZSChud.hpp"
};
#include "ZSCdefines.hpp"
#include "ZSCdialogs.hpp"
Grew tired with the combat logging on our server and felt like I had to do something about it. What I came up with was actually pretty easy - and as such - has probably already been done loads of times before but since i couldn't find it -> here goes.
What this does
Whenever a player combat logs from the server ALL of his gear will be taken from his body and put in a crate right where he logged off. This way, when it was a malicious log, the other side has the possibility to get the (well deserved) gear. When it was an accident log, there is a good chance the box will still be there when the player logs back in and he can safely take his stuff back.
If you ever wanted to have your own Evac-Chopper you can place anywhere you want, that picks you up where and when you want.
This is the Mod you would like to have!
This Mod allows you to make a Evac-Chopper Field next to your Base or another place you like and use it with any Chopper on it as a Evac-Chopper.
If you start fresh all you need is a Chopper with a Key, which you should have in your Inventory, and for the Evac-Field marking a full Briefcase as payment.
This will make a Evac-Chopper field under your Chopper.
If this Chopper gets destroyed or stolen or just lost, no problem just place any other Chopper you like on it and it will act as your Evac-Chopper!
The "Call Evac-Chopper" action menu entry is just shown if you have a Evac-Chopper field, it checks on activation for:
Chopper is on the field
Enough fuel
Damage status
The Evac-Chopper locks itself on start so no passenger can hop in.
It will stay locked when reaching the Evac-Zone until the player who called it gets close to the Evac-Chopper.
This way no thief could get it before the player is in it.
If the player dies, before or after the Evac-Chopper has reached the Evac-Zone, the Evac-Chopper will be reset to Evac-Field!
JAEM 1.4 changelog:
"evac_AllowedChoppers = ["x","y","z"]"
A new configuration entry is in the EvacChopper_init.sqf
With that configuration entry you can decide which Choppers are allowed as Evac-Choppers!
With many thanks to ebayn0.0b for the Chopper-List in his post, the default config should now implement all available Choppers from Arma2 and Epoch.
I'm really not sure and never tested it if you can use the MV-22 aka Osprey as a Evac-Chopper i just leaved it in the list.
"BE Filters"
Again thanks to ebayn0.0b for solving that, never got very familiar with these BE filters anyway ^^
Changed the files as you suggested!
"Join lag"
The lag was due to the fact that every player had to search for all Evac-Chopper-Fields on Server themself.
To support all kinda Maps, also the hughe ones like Sauerland, i had to put in a very high number to the "nearestObjects" call, that caused the join lag
I decided to put the Evac-Chopper-Fields in a Array now.
A function in the scripts send a PublicVariableServer call to the server to add/rem a field from that array and send that array again via publicVariable to all players.
On Serverstart the Array gets filled with all available Evac-Chopper-Fields on Server and is then send via publicVariable to connecting players.
This should remove the join lag!
"PlayerUID with Characters"
A new check is implemented for these Players with the Arma2 anniversary edition.
Like RimBlock wrote me in a PM these Players have characters in their PlayerUID and cause the Database entry just hold numeric it doesnt worked good for them.
I tooked the function from RimBlock his "A Plot for life v1.1" and implemented it in the JAEM scripts so that should not be a problem anymore
As i took this function from RimBlock his scripts i gave Credits to him here! Dont know who wrote it first if it not was RimBlock himself! "Cant call after Die / Call is always available even if no Evac-Field / and other cal/set/clear related errors"
Clear Evac-Chopper so Field gets delted - CHECK
Set new Evac-Chopper so old field gets deleted - CHECK
Call-Evac-Chopper on login - CHECK
Call-Evac-Chopper on relog - CHECK
Call-Evac-Chopper after die - CHECK
Sorry that the update took such a long time now but this mod was now completely running on my Headless-Client and the port to a working Missionfile system was not that easy!
1. Download JAEM_v1.4.zip and extract it
2. unpbo MPMissions\YOURMISSIONNAME.pbo
3. copy the custom folder from the extracted JAEM_v1.4.zip to MPMissions\YOURMISSIONNAME\
4. Edit MPMissions\YOURMISSIONNAME\init.sqf
Find this block:
if (!isDedicated) then {
0 fadeSound 0;
waitUntil {!isNil "dayz_loadScreenMsg"};
dayz_loadScreenMsg = (localize "STR_AUTHENTICATING");
_id = player addEventHandler ["Respawn", {_id = [] spawn player_death;}];
};
And insert this line above the closing bracket };
_nil = [] execVM "custom\JAEM\EvacChopper_init.sqf";
If you dont have already a custom variables.sqf do step 4a) else do step 4b)
4a)
Find this line:
call compile preprocessFileLineNumbers "z\addons\dayz_code\init\variables.sqf";
and ADD BELOW
call compile preprocessFileLineNumbers "custom\JAEM\variables.sqf";
4b)
Copy this line to the very bottom of your custom variables.sqf
dayz_allowedObjects = dayz_allowedObjects + ["HeliHRescue"];
Whoever says that this line not works, i do it like this for almost a year now on my Server!
5.
Copy these 3 files from the downloaded JAEM_v1.4 to your Servers BattlEye filters folder:
If you already have edited ones you need to compare my changes! remoteexec.txt waypointcondition.txt waypointstatement.txt
Edit this block to your likings!
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// Edit these settings to fit your needs/likes //
/////////////////////////////////////////////////
/////////////////////////////////////////////////
/// Amount of Briefcases a Evac-Chopper costs ///
/////////// Any amount between 1-12 /////////////
evac_chopperPrice = 3;
/////////////////////////////////////////////////
////// Need a Radio to call Evac-Chopper? ///////
////// 1 = Need Radio | 0 = No need Radio ///////
evac_needRadio = 0;
/////////////////////////////////////////////////
// Evac-Zone marker type Smoke or Landingpad? ///
////////// 0 = Landingpad | 1 = Smoke ///////////
evac_zoneMarker = 0;
/////////////////////////////////////////////////
/// Minimum Distance to call for Evac-Chopper ///
///////// Dont set this lower then 500! /////////
evac_minDistance = 500;
/////////////////////////////////////////////////
/// Allowed Choppers to use as Evac-Chopper ///
evac_AllowedChoppers = [
"AH1Z","AH64D_EP1","AH64D","AH64D_Sidewinders","AH6X_DZ",
"AH6X_EP1","AH6J_EP1","AW159_Lynx_BAF","BAF_Apache_AH1_D","BAF_Merlin_HC3_D",
"CH_47F_BAF","CH_47F_EP1","CH_47F_EP1_DZ","CH_47F_EP1_DZE","CSJ_GyroC",
"CSJ_GyroCover","CSJ_GyroP","Ka137_MG_PMC","Ka137_PMC","Ka52",
"Ka52Black","Ka60_GL_PMC","Ka60_PMC","Mi17_CDF","Mi17_Civilian",
"Mi17_Civilian_DZ","Mi17_DZ","Mi17_Ins","Mi17_medevac_CDF","Mi17_medevac_INS",
"Mi17_medevac_RU","Mi17_rockets_RU","Mi17_TK_EP1","Mi17_UN_CDF_EP1","Mi171Sh_CZ_EP1",
"Mi171Sh_rockets_CZ_EP1","Mi24_D","Mi24_D_TK_EP1","Mi24_P","Mi24_V",
"MH60S","MH6J_DZ","MH6J_EP1","MV22","MV22_DZ",
"pook_H13_medevac","pook_H13_medevac_CDF","pook_H13_medevac_TAK","pook_H13_medevac_INS","pook_H13_medevac_UNO",
"pook_H13_medevac_PMC","pook_H13_medevac_GUE","pook_H13_medevac_CIV","pook_H13_medevac_CIV_RU","pook_H13_gunship",
"pook_H13_gunship_CDF","pook_H13_gunship_UNO","pook_H13_gunship_PMC","pook_H13_gunship_GUE","pook_H13_gunship_TAK",
"pook_H13_gunship_INS","pook_H13_transport","pook_H13_transport_CDF","pook_H13_transport_UNO","pook_H13_transport_PMC",
"pook_H13_transport_GUE","pook_H13_transport_TAK","pook_H13_transport_INS","pook_H13_civ","pook_H13_civ_white",
"pook_H13_civ_slate","pook_H13_civ_black","pook_H13_civ_yellow","pook_H13_civ_ru","pook_H13_civ_ru_white",
"pook_H13_civ_ru_slate","pook_H13_civ_ru_black","pook_H13_civ_ru_yellow","UH1H_DZ","UH1H_DZE",
"UH1H_TK_EP1","UH1H_TK_GUE_EP1","UH1Y_DZ","UH1Y_DZE","UH60M_EP1",
"UH60M_EP1_DZ","UH60M_EP1_DZE","UH60M_MEV_EP1"
];
/////////////////////////////////////////////////
/////////////// DONT EDIT BELOW ! ///////////////
/////////////////////////////////////////////////
- Config notes -
If you set evac_needRadio to 1 and you dont have Radios in your respawn loadout, this breaks the call Evac-Chopper for respawners!
If you set evac_zoneMarker to 1 the Smoke in the evac-zone will not last until the Chopper arrives if the distance is very far!
In "evac_AllowedChoppers" the LAST entry in the list DOES NOT HAVE A COMMA ON THE END!
BangL got a reaction from cheech in [Alpha Release] Single Currency 3.0 & Storage DEFAULT HIVE ( No global banking).
BangL got a reaction from TNT in [Alpha Release] Single Currency 3.0 & Storage DEFAULT HIVE ( No global banking).
BangL got a reaction from Proofer in [Alpha Release] Single Currency 3.0 & Storage DEFAULT HIVE ( No global banking).