MDCCLXXVI

http://www.ahoyworld.co.uk/topic/2495-submit-your-questions-here/

our community hosts an edit of I&A and a few weeks ago I added this: briefing.sqf _null = [] execVM "briefing.sqf"; minus the shoddy formatting, maybe a template for people hosting the mission.

very handy ty

I'll test this in the next day or two and report whether it's stable or not. The weapon resting part of it was never an issue, only the weapon/firing effects.

looking into it could be some server<------->mission configuration is required 2.70 was tuned for AOs to take about 40-60 minutes with 30-40 average pub players, though that is with FFIS mod running serverside, and parameters abit different from whats currently on EU1 and 2. lowering quantity of troops and some parameter settings will naturally bring that number down slightly. it depends how AW wants it to play. weapon restrictions is a topic for a separate thread i think you'll find many public players will be irate when they find their favorite kit from the VAS box no longer has a Nightstalker attached. some basic further restrictions that could be implemented, food for thought: - GLs to grenadier only - LMGs to Autoriflemen only - Satchel charges to Explosive spec only - Pilots = no primary weapon - [ may already be in 2.70a, i forget] close the loophole whereby players can pick up enemy titan launchers and save to VAS - [if implemented] Ammo bearer only, for Carryall backpack - remove Nightstalker, TWS, TWS MG optics from VAS and integrate them into SM rewards (cant be saved to VAS anyways). - rangefinders and laser des can also be attributed to a certain class only ^ while promoting role play, you might find people will be angry esp with the nightstalker and LMG restrictions. tread carefully!

The version on EU #2 right now is a bit different.

Arma 3 Main Menu -----> Configure ------> Game -------> Difficulty -------> Auto Report = Disabled To do it on a server, you would have to drop those config options into your DefaultServer.Arma3Profile and then set AutoSpot = 0

I've removed them on my version for just this reason. It causes issues with BLUFOR recognition and map markers. Pilot makes a hard landing and injures a passenger at the AO, comes back to base and gets gunned down by the bots. Even worse (imo) is that his name and BLUFOR tracker map marker disappear from the map. He is reclassified by the AI as just 'Man' with purple dot. I'd like to put an empty AA vehicle at base that guys could jump into and use when needed .. But that just becomes a juicy tool for trolls. The AI-controlled Cheetahs were a good idea but in practice it seems theres some issues with BLUFOR recognition.

Re the enemy waypoint issue for some of the fireteams I think Jester has fixed that for next release Spetznaz human enemy would be cool, but any sort of human opposition would create havoc with the mission. ie. assume enemy has command of 100+ OPFOR and there are only 10 human players on the server ... there is some merit to having an admin-only MCC-like tool whereby a responsible admin, when on, could spice up the missions abit. the new EOS tool in use opens the possibility for lots of small random encounters around Altis, im sure the AW Dev team have some ideas.

It is possible to some extent, to adjust how they are randomly spawned around the objective. It seems to be more fun when the defend circle is a bit tighter. And its a fine balance of how many AI are added, because there is no adjustment for how many people are on the server at the time. If 50 people = 50 AI spawn. If 5 people, 50 AI spawn. So difficulty has to be moderated abit, both for that and server performance. The only issues I've had with AO Retake so far that I'm having trouble resolving: - is sometimes an AI squad or two not de-spawning. after a few hours the map is littered with stray AI. - One of the AI squads always spawns at coordinates 1010 (the narrow bit of land connecting the mainland with the Skopos peninsula. right beside Drimea) * ^ in EOS there appears to be a waypoint cycle around that location. I'll try to dig it out of the files and post here if I can get rid of that waypoint spawn.

This seems like just a cosmetic change. I suppose it could be done without too much trouble. Would be neat to go up against BLUFOR some time too. I am working on an I&A mod that contains parallel AOs, one main and one "side AO" which is Independent-related. more light infantry and less heavy armor. As it stands now, its hard for small teams to really affect the battlefield, even at side missions, due to all the armor. Some small objectives with 8-16 infantry and no armor would be a nice change and attract people to even a lightly populated server. When I'm done I'll post the relevant information somewhere here

Just about done my head in trying to sort this one out. Trialed all sorts of arrangements and spawn conditions for the UAVs, they still blow up when trying to connect to them about half the time or more. Spawning them flying doesn't work too well due to respawn issues. AFAIK they occupy more space than they actually appear to. When the AI pilot and gunner spawn into the vehicle, I believe they appear below-ground, underneath the UAV. Instead of them 'moving in' to the UAV, the UAV appears to 'move onto' them, causing it to spawn 'again' slightly underground and then maybe its a toss of the dice (combined with server performance) whether it rises up correctly or collides with the terrain and poof.

Just a little update. Note sure whether I broke something in recent versions but even adding it to individual vehicles doesn't seem to work correctly (anymore). after respawn it has all its default inventory back again. you fixed that with the "if((_unit isKindOf "B_MRAP_01_F") OR (_unit isKindOf "B_MRAP_01_hmg_F")) then {clearitemcargo _unit; clearWeaponCargoGlobal _unit; clearMagazineCargoGlobal _unit;};" line which Ive had hard trouble replicating just adding to individual vehicle inits. in order to make them functional for custom loading without despawning of inventory items. -- on another note, have AW tried to find a workaround for the chat-disappearance/stream-friendly UI issue? Some Wasteland servers don't seem to be afflicted by it. I wonder if it is a client-side default issue, or serverside, or just Bohemia/Arma issue. I poked through some server cfgs and mission sqfs but couldn't find anything that might lend itself to a solution.

The way the clearMagazines; clearCargo script has been implemented, has caused any gear that is loaded into an affected vehicle by players, to disappear after a short time. Example: Get an 'emptied' Hunter from the motor pool. Load with rockets and ammo. Drive to AO Get out to shoot. Go to vehicle for rockets/ammo. Vehicle cargo empty again. --- I've had better luck just applying the clearCargo; clear Magazines script straight to the particular vehicle init rather than applying it to all vehicles of a certain type. It also allows some vehicles of a certain type to retain their stock cargo/mags for grab-and-go use.

loving the new Retaliation feature Jester !

I agree re infantry-based those were good days in the beta, spent most of my play time on AW US#1 and #2 I 'contructed' a couple AOs to the north end that weren't there in the Stratis Annex I remember on AW. Dont recall ever going north of Agia Marina/Rogain so I put an AO up there. "Transmitter Station" "Hill 144" are the two fabricated ones (look for the yellow blobs in editor ) I did not put back the "Lighthouse" AO on the southern tip, as AI used to get stuck in the rocks by the coast.

Decided to port 2.57d Annex back to Stratis (for our servers), maybe save Jester a little effort if he wants to adapt back to AW. https://www.dropbox.com/s/4qib15n9y7zxod3/co40_AW_Invade_%26_Annex_2_57_4.Stratis.pbo known issues: - needs a 3-sided highwall box constructed around UAV spawn (pull it out of hangar too) to prevent long-range targeting by enemy heli. - I didnt bother to reduce AO diameter by too much. Id suggest reducing it to 400m-500m. - OPFOR artillery might be a little much for Stratis, perhaps replace with mortar team. - OPFOR tanks when on the hill north of Agia Marina can target the helipads at base. - enemy heli also spawns perilously close to base over Agia Marina. It is just the PO-30 Orca but can be a nuisance.

Is 2.56 being freely released for hosting? If not, what is the cost for rights to host it? cheers - Stallion 6-4

couldnt make it sounds like it was a great time!

It also only affects players who are de-synced.

I'm actually surprised an Assault ship isnt in the vanilla game, what with all the amphibious vehicles.

I like the idea but it is not compatible with the current I&A mission, IMO. with respect to gameplay. That said, when I fly the MH-9 I usually co-ordinate with a Medic and Repair specialist for certain tasks, but it is not formal. Here is a problem with you idea ... when you have casualties down in the field, they are usually in 'hot' areas. combine that with the 10/10 enemy AA defenses who can fire a Titan up your ass from 5km away ... It is not a situation where CSAR (combat search & rescue) can operate effectively. If you want tactical inserts/extracts like that to be feasible, the mission would have to be altered to drastically reduce the capabilities of enemy guided AA, instead giving them RPGs instead of Titan launchers. If that was done, then yes it would be possible.

Can you clarify: Can only Arty slot use it still?

That would be a handy feature to have, and a very convenient time for a consistent server reboot. From another angle, it would also cut down on some gameplay logistics since the next sequential AO would be close enough for vehicles to traverse without an airlift. That alone would cut down the need for a fourth pilot slot, if the AOs are close to each other. Being objective however, if the AOs are close it tends to encourage swarming instead of using the helicopters/transit methods as a time to rejoin their squad. Not too sure about having an AO spawn at the airbase though, its a handy spawn point for BLUFOR. I don't think this aspect is high on the priority list, but if a re-write was to come, here's my take on it: Have a few different, parallel versions of the mission ie. 2.51a ie. 2.51b ie. 2.51c Each with a different set of AOs, perhaps with some overlaps of the more popular ones. The reason for the above is that ArmA 3 is really server-intensive and after a few hours of AOs, performance degrades to the point where people begin to complain and rally support for a #vote restart So if there were say, 6 AOs on each a/b/c then after a Mission Complete of (a), we could vote for ( and fire that one up for a new set of AOs while retaining the mission itself, after ( , we load up © to complete the series. I disagree with the AOs spawning in a predictable fashion though. That would encourage players to break off from the ongoing AO and get into their favorite shooting position before the next AO starts (ie. Static AA launchers). I believe the random spawning is important to prevent exploitation in that manner. cliffs: separate the AOs onto a few different, parallel missions, so that we can have more total AOs that are playable in harmony with server limitations. dont make AO order predictable, or it will be exploited cliffs of cliffs: another thankless task added to Mount To-Do-List

im going to withdraw my name from the hat cant make it during the time windows posted