SavageCDN

Yes there is a VAS\config.sqf file - open it up and you can see there is a whitelist and blacklist section. For example I have a CAF mission using VAS which only includes the Canadian weapons, ammo and items. I hear you though regarding limited resources.. for most COOP clan or group missions this is easily done as everyone is kinda on the same page. With a public server and a persistent mission like Insurgency, etc you need something that will not run out of items/ammo... and with VAS it's actually easier to lock things down than creating your own ammo box script. You can also consider respawn loadouts which allow you to assign different configs to players (like the class system - rifleman, grenadier, AT, etc). Remove all weapons/items at mission start and assign each player a 'role' - they will be limited to those items/weapons and gets rid of ammo boxes entirely.. although it's usually best to put down some extra mags/smoke/etc in a box somewhere. http://community.bistudio.com/wiki/Arma_3_Respawn

Really all of the things that this thread deems 'negative' about VAS are completely customizable and up to the mission maker to fix. You can exclude certain weapons/items, add only the weapons/items you want, disable restoring saved loadouts... I mean what's not to like? It's certainly better than throwing down ammo crates and if your mission is a long/persistent one you also don't have to worry about refilling those ammo crates every X minutes. Also as someone mentioned in the Alpha using a fill crate script in MP was a mission-killer hence the birth/evolution of VAS.

Thanks for these as well!! edit: I think the original link is dead

Thanks for this will check it out.

Good to see you keeping up with this great mission!!

edit: nevermind

Do you have an updated PDF classlist by chance? edit: wow nice job on all the flags... great selection!! edit2: Here's what I got so far (no flags and probably missing more...) Infantry Arid "CAF_OFFICER_AR" "CAF_SECTIONIC_AR" "CAF_SECTION2IC_AR" "CAF_SPOTTER_AR" "CAF_SNIPER_AR" "CAF_84GUNNER_AR" "CAF_ATASST_AR" "CAF_C6GUNNER_AR" "CAF_GPMGASST_AR" "CAF_C9GUNNER_AR" "CAF_CBTENGINEER_AR" "CAF_GRENADIER_AR" "CAF_MEDIC_AR" "CAF_RIFLEMAN_AR" Infantry Woodland "CAF_OFFICER_TW" "CAF_SECTIONIC_TW" "CAF_SECTION2IC_TW" "CAF_SPOTTER_TW" "CAF_SNIPER_TW" "CAF_84GUNNER_TW" "CAF_ATASST_TW" "CAF_C6GUNNER_TW" "CAF_GPMGASST_TW" "CAF_C9GUNNER_TW" "CAF_CBTENGINEER_TW" "CAF_GRENADIER_TW" "CAF_MEDIC_TW" "CAF_RIFLEMAN_TW" Vehicles "caf_HLVW_open" "caf_HLVW_covered" Ammo crates "CAF_GPMG_AMMO" "CAF_C7A2_AMMO" "CAF_C8A3_AMMO" "CAF_C9A2_AMMO" "CAF_Optics" "caf_CarlG_AMMO" Backpacks "B_CAF_Carryall" 72 hour ruck "B_CAF_84bag_cbr" brown "B_CAF_84bag_sgg" sage "B_CAF_C6bag_cbr" brown "B_CAF_C6bag_khk" khaki "B_CAF_CBTENGINEER_tan" tan "B_CAF_CBTENGINEER_sgg" sage "B_CAF_Carryall_Medical" medic Weapons "caf_c6gpmg" "220rnd_762x51_Belt" "caf_C7A2" "30Rnd_556x45_NATO","30Rnd_556x45_stanag","30Rnd_556x45_T_stanag" "caf_C7A2_M203" "caf_c8a3" "caf_c8a3_cqb" "caf_c8a3_M203" "caf_c9a2" "200rnd_556x45_Belt","30Rnd_556x45_NATO" "M2CG" "FFV551_HEAT","FFV441_HEDP" Items and equipment "CAF_muzzle_snds" "CAF_muzzle_snds_556_blk" "H_CAF_Boonie_AR" "H_CAF_Boonie_TW" "H_CAF_CG634_AR" "H_CAF_CG634_AR_net" "H_CAF_CG634_AR_scrim" "H_CAF_CG634_TW" "H_CAF_CG634_tw_net" "H_CAF_CG634_tw_scrim" "H_CAF_CREWHELMET" "optic_carryhandle" "optic_elcan" //"optic_elcan_3d" "optic_M2CG" "U_CAF_GhilleSuit_AR" "U_CAF_GhilleSuit_tw" "U_CAF_uniform1_cadpatAR" "U_CAF_uniform1_cadpatTW" "U_CAF_uniform2_cadpatAR" "U_CAF_uniform2_cadpatTW" "V_CAF_PlateCarrier1_AR" "V_CAF_PlateCarrier1_TW" "V_CAF_PlateCarrier2_AR" "V_CAF_PlateCarrier2_TW" My VAS config for CAF:

edit: ^ what he said Just a guess but what about missions that use a function to search for house positions or locations to spawn stuff?

I think that error is due to database.txt file not being in the correct location (look back a few pages they go over this). You can also join the MSO skype channel and they will help you out (that is your best bet).

Why did I decide to come into work today????? :mad: Thanks for the update!!

Yeah and it looks like he'll be releasing stuff for A3 as well

Quoted for truth. NEVER download .dll files from those sites.... you may have been lucky in the past but chances are you'll get nailed with something nasty.

The script Harzach posted is the best for ACE IMO. I'm not sure if they are compatible but you could try DAP's AI medic http://www.armaholic.com/page.php?id=13842 Put this in your init.sqf: ace_sys_wounds_noai= true; - this disables ACE wounding for the AI

I thought they already did this for some of the ACE models in A2?

Thanks for the update!!

+ 1 here :dancered:

Nice%20%one%20%Kylania :) I'm assuming it does some kind of check for each mission to make sure it's the most recent version?

Somehow I misses this before... thanks for the Fallujah version!!

Two words: Briefing Porn :p

Great another one of these threads. At least my ignore list is getting a workout....

Yeah looks great will add it to server rotation

Fapfapfapfap

No problem thanks for fixing it

Ah OK sorry :p For A3 it will throw up a bunch of errors at start and every few seconds for each player (s1, s2, etc) that are not in-game. Most of them are undeclared variable type stuff (hopefully someone with knowledge will have a go at fixing it as I don't think Silola is around for an A3 version). You will also need to change the classname from "dot" to "mil_dot" in the DAC_Config_Marker.sqf file (might be other locations too can't recall) http://forums.bistudio.com/showthread.php?147891-DAC-Arma-3/page2

Drop Zeus... that mod has not been updated in years and can cause conflicts with other mods unless you are very familiar with it and do a lot of testing (ie: ChrisB). Add @ASR_AI instead if you want smarter AI that pop smoke and seek cover. UPSMON should not be the problem especially if it's set up as you described. It's possible there is an issue with your HC I would double-check that AI are spawning on it and not the server, etc. Make sure you have your bandwidth settings right for the HC and that your server.cfg has the HC line (can't remember the syntax ATM). You could also test without using the HC you won't get as good performance but surely you won't get the stuttering and AI not moving... not with just 90 AI.