kman

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.

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.

It's a radio frequency jammer. It is supposed to jamm transmissions in vicinity, making RCIED (remote controlled IEDs) triggered by radio/wi-fi/mobile phone unable to receive detonation signal, while jamming source (vehicle) is in vicinity.
 
It *MIGHT* protect against IEDs triggered by passive sensors (pressure plate, movement detection, laser trigger), but only if the sensor delivers trigger signal to the IED by wireless. If it's by metalic wire - which is more likely - it will not help.
 
I am not sure, if DUKE can IRL interferre with comm systems of vehicle's crew. I suppose it depends on how aggressively it's currently configured.
In ARMA, there is no configuration and it does not interfere with comms AFAIK.

I agree.
 
When the troops are slacking around its 8/10 because command is slacking around. But remember, they too sometimes need to go AFK..
 
Rest 2/10 are disconnects in command structure / vortex or re-slotting due to multiple players leaving/joining, that can't be rly prevented.

I agree.
 
When the troops are slacking around its 8/10 because command is slacking around. But remember, they too sometimes need to go AFK..
 
Rest 2/10 are disconnects in command structure / vortex or re-slotting due to multiple players leaving/joining, that can't be rly prevented.

All it usually takes is someone giving a loud 'Lets get going' to give everyone the kick up the arse they need. Most of the time people are procrastinating because they think they are waiting for a plan or transpot etc, when everyone does this is when the problem starts. Of course it helps if teamleads and squad leads hurry everyone along as well.

Great mission, thx Benjamin
 
for a feedback:
there were some resupply issues (mostly when we ran out of AT) and that radio bug, where radios taken from spawned Arsenal did not worked - I would probably avoid spawning Arsenal during missions altogether, it creates various problems. Resupply crates are safer. Can they be perhaps pre-prepared as part of mission file and placed somewhere out of AO, so Zeus can just drag&drop them when deemed appropriate? I don't like friendly AI troops. They create confusion on battlefield because you can't tell them from enemy at distance. they move like AI they don't communicate they are not on CTAB Other than this, all went smooth.
 
 

Hi Dusty
 
welcome back, I remember taxiing your team around in Vortex while back on EU2.
 
If you and your buddies ever want to try playing coordinated in even bigger team, give shot to the Enhanced Server (formerly EU3):
 
https://forums.ahoyworld.net/topic/7483-awe-basic-introduction/
 
good hunting

I thank everyone for coming and participating!
 
Ill take the feedback given to me and use it, I promise.
I think everyone, including me, had a blast during the event!

AFV - armored fighting vehicle - is the general class for all motorized, small rifle resistant, vehicles.
If you don't know/not sure what type you are facing, and it's not a car, call out an AFV, or "armor"
 
common sub-classes encountered in AWE theaters
 
APC - armored personnel carrier 
Role: fast, safe movement of forces in the rear, reconnaissance tasks, NBC troop protection.
Generally armed with medium caliber MGs. usually carry 8-14 dismounts (squad).
Protects from MG fire. 12.7/.50 AP and all RPGs are a threat.
 
Opfor include soviet BTR (8-wheeled transporter), BRDM (4-wheeled recon). Note, russian APCs have an advanced tire pressure control system, which allows them to move with flat tires, until the wheel is completely destroyed (simulated by RHS mod)
Blufor counterparts are M113, AAV, LAV, MRAP
 

 
 
IFV - infantry fighting vehicle
Role: enables infantry to keep up with MBT movement, carry/fire heavy armament and/or AA/AT rockets.
Armored front-line vehicles for mechanized infantry teams (6-8). Tracked, for true all-terrain movement. generally armed with large caliber MGs.
Resistant to 12.7, partially to 20mm. 30/40 AP and small RPGs will usually deliver a kill.
 
opfor: BMP (infantry - "pekhota") or the smaller BMD (paratroopers - "dessant" ) families.
blufor: M2 bradley
 
 
 
 
MBT - main battle tanks
Role: fast flanking attack of AT forces, support infantry by fighting enemy tanks. Note, since ww2 there are no real tank classes, so "tank" means MBT.
It has tracks and a big cannon. Also armed with coaxial MG, optionally independent medium MG.
Completely resistant to 12.7 and even 20mm. 30/40 AP may cause damage to engine from side/rear and tracks/MGs. only large RPGs are a real threat.
 
This is the soviet/russian "T" line (ww2 T-34/85, slow T-55, decent T-64 and T-72. top of the line are T-80 and T-90)
Blufor: 105mm Merkava and 120mm M1/Leopard2 lines.
 

 
 
You may also encounter the AA gun ZSU "Shilka", which boasts a nasty quad 23mm cannon (4000 rounds per minute which can and will be pointed at infantry). Or if Zeus really hates you a MRLS (multiple rocket launch system) BM-21 "Grad", which brings a battery of 40(!) 122mm rockets launched at once, designed to purge large areas. These are 'vintage' models designed more than 50 years ago, having very light to none armor, but their brute destruction force is not to be neglected.
 

 

Operation Whiskey Delta
 
Time: 1800 GMT (1900 UK LOCAL)
Date: Saturday 29th of October 2016
ASSEMBLE IN MISSION PLANNING 15 MINUTES BEFORE MISSION START.
Cover to your local time zone here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=AWE+Operation+Whiskey+Delta&iso=20161029T18&p1=1440
Correct Mission Version for Server: 1.10
Join Session in Progress is allowed, with the same rules as for unfair deaths (see below in important notes).
 
First off this is my first gamenight, and while every effort has been made to ensure no bugs  affect your experience, there may still be some present. My apologies ahead of time if this is the case.
 
So, the details. This is a ZEUS gamenight. This will probably be streamed, and if not, definitely recorded.
 
Map: Gorgona
Base: Main Base on the Island
Mission: A mission to recover Intel and render assistance to a local asset. This is all the information available at this time. The ASL or PLTCO will have ahead knowledge of the goings on of the operation, and they can disseminate information as they see fit. Be aware, this will not be an easy op, but I will not try to make you fail, expect a good fight. Be advised there is a road out due to a rockfall, shown on map by a red exclamation mark. This road is impassable and should not be used.
Time: Evening, not yet night.
Restrictions: No AT LAUNCHERS (You won’t be needing them). HAT, MAT, LOGI, TORCH, HAMMER and VORTEX 2 slots have been removed. In addition to this the COMMAND group consists of PLTCO and 2 Medics Only.  Normal gauntlet rules apply throughout.
Important Notes: Ace Medical Basic. Medics are the only ones able to administer Epi and Blood. If you aren’t familiar with basic please look here: ACE Wiki
Players should also be aware that there is a 1 life policy, ie. you die, you're done. HOWEVER, I have made it quite hard for you to die outright. There are no insta-deaths. Once in the down but not out stage, you have 150 seconds to be revived by a medic. You can be revived 2 times. After this you will die, and be able to spectate the mission, this is something you might want to do, instead of just disconnecting (HINT HINT). If you are killed unfairly (bad frag, or disconnect due to error etc.) you can respawn at a debug island. Ping Zeus to be re-inserted via a teleport. DO NOT SPAM ZEUS. Anybody trying to circumnavigate this process will be dealt with in a fashion...lightning bolts.
 
As there is only 1 vortex team slot,, there can only be one vortex bird, this will be the Littlebird Medium CAS variant. All troop movement will be done through Humvees, 4 door, open types. However others may be made available. This is designed to be a fun, infantry based mission, so don’t come packing loads of mags and ammo, 6-7 should suffice for the standard rifleman. This said, you may wish to have an ammo  bearer for normal mags within a team (perhaps whoever would normally bring AT). Due to the islands size (it is very small) there may be portions of the mission where you actually have to walk around, this will not be more than a click, so no moaning about a little legwork! While the armoured slots have been removed, the vehicles will remain spawned in.  They are there to look pretty and give you an idea what the base may look like when we put Gauntlet onto this map (or something requiring a base).
 
The arsenal used in this gamenight will be exactly the same as guantlet's.
 
ALL PLAYERS should be aware that the default loadouts are for ACE advanced. This is especially apparent for medics who will need to get blood instead of plasma (which is what  you are given by default). Basic bandages also suffice for all wounds, instead of the various types used in Ace Advanced.
 
And no, this won’t end with a nuke (Skull). Sigh.

 
Requesting a slot: Sign Up Here!: Google Form
 
I will try to post a roster ahead of mission start below, PLTCO and SLs will be aware ahead of time that they have this slot, as they will require a briefing from me. People who apply for this role will be screened, and I will only give it to someone who I feel is appropriate and can handle the workload. Per say, I would not recommend applying for PLTCO if it would be your first time in the role.
 
#SpoilerPhotos

lets sum up:
 
30 minutes waiting for server start&latecomers
45 minutes connecting & dress-up to scavenge some mis-matched OPFOR leftover gear
15 minutes driving truck throu the woods
15 minutes coming close to the objective
 
The moment we enter the village, walking with 2 teammates in front of me and 2 behind me - bang bang, instakill from god knows where.
Thou I wouldn't be suprised if that was blue-on-blue, I did had OPFOR PKM in hands.
 
spectator mode bugs after 30 seconds and no longer works with nighvision (only pitch black is seen)
 
10/10, will come to help save resistance again
 
 
If I can plead for some changes with Ryko:
Please spawn players with pre-loaded gear. Please don't wait for players who are not online in time, or did not downloaded their MODS in advance. Give the slots to replacements right away.
If necessary, latecomers filling primary slots can be teleported by Zeus to join the rest. just these two things will cut at least 45 minutes from the starting delay

lets sum up:
 
30 minutes waiting for server start&latecomers
45 minutes connecting & dress-up to scavenge some mis-matched OPFOR leftover gear
15 minutes driving truck throu the woods
15 minutes coming close to the objective
 
The moment we enter the village, walking with 2 teammates in front of me and 2 behind me - bang bang, instakill from god knows where.
Thou I wouldn't be suprised if that was blue-on-blue, I did had OPFOR PKM in hands.
 
spectator mode bugs after 30 seconds and no longer works with nighvision (only pitch black is seen)
 
10/10, will come to help save resistance again
 
 
If I can plead for some changes with Ryko:
Please spawn players with pre-loaded gear. Please don't wait for players who are not online in time, or did not downloaded their MODS in advance. Give the slots to replacements right away.
If necessary, latecomers filling primary slots can be teleported by Zeus to join the rest. just these two things will cut at least 45 minutes from the starting delay

lets sum up:
 
30 minutes waiting for server start&latecomers
45 minutes connecting & dress-up to scavenge some mis-matched OPFOR leftover gear
15 minutes driving truck throu the woods
15 minutes coming close to the objective
 
The moment we enter the village, walking with 2 teammates in front of me and 2 behind me - bang bang, instakill from god knows where.
Thou I wouldn't be suprised if that was blue-on-blue, I did had OPFOR PKM in hands.
 
spectator mode bugs after 30 seconds and no longer works with nighvision (only pitch black is seen)
 
10/10, will come to help save resistance again
 
 
If I can plead for some changes with Ryko:
Please spawn players with pre-loaded gear. Please don't wait for players who are not online in time, or did not downloaded their MODS in advance. Give the slots to replacements right away.
If necessary, latecomers filling primary slots can be teleported by Zeus to join the rest. just these two things will cut at least 45 minutes from the starting delay

lets sum up:
 
30 minutes waiting for server start&latecomers
45 minutes connecting & dress-up to scavenge some mis-matched OPFOR leftover gear
15 minutes driving truck throu the woods
15 minutes coming close to the objective
 
The moment we enter the village, walking with 2 teammates in front of me and 2 behind me - bang bang, instakill from god knows where.
Thou I wouldn't be suprised if that was blue-on-blue, I did had OPFOR PKM in hands.
 
spectator mode bugs after 30 seconds and no longer works with nighvision (only pitch black is seen)
 
10/10, will come to help save resistance again
 
 
If I can plead for some changes with Ryko:
Please spawn players with pre-loaded gear. Please don't wait for players who are not online in time, or did not downloaded their MODS in advance. Give the slots to replacements right away.
If necessary, latecomers filling primary slots can be teleported by Zeus to join the rest. just these two things will cut at least 45 minutes from the starting delay

Hi
 
as you probly know me and at least 2 other guys run into the "spamm protection" bug in TS again today when using TFAR. It has happened to people before and usualy clears out when you are out of TS for extended period of time.
 
But it needs to be fixed more properly
 
Don Cambio and me googled it, all seems to point to TS "flood protection feature" as in:
http://forum.teamspeak.com/threads/73725-Action-currently-not-possible-due-to-spam-protection
 
aslo suggestion on TFAR page:
 
To TeamSpeak servers admins
To be on the safe side, reduce the level of flood protection: Right-click on the server> Edit Virtual Server> More> Anti Flood, set 30, 300, 3000 values (top to bottom).
 

OPERATION ALIBI
Summary: a campaign-oriented, multi-session operation in which US Army SOCOM Green Berets (code name Panther) conduct special operations in the country of N'Ziwasogo.
Session 1 date: SEPTEMBER 23, 1900GMT (1500EST)
Your time: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Operation+Alibi&iso=20160923T1900&p1=0
 
Background
August, 2012. The government of N'Ziwasogo has been toppled in a military coup d'etat and the armed forces have assumed control.  The military junta has established martial law.  A group of guerillas, the Front de la Liberation du N'Ziwasogo seeks to restore the government to power, but they are woefully underequipped and poorly trained.  The whole mess has made it hard for international aid to get through: the FLN were on the USA's list of terrorist groups, and the junta doesn't want any outside intervention as they commence a program of ethnic cleansing.  Unofficially the US government has made contact with the FLN and will seek to covertly back them in overthrowing the junta.
 
Situation
Every Friday at 1900 GMT (1500 EST) either of Copey or Ryko will run the next chapter of the campaign. First session is September 23.
 
Alibi is primarily an infantry mission: there are four six-man fire teams, and one 2-man command group. If a player finds a vehicle and it's necessary to fly / crew it, then they can (ie., they don't need a special role to run a vehicle - we assume these soldiers are all trained to do a little bit of everything).
 
There are a maximum of 26 slots available in this mission, and signups will be opened on the preceding Friday, so you'll have one week to grab a slot.  You're welcome to switch up slots, but we'd love it if people stuck to a slot through the whole campaign.  Unfilled slots will be assigned on game night on a first-come, first-serve basis.
 
There will be no virtual arsenal.  Your equipment and ammunition will be limited, reinforced by covert air supply drop when possible: your ammunition will be tracked between missions.
 
Mission - CHAPTER 1
Panther will insert by HALO paradrop into guerilla-controlled territory and connect with a CIA asset (code name Atlanta) on the ground.  Atlanta will guide Panther to a truck park containing supplies for the construction of a FOB, from which Panther will conduct future operations.

Some points I would like to comment on.
 
I have logged into server just as Origins called everyone together and announced the "run down the airstrip for f*** around" command.
 
No idea what happened, I considered opting out for 1-2 seconds, but also understood this was a disciplinary thing and so made the run with others without any comments.
 
You mention that running isn't real punishment in game. I would submit, that the sole act of running isn't realy the point even in real life. The point is to make the person(s) responsible to feel guilty about dragging their comrades down with them. That's why units are often disciplined "as a whole" - because there is no "I" in the army.
 
Sure, we are neither an army nor a milsim, but my logic is:
Make EU3 play like a discussion society, and see how that will waste MUCH MORE of everyone's time, than one run down the airstrip.
And the more people are logged on, the more amplified this is.

I got wasted by BMP from behind too, when we were pushing from the forest to that last village. I would say our greatest weaknes were these armored vehicles - possibly because Apache was not utilised correctly.
 
As I understood from debriefing, Zeus was suggesting that Apache should have kept greater distance and perhaps used missiles against these hard targets.
But Helli pilots reported issues with visibility range which is why they come closer.
 
Admitedly, we were also stuck in that first compoud for far too long, because command structure was unluckily decapitated.

So it was U blowing that offroad in my face. Bad BAD Liru!!
 
Good fun overall, but the wheel-changing was rly draaaaag.
Next time lets do convoys with with simple repair mode on.
 

OK
Let me just sum up what I - as a casual player on AhoyWorld - experienced.
 
Couple days ago I have seen Liru's post that he wanted to run an unofficial gamenight - an even that would last about 1 hour. I signed up thinking it's nice that AhoyWorld members come up with such activity.
 
Yesterday I went to Ahoy TS and found the participating people in one TS room. It was stated that Shadow(if memory serves) will create ad-hoc server instance for this event - which seems reasonable, as not to interfere with usual activity on I&A. The server IP was eventually given in channel description. We logged, had one hour of fun and then went to do a debriefing - to have some discussion what went wrong etc..
 
About 1 minute into debriefing Liru disconnected from TS mid-sentence.
Some people then noted, that he got banned from the server. Since this greatly surprised me I stayed a bit to hear the staff explanation.
I did not caught it all, but seems that the problem was that non-AhoyWorld server address was given out on AhoyWorld TS.
 
Let me say two thing:
 
1) Never during the planning or execution of the event did I have impression that Liru or anyone else is trying to create new/separate community to the AhoyWorld.
In fact, I have chalked this event up as another proof that AhoyWorld is nice and active community.
Apparently, some members of the staff seen this in very different way. I wonder why that is? Miscommunication?
 
2) Even thou Liru might have broken house rules, I would expect that staff would give him a warning that when running event outside AhoyWorld, he needs to use separate TeamSpeak as well. Booting him from TS mid-sentence when there is ~15 other people listening to conversation seems very ham-fisted and paints bad picture.
 
I would appeal to staff, to take a moment and consider, if this could perhaps have been handled much, much better?
 

I joined a server I was given an IP to. I didn't notice what it was called or anything like that.

TL:DR -
Some people knowingly did wrong and got what they deserved, but let's not shaft Liru because of those people.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Content -

As Shadow explained on TS, the Server name was an oversight.
It had originally been created to test Mission files etc and was not intended to be used with the title as shown.

I am a part of the other community and have spoken with the Staff here also, and am fully in suppport of them banning people for blatant subversion of rules.

However, in regard to Liru, I believe the actions were a little rash.
Liru had no intention of 'luring' (lets use this term, it removes confusion) people away. He simply created a Mission for people to enjoy.

A former AW Staff member chose, stupidly, to post the website address for 'our' community which in both my eyes and the eyes of AW staff was the wrong thing to do.

I will not step up and defend those people who were banned for their own actions, they deserved it and are not likely to care.
I WILL STEP UP AND ASK THAT LIRU NOT BE TREATED AS THE GUILTY PARTY BY PROXY/ASSOCIATION.
 

It saddens me that it had to come to this. I see good intentions on both sides of this "episode". Shame you could not find common ground with Liru before this drama happened. 

This thing about luring people to other communities honestly seems little paranoid.
It's not like we are MMORPG hardcore raiding guild, freaking about losing key player(s) in middle of progress.
 
Been there, done that + all the Dramas, Ragequits & Flamewars™. I'm almost crying with nostalgia (almost).
 
PS:
I would speak for giving Liru some leeway about his ban appeal post. He wrote it shortly after ban and was clearly angry (who wouldn't).
Crucifying him over it is child's play, but also perhaps opportunity to be magnanimous.