ShadowAce11

1 listening to all sides is a major prerequisite for any improvement (and not any personal vendetta)
2 the truth also
3 "warnings" instead of teaching him something about advanced models flight characteristics / AO veteran approach tactics etc obviously didn't improve anything
4 as  a "veteran",  getting shot down by a BMP (not an AA asset) didn't teach the kid by example much either, disconnecting right after the "wrong doing" (avoiding thus any kind of responsibility) taught him even less and he picked up on it, behaving exactly the same way later, once himself got shot down
5 after 1h , finding the desired slot taken by the kid and starting a "personal vendetta", still not giving him any advice but continuously looking for evidence of wrong doing (even while you were offline!?!) while he was trying to play his role and do his job of flying people and equipment wasn't helpful at all. You did not want to teach the kid anything at that moment, you just stood there watching him fail, that's the truth. "Tacticool, milsim-ish" = we don't just watch friendlies fail and die, right ?
6 make an objective, transparent, tough test, like a pilot's license, everyone takes it if wants to be certified and allowed to fly, once the pilot gets his license then all trolling and picking on must be completely stopped
7 judging an idea based 100% on the issuer and not the content is a major lack of "professionalism and focus on improvements"
 
plan B :"Kid i see you would like to fly. In this server we have strict rules about slotting and advanced flight model assets. If you want to learn i could teach you a lot at x o clock on the x of July if you desire , because the server is usually empty then"
plan C:"Kid i see you would like to fly. In this server we have strict rules about slotting and advanced flight model assets. But i am sure, given that the server is almost empty, nobody would truly mind  a veteran taking a kid as co-pilot and teaching him something useful. Hop in as co-pilot for 10 min, but not more, because the rules must still be enforced here"
etc.
If he refuses and still trolls, shoot him in the head, report him and perma-ban him like the worst kind of traitors deserve.
 
just the little devil's advocate point of view  (overemphatic, against the tide, lacking omnibenevolence, omnisciently delusional, suicidely non dogmatic, indisputably black sheep-ish) ...
 

@Michal
 
 

Continuation, rebuttals, etc. below. I was trying to type the above as quick as possible so I'd make it to work on time.
 
The reason why I bring up the matter of official personnel is because new players (at least, if they were me) would be more keen on obeying the lessons taught by those you should not ignore. If a player with just a member tag or no tag at all tells a newcomer what they can and can't do, that may be received as condescending, overly strict, and rude. And if the new player is like me, they'd just pretend not to hear the advice and keep doing their thing. While it is always nice to see everybody pitching in with following the rules, I think everybody can agree that receiving a reprimand from a staff member or veteran is a better reason to follow the rules than a member or guest saying "Hey, you can't do that".
 
This is something I mulled over for a couple hours while at work: I'd like to propose that the main Arma 3 Modded channel (the main channel that holds all channels for AWE, EU6, and A3 Custom) become password protected, with the password being added at the end of, or encoded within (this option pls), the rules (or the basic introduction). So for those of you who were here when we used ACRE, essentially that setup. This way, players are required to read the rules in-depth and get a basic understanding before even gaining access to the channel. Of course, TFAR just drags you straight in once you get on the server, but if there's some way to block that unless you have the key, that would be great. 
 
It's a fault on experienced players, too, that people don't learn as fast as they should. I hold a lot of that on my shoulders. Once you're on the server for so long, everything just becomes second nature; and suddenly anybody who doesn't know the systems, new or not, becomes this subgroup of inept players who should just leave the server and come back when they're more acquainted. The pilot I wrote about is a perfect example; rather than trying to help him through anything he might have been wondering about, I just turned my nose up and complained. And if that attitude isn't challenged, it makes the veteran more harmful to the server than the newcomer. 
 
While the following is a weak counter argument, it's a counter argument nonetheless: experienced players like me have no obligation to stalk the playerbase of the server and keep tabs on who is new, and so we don't. In the case of the pilot I described, I've only seen him on the server for a couple hours in total. In my eyes, he's completely new. But, my schedule is not aligned with his, and I may miss countless hours of him playing while I'm away or at work. To others, he might be a pro, but to me, he's just taking his first steps. And people rarely mention if they are new, so I usually default to thinking they've been on the server for a while and should be fully acquainted with the systems. When they don't return on that expectation, it's irritating. In short, I'm saying there's a massive lack of communication that leads to condescension. If that is cleared up, I would really hope the relations between specifically the veterans and newcomers will improve. 

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. 

Continuation, rebuttals, etc. below. I was trying to type the above as quick as possible so I'd make it to work on time.
 
The reason why I bring up the matter of official personnel is because new players (at least, if they were me) would be more keen on obeying the lessons taught by those you should not ignore. If a player with just a member tag or no tag at all tells a newcomer what they can and can't do, that may be received as condescending, overly strict, and rude. And if the new player is like me, they'd just pretend not to hear the advice and keep doing their thing. While it is always nice to see everybody pitching in with following the rules, I think everybody can agree that receiving a reprimand from a staff member or veteran is a better reason to follow the rules than a member or guest saying "Hey, you can't do that".
 
This is something I mulled over for a couple hours while at work: I'd like to propose that the main Arma 3 Modded channel (the main channel that holds all channels for AWE, EU6, and A3 Custom) become password protected, with the password being added at the end of, or encoded within (this option pls), the rules (or the basic introduction). So for those of you who were here when we used ACRE, essentially that setup. This way, players are required to read the rules in-depth and get a basic understanding before even gaining access to the channel. Of course, TFAR just drags you straight in once you get on the server, but if there's some way to block that unless you have the key, that would be great. 
 
It's a fault on experienced players, too, that people don't learn as fast as they should. I hold a lot of that on my shoulders. Once you're on the server for so long, everything just becomes second nature; and suddenly anybody who doesn't know the systems, new or not, becomes this subgroup of inept players who should just leave the server and come back when they're more acquainted. The pilot I wrote about is a perfect example; rather than trying to help him through anything he might have been wondering about, I just turned my nose up and complained. And if that attitude isn't challenged, it makes the veteran more harmful to the server than the newcomer. 
 
While the following is a weak counter argument, it's a counter argument nonetheless: experienced players like me have no obligation to stalk the playerbase of the server and keep tabs on who is new, and so we don't. In the case of the pilot I described, I've only seen him on the server for a couple hours in total. In my eyes, he's completely new. But, my schedule is not aligned with his, and I may miss countless hours of him playing while I'm away or at work. To others, he might be a pro, but to me, he's just taking his first steps. And people rarely mention if they are new, so I usually default to thinking they've been on the server for a while and should be fully acquainted with the systems. When they don't return on that expectation, it's irritating. In short, I'm saying there's a massive lack of communication that leads to condescension. If that is cleared up, I would really hope the relations between specifically the veterans and newcomers will improve. 

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. 

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. 

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. 

Alright, so how's this looking?
 
 

Alright, so how's this looking?
 
 

Alright, so how's this looking?
 
 

Because I have nothing better to do at 1:45 AM.

Because I have nothing better to do at 1:45 AM.

Because I have nothing better to do at 1:45 AM.

Just a quick concept i made. 
Note, it's gonna be a different picture and different text. It's just a layout/idea concept.


 

Encountered visual glitch today on Taki. Not sure if the incident could be isolated to that map, or if it does the same on others. Picture is below. 
 
Rain is just specs of light (looks like fast-falling snow), mysterious black rectangles in the distance. Multiple players could see this.  Once you looked away from the rectangles, the rain went back to normal. 
 
Server weather was foggy, don't know what percentage that was set to. None of the rectangles were ambient AI or part of the mission; for all I know, it could be buggy rock walls. We did not investigate. 

@ShadowAce11 @KingFronXos @GandalfTheCray @oO_ScarFace_Oo
 
 

The points are just a shorthand way of defining how much stuff you can deploy.  They are not reward points.  It reflects how much material is available in each crate with which to build.  The points stack, so if you bring multiple containers, you'll have a larger volume of points to build with.
 
Here's the current "price" list:
 
(10) Razorwire - Land_Razorwire_F
(15) Razor Fence - Land_Mil_WiredFence_F
(20) Razor Fence (Gate) - Land_Mil_WiredFence_Gate_F
(1) H-Barrier (1 Block) - Land_HBarrier_1_F
(3) H-Barrier (3 Blocks) - Land_HBarrier_3_F
(5) H-Barrier (5 Blocks) - Land_HBarrier_5_F
(16) H-Barrier Wall (Corner) - Land_HBarrierWall_corner_F
(12) H-Barrier Wall (Short) - Land_HBarrierWall4_F
(18) H-Barrier Wall (Long) - Land_HBarrierWall6_F
(35) H-Barrier Wall Watchtower - Land_HBarrierTower_F
(8) H-Barrier (Big, 4 Blocks) - Land_HBarrier_Big_F
(100) Bunker (Larger) - Land_BagBunker_Large_F
(25) Bunker (Small) - Land_BagBunker_Small_F
(50) Bunker (Tower) - Land_BagBunker_Tower_F
(20) Camoflague Net (Digital) - CamoNet_INDP_F
(20) Camoflague Net (Green) - CamoNet_BLUFOR_F
(20) Camoflague Net (Hex) - CamoNet_OPFOR_F

@fir_nev Lel, that was merely just trying to survive. If you'll consistently be on at times like before I'll be glad to do some run-downs with you; and hopefully ones where we're not constantly getting wasted by ambience. 

@fir_nev Lel, that was merely just trying to survive. If you'll consistently be on at times like before I'll be glad to do some run-downs with you; and hopefully ones where we're not constantly getting wasted by ambience. 

https://imgur.com/a/GZbua
 
Some splendid cam snapshots of today's session. A few great beauty shots, but they're unfiltered, unedited.