Copey

Upon us we find a great opportunity, and it brings great delight for me to inform you of decisions regarding the forward progress of the server and community. It has taken a great deal of time and discussion to reach this decision, but we now feel that it has been sufficiently planned - and, well…discussed. Following a unanimous vote amongst the AWE staff team, we are progressing with enacting these changes.
 
In addition to the changes detailed in this post, more will soon be announced that will contribute to the direction we seek for AWE, moving forward. As such, keep your eyes turned towards the AWE section of the forum. We are excited to deliver the new direction - and we hope you are too!
 
Monday 19th of June 2017.
 
Put a reminder in your calendar, this is when the changes will take effect (ensuring there are no snags or hiccups during the process).
The Steering Committee has reached the decision that the CUP, and all its dependencies will be removed from the modpack, and therefore the modset. The total list of removed mods, and their size, is:
CUP Terrains Core 7.8 GB CUP Terrains Maps 2.1GB Project OPFOR 1.5 GB Abramia 0.213 GB Isla Duala 0.328 GB Lingor and Dingor 0.633 GB Fallujah 0.201 GB  
The following mods will also be removed due to lack of development by authors, or bugs. This is pursuant to separate decisions by the Steering Committee, and are being enacted during this update.
Burnes_AAV 0.057 GB Spec4gear 0.391 GB  
This yields a reduction in repository size of 11.723 GB. 
 
As a result, several new maps will be added; these are:
JBAD Buildings 1.3 GB Lythium 1.0 GB Bornholm 1.5 GB Bozcaada 0.137 GB  
This totals 3.937 GB in additions.
 
Overall this gives us a 7.793 reduction in modpack and repository size. Reducing the size of the modpack is not our driving force in these changes, but rather a desire to offer a new, innovative and refreshing experience to the AhoyWorld Enhanced player-base.
  
These will be the core modded maps for AWE moving forward. Other maps will be added; however, they have not been decided upon, yet. Anything that has JBAD as a dependency will be considered, alongside stand-alone maps. Fayshhkabur, ToraBora are good examples of maps we are looking to consider.
 
The new playable maps will be:
Altis Stratis Tanoa (Will not be in gauntlet rotation) Gorgona Lythium Bornholm Bozcaada Kerama Islands (possibly)  
Other mods are also under consideration stemming from the request area of the forum. These have not yet been finalised and so have therefore not been included.
 
 
Best Regards,
 
Copey, Skullcollector and S0zi0p4th,
The Steering Committee of AhoyWorld Enhanced.

Upon us we find a great opportunity, and it brings great delight for me to inform you of decisions regarding the forward progress of the server and community. It has taken a great deal of time and discussion to reach this decision, but we now feel that it has been sufficiently planned - and, well…discussed. Following a unanimous vote amongst the AWE staff team, we are progressing with enacting these changes.
 
In addition to the changes detailed in this post, more will soon be announced that will contribute to the direction we seek for AWE, moving forward. As such, keep your eyes turned towards the AWE section of the forum. We are excited to deliver the new direction - and we hope you are too!
 
Monday 19th of June 2017.
 
Put a reminder in your calendar, this is when the changes will take effect (ensuring there are no snags or hiccups during the process).
The Steering Committee has reached the decision that the CUP, and all its dependencies will be removed from the modpack, and therefore the modset. The total list of removed mods, and their size, is:
CUP Terrains Core 7.8 GB CUP Terrains Maps 2.1GB Project OPFOR 1.5 GB Abramia 0.213 GB Isla Duala 0.328 GB Lingor and Dingor 0.633 GB Fallujah 0.201 GB  
The following mods will also be removed due to lack of development by authors, or bugs. This is pursuant to separate decisions by the Steering Committee, and are being enacted during this update.
Burnes_AAV 0.057 GB Spec4gear 0.391 GB  
This yields a reduction in repository size of 11.723 GB. 
 
As a result, several new maps will be added; these are:
JBAD Buildings 1.3 GB Lythium 1.0 GB Bornholm 1.5 GB Bozcaada 0.137 GB  
This totals 3.937 GB in additions.
 
Overall this gives us a 7.793 reduction in modpack and repository size. Reducing the size of the modpack is not our driving force in these changes, but rather a desire to offer a new, innovative and refreshing experience to the AhoyWorld Enhanced player-base.
  
These will be the core modded maps for AWE moving forward. Other maps will be added; however, they have not been decided upon, yet. Anything that has JBAD as a dependency will be considered, alongside stand-alone maps. Fayshhkabur, ToraBora are good examples of maps we are looking to consider.
 
The new playable maps will be:
Altis Stratis Tanoa (Will not be in gauntlet rotation) Gorgona Lythium Bornholm Bozcaada Kerama Islands (possibly)  
Other mods are also under consideration stemming from the request area of the forum. These have not yet been finalised and so have therefore not been included.
 
 
Best Regards,
 
Copey, Skullcollector and S0zi0p4th,
The Steering Committee of AhoyWorld Enhanced.

There is, and we have used it in the past. However, it introduced some issues regarding a bug. This bug meant people suffered broken legs constantly and it was not possible to fix without staff being present to manually execute a code. This bug does now have a fix but it can be cumbersome in its implementation.
Broken legs are not something we at all want to return to

There is, and we have used it in the past. However, it introduced some issues regarding a bug. This bug meant people suffered broken legs constantly and it was not possible to fix without staff being present to manually execute a code. This bug does now have a fix but it can be cumbersome in its implementation.
Broken legs are not something we at all want to return to

When we had no insta death no matter what, the gameplay devolved as did player skill. Massively. Players just rushed head-on with no fear of dying, because they couldn't, in fact, die.

Yeah I've seen this happen repeatedly for @hobnob . Pain in the rear end, perhaps try and use the black hawk, Super Stallion or Merlin moving forward?
 
Sent from my ONEPLUS 3T using a phone app that is really irritating because it constantly advertises itself.
 
 

Name: Operation Baker
 
When: 24/05/17
Time: 1900 UK Local (GMT +1). Check here for your local time!
Expected length: 2 hours
 
Server: EU1/EU2. It will be decided at the start time of the event
 
Hosted By: Chutnut (Spartan)
 
It is highly recommended that players join Teamspeak during the event.
 
Description: Defecting CSAT Scientist's are defecting to NATO, They wish to continue their work but for NATO, Your job is to transport these scientists and defend the facility they worked in until they have set up everything, Expect CSAT to respond to this, You will be able to hold out the facility with weapons and vehicular armament provided.
 
BLUFOR ASSETS:
A164 or Black wasp (Players may only choose 1)
Blackfoot
Slammer
Panther or Marshall (Players may only choose 1)
Two transport trucks (One will hold the scientists)
Two Prowlers/Hunters
 
Other notes:
If the scientist's die the mission will not fail and instead some of our own (NATO) Scientist's will arrive instead and instead of setting up the work will retrieve the work they have for analysis.
 
 

Name: Operation Baker
 
When: 24/05/17
Time: 1900 UK Local (GMT +1). Check here for your local time!
Expected length: 2 hours
 
Server: EU1/EU2. It will be decided at the start time of the event
 
Hosted By: Chutnut (Spartan)
 
It is highly recommended that players join Teamspeak during the event.
 
Description: Defecting CSAT Scientist's are defecting to NATO, They wish to continue their work but for NATO, Your job is to transport these scientists and defend the facility they worked in until they have set up everything, Expect CSAT to respond to this, You will be able to hold out the facility with weapons and vehicular armament provided.
 
BLUFOR ASSETS:
A164 or Black wasp (Players may only choose 1)
Blackfoot
Slammer
Panther or Marshall (Players may only choose 1)
Two transport trucks (One will hold the scientists)
Two Prowlers/Hunters
 
Other notes:
If the scientist's die the mission will not fail and instead some of our own (NATO) Scientist's will arrive instead and instead of setting up the work will retrieve the work they have for analysis.
 
 

Hello!
 
We are pleased to introduce a new team within AhoyWorld - “Outreach”. This team will be responsible for media distribution and communications within and outside AhoyWorld.
 
What are our aims?
 
The team has two main objectives within AhoyWorld. The first is to ensure that the staff have clear lines of effective communication with the AhoyWorld community. This is to ensure that any announcements are transparent and made to a professional standard.
 
The second aim is to increase the social media presence of AhoyWorld on all social media platforms. We believe this will improve player interaction through social media and will promote the community and the AhoyWorld servers, with important announcements also appearing on our social media.
This also means production of new media to promote AhoyWorld servers, and encourage greater player attraction  to  our community.
 
Our team
 
We are a five man team that consists of both players and staff members. This is to ensure that we can get feedback on updates from all levels of the community before changes are made and the announcements are published. We have decided on a team that will attempt to represent both our public servers and the Enhanced server equally.
 
MuckDuck - Team Lead Ghostdragon - Website Coordinator D.Devil - I&A Coordinator Amentes - Spartan Contact Kingfisher - Media Coordinator Origins  
We feel that the Outreach initiative will open up new and transparent avenues of communication to benefit the community as a whole. As such we hope to engage you all in discussion and get everyone involved in the goings-on of AhoyWorld.

 
Regards,
The Outreach Team

FAO All:
 
Mission will be re-run this Saturday, as the mission has been entirely remade by Tut. We hope this has fixed the issues preventing it from running correctly last time, and we thank you for your patience.
 
Regards,
Copey

FAO All:
 
Mission will be re-run this Saturday, as the mission has been entirely remade by Tut. We hope this has fixed the issues preventing it from running correctly last time, and we thank you for your patience.
 
Regards,
Copey

FAO All:
 
Mission will be re-run this Saturday, as the mission has been entirely remade by Tut. We hope this has fixed the issues preventing it from running correctly last time, and we thank you for your patience.
 
Regards,
Copey

It did this pre jets dlc. It's a flight model problem bug with RHS

People taking less ammo on purpose is a very serious problem, but i dont think this is the solution. I would suggest a good old fashioned shouting at as a solution for that. when you have a AO thats set to nightmare and even with vortex on eagle you're surrounded by btr's and bmp's, that rpg would come in real handy.

I have not seen any problem with players using Russian equipment or purposefully taking too little ammo to justify taking enemy weapons. And the option to use enemy weapons have saved my ass plenty of times when prolonged combat has eaten all of my ammo and imidiate resupply was not available or possible
 
or we have used our M72/at4s  and we have a tank that mat cannot deal with  then I usually borrow rpg 26s until M72s or at4s are available via ammo crates or someone brings a back pack with it.
 
And if it was such a huge issue that it was needed
 Why have I not heardabout this from the admins or the moderators or the playerbase In General?

If you get shouted at, there's a damn good reason for it 
 
But, I must say; I approve @Stip hahaahaha

Sure, but then I don't recall having or seeing anybody else have a reason to yell at you

Good morning everyone.
 
First off, some mumbling on my behalf.
 
For years now I have been watching various youtube videos on arma gameplay, and I was always keen on the ACE games and the large scale co-ops and I was always so very fascinated by them. Damn, i even lay at night trying to fall asleep dreaming about these scenarios. All the depth and realism involved makes this so addictive.
 
So far I only knew how to play the public servers that one finds online, which is littered with trolls and solo-heroes. 

I then finally took the time to download and install all the mods required for AWE, and when  I logged in the for the first time, I was in heaven .
 
Going through the arsenal the first time was intimidating. All the small gadgets and tools, and various "thingies" in there. Sure, on youtube it all seemed to simple and easy, especially the med stuff, all the different bandages, shots, etc...
 
I then went on to setup and customize a loadout and play style for a marksman (my fav class on the public servers). Offcourse all i knew at that time was from my experience on public servers, as in pull out rangefinder, get range, click on PageUp to get the range, and just start firing at targets, with good hits most of the time.
 
On AWE though at first (without the great help and support from the people here) i saw that after a few hours of gameplay, i actually didnt hit a SINGLE target .
 
So after asking some of my nice fellow players and team-mates (who were really all very friendly and helpful, thanks guys) i learned how to aquire the range of a target here on AWE, how to use the range card to setup the scope, and how to calculate wind effects on long range shots. I went out far away from base solo and just tried to experiment a bit, getting a range of a tree or a rock, using the range card to help me adjust the scope, and then finally getting the hang of hitting a target with the wind calculations. I was so happy and proud that i finally manage to hit a target (a tree at 500m).
 
So i go out on a mission again with a team, and look there, few hours later, i come back to base, with 0 actual hits on targets.
 
Please do not get me wrong, by no means is this post a rant or complaint. I really love it, its awesome. But there are some questions that arise.
 
Example and question 1:
 
I was running down a hill with a small squad (me being a marksman). At some point an enemy technical came racing towards us. My SL said: Marksman, take down gunner.

At first i didnt even see or find the technical. By the time i saw it it was closing in fast. I took out my rangefinder, and for some reason, i couldnt get it to give me a range ( is there some limit on how many uses, or if its too far away, it won't give a range? ), and by the time i got the range and hit the keys to get out my range card the technical was already taken care off.
 
So my question here is:
 
First i need to get a range, which doesnt always show or work.
I then have to get out the range card to see what i need to set on the scope.
I then need to adjust the scope.
 
How can all this be done the moment the team comes under attack, or a target needs to be taken out asap?
Thers not time to go through all these steps. By the time i get the range, or the range card, its already too late (either we are dead, or target is already gone/dead).
And me in a moment like that asking my team whats the range, is not right either (makes me sound like i can't wipe my own ass)....

So am I missing something here? How does someone using a marksman role get ready for a shot within seconds of sighting an enemy?

Are there any tips that you can provide on this?
 
Question 2.
 
I would love to also try the vortex role, but before I take a vortex slot on AWE and become fudder, is there anything I need to know (compared to the normal public servers) when flying? Is there any difference? Any surprises or extra knowledge needed? I don't wanna jump in blind and get my team killed in mid air)...
 
 
All in all, my experience so far on AWE is really nice, im loving it (although I suck really bad so far at it) but its truly everything I was looking forward for years. I just hope you folks have the patience to put up with me till i get sorted and learn all the stuff required for AWE. Im going daily through a ton of vids, tutorials, guides, reading a lot of forums and so on but in the end, I need to be able to accomplish all that in the field too.
 
Also thanks to all the folks who helped me get sorted this far, I really apreciate it.
 
Regards,
Theronas

What do sprinters eat before a race?
Nothing, they fast.
 
Oh god I'm not proud of that.

Ahoy,
 
Those of you that have been with the crew for a long time will know our beloved server, the mighty "Flagship". It's only fitting that tribute be paid to her as she has served us well over the years.
 
She's seen 3 captains in her days on operations and many different staff have manned her gun ports (giggedy), Hosting things like ArmA, Teamspeak, Squad, Kerbal space program, Farm sim, various racing titles, and probably more titles. It's fair to say that many people have enjoyed her service (how many innuendos?). However there comes a time when you need the Germans to build us a new one.
 
And so, she has been laid up in dry dock and the new Flagship'o the line is setting sail out of port, her sea trials went well and we're happy that she's going to be available for all you scurvy dogs for all of your future adventures! (Special thanks to Soziopath for his hard work in this). That said, never forget the great times you had on our beloved Flagship, those memories are priceless.
 
Lads, charge your glasses and raise them high!
To flagship!

Depending on if it goes smoothly it will be held later after its moved, if not it will be postponed to next Friday =)
Sorry for any inconvenience this will make 

I'll re-iterate here what I've said in practice and in other places.
 
I believe the following illustrates how leadship on AWE "should" work: imagine the objective is to destroy an enemy radar installation.
 
1) at the Platoon Commander level:
a) before the operation begins, the PC organizes the rough plan of how all the squads are meant to carry out the overall objective. How infantry is to be inserted and extracted, what the heavy asset teams will be doing to support the infantry, and who is responsible for what level of the overall plan.  If players need to re-slot to take on different roles, it's coordinated by the PC.
b )  during the operation, the PC serves as a traffic coordinator - managing the flow of information and requests from one squad to another.
 
2) at the Squad Leader level:
a) before the operation begins, the SL coordinates with PC to determine best how they will be used in the mission. The SL can offer suggestions and debate heatedly over proposed landing zones, avenues of attack and so forth, but ultimately the PC has final say on what will happen.
b ) during the operation, the SL implements the plan on a strategic level, making adjustments based on developments that arise in the field. A pilot may choose a different LZ because the intended LZ has enemy units on it; an infantry squad leader my choose to send the squad in a different direction due to terrain; a HAT team may choose a different overwatch point based on limited visibility.
 
3) at the Team Leader level:
a) before the operation begins, the TL receives the mission plan from the SL and ensures that his team has the proper resources to accomplish their part of the mission: for example, in the radar installation objective, if their infantry squad has an engineer, ensuring that that soldier has adequate explosives to do the job. Ensuring that there is a backup in place. Ensuring that autorifleman assistants carry the right type of ammo for the autorifleman. That sort of thing.
b ) during the operation, the TL implements their part of the plan on a tactical level, making adjustments based on developments that arise in the field. For example, the Squad Leader of an infantry squad may push the part of the plan that has the fire teams pushing up a hill, but if the fire teams are taking major fire from entrenched positions, the FTL has the tactical authority to choose another path, or pull back to avoid taking losses, perhaps suggesting the help of a support team.
 
I find AWE works best when leaders at all levels avoid micromanaging the level beneath them; there is a real attraction to do so, but ultimately it makes your own job harder and takes away the job of the person beneath you. Yes, they may not appear to be doing what you've told them ("I have told Alpha 1 to move up onto that ridge, and they are still there in the valley. What are they doing?") but usually there is a good reason, and if there isn't, that's when you may need to investigate further.
 
In all of this it should be stressed that the leader at the particular level is ultimately responsible for the well being of the units under their direct command. Players must follow the chain of command, but they do so to the best of their ability and in a way which doesn't violate other rules - so if ASL is telling you to charge across a field that's being pounded by artillery shells, this could be interpreted as inciting to teamkill.
 
- R

Stay on topic, leave policing of English literature to Oxford please.
 
All leadership ideas go here: 
 

Having read what was posted while I was typing that - be careful not to drift off topic.
Even if no finger pointing was intended, it may be perceived; so just be mindful of what is being said.
 
Ta