Ghostrider-GRG

Video tutorial that covers editing new crafting menu configs in an upcoming patch. Please note that any current custom cfgCrafting edits you have for old system will break the server and requires to be updated.
Hoping to see some cool releases from you guys!
Enjoy!
 

If you look inside the database with Redis Desktop Manager or something similar you'll see the ban reason, they're stored in 'AHB-log'

I will make the default timeout for this check 180 seconds instead of 90 to help with false positives, till I or someone else find the time to rework this system.

Hi Peeps,
A short little video showing what I am working on: A new HUD for Epoch (Or ArmA 3 in general)

With respect to the developers and recognition of the hard work the put into continuing to add to Epoch, I have watched most of the settings for customization moved out of the mission file, which adds substantially to the work server owners must do to keep our servers running as we intend them to be configured.  I would like to make a plea that there be a config.cpp included in the mission file for basic settings such as build limits, custom zones where building is prohibited, etc. These settings might be included in a config.cpp in the mission.pbo. I have seen config.cpp applied to this purpose very nicely in several modes for Epoch and elsewhere. Asking server owners to dig through the various cfgs and troubleshoot the steps needed to get things working once the description.ext has been modified with little documentation seems a lot to ask.  I am hopeful that future versions will see a little less economy of code and more of an effort the present Epoch as a platform as was said to be the long-term objective a while back.

Thought I would share a nice piece of info about CPU load for running a single server or multiple servers.
 
Server startup parameters via .bat file
 
Example:
 
@echo off
start "arma3" /HIGH /affinity 30 "arma3server.exe" -mod=@Epoch;@allinarmaterrainpack;@EpochHive;@sem;@asm -config=E:\Cherno\SC\config.cfg -port=3302 -profiles=SC -cfg=E:\Cherno\SC\basic.cfg -name=SC -loadMissionToMemory -enableHT -autoInit -malloc=system
@exit
 
So my .bat file looks something like this /HIGH is priority /affinity is which CPU's I will use "your server executable" [Mods you are running] [server config/port/profile/performance config] variables you can use which depending on hardware will either help or hurt your server so be careful with these except -autoinit as this will start your server's mission.
 
/affinity
CPU's then /affinity value
 
0-1 /affinity 3
2-3 /affinity C
4-5 /affinity 30
6-7 /affinity C0
 
Now if you want to dedicate 4 cores
0-3 /affinity F
4-7 /affinity F0
0,2,4,6 /affinity 55
 
 
I hope this helps some of you and the players that connect to your server's

Ok so I have modified base building settings so I am still managing everything in my description.ext as discussed above. However my users are reporting that they are getting the frequency blocked message when building near military, is there an issue with the latest version ignoring the description.ext for buildingNearbyMilitary? here are my settings:
 
class CfgEpochClient
{
    epochVersion = "0.3.4.0";
    sapperRngChance = 100; // increase number to reduce chances and reduce to increase. Default 100 = 1% - 55% if soiled (+ 2% if in city) chance to spawn sapper
    droneRngChance = 100; // increase number to reduce chances and reduce to increase. Default 100 = // 2% chance (+ 4% chance if in city) (1% - 2% Half if using silencer) to spawn drone if shot fired
    buildingNearbyMilitary = 1; //1 to allow building nearby
    buildingNearbyMilitaryRange = 300; //Define radius of blocked area
    buildingRequireJammer = 0; // 1 = to allow building without a jammer
    buildingCountLimit = 500; // how many objects can be built within range of a jammer
    buildingJammerRange = 100; // jammer range in meters

The cure would be to disable or dumb down the anti-teleport check in the default antihack. My understanding is that infiStar does not demonstrate this behavior. Halve has a post on page 21 of this thread that points you in the right direction. His proposed fix did not work for me but there are probably other approaches including a few carefully placed comments.

this was adressed when the current epoch version released ... its not illegal to flip back a page or 2 in order to search for an answer.

No changes required. Our version is linked below
 
https://www.dropbox.com/s/c0t152451v6ke7a/cpcnametags.sqf?dl=0

You need to check your createvehicle.log and see what the reason is for getting kicked
 
Saw your other post. You missed this when you were comparing your createvehicle.txt to the 0310 version..
 
!="I_(Soldier[1-3]|Soldier)_EPOCH"

Let's open Pandora's Box, I'm up for some good Ole fun.

I'm installing this on Chernarus winter in a Lil bit today, wanna see what this bitch got.

Thanks ghostrider for picking this back up, can't wait to peek inside.

This was answered on one of the previous pages.
Just comment out some of the missions spawns:

so i realized that some server owners has been checking out my github and noticed the Taru pods mod/script i made.
 
however, unfortunatly not as many has had the courtesy of actually reporting back to me about functionality/bugs, so i decided to just release it here for everyone to enjoy and i can see what everyone has to say about it.
 
What is this?
 
this script was inspired by this mod:
http://www.armaholic.com/page.php?id=27532
 
one of my players asked me to add this mod, but i feelt that this could be done without having to add an extra mod to every client, so i created this:
 
this is a script that will allow players to attach the taru pods to the base taru that does not have a pod attached by default, if the pod is dropped above 25m height, the pod will be dropped in a parachute, else the pod is just dropped.
 

(more pics soon)
 
i also made possibility to sell pods at the traders without getting in as driver (claim action) that i will be uploading to my github soon.
 
to attach a pod:
Land "on" the pod with a wheel on each side as close as possible make sure wheels are touching ground scroll and use the attach scroll action to attach a pod scroll to detach/para drop it again.
 
to make sure the pod saves new position after being moved, then either enter the pod or change inventory in it.
pods should now save when dropped.
 
so here goes:
https://github.com/Halvhjearne/taru-pods
 
to install this, add to the bottom of your init.sqf:
execVM "addons\taru_pods\taru_init.sqf"; (or wherever you decide to install it, folder is not important)
 
if you have antihack, you will need to disable attach and scroll actions checks (more info on this will come soon).
 
you will also need to add the pods to traders / epochconfog.hpp
the pod classnames are:
"Land_Pod_Heli_Transport_04_bench_F" "Land_Pod_Heli_Transport_04_covered_F" "Land_Pod_Heli_Transport_04_medevac_F" "Land_Pod_Heli_Transport_04_box_F" "Land_Pod_Heli_Transport_04_fuel_F" "Land_Pod_Heli_Transport_04_repair_F" "Land_Pod_Heli_Transport_04_ammo_F"

Well now, its been about a week of 0.3's public release and again no posts regarding this one.
So now everyone has seen the array of Epoch Events in their epochconfig.hpp file.
And I hope everyone has looked into their new epoch_server_settings.pbo file, which now holds an EpochEvents folder.
 
Yep that's right, add an event into that folder and add the filename to the events array giving it a respawn time and voila!
 
You now have your own events/missions baked right into epoch.
So far I have tested a Hunter Mission with random placed objects and 5 Epoch Based AI infantry.
 
I am going to keep it as is but add a line of code for a random vehicle spawn to keep the vehicle count balanced evenly.
 
There is much much more potential here, if you are like me and just like to tinker, check out the main 4 events and you can grasp what they are about. Screw around with a little code and I am sure you will get what you are looking for.
 
Thanks Devs for this update and all these options, we really really needed this!
 
Just a quick dirty (LOL) example

Add a new array for the "Hunter" event and give it a respawn time, then 
Save this code as hunter.sqf in your epoch_server_settings.pbo epochevents folder

_hunterPosition = [epoch_centerMarkerPosition, 0, EPOCH_dynamicVehicleArea, 10, 0, 4000, 0] call BIS_fnc_findSafePos; if ((count _hunterPosition) == 2) then{ _item = createVehicle["B_MRAP_01_EPOCH", _hunterPosition, [], 0.0, "CAN_COLLIDE"]; _item setDamage 0.8; _item setFuel 2; _item setVariable["LASTLOGOUT_EPOCH",1000000000000]; _item setVariable["LAST_CHECK",1000000000000]; //So Vehicle doesnt despawn EPOCH_VehicleSlotsLimit = EPOCH_VehicleSlotsLimit + 1; EPOCH_VehicleSlots pushBack str(EPOCH_VehicleSlotsLimit); _slot = EPOCH_VehicleSlots select 0; _item setVariable ['VEHICLE_SLOT',_slot,true]; EPOCH_VehicleSlots = EPOCH_VehicleSlots - [_slot]; EPOCH_VehicleSlotCount = count EPOCH_VehicleSlots; publicVariable 'EPOCH_VehicleSlotCount'; _item call EPOCH_server_setVToken; //Creates vehicle inventory clearWeaponCargoGlobal _item; clearMagazineCargoGlobal _item; clearBackpackCargoGlobal _item; clearItemCargoGlobal _item; //Static Position Objects _item = createVehicle["Land_Cargo_Patrol_V1_F", _hunterPosition, [],20, "NONE"]; _group = createGroup RESISTANCE; _group createUnit ["I_Soldier_EPOCH", _hunterPosition, [], 10, 'NO_COLLIDE']; _group createUnit ["I_Soldier_EPOCH", _hunterPosition, [], 10, 'NO_COLLIDE']; _group createUnit ["I_Soldier_EPOCH", _hunterPosition, [], 10, 'NO_COLLIDE']; _group createUnit ["I_Soldier_EPOCH", _hunterPosition, [], 10, 'NO_COLLIDE']; _group createUnit ["I_Soldier_EPOCH", _hunterPosition, [], 10, 'NO_COLLIDE']; sleep 0.1; { //Random Position Objects based on distance in array _item = createVehicle[_x, _hunterPosition, [], 50, "NONE"]; sleep 1; } forEach["Land_Wreck_Heli_Attack_02_F", "Land_Wreck_Heli_Attack_02_F"]; if (EPOCH_showShippingContainers) then{ _marker = createMarker[str(_hunterPosition), _hunterPosition]; _marker setMarkerShape "ICON"; _marker setMarkerType "mil_dot"; _marker setMarkerText "Hunter"; _marker setMarkerColor "ColorRED"; }; };

EPOCH VGS by IT07
Here it is :D
Detailed info is in the README.md on GitHub
https://github.com/IT07/Game_code/tree/master/ArmA_3/A3_EPOCH_virtualGarage

Updated code: https://github.com/ravmustang/Game_code/tree/VGS-Overhaul/ArmA_3/A3_EPOCH_virtualGarage

EDIT: please describe what you were doing when this happened. I have heard one player on our servers report ARMA crashes when missions trigger. 

Easy, just find the init.sqf in the custom_server.pbo and comment out the missions you don't want to spawn
 



 
Just add // before the [] execVM line and that line won't be read.

Originally concieved by Blckeagls and supported here with permission
Completely rewritten  to remove bugs and add functionallity.
 
 
Current Version: Version 7.06
Current Build: 239
Description.
Built-in support for Epoch or Exile.
Updated: Built in Headless client support.
New: includes tools to export missions from A3EDEN Editor - minimal editing/scripting required to generate new missions once the design is completed in the editr.
A complete static and dynamic mission system rolled into one.
New:
Many new Missions (Thanks to Thomas_TKO)
CHANGES:   https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf To download go to: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC
For installation see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/INSTALLATION.txt
For a complete changelog see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf
Credits:
    Epoch Mod developer team, and in particular AWOL whose code has provided many lessons in scripting.
  blckeagls - Original developer of mission system 2.0.2   Narines - bug fixes and improvements.   Bill (DBD Clan) example compositions.   cyncrwler for help with troubleshooting and testing   Brian Soanes for helpful changes and performance tweaks.   Grahame for many rounds of testing, feedback and suggestions regarding features.   zxbutchxz for extensive testing of AI behavior. MGTDB for the fix for an issue with interacting with captives/targets on Exile servers. Porkeld for the CBA compatability fixes and debugging. Thomas_TKO for debugging and many new missions. * Additional Credits include authors of other missions systems and scripts who's work influenced this release:
   Halve and He-Man.     Face (A3EAI)     KiloSwiss (SEM)     Hogscrapper (HC missions for A3)     the Vampire (DZMS and VEMF)     The FUCHS (EMS)     lazylink (early A2 Epoch mission system)     Matt11 (Wicked AI) Updates: License
This Mission System is provided under an Attribution Non-Commercial ShareAlike 4.0 Commons License.
http://creativecommons.org/licenses/by-nc-sa/4.0/
 
 

 

Epoch Mod 0.3.2.0 Client Files have been released on Steam Workshop and the rest of the download links on epochmod.com will be updated soon.
 
Server files released on github.com/EpochModTeam
 
Change logs - Also see what server files have changed here.
 
Report bugs
 
Feedback

We all have updated many times over the past months.
We all love updates RIGHT?

Well sometimes these Epoch updates have quite a bit that are different from the last.

1. download the full Epoch_Server_Install pack from github or from the main page here at EpochMod.Com (links below)

Github - https://github.com/EpochModTeam/Epoch
EpochMod - http://epochmod.com/and goto downloads-server
As well as http://epochmod.com/and goto downloads-client

Or use the steam workshop for Client files.

Both the @epochHive as well as the @epoch folders must be updated on each incremental update.
So if you currently run Epoch 0.3.0.4, you must update both @folders mentioned above with the newest downloads for Epoch 0.3.1!

2. Backup the working set that you have on your server.

I generally will do a copy paste of my entire server folder and rename it adding the old version number. For example my back now will be EpochServerAltis0304. Then I will rename the @folders to @EpochHive0304 and @Epoch0304. This allows for you to make sure you don't screw up your old install before getting the newest updates to work and provides you with a way to do WinMerge's or manual merges without fault all while retaining your old setup and not interfering with your players on your LIVE server

3. Prepare for your update

I cant stress this enough: READ, READ and READ some more.
Make sure you know whats been updated and understand, not only to be able to perform the update with ease but also so that you are educated enough to explain to your players What changed and How it will effect them as players in your community.

There are several places you can go for this information
http://epochmod.com/forum/index.php?/forum/43-announcements/

or directly to todays current 0.3.1 update changelog notes on github
https://github.com/EpochModTeam/Epoch/pull/339/files

4. Start your updating process

Now I take my newly downloaded @folders and move them into the EpochServerAltis0304 folder.
You will have 2 folders for the EpochHive to work from. Keeping the newest updated files as your base for your update.
I like to use Notepad++ "move to other view" so that I have a side by side view of the 0.3.0.4(old) and the 0.3.1(new) files.
Again remember that the 0.3.1 files are going to be the base and the 0.3.0.4 files will provide you with your current settings that will be moved into the newest 0.3.1 files.

Then your mission file udpates. Prepare the mission file the same way as above, renaming the old epoch.Altis to epoch.Altis0304 and moving the updated epoch.Altis. Again allowing you to have a smooth update by comparing your old files to the new updated files and adding your settings to the newest updated files.

For those that are newer to the process this will make your update process smooth allowing you zero probability of screwing up your current LIVE build and allowing you to test your update until its perfect before making it LIVE.

I hope that this will help out you newbies out there get your servers updated properly without too much spilled blood, sweat and tears!

ENJOY

Originally concieved by Blckeagls and supported here with permission
Completely rewritten  to remove bugs and add functionallity.
 
 
Current Version: Version 7.06
Current Build: 239
Description.
Built-in support for Epoch or Exile.
Updated: Built in Headless client support.
New: includes tools to export missions from A3EDEN Editor - minimal editing/scripting required to generate new missions once the design is completed in the editr.
A complete static and dynamic mission system rolled into one.
New:
Many new Missions (Thanks to Thomas_TKO)
CHANGES:   https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf To download go to: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC
For installation see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/INSTALLATION.txt
For a complete changelog see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf
Credits:
    Epoch Mod developer team, and in particular AWOL whose code has provided many lessons in scripting.
  blckeagls - Original developer of mission system 2.0.2   Narines - bug fixes and improvements.   Bill (DBD Clan) example compositions.   cyncrwler for help with troubleshooting and testing   Brian Soanes for helpful changes and performance tweaks.   Grahame for many rounds of testing, feedback and suggestions regarding features.   zxbutchxz for extensive testing of AI behavior. MGTDB for the fix for an issue with interacting with captives/targets on Exile servers. Porkeld for the CBA compatability fixes and debugging. Thomas_TKO for debugging and many new missions. * Additional Credits include authors of other missions systems and scripts who's work influenced this release:
   Halve and He-Man.     Face (A3EAI)     KiloSwiss (SEM)     Hogscrapper (HC missions for A3)     the Vampire (DZMS and VEMF)     The FUCHS (EMS)     lazylink (early A2 Epoch mission system)     Matt11 (Wicked AI) Updates: License
This Mission System is provided under an Attribution Non-Commercial ShareAlike 4.0 Commons License.
http://creativecommons.org/licenses/by-nc-sa/4.0/
 
 

 

Originally concieved by Blckeagls and supported here with permission
Completely rewritten  to remove bugs and add functionallity.
 
 
Current Version: Version 7.06
Current Build: 239
Description.
Built-in support for Epoch or Exile.
Updated: Built in Headless client support.
New: includes tools to export missions from A3EDEN Editor - minimal editing/scripting required to generate new missions once the design is completed in the editr.
A complete static and dynamic mission system rolled into one.
New:
Many new Missions (Thanks to Thomas_TKO)
CHANGES:   https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf To download go to: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC
For installation see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/INSTALLATION.txt
For a complete changelog see: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/blob/master/changeLog.sqf
Credits:
    Epoch Mod developer team, and in particular AWOL whose code has provided many lessons in scripting.
  blckeagls - Original developer of mission system 2.0.2   Narines - bug fixes and improvements.   Bill (DBD Clan) example compositions.   cyncrwler for help with troubleshooting and testing   Brian Soanes for helpful changes and performance tweaks.   Grahame for many rounds of testing, feedback and suggestions regarding features.   zxbutchxz for extensive testing of AI behavior. MGTDB for the fix for an issue with interacting with captives/targets on Exile servers. Porkeld for the CBA compatability fixes and debugging. Thomas_TKO for debugging and many new missions. * Additional Credits include authors of other missions systems and scripts who's work influenced this release:
   Halve and He-Man.     Face (A3EAI)     KiloSwiss (SEM)     Hogscrapper (HC missions for A3)     the Vampire (DZMS and VEMF)     The FUCHS (EMS)     lazylink (early A2 Epoch mission system)     Matt11 (Wicked AI) Updates: License
This Mission System is provided under an Attribution Non-Commercial ShareAlike 4.0 Commons License.
http://creativecommons.org/licenses/by-nc-sa/4.0/
 
 

 

Did a quick fix till I can find a better place to put the box. This is to get you up and running.
Change to this in mission.sqm:
class Markers { items = 3; class Item0 { position[] = {10058.347,117.54227,9015.848}; name = "center"; type = "Empty"; }; class Item1 { position[]={13928.687,96.518669,6557.8232}; name="respawn_east"; type="Empty"; }; class Item2 { position[]={13928.659,96.514503,6557.8701}; name="respawn_west"; type="Empty"; }; }; };

The idea behind the change I think is to make it easier to go to different maps. Simply place your respawn and bam insta- portals.