natoed

So there are a couple of serious glitches that are possible with the use of the Enhanced Interaction functionality within the Enhanced Movement mod on Epoch servers. Not going to list them here but they are incredibly serious and need to be fixed if you are running EM on your Epoch server. Thankfully, there is a quite easy solution to "turn off" Enhanced Interaction within the mission file. If you are already using the initPlayerLocal.sqf file for things like the autolockpicker, attaching demo charges to things and other stuff, then just add the following to it:
[] spawn { while {true} do { if !((profilenamespace getvariable ["babe_int_keys_Use",[0,""]]) isequalto [0,""]) then { profilenamespace setvariable ["babe_int_keys_Use",[0,""]]; }; uisleep 1; }; }; If you are not already using the file, but are using EM then create an initPlayerLocal.sqf with the following:
if (!isDedicated and hasInterface) then { waitUntil {alive vehicle player}; waitUntil {typeOF player != "VirtualMan_EPOCH"}; uisleep 15; [] spawn { while {true} do { if !((profilenamespace getvariable ["babe_int_keys_Use",[0,""]]) isequalto [0,""]) then { profilenamespace setvariable ["babe_int_keys_Use",[0,""]]; }; uisleep 1; }; }; }; Repack the mission PBO, upload to your server and the possible glitches are dealt with, while still allowing the lovely niceness of Enhanced Movement to continue.
Thanks very much to @He-Manfor invaluable help in crafting the solution and thanks to Duralius, a player on my server for finding the glitches and not exploiting them. Good man!

Try this:
class Crafting { condition = "true"; action = "'' call EPOCH_crafting_load"; icon = "x\addons\a3_epoch_code\Data\UI\buttons\player_inspect.paa"; tooltip = "Crafting"; };  

Another class of item added to EpochCore client-side in 1.1 are deployable sleeping bags. Here is the code for placing them and a suggestion (and code) for actually making use of them to provide greater flexibility at respawn for your players.
Installation Instructions
(1) Add the sleeping bag "kits" to your loot tables and trader price lists. The class names are KitSleepingBagGreen, KitSleepingBagBlue and KitSleepingBagBrown
(2) Add the following to epoch_config/Configs/CfgItemInteractions.hpp:
class KitSleepingBagGreen : Item_Build_base { buildClass = "SleepingBagGreen_SIM_EPOCH"; }; class KitSleepingBagBlue : Item_Build_base { buildClass = "SleepingBagBlue_SIM_EPOCH"; }; class KitSleepingBagBrown : Item_Build_base { buildClass = "SleepingBagBrown_SIM_EPOCH"; }; (3) Add the following to epoch_config/Configs/CfgBaseBuilding.hpp:
class SleepingBagGreen_EPOCH : Default { removeParts[] = {{"KitSleepingBagGreen",1}}; GhostPreview = "SleepingBagGreen_Ghost_EPOCH"; staticClass = "SleepingBagGreen_EPOCH"; simulClass = "SleepingBagGreen_SIM_EPOCH"; bypassJammer = 1; }; class SleepingBagGreen_SIM_EPOCH : SleepingBagGreen_EPOCH { removeParts[] = {}; }; class SleepingBagGreen_Ghost_EPOCH : SleepingBagGreen_SIM_EPOCH {}; class SleepingBagBlue_EPOCH : Default { removeParts[] = {{"KitSleepingBagBlue",1}}; GhostPreview = "SleepingBagBlue_Ghost_EPOCH"; staticClass = "SleepingBagBlue_EPOCH"; simulClass = "SleepingBagBlue_SIM_EPOCH"; bypassJammer = 1; }; class SleepingBagBlue_SIM_EPOCH : SleepingBagBlue_EPOCH { removeParts[] = {}; }; class SleepingBagBlue_Ghost_EPOCH : SleepingBagBlue_SIM_EPOCH {}; class SleepingBagBrown_EPOCH : Default { removeParts[] = {{"KitSleepingBagBrown",1}}; GhostPreview = "SleepingBagBrown_Ghost_EPOCH"; staticClass = "SleepingBagBrown_EPOCH"; simulClass = "SleepingBagBrown_SIM_EPOCH"; bypassJammer = 1; }; class SleepingBagBrown_SIM_EPOCH : SleepingBagBrown_EPOCH { removeParts[] = {}; }; class SleepingBagBrown_Ghost_EPOCH : SleepingBagBrown_SIM_EPOCH {}; So, at this point you can place sleeping bags and they look pretty nice, but what's the point. Well, say for example that you would like to seal your jammer away in a dark place in your base but don't want to respawn in that room, but do want to respawn somewhere in a base; or perhaps you are doing a mission or you're off hunting heroes and don't want to make your way from the coast all over again... well, you can set sleeping bags to be spawn points too!
(4) Change the definition for the select_jammer class in epoch_config/Configs/CfgActionMenu/cfgActionMenu_target.hpp to:
class select_jammer { condition = "((dyna_cursorTargetType isEqualTo 'PlotPole_EPOCH') || (dyna_cursorTargetType isEqualTo 'SleepingBagGreen_EPOCH') || (dyna_cursorTargetType isEqualTo 'SleepingBagBlue_EPOCH') || (dyna_cursorTargetType isEqualTo 'SleepingBagBrown_EPOCH')) && (damage dyna_cursorTarget < 1)"; action = "[dyna_cursorTarget,player,Epoch_personalToken] remoteExec [""EPOCH_server_makeSP"",2];"; icon = "x\addons\a3_epoch_code\Data\UI\buttons\player_inspect.paa"; tooltip = "Make Spawnpoint"; }; RePBO your mission file and upload it to the server.
(5) Now unpack epoch_server.pbo. There is one file in there that needs a change which is compile/epoch_player/EPOCH_server_loadPlayer.sqf. Change line 145 from:
_jammers = nearestObjects[_CheckLocation, ["PlotPole_EPOCH"], 6]; to:
_jammers = nearestObjects[_CheckLocation, ["PlotPole_EPOCH","SleepingBagGreen_EPOCH","SleepingBagBlue_EPOCH","SleepingBagBrown_EPOCH"], 6]; RePBO epoch_server.pbo and upload to your server. You now have sleeping bags that can be built anywhere and used as respawn points.
Be aware though! Anyone can pick yours up in the wild (as they should be able to) and you will no longer spawn at its location!
(Optional 6) Also note that should you give these as starting gear you may want to add energy to a player at spawn by changing the energy entry in the CustomVarsDefaults array in epoch_config/CfgEpochClient.hpp to something like the following (which gives 1250 energy to a new spawned player):
{"Energy",1250,{2500,0}},  

Another item added to EpochCore client-side in 1.1 is a Large Workbench - using the ARMA model for a steel work table with drawers and a vice. Here is the code for placing them and a suggestion (and code) for actually making use of them to provide greater flexibility in crafting for your players.
Installation Instructions
(1) Add the large workbench "kit" to your loot tables and trader price lists. The class name is KitWorkbenchLarge
(2) Add the following to epoch_config/Configs/CfgItemInteractions.hpp:
class KitWorkbenchLarge : Item_Build_base { buildClass = "WorkbenchLarge_SIM_EPOCH"; }; (3) Add the following to epoch_config/Configs/CfgBaseBuilding.hpp:
class WorkbenchLarge_EPOCH : Default { removeParts[] = {{"KitWorkbenchLarge",1}}; GhostPreview = "WorkbenchLarge_Ghost_EPOCH"; staticClass = "WorkbenchLarge_EPOCH"; simulClass = "WorkbenchLarge_SIM_EPOCH"; }; class WorkbenchLarge_SIM_EPOCH : WorkbenchLarge_EPOCH { removeParts[] = {}; }; class WorkbenchLarge_Ghost_EPOCH : WorkbenchLarge_SIM_EPOCH {}; So, those minor changes will allow you to build a large workbench from a kit and then utilize it within Epoch's crafting system. All further changes will be made to epoch_config/Configs/CfgCrafting.hpp.
Let's start our examination of that with the crafting of the large workbench itself. The crafting system in Epoch is really nice, quite simple (though it can look imposing at first glance) and very flexible. Basically it comprises parts and kits that are built from them and allows the specification of either things (water or fire) or objects to be nearby in order to build the kit. For the building of the large workbench you will need to add the following new entry:
class KitWorkbenchLarge : Kit { recipe[] = {{"PartPlankPack",8},{"ItemCorrugatedLg",2},{"ItemPipe",2},{"ItemCorrugated",2},{"VehicleRepair",1}}; nearby[] = {{"Workbench","","workbench",{1,{"WorkBench_EPOCH","WorkbenchLarge_EPOCH"}},3,1,0,1}}; model = "\A3\Structures_F_Heli\Furniture\Workbench_01_F.p3d"; previewPosition[] = {0.8,1,0.27}; previewScale = 0.15; previewVector = 0; }; This entry illustrates nicely the configuration for a craftable item. Let's look at a few lines in it starting with the recipe[]. This specifies which items are needed to build the kit, in this case 8 lumber packs, 2 large salvage metal, two pipes, two small salvage metals and a vehicle repair parts (for the vice). In order to show the Large Workbench as a buildable from these individual items in the crafting menu you need to add the Large Workbench to their entries' usedin[] array, for example:
Okay, at this point you can click on any of these parts and a Large Workbench will be shown as a possible recipe for the part. Now let's look at the nearby[] array in the Large Workbench's crafting definition. This specifies things that are needed nearby in order to complete the crafting, in this case:
nearby[] = {{"Workbench","","workbench",{1,{"WorkBench_EPOCH","WorkbenchLarge_EPOCH"}},3,1,0,1}}; Now, reading the very handy comment at the head of CfgCrafting.hpp shows what each part of this line means:
USAGE: nearby[] = { { "Fire", //Name of field, anything "", //image folder path (ie "\x\addons\a3_epoch_code\Data\UI\crafting\"), empty for Epoch default "fire", //image prefix, suffix will be added by code. 2 possible suffixes: [_true.paa, _false.paa] {1,{"ALL"}}, //ARRAY of p3D {0,{"filename.p3d","filename.p3d"}} or ARRAY of logic classes {1,{"AIR","LAND","className"}} or 2 WorldInteractions check {2,{"water"}} Integer to switch array mode 3, //distance to check in meters 1, //count 1, //BOOL: object has to be on fire 0 //BOOL: object has to be alive (not destroyed) }; }; So you can see in the nearby[] array for Large Workbenches that it needs either a standard Epoch workbench or a large workbench itself within 3m of the player in order to build one. You can have as many requirements as you want in that list including categories defined in epoch_config/Configs/CfgEpochClient/WorldInteractions.hpp like "Water" or "Tree" or ... "bankTerminal" 
Now you can craft a Large Workbench and then build it, you can now use the fact you have one to make crafting just a little more immersive by, for example, only allowing small things to be crafted with a standard Epoch workbench and requiring a large workbench for more complicated or larger buildables. For example, let's say we leave buckets of mortar as being able to be crafted on a small one. You probably also want to allow your to craft them on a large one as well so you would have both items in the nearby[] array for them:
class MortarBucket : Item { usedIn[] = {"KitFoundation","KitCinderWall","KitHesco3","KitCinderFloor","KitCinderHalfFloor","KitCinderQuarterFloor","KitCinderTower","KitSandbagWall","KitSandbagWallLong","KitBagBunker","KitWaterPump","KitWell"}; nearby[] = {{"Fire","","fire",{1,{"ALL"}},3,1,1,0},{"Workbench","","workbench",{1,{"WorkBench_EPOCH","WorkbenchLarge_EPOCH"}},3,1,0,1}}; recipe[] = {{"ItemRock",12},{"water_epoch",2}}; previewPosition[] = {0.799442,1,0.426761}; previewScale = 0.6; previewVector = 0; }; Now this is an interesting item (the reason I picked it...) because it demonstrates making a craftable dependent on multiple things nearby, in this case a burning fire and either a small or large workbench... cool huh?
For the wooden buildables I like to allow a small workbench so each of their definitions would have both the large and small workbench in the nearby[] array like this:
class KitStudWall : Kit { recipe[] = {{"PartPlankPack",4}}; model = "\x\addons\a3_epoch_assets\models\Wooden_Wall_SIM.p3d"; nearby[] = {{"Workbench","","workbench",{1,{"WorkBench_EPOCH","WorkbenchLarge_EPOCH"}},3,1,0,1}}; previewPosition[] = {0.797675,1,0.398882}; previewScale = 0.07; previewVector = 0; }; But for cinder buildables I think you need a more flexible work environment, thus the small workbench is removed from their nearby[] arrays, for example:
class KitCinderFloor : Kit { usedIn[] = {"KitCinderTower"}; recipe[] = {{"CinderBlocks",4},{"MortarBucket",4}}; nearby[] = {{"Large Workbench","","workbench",{1,{"WorkbenchLarge_EPOCH"}},3,1,0,1}}; model = "\x\addons\a3_epoch_community\models\cinderfloor.p3d"; previewPosition[] = {0.800198,1,0.262418}; previewScale = 0.055; previewVector = 3.6; }; That's pretty much it. Now you can build a large workbench, craft one and make other items dependent on it - or indeed any other object in the game. As a final example here's a modified entry for an energy pack that relies on you having a power source within 30m, and a fire and a large workbench within 3m:
class EnergyPack : Item { usedIn[] = {"EnergyPackLg"}; nearby[] = {{"Fire","","fire",{1,{"ALL"}},3,1,1,0},{"Large Workbench","","workbench",{1,{"WorkbenchLarge_EPOCH"}},3,1,0,1},{"Power Source","","electricity",{1,{"Land_spp_Tower_F","Land_wpp_Turbine_V2_F","Land_wpp_Turbine_V1_F","SolarGen_EPOCH","Land_Wreck_Satellite_EPOCH"}},30,1,0,1}}; recipe[] = {{"CircuitParts",1},{"ItemCopperBar",1},{"clean_water_epoch",1}}; previewPosition[] = {0.8,1,0.29}; previewScale = 1.75; previewVector = 2.8; }; Now let your imagination run wild!

I decided to collaborate a couple of different statusbars.
All credits goes to: Creampie -  Osef - All The Others!
 
Screenshot
 
Download: Github
Installation: Drag the map status_bar into your mission.pbo.
Init.sqf: add the lines in your existing init.sqf file, or drag init.sqf into your mission.pbo:
// Status Bar [] execVM "status_bar\fn_statusBar.sqf"; Description.ext: open up your existing description.ext and add the lines on the bottom:
class RscTitles { #include "status_bar\dialog\statusBar.hpp" };  
BE Problems? Post your kicks.
 
It is possible to add additional status information, for example: Energy status display,
But keep in mind the background space is limited, Note: Toxicity will expand to 4/5 extra digits.
 
Did i forget any other Author? please send me a message i will update the post asap.
 
-Greetings
 

I have ported some of the Extra Wicked AI missions from ARMA2/DayZ/Epoch's Wicked AI system. They are a purely derivative product based on this work:
Missions ported so far are: Abandoned Trader, Ambushed HMMWV, Army Base, Drone Pilot, Old MacDonald's Farm and Slaughter House. 
I will be continuing this work with the others when I have time.
NOTE: In order to use these missions you will require CUP Terrains Core on your server. For those running non-vanilla ARMA3 maps, for example Chernarus Redux that should not be an issue.
Download
https://www.dropbox.com/s/19ln1t6yhsmbldw/Extra_WAI_Missions.zip?dl=0
Installation
(1) Copy the files in the downloadable archive to your Wicked AI's missions/bandit folder.
(2) Add the missions to the mission array in WAI's config.sqf, for example:
wai_bandit_missions = [ ["abandoned_trader",5], ["ambushed_hmmwv",5], ["army_base",5], ["drone_pilot",4], ["macdonald",5], ["slaughter_house",5], ["nuke",4], ["Mi_48",6], ["MV_22",6], ["sniper_team",8], ["rebel_base",5], ["medi_camp",5], ["dropside",5], ["comm_center",10], ["C_192",11], ["destroyed_ural",11] RePBO Wicked AI and upload to @epochhive/addons and enjoy!

In your side, you have missed nothing. 
This is a bug in the current release. 
To fix it:
https://github.com/EpochModTeam/Epoch/commit/92035636be7fe2879080a360e26161c2d9887fd7

Another WIP thing... testing the Left Shoulder Scripted Weapon mod with Epoch. Server side mod only so no worries about adding to player's clients.
While the animations are a bit clunky it works... Need to add code to Epoch to save the "hidden" weapon in the database or it will be lost on a disconnect
https://steamcommunity.com/sharedfiles/filedetails/947704792
 

@Efixea
try this post first
also check your settings in epochconfig.hpp  and  yourmissionfile\epoch_config\ConfigsCfgEpochClient.hpp shitload of settings in this one....
 

First test of infected spawns via the standard ARMA3 Epoch lootbubble. Infected spawn out of LOS and right now just a hard coded one per building.   No DayZ code was used in this new feature.   As always, apologies for the video quality, my PC is a potato...    

I got certain configs updated in the EpochCore client files allowing a few extra nice features to be deployed in A3/Epoch, and I'll start off by posting the information to set up portable generators to allow fuel pumps to be used for refueling vehicles if auto-refueling is turned off on your server. 
Installation Instructions
(1) Add the portable generator "kit" to your loot tables and trader price lists. The class name is KitGenerator
(2) Add the files in this downloadable archive to a folder in your mission called, for example, sounds:
https://www.dropbox.com/s/75gq2rezy1tcbe2/generator_sounds.zip?dl=0
The license file is required! It is a Creative Commons Attribution Only license for the sound file.
(3) Add the following lines to your mission file's custom description.ext (replacing the path for the generator1.ogg sound with the location in which you put it):
// Portable Generator Sounds class CfgSFX { class Generator { sounds[] = {"Generator"}; name = "Generator"; Generator[] = {"sounds\generator1.ogg","db+10",1,200,1,0,0,0}; Empty[] = {"",0,0,0,0,0,0,0}; }; }; class CfgVehicles // NOTE: CfgVehicles definitions are only permitted in description.ext for sound sources. It cannot be used for CfgVehicles customizations { class PortableGenerator { sound = "Generator"; }; }; (4) Create a file in the folder of your mission file where you store your own scripts, e.g. custom called PortableGenerator.sqf and paste the following code into it:
(5) Add the following lines to your mission's init.sqf (replacing the path with whatever you used in step (4)):
if(hasInterface) then{ PortableGenerator = compileFinal preprocessFileLineNumbers "custom\PortableGenerator.sqf"; }; (6) Add the following to epoch_config/Configs/CfgItemInteractions.hpp:
class KitGenerator : Item_Build_base { buildClass = "Generator_EPOCH"; }; (7) Add the following to epoch_config/Configs/CfgBaseBuilding.hpp:
class Generator_EPOCH : Default { removeParts[] = {{"KitGenerator",1}}; GhostPreview = "Generator_Ghost_EPOCH"; staticClass = "Generator_EPOCH"; simulClass = "Generator_SIM_EPOCH"; limitNearby = 2; bypassJammer = 1; }; class Generator_SIM_EPOCH : Generator_EPOCH { removeParts[] = {}; }; class Generator_Ghost_EPOCH : Generator_SIM_EPOCH {}; (8) Add the following code to epoch_config/Configs/CfgActionMenu/cfgActionMenu_target.hpp:
// Portable Generators class generator_refill { condition = "((dyna_cursorTarget isKindOf 'Generator_EPOCH') && !(dyna_cursorTarget getVariable [""GeneratorFueled"",false]) && !(dyna_cursorTarget getVariable [""GeneratorRunning"",false]))"; action = "[dyna_cursorTarget, 2] call PortableGenerator;"; icon = "x\addons\a3_epoch_code\Data\UI\buttons\vehicle_refuel.paa"; tooltip = "Refuel generator"; }; class generator_start { condition = "((dyna_cursorTarget isKindOf 'Generator_EPOCH') && (dyna_cursorTarget getVariable [""GeneratorFueled"",false]) && !(dyna_cursorTarget getVariable [""GeneratorRunning"",false]))"; action = "[dyna_cursorTarget, 1] call PortableGenerator;"; icon = "x\addons\a3_epoch_code\Data\UI\buttons\Replace_Engine.paa"; tooltip = "Start generator"; }; class generator_stop { condition = "((dyna_cursorTarget isKindOf 'Generator_EPOCH') && (dyna_cursorTarget getVariable [""GeneratorRunning"",false]))"; action = "[dyna_cursorTarget, 0] call PortableGenerator;"; icon = "x\addons\a3_epoch_code\Data\UI\buttons\Remove_Engine.paa"; tooltip = "Stop generator"; }; RePBO your mission file and upload it to the server. That should be it.

That could be. 
But the radiation suit has anyway a texture error atm. It should be already fixed by Helion in current experimenta. We will test it tomorrow.
Then I can also add the missing classes to Loot, Pricing and Itemsort and AWOL sayd, he will push another small update for these fixes in the next 2 weeks.
If you find more bugs / missing things, let us know and we try to add it asap

The Heli crash not not working for now. It is only defined for later usage. I have a working Heli-Crash and I am planning to add it. But I have to recode some things first.
Yes, the Vehicle properties are completely redefined. I have added some more upgrade classes (lvl1-4). For this it was necessary to reduce some max loads to make it possible to increase the loads for each upgrade.
You can find a List of these Vehicles and the properties here:
https://github.com/EpochModTeam/EpochCore/raw/release/EPOCH_VehicleProperties.xlsx
So if you want back more loads, just use another lvl. I prefer to make use of the upgrade system. 

Arma 3 Epoch 1.1 has been released!
Server Files:
https://github.com/EpochModTeam/Epoch/archive/1.1.0.1195.zip
File Changes:
https://github.com/EpochModTeam/Epoch/pull/969/files
Client Files
https://github.com/EpochModTeam/EpochCore/releases/download/1.1.0.1194/Epoch_Client_1.1.0.0.zip
Changelog:
Added
Plant Spawner: vehicle object for sunflower. @Helion4 MoneyDrop Event: Random Money lump with Mapmarker (like Plants) @he-man Examples for Vehicle upgrades for Server Admins into CfgVehicleUpgrades.hpp @he-man Make Lighter refillable at Fuel-Sources (Gasstations / Vehicles) @he-man Make Trader more configurable in epochconfig.hpp @he-man Added Examples for Batchfiles to control Server Restarts @DirtySanchez default pops for "center" marker @awol More map supports @awol Lighter is needed to imflame fires @DirtySanchez FireExtinguisher is needed to "put our fire" on Burn Barrel @DirtySanchez Rope is needed for SlingLoad (get back on release) @DirtySanchez R3F compatibility for SlingLoad @DirtySanchez Hints while using Vehicle Repair (MultiGun) @he-man Config to completely disable Simulation for BaseParts (if not needed) @he-man Made Radiation configureable by cfgepochclient.hpp @raymix Hints for lock / unlock Vehicles / Storages @he-man Nuisance multiplicator in cfgepochclient.hpp @he-man Reduce rads over time at cost of immunity @raymix Wearable Male & Female wearable full radiation suit @Helion4 December seasonal items (Santa hat / Snowman) @Helion4 Autorun function (suggested by Ghostrider) @he-man Default Key is "W" You can change the key in EPOCH ESC Menu If choosen key is same as "moveforward" (default), you have to 2x tap it, else you only have to 1x tap it If your legs are broken, you get a hint "can not autorun - legs are broken" If the terrain is too steep, you only walk in AutoRun Inside Water, you can not Autorun Helper 3D-Icon + Line on the part, where element is snapped on (while Base-Building) @he-man Config in cfgepochclient.hpp to block ATM's in Plotpole range @he-man Power Sword @helion Fixed
False BE kicks since Arma 3 1.80 update. Nightlight now also follow players inside Vehicles @he-man Fixed fault disabled DynamicDebris @morgoth0 SERVER_VARS (BaseSpawn) was not saved on revive @morgoth0 Without Advanced Vehicle Repair, Vehicle upgrade was not available @he-man Base Storages could be deleted if near Loot containers were auto-deleted @he-man Some Tarp Loot was spawned under the Floor @he-man Reworked wall check by getting out of Vehicles @he-man Garden Plot had no physical ground @Helion4 Some Vehicles were missing in EPOCH Admin Spawn Menu @he-man Changed
RCon Port is now set to 2307 by default since changes in A3 1.78 prevent use of 2306. @awol SnapPoints for Building objects (especially full / half / quarter Floors) @he-man Some performance tweaks Inventory will be opened automatically, if "you found something" @awol EPOCH Events reworked (Markers will change if players near / event looted) @DirtySanchez Traders will no longer refill sold magazines @he-man Magazines will automatic be repacked in Trader First the trader offers full magazines If no full magazine is available, the Trader offer the last not full magazine Not full magazines are colored: Yellow (nearly full) -> Red (nearly empty) You also get a Tooltip, how much bullets left in magazine The prices are calculated by the left bullets in the magazine Increased snap-distance for Foundations (much easier to find snap positions) @he-man Reworked and added EPOCH Vehicle Classes @he-man Each upgrade increase Speed, Torque, Fuel, Terrainbehaviour, Load and Armor Hatchback >= lvl2 will no longer stuck in forests Added M900 forced without Backseats -> "C_Heli_Light_01_civil_2seat_EPOCH" Added M900 forced with Backseats -> "C_Heli_Light_01_civil_4seat_EPOCH" The Random M900 will also stay available -> "C_Heli_Light_01_civil_EPOCH" Added very low EPOCH variants of VTOL and Xi'an (eventually we have to change them with the next update a bit) Added Door-Animations to some Vehicles by GetIn / GetOut

I'll pass back the code to the A3/Epoch devs if they want it and if someone has or can get a public domain generator sound... obviously the one I use on my servers is not afaik (though it might be...)  
P.S. Apologies for the poor quality of the video, my PC is a potato...

Will be fixed with the next Client Side Epoch update. Should come very soon...

from build 118 on check in the mod-specific config for the definition for vehicles for each level of mission. These are listed right at the top of that config file.

@Ghostrider-GRG
Fuck'n brilliant update mate, I only get 1 rpt error thou the underwater mission started and finished as it should
thx again
cheers
natoed

Hmm, okay...
Let's fix it in private and if we found it, we can publish it. I'll write you

@Tarabas

You will need to add this to CfgActionMenuCore.hpp
 
dyna_AtHome = "call {_config = 'CfgEpochClient' call EPOCH_returnConfig;_buildingJammerRange = getNumber(_config >> 'buildingJammerRange');_nearjammers = nearestobjects [player,['Plotpole_EPOCH'],_buildingJammerRange];if (_nearjammers isEqualTo []) exitwith {false};_nearestJammer = _nearjammers select 0;((_nearestJammer getVariable['BUILD_OWNER', '-1']) in[getPlayerUID player, Epoch_my_GroupUID])}"; He recently added that line into Epoch experimental here:
https://github.com/EpochModTeam/Epoch/compare/1e8a428d3c26...2fe4b0ff969e#diff-fd142c19fa4ee8fc1dbfbbb6bc8411c6R52

And thats whats needed in both "conditions" in here:
https://github.com/Ignatz-HeMan/Door-Opener/blob/master/CfgActionMenu_self.hpp#L3

I love this community.. The scripts works great.. it's even showing what components are missing.. the idea with energy using is brilliant aswell.
thanks again to all of you.
yayy :)

We have solved it.
It was only a wrong order of the Variables in cfgactionmenu_core.hpp.
The files are correct and work.

custom_server\Configs\blck_configs_epoch.sqf
line 52
blck_AIPatrolVehicles = ["I_G_Offroad_01_armed_F","I_mas_cars_UAZ_M2","I_mas_cars_LR_soft_M2","B_LSV_01_armed_F"]; // Type of vehicle spawned to defend AI bases heli
custom_server\Configs\blck_configs.sqf
from line 136
/////////////////////////////// // Heli Patrol Heli Types // Armed Helis ////////////////////////////// _blck_littleBirds = ["B_Heli_Light_01_armed_F"]; // AH-9 Pawnee (WEST) _blck_armed_hellcats = ["I_Heli_light_03_F"]; _blck_armed_orcas = ["O_Heli_Light_02_F","O_Heli_Light_02_v2_F"]; _blck_armed_ghosthawks = ["B_mas_UH60M","B_mas_CH_47F","I_mas_MI8","B_mas_UH1Y_UNA_F"]; //_blck_armed_ghosthawks = ["B_Heli_Transport_01_F","B_Heli_Transport_01_camo_F"]; _blck_armed_hurons = ["B_Heli_Transport_03_F","B_Heli_Transport_03_black_F"]; _blck_armed_attackHelis = ["B_Heli_Attack_01_F"]; _blck_armed_heavyAttackHelis = ["O_Heli_Attack_02_F","O_Heli_Attack_02_black_F"]; _blck_fighters = [ "O_Plane_CAS_02_F", // /ti-199 Neophron (CAS) "I_Plane_Fighter_03_AA_F", // A-143 Buzzard (AA) "I_Plane_Fighter_04_F", // A-149 Gryphon "B_Plane_CAS_01_F", // A-164 Wipeout (CAS) "B_Plane_Fighter_01_F" // F/A-181 Black Wasp II ]; blck_blacklisted_heli_ammo = ["24Rnd_missiles","24Rnd_PG_missiles","12Rnd_PG_missiles","2Rnd_LG_scalpel","6Rnd_LG_scalpel","8Rnd_LG_scalpel","M_Scalpel_AT ","14Rnd_80mm_rockets","38Rnd_80mm_rockets"]; blck_blacklisted_heli_weapons = ["missiles_SCALPEL","missiles_titan","rockets_Skyfire","missiles_DAGR","missiles_DAR"]; and
from line 159
/////////////////////////////// // Heli Patrol Settings /////////////////////////////// blck_chanceHeliPatrolBlue = 0; //[0 - 1] Set to 0 to deactivate and 1 to always have a heli spawn over the mission center and patrol the mission area. // The chance of paratroops dropping from the heli is defined by blck_chancePara(Blue|Red|Green|Orange) above. // Recommend setting the change = 1 if you wish to spawn multiple helis at a mission. blck_patrolHelisBlue = _blck_armed_ghosthawks; blck_noPatrolHelisBlue = 0; blck_chanceHeliPatrolRed = 0.1; // 0.4; blck_patrolHelisRed = _blck_armed_ghosthawks; blck_noPatrolHelisRed = 1; blck_chanceHeliPatrolGreen = 0.2; blck_patrolHelisGreen = _blck_armed_ghosthawks; blck_noPatrolHelisGreen = 1; blck_chanceHeliPatrolOrange = 0.3; blck_patrolHelisOrange = _blck_armed_ghosthawks; blck_noPatrolHelisOrange = 1; static Weapons
custom_server\Configs\blck_configs.sqf
from line 228
blck_useStatic = true; // When true, AI will man static weapons spawned 20-30 meters from the mission center. These are very effective against most vehicles blck_killEmptyStaticWeapons = true; // When true, static weapons will have damage set to 1 when the AI manning them is killed. blck_staticWeapons = ["B_HMG_01_high_F","I_mas_DSHKM_AAF","I_mas_KORD_high_AAF","I_mas_M2StaticMG_AAF","I_static_AT_F"/*,"O_static_AT_F"*/]; // [0.50 cal, grenade launcher, AT Launcher] //////////////////// // Mission Static Weapon Settings //////////////////// // Defines how many static weapons to spawn. Set this to -1 to disable spawning blck_SpawnEmplaced_Orange = [2,4]; // Number of static weapons at Orange Missions blck_SpawnEmplaced_Green = [1,3]; // Number of static weapons at Green Missions blck_SpawnEmplaced_Blue = 0; // Number of static weapons at Blue Missions blck_SpawnEmplaced_Red = [1,2];; // Number of static weapons at Red Missions hope it helps
natoed
 
 
i lose my way around in the custom_server.pbo from time to time lol

A few days ago I started to write a script together with my friend PirateLaserBeam to remote gates from vehicles in Epoch.
I was getting great support from the community and He-Man finished that script in a impressing way.
http://plays.tv/video/5aa4580e23dbbbd67b/door-opener
And here it is for first release :
Read readme for install instructions
https://github.com/Ignatz-HeMan/Door-Opener

Hey, I have played a bit with this function and have a sample for you.
This Script will check, if you are in your Plotpole-Range and will open / close the nearest handleable visible Door from your Position.
Eventually you have to add some Door classes and add a distance check (if wanted).
To Close the nearest opened Door, just change "_open = true" to "_open = false".
_open = true; _config = 'CfgEpochClient' call EPOCH_returnConfig; _buildingJammerRange = getNumber(_config >> "buildingJammerRange"); _nearjammers = nearestobjects [player,["Plotpole_EPOCH"],_buildingJammerRange]; if (_nearjammers isEqualTo []) exitwith { ["You are not in your PlotPole-Range",5] call Epoch_Message; }; _nearestJammer = _nearjammers select 0; if !((_nearestJammer getVariable["BUILD_OWNER", "-1"]) in[getPlayerUID player, Epoch_my_GroupUID]) exitwith { ["You are not in your PlotPole-Range",5] call Epoch_Message; }; _OpenableItems = ["CinderWallGarage_EPOCH","WoodLargeWallDoorL_EPOCH","WoodLargeWallDoor_EPOCH","Land_BarGate_F","CinderWallDoorwHatch_EPOCH"]; _NearestDoors = []; _fnc_CheckDoorsToOpen = { _NearestDoors = (nearestobjects [_nearestJammer,_OpenableItems,_buildingJammerRange]) select { ([_x, "VIEW"] checkVisibility [eyePos player, [(getposasl _x select 0),(getposasl _x select 1),(getposasl _x select 2) + 1.5]]) > 0.5 && ( _x animationPhase "open_left" < 0.5 && _x animationPhase "open_right" < 0.5 && _x animationPhase "Door_1_rot" < 0.5 && _x animationPhase "Open_Door" < 0.5 ) }; _NearestDoors }; _fnc_CheckDoorsToClose = { _NearestDoors = (nearestobjects [_nearestJammer,_OpenableItems,_buildingJammerRange]) select { ([_x, "VIEW"] checkVisibility [eyePos player, [(getposasl _x select 0),(getposasl _x select 1),(getposasl _x select 2) + 1.5]]) > 0.5 && ( _x animationPhase "open_left" > 0.5 || _x animationPhase "open_right" > 0.5 || _x animationPhase "Door_1_rot" > 0.5 || _x animationPhase "Open_Door" > 0.5 ) }; _NearestDoors }; if (_open) then { _NearestDoors = call _fnc_CheckDoorsToOpen; } else { _NearestDoors = call _fnc_CheckDoorsToClose; }; if (_NearestDoors isequalto []) exitwith { [format ["No Door to %1 found",if (_open) then {"open"} else {"close"}],5] call Epoch_Message; }; _DoorToHandle = _NearestDoors select 0; _value = (if (_open) then {1} else {0}); _DoorToHandle animate ['open_left', _value]; _DoorToHandle animate ['open_right', _value]; _DoorToHandle animate ['Door_1_rot', _value]; _DoorToHandle animate ['Open_Door', _value];