ShadowAce11

Tonight marked my 1,000th hour on Arma 3; surpassing my second most-played game by over 200 hours and my third-most by nearly 400.
 
 
These 1,000 hours have been spent exclusively on AW servers (and AW members' private servers), with likely 930 spent on AWE alone. And so, I just wanted to make this little appreciation post thanking the community for the fun times had. You all are great.
 
A special shout out to BaeCollector (@SkullCollector) for introducing me to the game and AW. You're a darling. dont kill me pls senpai
 
I'm looking forward to hundreds more hours of enjoyment with you guys in the coming months, and I hope I can repay you guys somehow for it in the future.
 
 - Shadow

Tonight marked my 1,000th hour on Arma 3; surpassing my second most-played game by over 200 hours and my third-most by nearly 400.
 
 
These 1,000 hours have been spent exclusively on AW servers (and AW members' private servers), with likely 930 spent on AWE alone. And so, I just wanted to make this little appreciation post thanking the community for the fun times had. You all are great.
 
A special shout out to BaeCollector (@SkullCollector) for introducing me to the game and AW. You're a darling. dont kill me pls senpai
 
I'm looking forward to hundreds more hours of enjoyment with you guys in the coming months, and I hope I can repay you guys somehow for it in the future.
 
 - Shadow

Tonight marked my 1,000th hour on Arma 3; surpassing my second most-played game by over 200 hours and my third-most by nearly 400.
 
 
These 1,000 hours have been spent exclusively on AW servers (and AW members' private servers), with likely 930 spent on AWE alone. And so, I just wanted to make this little appreciation post thanking the community for the fun times had. You all are great.
 
A special shout out to BaeCollector (@SkullCollector) for introducing me to the game and AW. You're a darling. dont kill me pls senpai
 
I'm looking forward to hundreds more hours of enjoyment with you guys in the coming months, and I hope I can repay you guys somehow for it in the future.
 
 - Shadow

Tonight marked my 1,000th hour on Arma 3; surpassing my second most-played game by over 200 hours and my third-most by nearly 400.
 
 
These 1,000 hours have been spent exclusively on AW servers (and AW members' private servers), with likely 930 spent on AWE alone. And so, I just wanted to make this little appreciation post thanking the community for the fun times had. You all are great.
 
A special shout out to BaeCollector (@SkullCollector) for introducing me to the game and AW. You're a darling. dont kill me pls senpai
 
I'm looking forward to hundreds more hours of enjoyment with you guys in the coming months, and I hope I can repay you guys somehow for it in the future.
 
 - Shadow

An accurate representation of Nomad does on their time off.
 
 

An accurate representation of Nomad does on their time off.
 
 

An accurate representation of Nomad does on their time off.
 
 

An accurate representation of Nomad does on their time off.
 
 

An accurate representation of Nomad does on their time off.
 
 

An accurate representation of Nomad does on their time off.
 
 

There have been a few events recently which have called into question the nature of gameplay on the AWE server. This statement will serve to clarify AhoyWorld’s official position on the style of gameplay that should take place there.
 
To summarize, the server has, and will continue to, operate in the grey zone between public casual play and serious community play ("milsim"). Part of the allure of AWE is that the barrier to entry is the size of the MODs and the ability of the players to follow only a few rules. There is no application process, mandatory training, ranking system and requirement to play in only our community.
 
The problem with this situation of course, is that it means different players have different interpretations concerning where in that grey zone they are actually expected to operate.  To that end, we refer you to the current rules, which give all the guidance that is required. Staff are constantly reviewing these rules, but the core rules will always be applicable, and can be summarized as:
 
Play your role and perform the functions required by it. This means not doing something “out of character” for that role, like charging the front lines as a missile specialist, or sniping as a medic. Players are encouraged to take a realistic loadout for their role.
Obey the chain of command. If someone is of higher rank than you, you must follow their orders, to the best of your ability, within reason. Playing on AWE is all about teamwork and coordination, and nothing gets done if there isn’t a command structure.
Help enhance the gameplay for every player to enjoy the mission and your company. If someone needs help, give it to them. If you need help, ask for it.The greater good should be your mandate; overbearing or disruptive behaviour is not acceptable. A player should try to bring their skills to the table or enable others to do so. AhoyWorld Enhanced is a community of friends, with common interests - welcome and treat others as you would like to be treated yourself.
 
There are currently several guidelines which further clarify specific situations (ie., not parking vehicles in infantry spawn, not teamkilling, and not typing in side chat), but those are all extensions of these three core rules. Players who don't follow the rules are subject to administrative sanctions (warn, kick, ban). While these rules may seem fairly wide-ranging and open to interpretation, they are not. Followed in this order, they are generally complementary and cover 99.9% of situations that arise.
 
Now, some specific notes, to address some situations which have arisen over the last few months.
You are the author of your own experience.
Players are encouraged to play to whatever level of realism that they prefer. If you want to play a first-person only, completely realistic experience - that is your prerogative. If you want to play a more relaxed style, using third-person, and play it more like a game, that is also possible.
 
As long as you play your role, follow the orders of your superior, and follow the server guidelines, everyone should be able to get along no matter what style of gameplay you wish to follow. However, it is possible that one player's gameplay preference may rub up uncomfortably against the preferences of another. At that point, you have three options:
 
Ask the other player to respect your preference (this can be as simple as a player in third-person revealing targets to a player who is playing first-person, who couldn't normally see them).
Acknowledge that other players have alternate preferences, and live with it.
Play somewhere else.
Play your role trumps Follow Chain of Command.
There aren't many situations where this applies, but in general, a player can't be ordered by another player to do something that is outside of the reasonable requirements of their role. For example, a medic cannot be ordered to NOT bring medical supplies to the field; a soldier cannot be ordered to NOT bring and wear a helmet. If it's reasonably applicable to your role, a player CAN be ordered to adhere to their role (for example, a front-line soldier wearing a helmet).
 
Otherwise, if a player chooses to bring or not bring gear which is typical to their role, and their superior officers don't have a problem with it, they are free to do so. (An example would be a player choosing to wear a cap instead of a helmet, if their superior officer doesn't order them to wear a helmet, or better yet the player asks if they can just wear a cap instead of helmet and the superior officer agrees, they are free to do so. Yes, it's stupid, but it's their choice to be stupid.)
 
There are probably situations where these rules and principles don’t make sense; where this occurs, staff have the right to arbitrate a solution which makes sense in the context of these principles and rules of the server.
The application of sanctions, the implementation of bans, and the removal of bans.
There are only a couple of instances where a player will be instantly banned: repeated and/or unapologetic teamkilling, hacking, or other offences of that nature. While these notes serve to clarify the sanction policy on AW, they can’t possibly cover every future scenario, so the moderation team reserve the right to issue sanctions for against any behaviour which runs contrary to the general principles of the AhoyWorld community.
 
Players are subject to the Warn → Kick → Ban procedure of sanctioning. If a ban is instituted the player will be notified at the time, the reason that this action was taken. In addition to this, a specific time will be given for when the ban will automatically lift, or when they may appeal to have the ban removed.
 
A ban is removed completely at the discretion of the community referee or Core Staff, depending on the circumstances of the appeal. If a player is unbanned, they revert to the status of being warned against the offences that resulted in them being kicked.
Rules lawyering and player enforcement.
We appreciate that some players want others to play the game as they do, and to follow the rules as seriously as they do. Unless you are staff, it is not your job to enforce the rules (but you can - and should, if asked - offer advice to players). If you are being personally inconvenienced by another player's failure to follow the rules, you are encouraged to report the offending player to moderators, whose job it is to enforce the rules.
 
I helpfully direct you to the player report form, and as always, you can also message anyone on teamspeak.
 

Following talk about ACE Advanced Ballistics training and Ryko's post here:
I set on to find what it all means and how it works, because my previous attempts to play Marksman on AWE gave VERY chaotic experience.
Now I know why.
 
Advanced Ballistic test on AWE 31.7., COx Gauntlet Altis
test is aimed on how does Advanced Ballistics work with selected High-Powered scopes
 
First set of tests done on non-Marksman position (spawned as Rifleman)
Weapon: MK 18 Mod1, ammo: 5.56mm Mk262
 
1) Trijicon ACOG TA648RMR (marksman scope with 6x magnification but no dialing - only fixed reticle)
RESULT: scope is hitting according to reticle and with quite OP magnification for non-marksman
 
2) SUSAT L9A1 (primarily Autorifle/LMG scope with 4x magnification and VANILA dialing: 100m,200m..up to 600m)
RESULT: scope is hitting according to simplified vanila Arma dialing
 
3) TA31RCO (magnification is not listed, but feels like 3x to me, yet scope has MIL dialing)
RESULT: scope is hitting according to ADVANCED BALLISTICS - target 434m away is not hit on 4.3 MIL (like it would be on vanila) but rather 3.4 MIL as suggested by ATragMX after proper input

Second set of tests done in Marksman slot
Weapon: MK 11 Mod 0, ammo: 7.62mm M993
 
1) Trijicon ACOG TA648RMR (marksman scope with 6x magnification but no dialing - only fixed reticle)
RESULT: scope is visibly over-shooting when using Reticle. Since it's fixed reticle, it is likely because it's not made for 7.62mm calliber.
 
2) SUSAT L9A1 (primarily Autorifle/LMG scope with 4x magnification and VANILA dialing: 100m,200m..up to 600m)
RESULT: scope is hitting according to simplified vanila Arma dialing
 
3) TA31RCO (magnification is not listed, but feels like 3x to me, scope has MIL DIALING!)
RESULT: scope is significantly over-shooting when dialed to "7" (vanila value for 700m)
When dialing 5.7 MIL value offered by ATragMX, it is only slightly over-shooting, it is possible I do not have proper Gun&Ammo values (I'm suspecting Ballistic Coefficient)
 
3) AMS (3x-10x magnification sniper scope has MIL DIALING)
RESULT: same as TA31RCO - slight over-shooting when using ATragMX value
 
4) Leupold Mark 4 ER/T (max magnification not listed, but seems the same as LRPS - 25x, scope has VANILA dialing 100m,200m..up to 1000m)
RESULT: scope is hitting according to simplified vanila Arma dialing - I call this "cheater sniper scope of the year"
 
5) LRPS (max 25x magnification scope with MIL dialing)
RESULT: Just like TA31RCO and AMS, scope is affected by Advanced Ballistics and uses ATragMX values
 
 
TEST RESULTS:
Advanced Ballistics on AWE are governed by scopes used - MIL Dialing scope will enable them, even for NON-marksman position (currently only for TA31RCO)
other scopes are not affected even if they are high-powered (SUSAT and particulary Leupold)
 
Side notes:
1) Range Card is not pulling Gun & Ammo values when gun is equiped and loaded, making creating new Gun&Ammo combination in ATragMX impossible in-game
This is definitely due to "Advanced Ballistics: Disabled" server setting - tested in Editor that they appear when this is "Enabled"
 
2) When MIL dialing scope is equiped, ACE Self-Interaction > Equipment is not offering "Set Zero Adjustment" option to correctly ZERO scope.
This is also due to "Advanced Ballistics: Disabled" - verified in Editor.
 
3) Bullet Spin Drift seems completely turned off, even ATragMX is not showing any Windage values, despite Rifle Twist value entered in gun parameters (there should always be some Spin Drift, especially for longer ranges).
I'm again suspecting "Advanced Ballistics: Disabled"

Conclusion:
Currently (31.7.2017) according to Ryko's information, we have these Advanced Ballistic settings on AWE:
Advanced Ballistics: Disabled
Enabled for Snipers: Enabled
Enabled For Group Members: Disabled
Enabled for Everyone: Disabled
Disabled In FullAuto Mode: Disabled
Enable Ammo Temperature Simulation: Disabled
Enable Barrel Length Simulation: Disabled
Enable Bullet Trace Effect: Disabled
Sim Interval: 0.0
Sim Radius: 3000
 
 
This is actually not working like I thought it was. I will enumerate:
 
1) "Advanced Ballistics"
Having this disabled (in conjunction with second setting) is NOT making AB exclusive to Marksmen, it is OVERALL module setting and actually prevents AB from functioning properly:
* range card don't populate with Gun&Ammo data
* MIL scopes can't be properly zeroed (default zeroing is always slightly off - confirmed in Editor)
* likely cause of non-existent bullet spin drift and maybe other minor variables as well
 
2) "Enabled for Snipers"
When enabled, this makes AB work, when any player shoots through MIL dialing scope, regardless of their slot or gun.
(although AB is in crippled state if first setting is disabled)
 
3) "Enabled For Group Members"
I have not been able to find what this actually means, but in editor I letf it disabled and AB was working fine for Marksman/Sniper purposes.
 
3) "Enabled for Everyone"
According to some sources I red, this is the setting that would cause Server FPS problems when enabled. However testing in Editor, I can confirm this will STILL NOT affect NON-Dialing scopes and Vanila-style "Step-scopes" 100m, 200m, 300m....
 
4) "Disabled In FullAuto Mode"
When enabled, this prevents FullAuto weapons like Autorifles and LMGs equiped with MIL-dialing scopes from being affected by AB (verified in Editor).
If we want AB enabled, this should be ENABLED TOO, to prevent lag should some Autorifleman find himself MIL scope and start spraying.
 
5) "Enable Ammo Temperature Simulation" - additionaly populates Range Card with information, how does temperature of Ammo before shooting (e.g. ambient temperature) affects Muzzle Velocity due to influence of temperature on powder-burn speed, when bullet is fired. "Cold" gunpowder burns slower and lowers Muzzle Velocity.

6) "Enable Barrel Length Simulation" - complicates entering Gun data into ATragMX if you use silencer, since it will affect Ballistic Coefficient of the gun.

7) "Enable Bullet Trace Effect" - when shooting high-calliber bullets with high-powered scope, you will actually see Mirage caused by your bullet cutting through air. Pretty.
 
 
Suggestions for changes:
 
Following my testing, I would like to suggest following changes to AWE Advanced Ballistic settings and Scopes:
 
1) settings:
Advanced Ballistics: Enabled
Enabled for Snipers: Enabled
Disabled In FullAuto Mode: Enabled
All other settings to remain disabled and current Sim Interval & Radius values kept.
 
2) Scopes
* Blacklist "Leupold" scopes for everyone, they bypass any AB settings and allow simplistic vanila targeting on extreme ranges (25x magnification).
* Blacklist "Trijicon ACOG" scopes, they offer very hight 6x magnification and bypass any AB settings
* I'm not sure about "SUSAT L9A1", it cheats the system like Leupold/Trijicon, but only have 4x zoom, ranges to 600m and is intended for LMG, that is perhaps reasonable. Maybe whitelist it only to Autorifleman and FSG?
* I would also remove "TA31RCO", not because it's OP, but because it sucks. 3x magnification and requirement to use AB dialing to make it work.
It's basically punishment, to issue this to troops.
 
I would like to know, how does community feels about this.
I'll be glad to share all things I learned during testing about Advanced Ballistis on training session, should we choose to make AB work properly.
 

I might suggest adding fast rope training into the mix. As far as I know if even one person messes it up, it sends the helicopter flying or some other weird physics glitch. It's a technique that could be used a lot more often, especially on urban or forested areas. Kerama is amazing for this. 
 
I've only skimmed through this topic, so forgive me if this has already been mentioned, but I would highly recommend training nights from here on become exclusive to the trainees and the trainers. Having others come in only to go mess around on their own takes away the entire purpose of having a serious, educational couple hours.
 
Last time I was on a training night, Skull was hosting and had an AT range for us, occasionally spawning in live vehicles. This was amazing practice for anything from M60s to the MAAWS, and should definitely be replicated.

I might suggest adding fast rope training into the mix. As far as I know if even one person messes it up, it sends the helicopter flying or some other weird physics glitch. It's a technique that could be used a lot more often, especially on urban or forested areas. Kerama is amazing for this. 
 
I've only skimmed through this topic, so forgive me if this has already been mentioned, but I would highly recommend training nights from here on become exclusive to the trainees and the trainers. Having others come in only to go mess around on their own takes away the entire purpose of having a serious, educational couple hours.
 
Last time I was on a training night, Skull was hosting and had an AT range for us, occasionally spawning in live vehicles. This was amazing practice for anything from M60s to the MAAWS, and should definitely be replicated.

After some time of abscense, I joined AWE the other day and this was the first thing I noticed.
At spawn, during mission prep, everyone was just talking random nonsense totally unrelated to anything ArmA, there was a prowler driving through and almost crashing into people, a few guys were playing dress-up in the arsenal etc.
Best of all, over the course of 5 minutes, 2 or 3 grenades went off, injuring / killing several. Not once did I hear anyone complain about it, almost as if it's completely normal...
 
Now, though annoying, if this behaviour was restricted to the downtime between missions, I could sort of deal with it. Unfortunately, it continued into the mission, with someone constantly calling out/nagging ASL's name (every few seconds for nearly a minute), people suddenly making weird noises or beginning to sing, opening fire despite ASL's repeated instruction to keep weapons cold, collectively bursting into laughter when someone from another squad comes in over the radio saying he's the only survivor of a T-72 that rolled up on them, and then making no effort whatsoever to go and help even though we were just 300m away, ...
 
 
Part of my abscence is because I'm more active on a more mil-sim-oriented server nowadays, where the behaviour I just described would result in an instant kick or even ban, or at the very least a stern speech from staff.
To be honest, my experience from the other day isn't much of an incentive to return here. Quite the opposite actually, since I feel AWE has basically turned into an EU1/2/4 style of play, but with mods...

Let it be noted I fervently dislike writing things like this, but as a player and more specifically a veteran, I feel obligated to do so. 
 
Over the past couple months, I have seen a drastic decrease in organization and coherence on Enhanced due to an influx of newcomers. While, for the first couple weeks, becoming acquainted with the learning curve is to be expected, it is wholly ridiculous for this process to go on for months at a time. Additionally, with the typical process of "learning in the field" rather than through an official training night or a personal training session, vital concepts are being missed, ranging from improper radio use to failing to understand the medical system. Most importantly though, a sense of obeying the command structure is generally left out. 
 
I would highly recommend new players be required to attend a training night, or a personal session scheduled with an official Enhanced representative (mods, maybe Spartans and veterans) before being permitted to equip any roles that require a somewhat advanced knowledge of the systems in play on the server. How would this be enforced? That's a good question that I don't have an answer for. But is it becoming more and more necessary? Without a doubt, yes. I would be more than willing to volunteer any time I have to help with this process if need be. 
 
So that covers my little rant about player competence, now let's discuss a case of pilot competence that happened today (20/7/17) on the server. Names will be excluded for privacy.
 
Most pilots are extremely good at what they do, and I applaud them for the good experiences they help foster on the server. And I do not intend for the following to apply to them. Some, however, desperately need to be dealt with. Today, a player joined while I was piloting. Including him, there were two others on the server. He took the copilot slot. I immediately warned him that he was not allowed to be there; he needed to slot to Alpha. It took up to my fourth warning before he obliged and switched. In that time I was giving him warnings, he went over to the heli maintenance, spawned a helicopter (did not know what it was at the time), hopped in, and nearly took off. Carrying the single Alpha member in my helicopter (I assume the copilot was waiting for his reslot timer to end), I dropped him off to the AO and cleared a majority of the hostiles. After being shot down by a BMP, I disconnected. 
 
After leaving the server for roughly an hour, I came back and slotted up as an Alpha member. The copilot had switched to Alpha, then back to Vortex when I left. Upon reentering the AO, the pilot flew dangerously high and used autohover for landing, resulting in a nearly-shot-down situation. Upon landing, he continued to sit there for about 10 seconds, before turning his engine off entirely to communicate with Alpha Lead. He did return to base, but not before almost getting shot down again by the BMP due to his slow speed and high flight. Having to attempt landing three times (with that BMP still on him), he repeated this process while bringing in the FSG team. 
 
While he was making his trips, I notice something:
 
 
An Apache crash. That unknown helicopter he spawned was a two-seater Apache. During the time I was offline, he one-manned it, and proceeded to fly it into the AO and crash it. 
 
This was a "set up a comms tower" mission, so once Alpha and Nomad cleared the AO, he began to fly the crate in. Upon entering the vicinity, he was shot down by a BMP due to his once again linear path and slow speed. At that time, he disconnected.
 
My point here is that:
 
People should know the command structure, and know to obey the slotting rules. People, especially pilots and other specialty slots, should know proper conduct on the server. This is not a training server. You should know how to fly properly before touching these more advanced, modded models.   
-----
 
Once again, I would be more than willing to volunteer to help with training nights to help resolve these issues. Anything I can do to help I'm happy to. I had to put this rant/report out here, not because I wanted to, but because I felt responsible as a person who has a duty to the server and its population to obey the rules and make sure they're followed by others. The things above are beyond unacceptable, and need to be dealt with. 

@Michal
 
 

Let it be noted I fervently dislike writing things like this, but as a player and more specifically a veteran, I feel obligated to do so. 
 
Over the past couple months, I have seen a drastic decrease in organization and coherence on Enhanced due to an influx of newcomers. While, for the first couple weeks, becoming acquainted with the learning curve is to be expected, it is wholly ridiculous for this process to go on for months at a time. Additionally, with the typical process of "learning in the field" rather than through an official training night or a personal training session, vital concepts are being missed, ranging from improper radio use to failing to understand the medical system. Most importantly though, a sense of obeying the command structure is generally left out. 
 
I would highly recommend new players be required to attend a training night, or a personal session scheduled with an official Enhanced representative (mods, maybe Spartans and veterans) before being permitted to equip any roles that require a somewhat advanced knowledge of the systems in play on the server. How would this be enforced? That's a good question that I don't have an answer for. But is it becoming more and more necessary? Without a doubt, yes. I would be more than willing to volunteer any time I have to help with this process if need be. 
 
So that covers my little rant about player competence, now let's discuss a case of pilot competence that happened today (20/7/17) on the server. Names will be excluded for privacy.
 
Most pilots are extremely good at what they do, and I applaud them for the good experiences they help foster on the server. And I do not intend for the following to apply to them. Some, however, desperately need to be dealt with. Today, a player joined while I was piloting. Including him, there were two others on the server. He took the copilot slot. I immediately warned him that he was not allowed to be there; he needed to slot to Alpha. It took up to my fourth warning before he obliged and switched. In that time I was giving him warnings, he went over to the heli maintenance, spawned a helicopter (did not know what it was at the time), hopped in, and nearly took off. Carrying the single Alpha member in my helicopter (I assume the copilot was waiting for his reslot timer to end), I dropped him off to the AO and cleared a majority of the hostiles. After being shot down by a BMP, I disconnected. 
 
After leaving the server for roughly an hour, I came back and slotted up as an Alpha member. The copilot had switched to Alpha, then back to Vortex when I left. Upon reentering the AO, the pilot flew dangerously high and used autohover for landing, resulting in a nearly-shot-down situation. Upon landing, he continued to sit there for about 10 seconds, before turning his engine off entirely to communicate with Alpha Lead. He did return to base, but not before almost getting shot down again by the BMP due to his slow speed and high flight. Having to attempt landing three times (with that BMP still on him), he repeated this process while bringing in the FSG team. 
 
While he was making his trips, I notice something:
 
 
An Apache crash. That unknown helicopter he spawned was a two-seater Apache. During the time I was offline, he one-manned it, and proceeded to fly it into the AO and crash it. 
 
This was a "set up a comms tower" mission, so once Alpha and Nomad cleared the AO, he began to fly the crate in. Upon entering the vicinity, he was shot down by a BMP due to his once again linear path and slow speed. At that time, he disconnected.
 
My point here is that:
 
People should know the command structure, and know to obey the slotting rules. People, especially pilots and other specialty slots, should know proper conduct on the server. This is not a training server. You should know how to fly properly before touching these more advanced, modded models.   
-----
 
Once again, I would be more than willing to volunteer to help with training nights to help resolve these issues. Anything I can do to help I'm happy to. I had to put this rant/report out here, not because I wanted to, but because I felt responsible as a person who has a duty to the server and its population to obey the rules and make sure they're followed by others. The things above are beyond unacceptable, and need to be dealt with. 

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.

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.

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.