Kingfisher

-hud

My Resignation.
 
First let me say this is not a decision I have reached lightly, nor without great turmoil; it has taken me a considerable effort to reach this decision. If you don’t want to read further into this (but I’d suggest you do); the short version is that I am resigning from all AhoyWorld administrative responsibilities with immediate effect.
 
There have been many great times spent on this server for me, at this point I easily have 1000+ hours of Arma 3 invested with AhoyWorld. I remember the days when I first came to the server, fresh out of a milsim unit, and looking for something just as serious, but more chilled out. EU3, as it was then, was just what I wanted. Back in what I can only describe as it’s heyday back then, 3 was one of the best environments to game in; full of fun, approachable and ultimately very caring people. You had a laugh, but you got the job done while you were at it - you would fight tooth and nail for your team-mates.
In contrast: if I were to compare this to the current environment of AWE, I find myself reaching a stark conclusion - it is nothing close to that now. The AWE we all know now is not one true to the original spirit of EU3. 
 
Not being of the original spirit of EU3 is a crucial issue to me; for now over a year I have been part of the team at the top of AWE. We came into being at a time of great uncertainty for EU3. We worked hard, extremely hard to arrest the freefall the community was facing at that time - and we did just that. In the short term we even enabled the server to prosper - player numbers went up. We managed to start rebuilding. But something went awry along the path, it has led us to the place we find ourselves now. A server where everything has been done with the best intentions, done for the right reasons, but not yielded the right results.
 
I set myself the personal goal of redeveloping EU3, making it into something better than what it had been before steering committee came to be. I wanted, and still do, to leave AWE in a position of strength, a position much better than the one it had been in. I have come to the realisation that this is something I have ultimately failed to achieve. And I hold myself personally accountable for that, for right or for wrong, for better or for worse. I have reached a point in life where I feel I have given everything there is for me to give to AW. Every time we have reached a milestone with AWE, I have known that we can do better, do more. This is perhaps why my goal has proven so elusive. However, the will to push forward, to do more and be more is no longer with me. I find myself more going through the motions, than actively driving myself to do better. I have lost the motivation to continue to fight forward. I must confess that I have been carrying on for some time knowing I perhaps needed a break, but I’m a give it your all, or not at all type of guy. I tried to take some time off during a holiday in the summer; it didn’t go well. Let’s just say there was a heated discussion amongst the staff team. Ultimately I felt that I had to do my part, step up to the plate as part of the team. That stopped me from taking the time away I probably needed to. It speaks to a larger issue within the staff team at AhoyWorld; but I’ll come to that further in.
 
Amentes made me aware of sunk cost fallacy, and this pretty much describes my feelings towards the situation I find myself in, perfectly. I have poured my heart and soul into AW, often to the detriment of other things in my life - but that’s the type of person I am, and I make no apologies for that. It is this total commitment, and the ultimately unattainable goal that I believe has left me in the position of carrying on now, for only the reason I have put so much into AW. That’s not something that is healthy, it is not something I should be doing to myself. It is not something I can continue to do any longer. The stress and weight of the responsibility that I hold is not something I can continue on with; not because of the expectations of others, but because of my own. Without some things seriously changing I cannot continue to give my all, give what I feel you, the community, deserve. And to me, that is not on.

If AWE were to be taken in a new, renewed direction; then I would most definitely wish to continue to fight on. I feel that if we were to return to some of the original beliefs of EU3 then we could, and would, progress forward. I am afraid that nothing will change without a radical shift in thinking though, and this is perhaps the straw that broke the camel's back. Coming to the realisation, that no matter how hard I push, some things will just not happen.
As for the staff team; there are elements of it that just don’t work at the moment. It is in a position of turmoil, where there is very little cohesion, and many divisions. I shall not name names, because that is not something I should do. However, I do believe in honesty and transparency, and so you, the community, should know about it. Those wishing to join the team should be critically aware of what they are getting into. I mean this with no malice, but instead a fundamental respect for those people who wish to step up, and do what is necessary.
 
I would like to pay homage to those past and present who have put every effort into EU3, now AWE; thank them for everything they have done. I would also like to say thanks in advance for everything that those who will follow me do. Without the dedication of so many people AWE would not be where it is now, and it will not go where it may go either. 
In the end I hold myself personally accountable for failings here at AW. Because I know I should do better, but I can’t, not right now, and I don’t know if I will be able to again.

I promise you this, I will do my best to stay around AW as a regular player, to push for change as a regular player. I care deeply for this community, and writing this has been one of the hardest things I’ve had to do in a long, long time. I’ve had to stop 3 times now - and I confess, every time has been because I have teared up pretty badly. I suppose, I should probably finish this off with an apology.
 
I am truly very sorry for not doing better by you AhoyWorld.

Best Regards and Goodbye,
Copey
 

Dedication does not imply competence. However, it does imply perseverance in an effort to get involved, evolve and improve, yet there must still be an opportunity to do so which we, as a community, have to offer unequivocally to anyone who does indeed make the effort to download mods, join TS and hop on. We're exclusive in the way that we facilitate a play style rarely found on open servers, but we're still public and do not resent anyone's attendance by default.
 
We cannot choose who joins us, but we can choose to welcome them.
 
 
Yes. Yes, I would.
 
Surmise that all of those 30 new players are in fact of lower quality, because that is what this thread posits as truth. Then assume that that fireteam's worth of veterans take leading roles, which means they hold sway over every decision of consequence. Your ideal player is now responsible for the fluidity of the mission and because they're perfect, they lead perfectly as well. As such, the thirty randoms under their command are employed optimally, meaning you have the concerted force of a platoon's worth of assets plus attachments, far outshining anything a black-clad spec-ops team can do.
 
So far for the horrible conjecture. If anything, this should illustrate that any veteran worth their salt is a force multiplier in any element they join -- their guidance is far more important than their marksmanship or sector security.
 
All that said, the basic premise this topic drifted off to is skewed.
What you experience is a classic negativity and subsequent confirmation bias. You have a huge data set, but the terrible experiences will always stick out more and because they're so annoying, it's tempting to look for proof that most things are in fact horrible as a result.
 
The average player is not stupid. The average player is average.
 
There is one in twenty that sticks out when they crash helicopters, teamkill, troll or otherwise fail to perform. The nineteen others who do their jobs and have a great time with you are ignored because they're deemed normal.
 
If you are uncomfortable or unsatisfied with what is the average, you are very welcomed to get up and communicate your ideals to the playerbase at large. Talk with them, not just at them.
Our players are already shifted towards the positive end of the bell curve due to the nature of our mods and what they impose. I promise they're just as eager as you are and you'll quickly notice how utterly normal skill can be.

Agreed. If we do this we're just becoming a network of Big Brothers. Don't think any new person would take kindly to superiors always watching over his/her shoulder.
 
 
 
Big objections to this here. Personally, I would classify AWE as private; or at minimum, exclusive. I say this because most players, unless they're serious about joining, would not usually put in the effort to go through the mod/repo installation and familiarize themselves with the rules and systems of the server. In short, it's not private because the staff chooses to make it, but because it takes more dedication and patience than regular servers.
 
Secondly, yes, there should definitely be stopping anyone from taking what they choose, that's why we have the server slotting rules.
 
If individuals prove, time after time, that they are incapable of handling the slot they choose, either some sort of assistance should be given or they should be postponed from the role (for how long would likely be the staff's jurisdiction). Else, they will continue dragging the team down and ruining others' experience.
 
 
No permanent repercussions, correct. But something should be done ASAP to help the player improve or else immersion-breaking things like one-manning and crashing Apaches will be seen by the newcomer as "eh, I can just spawn another one in." Get enough people with that mindset and the whole concept of a serious milsim vanishes.

Share names of players? No. I don't think spreading around someone's inabilities to everyone is right, and making people feel paranoid to try out roles if they are new. I feel we have it in a good state where a brand new/newer player to AWE can slot into a role without feeling like everyone on the server has their eyes on them for any slip up or error they make. You can always mention it to other players that someone may be inexperienced, but how you mentioned it sounded a bit more organised than that.
 
Politely, I disagree with you there @Noah_Hero.
 
I completely understand that when someone has a lack of understanding of their role and is proving detrimental to the mission, it is frustrating. But locking AWE behind training sessions or refusing players from selecting specific roles turns it into a private milsim community. AWE IS a public server. There isn't - and there shouldn't - be something stopping anyone taking what they choose. Although we are more 'closed' than I&A through the TS, modset/repo, etc etc, we aren't private, and we don't vet our players.
 
New dude is doing a poor job of their role? Frequent player is doing a poor job of their role? So. What. It isn't a requirement to know your shit. We actively promote and seek to help people learn on this server, but we never tell someone they have to attend a meeting or training session before they can begin playing. Quality shouldn't always be above Quantity. Save that for other Milsim groups, or push that behaviour and ruling for the MSO, I don't know.
 
I get it that a dude crashing a heli or wasting resources is annoying when you're playing. But ultimately, it's a mission that will last about 30 mins, then there is a new one, or the map changes. There is no permanent repercussion for them not playing right. You tell them if they're doing something wrong, offer help, potentially advise them to take a different role, or you inform an admin if they're pissing around. I feel we do a good job of helping people improve, but blocking players from roles because they're not good at it is not what this server is about.
 

Share names of players? No. I don't think spreading around someone's inabilities to everyone is right, and making people feel paranoid to try out roles if they are new. I feel we have it in a good state where a brand new/newer player to AWE can slot into a role without feeling like everyone on the server has their eyes on them for any slip up or error they make. You can always mention it to other players that someone may be inexperienced, but how you mentioned it sounded a bit more organised than that.
 
Politely, I disagree with you there @Noah_Hero.
 
I completely understand that when someone has a lack of understanding of their role and is proving detrimental to the mission, it is frustrating. But locking AWE behind training sessions or refusing players from selecting specific roles turns it into a private milsim community. AWE IS a public server. There isn't - and there shouldn't - be something stopping anyone taking what they choose. Although we are more 'closed' than I&A through the TS, modset/repo, etc etc, we aren't private, and we don't vet our players.
 
New dude is doing a poor job of their role? Frequent player is doing a poor job of their role? So. What. It isn't a requirement to know your shit. We actively promote and seek to help people learn on this server, but we never tell someone they have to attend a meeting or training session before they can begin playing. Quality shouldn't always be above Quantity. Save that for other Milsim groups, or push that behaviour and ruling for the MSO, I don't know.
 
I get it that a dude crashing a heli or wasting resources is annoying when you're playing. But ultimately, it's a mission that will last about 30 mins, then there is a new one, or the map changes. There is no permanent repercussion for them not playing right. You tell them if they're doing something wrong, offer help, potentially advise them to take a different role, or you inform an admin if they're pissing around. I feel we do a good job of helping people improve, but blocking players from roles because they're not good at it is not what this server is about.
 

Share names of players? No. I don't think spreading around someone's inabilities to everyone is right, and making people feel paranoid to try out roles if they are new. I feel we have it in a good state where a brand new/newer player to AWE can slot into a role without feeling like everyone on the server has their eyes on them for any slip up or error they make. You can always mention it to other players that someone may be inexperienced, but how you mentioned it sounded a bit more organised than that.
 
Politely, I disagree with you there @Noah_Hero.
 
I completely understand that when someone has a lack of understanding of their role and is proving detrimental to the mission, it is frustrating. But locking AWE behind training sessions or refusing players from selecting specific roles turns it into a private milsim community. AWE IS a public server. There isn't - and there shouldn't - be something stopping anyone taking what they choose. Although we are more 'closed' than I&A through the TS, modset/repo, etc etc, we aren't private, and we don't vet our players.
 
New dude is doing a poor job of their role? Frequent player is doing a poor job of their role? So. What. It isn't a requirement to know your shit. We actively promote and seek to help people learn on this server, but we never tell someone they have to attend a meeting or training session before they can begin playing. Quality shouldn't always be above Quantity. Save that for other Milsim groups, or push that behaviour and ruling for the MSO, I don't know.
 
I get it that a dude crashing a heli or wasting resources is annoying when you're playing. But ultimately, it's a mission that will last about 30 mins, then there is a new one, or the map changes. There is no permanent repercussion for them not playing right. You tell them if they're doing something wrong, offer help, potentially advise them to take a different role, or you inform an admin if they're pissing around. I feel we do a good job of helping people improve, but blocking players from roles because they're not good at it is not what this server is about.
 

I wholeheartedly agree that this MUST be an effort from everyone in the community. It cannot and should not be left to official, designated means. We should all muck in together with enabling new community members develop their skills; as this is the only way we can as a group of players, achieve this collective goal.

LWIRCM isn't anything like flares, it means Light Weight Infrared Countermeasures - Pretty much an electro magnetic countermeasure system, i don't want to go indepth but in basic words, it pulses electromagnetic waves trying to confuse the Infared guidance system on the rockets used by MANPAD's.
 
Sorry to say, that's how it works. And the only thing to do, is learn how to do evasive. Quite often I survive a few missiles, it's just the matter of understanding how the Countermeasures work. Littlebird is a helicopter made for special purpose and therefore it isn't as sturdy as say blackhawk or a merlin, it's not supposed to be, it's supposed to be as light and agile as possible, it isn't supposed to be used when enemies are known to have AA coverage, flares add to the weight, and trust me, you don't want it to be heavier than it is. I am happy that we at least have the Electro Magnetic Interference Countermeasure system, as in real life only the very special purpose Mission Enhanced Littlebird have any kind of advanced countermeasures. As, well, it's not really in need of any kind, because when used according to what it was made for, in the time it takes the enemy to lock it, it will be long gone and if it was the armed variant, the enemy manpads will be gone too.
 
My advice, train in using the speed and agility of the helicopter in addition with LWIRCM, to evade the threat, hide behind hills, turn hard and fly faster than enemies can track you. Appear, deliver democracy and freedom and dissappear again. That's what the Mission Enhanced Littlebird was made for. Don't rely on the electro magnetic jamming to work like flares, that you can just pop flying in a straight line and hope for the best. And if a lead tells you to do something else, just inform him, that he put you in the wrong helicopter. It's not the machine that is the problem, it's just used where it shouldn't be.
 
Sent from my SM-G935F using a phone app that is really irritating because it constantly advertises itself.

I recently noticed that on AWE the I&A server message is displayed (as seen in the picture below). Nothing big or serious but if there is time may remove or even better replace that one to something like:
"Welcome to Ahoyworld.net the official Gauntlet server !
Make sure to read the rules at ahoyworld.net/enhanced/rules-and-guidelines/" (but for this link @Copey should better update them there)
 
 
 
 
 
(Haven´t posted it in the Gauntlet Feedback thread since it is not related to Gauntlet itself)
- Noah

The general consensus regarding third-person gameplay is a 'don't ask, don't tell' mentality. As long as you don't call out targets you see glancing over that three-metre wall, I won't call you out on using that view.
 
AWE brings together a variety of different mindsets and many will, over time, pick up different traits from one another. In the case of third- or first-person views, it's far more likely that third-personers adopt the serious, realism-centric mentality of first-personers than the other way around. Someone who's learned to play with it won't just fall back on that old crutch.
In turn we get to enjoy banter with a larger, more open player base. I'd wager most of us wouldn't be here otherwise.
 
So we benefit each other.
Bringing about a change specifically in order to rid yourselves of an entirely non-harmful way of enjoying the game is the polar opposite of what AWE has been so far.

I suggest that we also make a new installation video on Youtube. I know I found the existing one useful, but it wasn't 100% up to date. It would make it easier for people to join. 
 
I also think we could do with an Intro to AWE video, where someone explains the basics - rules, radio etiquette, organisation, etc.  I know this info is there for people to read, but I don't think everyone will, so it's another way to ensure that at least people know the basics when they join the site.
 
Thoughts?

Dress-up is a non-issue.
 
It's increased with the recent addition of MGP and the like, yet I'm willing to let this transition period pass as just that; a temporary thing.
Before, people stood at the arsenal because they were bored from idling. Get a rallying call out and most often you found they'd snap right back into mission-ready. That's exactly what we'll revert to in a couple weeks' time.
If you aren't bothered enough to give them a shout, for whatever reason, or they don't respond either way, I find myself agreeing with Miczils: leave them. They've made their choice.

Hello and welcome to the revised ACE Medical Guide: 2020 Edition.
 
This guide aims to be a comprehensive resource for the dedicated medic; to steel yourself with knowledge first so that you can hone it in combat. It will send you on a journey to become the best medic you can be.
It does not offer panacea. That's just called a packing bandage. It does offer the basis you need to understand the inner and outer workings of ACE Medical with an attempt to dispel some common myths.
 
You can find two proven sample loadouts at the very end of the document, as well as a spreadsheet with all the data there is about bandages.
 
For an easier read, here it is on Google Docs.
Link: ACE Advanced Medical Guide v2.3 (2020 Rework)
 
The GDoc is always going to be the most up-to-date version, but if you prefer PDF, here you are:
The PDF is now very much outdated. I will update it with the 2.4 revision, which will include a flowchart and procedure.
 
ACE Advanced Medical Guide v2.1 (2020 Rework) - 23-04-20.pdf
 
To-do
 

@ShadowAce11 @KingFronXos @GandalfTheCray @oO_ScarFace_Oo
 
 

The clue is in the definition of "role", which according to that so infrequently used tool called the dictionary is: the position or purpose that someone or something has in a situation
 
Position - where you sit in the hierarchy - obey orders. Don't give them if you're not supposed to.
Purpose - what are you there to do? Do you have the right kit to do it? In other words, let the medics do their stuff, pilots to their stuff, etc. Do what's expected of you and respect what others do.
Situation - Know the mission, know the orders. Adapt accordingly. Play according to the situation. For example, my AT guy gets killed, I'm the Medic, his AT launcher is right there and the BMP that is killing my teammates is within range. Should I, as the medic, shoot the BMP? I think yes, the situation demands it. Does that mean that I as the medic walk around with an AT launcher just in case? No.
 
 

RIP to Chernarus and Abramia, but defo a great decision to reduce the modset size. Looking forward to the next maps and I hope this will make a few people decide to give AWE a shot.

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.

I disagree it is unrealistic:
 
In Time of Need
U.S. service members need to be prepared to win in battle despite overwhelming odds. Soldiers engaged in combat operations need to know how to correctly employ the foreign weapons when required, such as when a soldier’s own weapon is rendered inoperable or a lack of ammunition requires him to use the enemies’ weapons — not only to survive but to defeat the enemy.
Col. James Coffman was awarded the Distinguished Service Cross after a lengthy battle on Nov. 14, 2004, in Mosul, Iraq, while assigned as the senior adviser to the 1st Iraqi Special Police Commando Brigade. At one point, an enemy round shattered Coffman’s shooting hand and rendered his M4 rifle inoperable. After bandaging his hand, the colonel picked up AK-47s from commando casualties and fired them with his other hand until they ran out of ammunition.
Then-1st Lt. Brian Chontosh was awarded the Navy Cross for his actions while assigned to the 1st Marine Expeditionary Force in Iraq on March 25, 2003. When his unit came under fire from enemy fighters occupying a nearby trench, Chontosh began to clear the trenchline. After his own ammunition was depleted, he twice picked up discarded enemy rifles and engaged the enemy. When a Marine following him found an enemy RPG launcher, Chontosh used it to destroy yet another group of enemy soldiers. When his audacious attack ended, he had cleared more than 200 meters of the enemy trench, killing more than 20 enemy fighters and wounding several others.
 
Source: http://armedforcesjournal.com/know-thy-enemys-weapons/
 
My proposal would be SLs and TLs are responsible for making sure this is kept to an absolute minimum. I always ask my TL if I can pick up an enemy weapon. If he says no, I wait until I can rearm.  

-hud

-hud

-hud

Event Date: Thursday, 11 May 2017
Event Time: 1830 UTC (see what time that is for you!)
 
Description: A combined session for aspiring tactical leaders to be run through the fundamentals and intricacies of battlefield leadership.
 
These workshops will run in parallel - the regular training team will be in charge of 111, while Copey will show you everything there is to know about good squad leading.
 
111 Fireteam Leadership
tasks of an FTL leadership fundamentals awareness tactics communication skills standard commands and phrases etiquette  
112 Squad Leadership
tasks of an SL how to not micromanage fundamental logistics low-level strategy communication on LR coordination between second-level elements target designation & fire missions  
To top this all off, we're going to have a mini-gamenight to put all of your newly acquired skills to the test. Volunteers will take (or a lottery will assign) leading roles to guide all the attendees and possible JIPs through a Zeus scenario. You will get a debrief so you know how you fared.
 
---
 
Because of an underlying issue on AWE that is the lack of volunteers for upper-echelon positions, we have decided to break up our intended progression and bring forward our leadership sessions right after the introduction.
Building upon this, we're going to return to our regular schedule for 103 Fireteam Tactics the session after.
 
Cheers
The Training Team

"Altis has fallen to the CSAT forces, and it is up to you to take it back. Embark with your teammates on a persistent campaign that will span several weeks of real time to liberate all major cities of the island."
 - GREUH Liberation
 
I'd like to see AhoyWorld host this as a weekly event, with minimal if any mods, but with a command structure closer to AWE.
 
Liberation essentially boils down to a teamwork-oriented PvE mission to slowly but surely conquer the major cities of Altis. Along the way, smaller points are contested for resource points and equipment unlocks.
It has currently been ported onto a great many maps, and as such it could feasibly be run on other maps after the completion of Altis, provided it attains the playerbase to make it worthwhile.
 
Liberation involves building defensible bases, attacking varying levels of enemy occupied strongholds and protecting captured areas from counter-attack, all the while capturing resources used to requisition vehicles.
The single Commander slot is essential, as he controls individual player permissions, default permissions for newly connected players and has the option of using a de-clawed Zeus interface to control friendly AI units should he deem this necessary.
Player permissions revolve around rights, essentially being the ability to operate Armor or Air vehicles, as well as the Buy and Build menus.
 
The event could be run weekly, with a trustworthy AhoyWorld representative taking the reins as Commander.
Players could join as an existing group of friends, or as single individuals. Singles would be grouped up together in any number of groups.
Groups could communicate via Group Channel or a TeamSpeak channel.
Commander could communicate with Groups via Command Channel or TeamSpeak Whisper. If necessary, could also relay faction-wide messages via Side Channel.
 
Microphone would preferably be a requirement for all players, and groups would be expected to work toward the task given by Command, but have autonomy on that task.
 
Liberation comes pre-packaged with a system to save the map state between sessions, and defaults to automatic saves every 60 seconds. As such, progress would be relatively safe from crashes.
Liberation is run by many servers, but almost exclusively constantly up, meaning mostly without a Commander present. This tells me that there is interest, but that it could be done in a more organized manner that may attract players.
 
Wiki link: http://greuh-liberation.wikia.com/wiki/GREUH_Liberation_Wikia
bistudio link: https://forums.bistudio.com/forums/topic/183734-mpcti-coop-liberation-beta/
 
Github link for Admin Staff: https://github.com/GreuhZbug/greuh_liberation.Altis
Setup link for Admin staff: http://greuh-liberation.wikia.com/wiki/Server_Admin
Commander Whitelist link for Admin staff: http://greuh-liberation.wikia.com/wiki/Permissions