Ghostrider-GRG

No, for that you need a roaming AI mod, such as A3EAI or DMS/Occupation which I believe DirtySanchez ported to Epoch a while back.

Thank you He-Man. I was on vacation when this was posted.

Thanks - I expect to be making a few more changes to that branch before merging it with the Master. If anyone notes any odd behavior related to simulation management please let me know.

There is a new build now in testing available on the github which includes many bug fixes and code enhancements. Many thanks to He Man for looking through and working on the code. https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/tree/V-6.88-Build-160

Updated to V 6.86 Build 155 to add some new functions and a set of tools for pulling missions from the editor without a whole bunch of copy/paste or reliance on editor plugins.

For 'blck_configs_epoch.sqf', there is near-duplication. It looks like I meant to have a conditional preprocessor command there to add the biopod provided by Apex. I will update accordingly. You are correct about bipods, silencers etc. See \custom_server\Compiles\Units\GMS_fnc_spawnUnit.sqf lines 131-135 for how this is coded.

Appologies - I did not. My bad.

I just created a new branch on the GitHub for Build 152 (Experimental) which adds two new functions: 1) I included tools and templates with which one can easily export mission configurations from the editor. You now just need to run one script for the markers and second for everything else, paste the output of each script into the template and add the new mission wherever you like. 2) One can now spawn AI in buildings. AI can be placed in specific locations in the editor, or you can designate a building as a location for AI, and AI and statics will be spawned at the predefined Arma building positions. See the directions for more information about designating buildings for use for garrisons using the Arma building positions. You do need to place a marker object inside the building. I also added a new feature for static missions AI patrols whereby you can limit the number of respawns. Setting this value to -1 disables tracking of number of respawns. That is the default, and the mission are backwards compatible with older builds of blckeagles. Download this updated version here: https://github.com/Ghostrider-DbD-/blckeagles-revisited-RC/tree/Build-152

There are four variables you could increase: Alert distance, which the maximal distance from an AI killed or hit that will result in the group leader being given info about the players location. Intelligence, which translates to how much information the group leader gets, where 4 would be a great deal. baseSkill, which is the overall skill level of ai before any modifiers are applied. spotDistance and spotTime, which are self-explanatory. 1.00 is maximal here. Start increasing these and the missions should get harder. blck_AIAlertDistance = [250,425,650,800]; // Radius within which AI will be notified of enemy activity. Depricated as a group-sed system is used now. The group is informed of the enemy location when a group member is hit or killed. //blck_AIAlertDistance = [150,225,400,500]; // How precisely player locations will be revealed to AI after an AI kill // values are ordered as follows [blue, red, green, orange]; blck_AIIntelligence = [0.3, 0.5, 0.7, 0.9]; blck_baseSkill = 1; // The overal skill of the AI - range 0.1 to 1.0. /*************************************************************** MISSION TYPE SPECIFIC AI SETTINGS **************************************************************/ //This defines the skill, minimum/Maximum number of AI and how many AI groups are spawned for each mission type // Orange Missions blck_MinAI_Orange = 30; blck_MaxAI_Orange = 35; blck_AIGrps_Orange = 5; blck_SkillsOrange = [ ["aimingAccuracy",0.6],["aimingShake",0.9],["aimingSpeed",0.9],["endurance",1.00],["spotDistance",1.0],["spotTime",1.0],["courage",1.00],["reloadSpeed",1.00],["commanding",1.00],["general",1.00] ];

Just start Arma3Launcher before starting the server. It will stay running if configured appropriately. You can start/stop your server and Arma 3 client any time and come back to restart Arma 3 client at a later time if for some reason it freezes or crashes.

Ahh I don't have them sorted on Exile

The hostage and capture missions work fine on Epoch as of the latest release on the Master branch. If you encounter problems let me know. Please note that interacting with these entities required some changes client-side so please be sure to update your mission.pbo accordingly.

Its a great map, with custom though simple trader cities, day/night, and the GRG version of blckeagls mission system which adds new missions. hope to see you on the server.

It looks from the command line that you are not loading GMS. If your provider does not allow you to change -servermod=... to -servermod="@epochhive;@gms" then just upload custom_server.pbo from @gms\addons into your @epochhive\addons folder and that should do it. The only thing you loose by doing this is optional headless client support on that particular Arma install. You can verify that everything is working by reading through the server .RPT files located in the SC directory shown on your screenshot. I just search for [blckeagls] ... and you should find the log entries as the mission system initializes.

From what you describe it sounds like you didi\ not unpack your Epoch.<MAP_NAME>.pbo and: 1. place the init.sqf and debug folder inside the unpacked folder; 2. repack the mission pbo. Missions should spawn and markers indicating their positions should show up on the map even if you neglected these steps. Note that it can take 5-20 min for missions to spawn. You can see if the mission system started server-side by checking your .RPT file. This is usually found in a directory named \SC, a subdirectory of the folder in which you placed @Epoch and @GMS. If the system loaded then you should see a bunch of lines beginning with [blckeagls] ... If you do not see those entries in the logs then there is probably and issue with the command line for the server.