Aces High Bulletin Board
Special Events Forums => Friday Squad Operations => Topic started by: APDrone on June 16, 2007, 10:50:06 AM
-
Greetings FSO Combatants!
Frame 3 finished up with another Axis victory.
A couple of notes. We're noticing some non-registered squad entries in the logs and have made adjustments to the scores to reflect that for this frame. This is not to say this is the first time it has happened, but to fire the warning shots that we will be paying closer attention to such infractions in the future.
Everybody who is a commander in FSO knows when the launch time is going to be. You MUST get your squad members signed to show on the logs. It is up to you to ensure your squad members show properly on the roster. Encourage your squad members to be present well before launch time to review last minute order changes and get properly signed into your squad.
This is especially true while scenarios are running and the higgledy-piggledy rigamoroll ( or substitute your own filter-safe rendition of FUBAR ) routine of squad shuffling happens every Friday.
Here are the scores for frame 3. Well fought all! I will have the synopsis of Summer Storm posted sometime before next weekend. I have bigger gators nearing my spleen..
(http://www.ka4zzq.com/Nightmares/CM/Frame3Score.JPG)
-
Drone:
I respectfully request reconsideration. Due to real ife issues, I was not able to even turn on my computer until after FSO had already started. Because I had walked on to Husky, my previous squad affiliation with the 332nd was erased -- and it just didn't occur to me till one of the CMs (was it Repo?) PM'd me and asked about my affiliation. I explained the situation, and he said "No problem -- jsut make sure you're in uniform next time."
Had I thought there would be a problem, I would have landed and either left the arena or gone as a gunner.
I flew with the 332nd the previous week, and have been with them both before and after their hiatus from FSO. I have not ever flown for another squadron in FSO. In short, I'm not a walk on, and I have a long standing affiliation with and FSO squad. Since my situation was discussed with and cleared by a CM during the frame, it seems unfair to penalize me or my teammates.
-
Thanks for the note.
We'll take that under consideration.
-
Originally posted by APDrone
Thanks for the note.
We'll take that under consideration.
Appreciate it. It wont change the team outcome, but it would have been the first time I finished an FSO alive, ever, in history...:lol
For what its worth, I immediately had TeeeRex invite me, but it didnt take because I couldn't relog.
-
Sorry APDrone. I was unable to attend that night. I had e-mailed my side and they knew about it. Ghosth and TeeeRex were running the show.
I usually make sure all my guys are in uniform. Simaril is good about that, but as he said he was involved with Husky too and he was late due to real life stuff. He has been an active member with our squad for a year and has flown in several FSO's.
dd
-
Allied: 1530+1191+1362=4066
Axis:1352+1349+1489=4190
Was concerned when most of my squad's leadership team missing Frame 1 and the complexity of my plan would hamper the Axis chances.
Glad to see those wiser than I closed the gap in the next two frames.
Was not able to attend any frame this go round and the loss is all mine :cry
And BIG to the community for cureing the (dare I mention) lowering Axis numbers problem we've had in the past when Frame 1 did not go so well. I remember simular settups that where a thump on the head for the Axis. Don't think the settup was that different, so it's got to be you guys.
-
a8thumpr popped into our mission about 30 seconds before we popped on the runway.
I sent a private message to REPO but I didnt really have time to figure out what to do about it.
-
was he supposed to be with you? If not, we will need to remove anything he did from the scores.
-
Originally posted by Gumbeau
a8thumpr popped into our mission about 30 seconds before we popped on the runway.
I sent a private message to REPO but I didnt really have time to figure out what to do about it.
Gumbeau, We need to know if he was supposed to fly with your squad. Or was he just someone that "popped" in.
-
I say penalize the Axis's 125 points for that mistake!
-
:lol Of course you do.
-
A8thumper was not part of the axis team. He was noticed by me on takeoff and I reported it to repo on 202. I believe kermit can confirm it.
I recognized the name as someone trying to get picked up during frame 2 the previous week.
I assumed he was kermits brother. :)
-
still need to hear from Gumbeau
-
Originally posted by SLED
still need to hear from Gumbeau
I can confirm a8thumpr was a gate crasher that just popped into our posted mission.
-
True...he flew along the outskirts of the 2 F8 squadrons and replied not to vox or text. :confused: No one in the strike group squadrons invited or claimed him.
-
Unless Gumbeau says otherwise, A8thumpr was not an legitimate player and his scores will not count.
Simaril's scores will count as he is a legitimate player in FSO.
Upon Drone's agreement he will tally the final scores with these changes in mind.
Regardless of final scores I feel this event was close to a tie, and well played by all.
IMHO events that score this closely are some of the best that are had. as the close scoring tells me that very few saw a one sided battle or died without having a good fight.
:aok
-
Sled,
As XXX has stated, A8Thumper was a gate crasher.
He joined our mission uninvited, and with no communication at any time before, during, or after the event.
Please do your score tally without counting his efforts.
!
Joe Savlan
-
So noted. Thanks for all your input gentlemen!
Simaril's efforts have been reinstated, since he had gotten the 'OK' from Repoman when he was having the roster problem.
A8Thumpr's contributions have been erased.
Now.. if everybody would stop for a moment and observe all the wasted effort we spent to clarify these issues, any doubts about why we insist on a clean roster should be expunged.
There are going to be times when people arrive late and won't be listed in the squad when it's time to roll. Commanders you do not need to be in the squads page in the O'club to manage your squadron. All the essentials you will need to perform you can do in flight.
Here is the page covering the radio dot commands:
Dot Commands (http://www.hitechcreations.com/ahhelp/dots.html)
Specifically, these are the ones you will need to know.
Command: .sqdname SquadName
--------------------------------------------------------------------------------
Parameters: SquadName; the name of the squadron
Available: Online
This command is used to change the name of the squadron. Only the CO or any persons in the squadron the CO has granted permissions to, can change the name of the squadron.
When you perform the .sqdname command, it will refresh the roster with the current squad name for all members, including any that may have just been invited. It is not necessary for new recruits to log out of the game and back in.
Command: .sqdinvite GameID
--------------------------------------------------------------------------------
Parameters: GameID; the pilot handle of the player
Available: Online
This command is used to send an invitation to a player requesting them to join the squadron. Only the CO or any persons in the squadron the CO has granted permissions to, can invite a player to the squad.
Command: .sqdeject GameID
--------------------------------------------------------------------------------
Parameters: GameID; the pilot handle of the player
Available: Online
This command is used to eject a player from the squadron. Only the CO or any persons in the squadron the CO has granted permissions to, can eject a player from the squad.
You will need that one for when your squad hits 32 members and you can't invite any more.
And, as is so often the case with scenarios running, you will eventually invite somebody who is already listed with a squad. If this is the case have them withdraw from their old squad. This can be done by them entering:
Command: .sqdwithdraw
--------------------------------------------------------------------------------
Parameters: NONE
Available: Online
This command is used to withdraw from a squadron. If the CO executes this command, the squadron is disbanded as well.
I hope you find this useful.
Oh.. and when you're mucking around with changing the squad names.. PLEASE, Oh Pretty Please, keep the name as close to possible as the name you have registered on the events server. It can be a headache trying to match up what squad is what when we're tracking things like attendance and CiC duties.
Thanks and good luck.
-
Even though the .sqdname SquadName command is for changing the squads name, you can in fact use the exact same name.
Just in case there are those as literal minded as I:D
-
Correct Hacksaw,
As a matter of fact, my squad "USMC/ 71sqn", is actually two separate squads in the SEA with the exact same name, CAPs and all. This way we are not constantly having to eject and invite people.
Also we all show together in the logs later.
-
Sorry I wasn't around to reply.
Glad XXX and Savlan covered for me.
Is there a CM command to send someone from flight to the tower?
If so... I would suggest a procedure to advise the CM of intruders so he can put them in the tower.
That would have been the desired result for me with A8thumpr.
I worried half the frame about his presence in our mission.
-
Originally posted by Gumbeau
Is there a CM command to send someone from flight to the tower?
If so... I would suggest a procedure to advise the CM of intruders so he can put them in the tower.
That would have been the desired result for me with A8thumpr.
I worried half the frame about his presence in our mission.
Better yet we have the eject button. But we only like to use this as a last resort.
-
Originally posted by Gumbeau
Is there a CM command to send someone from flight to the tower?
That's been on the CM Wishlist for a few years now.
Still hoping.
-
Originally posted by Gumbeau
Sorry I wasn't around to reply.
Glad XXX and Savlan covered for me.
Is there a CM command to send someone from flight to the tower?
If so... I would suggest a procedure to advise the CM of intruders so he can put them in the tower.
That would have been the desired result for me with A8thumpr.
I worried half the frame about his presence in our mission.
In that situation Gumbeau, and others. All you have to do is advise the Host CM that you have a possible "rouge" player that is flying without your consent. That set-up CM will contact that individual, and guide or eject him as necessary.
-
I always thought that "rouge players" were allowed. After all, Silat has ....umm...dressed up for years!
:lol
-
Rgr that Sim... there's a whole squadron of "rouge" players. :aok
*sigh* Is it really that hard to spell "Rogue"...? :confused:
-
You mean we're not a bunch of lipstick sissys? Dang, no more purses fights on Fridays and we'll have to stay exclusive to our 50 cal loving. Find us another fight Dux, I'm doing my part. :aok
-
Originally posted by APDrone
So noted. Thanks for all your input gentlemen!
Simaril's efforts have been reinstated, since he had gotten the 'OK' from Repoman when he was having the roster problem.....
Just wondering if you've had a chance to correct the logs. Daddog's been running cumulative stats for the squad since our return...and like I said, I don't want to miss the rare chance to log a landing and survival!
BTW, thanks for the dot command review. Not sure if he's said anything to you directly, but our squad BBS has been busy with discussion about using them!
-
When you say 'correct the logs'.. are you meaning to edit the log data and rebuild the reports showing you as in the squad?
If so, then the answer is 'no,' nor do I have any intention of changing the logs. Not to be mean, but mucking around with data seemingly leads to many hours of recovery due to a silly mistake.
I would highly encourage daddog to manipulate his data... please.
Glad you found the dot commands useful. Seems like every night there's a squad somewhere wrestling with them.
-
Hee hee...misunderstood the plan. If the logs are a headache, of course DON'T touch them. Leave it all alone!
Thanks for your help, and all the FSO work!