JaSmAn

Gutted that I will miss the first installment but I will be there for the next ones! Save me a chair in the torture chamber boys!

If JaSmAn were around and not have been left behind by his team he would say "please, this time, can you take me home? This is my second time being taken hostage and to be honest, it's painful. I re-enlisted as RTO in the hopes that a job where I got shot at less would take the edge off the PTSD, but obviously not."

Looking forward to another convoy duty!

The Frag-O for the third mission (30.01.2021) of the campaign is now ready📑:
FRAG-O_300121.pdf
 
 
Get ready for a roadtrip!🚙

Looking forward to rejoining MSO!

Has anything happened with AWE?

The server is currently down and in for a reboot when I&A4 comes out of beta. Quite a lot of us waiting for it.

Just want to give this thread a bump to see who's still around and playing and when?

Yeah, it's been dead on the server and the times people join the games aren't that fun because it's just a bunch of guys running around without organisation. A couple of guys do want to take it seriously but they usually just end up disconnecting.
It's sad to see the community is so inactive. I'm with you, let's get organised again.
 

Hi all,
I've been away from AW for a long time for a number of personal reasons, but am seriously considering coming back to the game and the community. Is AWE still up and running? What maps are mostly being used these days? Have the new Arma 3 mods been implemented?
 
Appreciate any feedback!
 
JaSmAn

Hi all,
I've been away from AW for a long time for a number of personal reasons, but am seriously considering coming back to the game and the community. Is AWE still up and running? What maps are mostly being used these days? Have the new Arma 3 mods been implemented?
 
Appreciate any feedback!
 
JaSmAn

You're never the only one. Not on the internet.

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?

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?

This thread is going off the rails, and here we are calling each other out on everything they ever did. Id recommend closing it.
I could say i saw quite a few of members/vet's/spartans/ambassadors/admins/ etc. say, do,  stupid stuff/disregard the rules etc., often with a reason, often not, yep, we all do it every now and then (recalling my stay in the community some year ago), and i have done quite a lot of that myself, I've learnt a little. In the end, it's a game, and yes i understand caring, discussing and enforcing the rules, but lets leave it a discussion please, because what this thread is becoming now is a war of "who has done more stupid shit" and how obviously everybody dislikes that. 

I may not agree with all the rules and their enforcement, but at the same time, i understand them & the thinking behind them, and well, if i can't change them, i try not to break them more than twice a day. Also, im sure that the ahoy-world staff knows about what happened/happens and deals with it, we don't need to all be judges of that and express our dislike/hatred/spite in a forum thread, yes he broke the rules, yes there is a longer story behind it, and yes Ahoy dealt with it, really, it's that simple.
But, as we all know, we aren't going anywhere with what is happening now, and id just like to ask everybody, to, please not hate each-other too hard, and if you really wan't to, at least do it in a fight-ring team-speak channel, in the end, it's just a game.
Next time file a report and get on.

Cheers Miczils
I should probably start counting dislikes^^

@oO_ScarFace_Oo totally irrelevant post on what should be a serious topic for those who care about seeing this community improve. 
 

@oO_ScarFace_Oo totally irrelevant post on what should be a serious topic for those who care about seeing this community improve. 
 

I was ASL during this op and all it seems MAT was upset at the quality of information they were getting (or not getting for that matter). It seems the behaviour in the video was a result of MAT being upset at the lack of communication - hear the opening comment in the video - "we've been left in the dark for so long I,m just leaving it."
 
If anyone has an issue with the amount of information they are getting they should speak up during the op and not act out like this. This incident resulted in ME getting a complaint, which I addressed with an Admin through the right channels. The rest of Alpha seemed OK with my communication and I didn't get any other complaints.
 
I agree with @kman. Unfortunately this sort of behaviour (not specific or limited to Moonfire) is becoming way too common on AWE and frankly, it's put me off from taking even a TL role, much less ASL (some might be happy about that!). However, it is limited to a few players. It's too bad that they are the "well known" guys, which makes them feel like it's ok to have fun any way they want but have very little regard for the rest of the community.

I debated with myself if I should comment on this or not, but most of people know when I have something to say I will say it even if people like or not.
So...here it goes:
 
In my opinion this kind of thing is clearly against the rules:
Not following command Wasting assets (shooting rockets at a house when it could be cleared with guns) Almost teamkilling by destroying a house where friendlies are near by  
Its not the first time that I see support teams doing whatever they want and to be honest I'm kind of tired of that and for me that means less AWE hours and availability to play there.

Noticed the same pattern lately - unfortunately A LOT.
 
1) MAT filled even when not warranted
People log in lobby and have to see, that Aplha squad looks like Swiss cheese, yet they fill MAT.
Worse - sometimes fill MAT even when ASL is not present.
 
2) Overuse of HE.
MAT purpose is to deal primarily with enemy armored vehicles, not to play line-of-sight mortar support, unless SPECIFICALY instructed to by command.
 
3) Giving sh** about command structure
If you joined MAT - a support unit - when ASL is not present, then you are under command of Alpha1 Team Lead.
You are not independent kaboom squad.
 
 
I can't stress enough, how does presence of MAT on almost empty server discourages me from logging in as Teamlead, and I bet its the same for others who want to help with more organised gameplay.

Since we are on the subject I would just like to ask @Ryko How did a flying submarine end up on the sever?

Ben don't feel too bad about the mission and the way it ended up. Some people gave you a hard time, but if they have opinions they should post them here along with suggestions on how to improve.
 
Here's my suggestion - and I'm going to sound like a broken record - IT'S ALL ABOUT THE ORDERS and the chain of command. 
 
In real life, combat operations go to wrong all the time, like this one was supposed to. The story is a crashed chopper, everyone's lost their kit, command is down, orders are not flowing. So, in real life, soldiers have standard procedures which they follow, as well as a standard chain of command. One of the things we do worst is AWE is give orders properly and follow chain of command. Very simply put, most ASLs (including whoever was ASL during your op) have no idea how to give clear orders ahead of the mission. I just watched the stream and ASL says "we have no orders....." Not good. EVERYONE should know what the hell is going, and last night, nobody did.
 
As a mission designer it is your job to help the ASL (or PlatCo) give good orders. In other words, you need to give him the scenario, the intel, the possible situations that may develop, and in a case where you need a heavily scripted turn of events like this one, some hints as to what might happen. In other words, "what happens if the chopper gets shot down....." If you did, then ASL didn't pass any of that on to the TLs or the TLs didn't pass anything down.
 
A couple of specific things:
 
1) The respawn was in a bad place. I spawned back after the crash and immediately got shot in the head. That means I lost 4 minutes, and when I came back the second time I had no weapon and it took me a good couple of minutes to find one. I was combat ineffective for a long time, and then it took me even longer to sort of make sense of what was going on. Suggestion, move the spawn to a safe place, inside a house or something like that. 
 
2) My Shacktac stopped working on respawn. This was bad, because it's hard enough to find your squad with it, more so without it. I don't know if that was unique to me. I think that what you want is for people to get organised as soon as possible to get on with the mission. On the flip side, TLs were terrible at getting people organised. I lost my team and never found them again until the very end. I'm pretty sure they weren't looking for me. TLs have a responsibility to make their team function and not just run off, which mine did.
 
3) Where I think things got very wrong was when the tanks showed up. I heard you say that the reason you put the tanks in was to keep people in the compound. But that was never going to happen. I think everyone just reacted to, "tank, we have nothing to kill it with, get the F out!"
 
4) You had a chance to let people regroup at the airfield. I'm not sure if it was you who placed the infantry there or not, but there were bad guys with RPGs at the airfield and it was only natural for the pilots and ASL to get the plane to safety. When the RPG hit the plane, that was it, game over. My suggestion would be that you should have kept the airfield safe and delivered an Overlord message to secure the airfield, or something like that.  
 
I think this just shows that players won't react how you expect, and if you expect them to react a certain way you should tell them. In other words, give them a Standard Operating Procedure ahead of the game.
 
My final thought, and a repeat of my previous comments: improve your briefing, take time to give good clear orders and intel. No mission in real life would happen without these. They shouldn't happen on AWE either.
 
And one for the community - ASLs and TLs, learn to give good orders!
 
Ben, don't get discouraged; don't give up on making missions.
 
And finally, I'm happy to help you write orders, give ideas for future missions, etc....
 

Ben don't feel too bad about the mission and the way it ended up. Some people gave you a hard time, but if they have opinions they should post them here along with suggestions on how to improve.
 
Here's my suggestion - and I'm going to sound like a broken record - IT'S ALL ABOUT THE ORDERS and the chain of command. 
 
In real life, combat operations go to wrong all the time, like this one was supposed to. The story is a crashed chopper, everyone's lost their kit, command is down, orders are not flowing. So, in real life, soldiers have standard procedures which they follow, as well as a standard chain of command. One of the things we do worst is AWE is give orders properly and follow chain of command. Very simply put, most ASLs (including whoever was ASL during your op) have no idea how to give clear orders ahead of the mission. I just watched the stream and ASL says "we have no orders....." Not good. EVERYONE should know what the hell is going, and last night, nobody did.
 
As a mission designer it is your job to help the ASL (or PlatCo) give good orders. In other words, you need to give him the scenario, the intel, the possible situations that may develop, and in a case where you need a heavily scripted turn of events like this one, some hints as to what might happen. In other words, "what happens if the chopper gets shot down....." If you did, then ASL didn't pass any of that on to the TLs or the TLs didn't pass anything down.
 
A couple of specific things:
 
1) The respawn was in a bad place. I spawned back after the crash and immediately got shot in the head. That means I lost 4 minutes, and when I came back the second time I had no weapon and it took me a good couple of minutes to find one. I was combat ineffective for a long time, and then it took me even longer to sort of make sense of what was going on. Suggestion, move the spawn to a safe place, inside a house or something like that. 
 
2) My Shacktac stopped working on respawn. This was bad, because it's hard enough to find your squad with it, more so without it. I don't know if that was unique to me. I think that what you want is for people to get organised as soon as possible to get on with the mission. On the flip side, TLs were terrible at getting people organised. I lost my team and never found them again until the very end. I'm pretty sure they weren't looking for me. TLs have a responsibility to make their team function and not just run off, which mine did.
 
3) Where I think things got very wrong was when the tanks showed up. I heard you say that the reason you put the tanks in was to keep people in the compound. But that was never going to happen. I think everyone just reacted to, "tank, we have nothing to kill it with, get the F out!"
 
4) You had a chance to let people regroup at the airfield. I'm not sure if it was you who placed the infantry there or not, but there were bad guys with RPGs at the airfield and it was only natural for the pilots and ASL to get the plane to safety. When the RPG hit the plane, that was it, game over. My suggestion would be that you should have kept the airfield safe and delivered an Overlord message to secure the airfield, or something like that.  
 
I think this just shows that players won't react how you expect, and if you expect them to react a certain way you should tell them. In other words, give them a Standard Operating Procedure ahead of the game.
 
My final thought, and a repeat of my previous comments: improve your briefing, take time to give good clear orders and intel. No mission in real life would happen without these. They shouldn't happen on AWE either.
 
And one for the community - ASLs and TLs, learn to give good orders!
 
Ben, don't get discouraged; don't give up on making missions.
 
And finally, I'm happy to help you write orders, give ideas for future missions, etc....
 

Ben don't feel too bad about the mission and the way it ended up. Some people gave you a hard time, but if they have opinions they should post them here along with suggestions on how to improve.
 
Here's my suggestion - and I'm going to sound like a broken record - IT'S ALL ABOUT THE ORDERS and the chain of command. 
 
In real life, combat operations go to wrong all the time, like this one was supposed to. The story is a crashed chopper, everyone's lost their kit, command is down, orders are not flowing. So, in real life, soldiers have standard procedures which they follow, as well as a standard chain of command. One of the things we do worst is AWE is give orders properly and follow chain of command. Very simply put, most ASLs (including whoever was ASL during your op) have no idea how to give clear orders ahead of the mission. I just watched the stream and ASL says "we have no orders....." Not good. EVERYONE should know what the hell is going, and last night, nobody did.
 
As a mission designer it is your job to help the ASL (or PlatCo) give good orders. In other words, you need to give him the scenario, the intel, the possible situations that may develop, and in a case where you need a heavily scripted turn of events like this one, some hints as to what might happen. In other words, "what happens if the chopper gets shot down....." If you did, then ASL didn't pass any of that on to the TLs or the TLs didn't pass anything down.
 
A couple of specific things:
 
1) The respawn was in a bad place. I spawned back after the crash and immediately got shot in the head. That means I lost 4 minutes, and when I came back the second time I had no weapon and it took me a good couple of minutes to find one. I was combat ineffective for a long time, and then it took me even longer to sort of make sense of what was going on. Suggestion, move the spawn to a safe place, inside a house or something like that. 
 
2) My Shacktac stopped working on respawn. This was bad, because it's hard enough to find your squad with it, more so without it. I don't know if that was unique to me. I think that what you want is for people to get organised as soon as possible to get on with the mission. On the flip side, TLs were terrible at getting people organised. I lost my team and never found them again until the very end. I'm pretty sure they weren't looking for me. TLs have a responsibility to make their team function and not just run off, which mine did.
 
3) Where I think things got very wrong was when the tanks showed up. I heard you say that the reason you put the tanks in was to keep people in the compound. But that was never going to happen. I think everyone just reacted to, "tank, we have nothing to kill it with, get the F out!"
 
4) You had a chance to let people regroup at the airfield. I'm not sure if it was you who placed the infantry there or not, but there were bad guys with RPGs at the airfield and it was only natural for the pilots and ASL to get the plane to safety. When the RPG hit the plane, that was it, game over. My suggestion would be that you should have kept the airfield safe and delivered an Overlord message to secure the airfield, or something like that.  
 
I think this just shows that players won't react how you expect, and if you expect them to react a certain way you should tell them. In other words, give them a Standard Operating Procedure ahead of the game.
 
My final thought, and a repeat of my previous comments: improve your briefing, take time to give good clear orders and intel. No mission in real life would happen without these. They shouldn't happen on AWE either.
 
And one for the community - ASLs and TLs, learn to give good orders!
 
Ben, don't get discouraged; don't give up on making missions.
 
And finally, I'm happy to help you write orders, give ideas for future missions, etc....
 

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.