Jump to content

JaSmAn

Donator
  • Content count

    117
  • Joined

  • Last visited

ArmA 3

  • ArmA 3 Player Name
    JaSmAn

TeamSpeak

  • TeamSpeak Name
    JaSmAn

Recent Profile Visitors

384 profile views
  1. When playing as EOD, does the Metal Detector (otherwise known as "selfie stick" by some players) do anything? Is it necessary to effectively detect mines/explosives? I am not talking about the Mine Detector ACE item.
  2. TVT Return?

    I seem to be the only one, but I vote against TvT/PvP. It just feels too Call of Duty for me.
  3. The Men of Operation Backfoot

    Nice one! And great op!
  4. 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?
  5. Is this ok or not ok?

    Context needed. When, where, who, what happened? Otherwise, not very useful IMHO.
  6. Is this ok or not ok?

    @oO_ScarFace_Oo totally irrelevant post on what should be a serious topic for those who care about seeing this community improve.
  7. Is this ok or not ok?

    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.
  8. PTSD Simulator

    Also know as "oh sh*t, run!!!!"
  9. @Ryko the "waking animation" was actually a black screen for a long time which then went to a respawn screen.
  10. Reversing ftw

    You probably survived because you were reversing. Moral is "always reverse into an IED truck."
  11. 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....
  12. I'm hoping we can do something. Judging by the turnout over the last two week I'd say our dear AWE has lost popularity!
  13. Again, I don't know much about programming, but I'm sure there's a way you can sort this out. We know that there are no people on the server at certain times - predictably. Surely we could limit the enemy advancing significantly during those hours and limit them to defend missions?
  14. I think the MSO concept is good, but it's missing one thing that I think would be key to my proposal - an overview map - some way of understanding what is actually happening on a grander scale. The MSO I played (and it's only been one) was quite boring - basically get in a car, go to where you are told and shoot. No communication as to why we are doing things, etc. I keep thinking back to Falcon 4 and the dynamic campaign there.
  15. Had a quick look and this very clunky with complex points mechanisms and not a very intuitive mission format. The map is the right idea though, although I would make it more simple.
×