• Pacific Time Mountain Time Central Time* Eastern Time Western European Eastern European Eastern Daylight
    (GMT -8) (GMT -7) (GMT -6) (GMT -5) (GMT 0) (GMT +1) (GMT +10)


    *Official unit time is Central Time. All times posted are in the Unit time unless otherwise indicated.

Col Penny

Command Element
  • Content count

  • Joined

  • Last visited

  • Days Won


Col Penny last won the day on June 1

Col Penny had the most liked content!

Community Reputation

1129 Excellent

About Col Penny

  • MOS
    8041 Colonel, Ground

15th MEU Personnel Profile

  • 1) School of Infantry
  • 2) Qualified MOS
    1371 Combat Engineer, 0311 Rifleman, 0331 Machine Gunner, 0369 Infantry Unit Leader, 8999 First Sergeant/Sergeant Major, 0302 Infantry Officer
  • 3) Corporal's Courses
  • 4) Sergeant's Courses
  • 5) Staff NCO Academy
  • 6) The Basic School
  • 7) Auxiliary Qualifications
  • 8) Date of Rank

Recent Profile Visitors

4036 profile views
  1. Servers - A Breakdown - Follow-up

    Attention All Hands, Following up with last cycle's post regarding server issues I would like to get everyone into the loop to what's going on now. Task Force Alpha, essentially, accidentally ran next week's test. The ping kicker was accidentally left off prior to the first catastrophic server crash (although the kicker for desync was left on). Task Force Bravo also had both of these disabled. Prior to combat I tried to keep an eye on ping/desync for Task Force Bravo, and everyone was below 250 ping and no desync, which is good. Once combat hit though, and given the other issues, I was unable to continue to look at this. Task Force Alpha's server was rebooted after the initial crash, re-enabling the ping and desync kicker. From this moment on they had no issues. We also encountered issues within the mission itself not related to players. We noted heavy desync increases when utilizing Zeus Artillery, especially heavy or concentrated fire. We also noted major jumps in playability when removing groups in buildings with ACE Garrison. This was also slightly marked with enemy air assets. We could also be experiencing issues with JSRS. It's still unknown exactly what caused the issues for Task Force Bravo to be unable to hear gunfire. What we did conclude was that gunfire was unable to be heard from downrange, though we could still initially hear it during testing by being right next to the OPFOR. Initially we believed this to be an issue with only GHM and BRG units, but it was also claimed to be heard with ChDKZ units (however many of these claims came during a period of time when there were zero enemy units on the map at all, so the complaint is suspect). Task Force Alpha had none of these issues. All of this could, also, be related to Tanoa, or at the very least the specific area of Tanoa Task Force Bravo was operating in. We also determined that, given the marked improvement for even Task Force Bravo with no 'safety net' that the datacenter hosting the Unit's server box is subpar. This server will likely be scrapped and we will move forward with the new procurement. We also noted some things we can do better on the S-Shop end of things to improve performance and cooperation. This includes the server load-in method. We are not seeing any marked improvement for performance using the all-in load-in method, and Zeus is instead suffering in focus and effectiveness. Thus we will be returning to the piecemeal method to allow Zeus time to set up and concentrate without rush. To summarize all of the above: Task Force Alpha's year-long issues can be linked to a particular set of personnel. TFA crashed initially due to a few reasons, but one of which was the ping kicker was not enabled (desync kicker was, that's why you saw some personnel kicked). TFB did not have these enabled either, and did not have as many issues (ie. server crashing). Ping/desync kicker is going to need to be enabled for the first time in Unit history (thanks ArmA). Changes to the coding have now made higher ping level unforgiving. JSRS is likely an issue, again. It should probably be removed from client side approved again. It's only partially confirmed it caused the inability to hear gunfire. This will continue to be evaluated, though it is recommended you cease running it. •The Unit Server Box datacenter is subpar (though the hardware was in a class of its own) and also likely contributed to TFA's issues this year. It should be canceled and scrapped. Zeus needs to lighten up on the artillery shells. It will not go away entirely, but it will be markedly less. ACE Garrison is wonky. TFB server FPS went from 19 (AI and players skating around the map) to 24 (passable) by removing garrisoned AI. This should be avoided. We are not gaining any marked server performance with 'all in one' join, and Zeus' performance is suffering because they are being rushed. We will return to piecemeal load (except for server crashes/reboots) and allow Zeus their set-up time again. S-4 Mission Team needs to be included on S-2's 'plan' so they can pre-place AI and objectives better on the mission file. This will not only enhance the experience, but server performance from pre-spawned AI and Zeus from rushing all the time. Enemy Air Assets need to be limited in their runs, much like ours. A Ka-52 was left free over TFB and not only did it wreak havoc on a TF that had no protection, it impacted the server quite a bit. These should be available for time intervals and then removed if they are not pursued or destroyed by ACE in that time. Potential for Tanoa to be fucking us over, but there's little we can do about that. Some of TFB's issues may have been related to the specific area we were in. The ping/desync kicker will be implemented effective immediately. For OP 04-18 it will be set at 450 ping and 1700 desync. Immediately following OP 04-18 these will be lowered to 300 ping and 1500 desync, and remain in effect until the ArmA code changes to be more forgiving again. Tests are, for the most part, concluded, and we should begin to see marked server improvement beginning this week with these new implementations. Further issues are likely to be related specifically to ArmA updates/mod issues (because of, or independent of, ArmA or other mod updates), the map, or (currently) JSRS specifically. -Col Penny MEU CO
  2. Father's Day/17JUN18 Operation

    Attention All Hands, This coming Sunday, 17JUN18 is Father's Day. Originally we were scheduled to have this operation off. However, given recent events of the past few operations, we feel it would be inappropriate to cancel this operation, and rather we should carry our positive momentum forward and finally have a good operation. Because of this we are going to have an operation. However, given that it is Father's Day, this operation will be non-mandatory. That means all absences are excused in light of the holiday and you are not required to attend (however if you're not attending festivities why wouldn't you?). Have a Happy Father's Day. And don't forget to call your dad. We'll see most of you Sunday. -Col Penny MEU CO
  3. The Tip of the Spear

    FROM THE DESK OF THE MEU CO 21JUL18 (IGT) 0930 Local (IGT) Sailors and Marines of the 15th MEU (SOC) [Realism Unit], We have been tasked with a difficult job: The recent cyclone and flooding of the island of Tanoa has devastated the local civilian populace and further destabilized the local government, who is already in the midst of a growing insurgency. We, having been in the area, were tasked to assist the local government with relief efforts and to quell the unrest. Another power of the area, the Democratic Republic of Borneo has also sent forces to the area to assist. It seems we may have ruined some of their plans. Approximately two hours ago forces of our India Company were conducting searches in our agreed-upon area of operation to find intelligence on the local insurgency. For this, as normal, we had rotary forces deployed in support. An unknown aircraft, since confirmed as a member of the air forces of Borneo, shot down and injured Marines operating one of our aircraft. Flying CAP in the area along the No Fly Zone, one of our F-35 pilots witnessed this and sprang into action to prevent further injury or loss of life. In his zeal to protect his comrades, this pilot crossed the No Fly Zone, which seems to be exactly what the Borneans wanted. Almost immediately artillery units of the Borneo Revolutionary Guard deployed to the area opened fire on India Company and attached elements, forcing them to take cover in the local jungle. Air forces of the BRG were further deployed to intercept our air assets, harass our ground troops, and even mounted an attack on the ESG Matthew Barton. I have since spoken with USPACOM, the Joint Chiefs, and the President. It is agreed that the rapidity and eagerness of the response by Borneo troops means they expected us to do exactly as we did and that we were led to such actions. We suspect that Borneo was going to attempt to utilize the recent natural disaster and local insurgency to expand their territorial holdings and take control of the island of Tanoa. The President has directed the 15th MEU to prevent this from happening. Intelligence has reached us that Bornean troops are now on the move across the borders of our agreed-upon area of operations. Effectively immediately I have given orders to our air forces that a No Fly Zone no longer exists for anyone except Bornean Air Forces, and they are to execute such a No Fly Zone aggressively. We have been directed, and orders are coming to you as you read this, directing our forces to intercept and block the movements of aggression of Bornean troops. It is no question that a state of war now exists between the Democratic Republic of Borneo and the United States of America. As the Tip of the Spear of US forces in the area we must, and will, aggressively defend not only ourselves, but our local Tanoan allies. We will seek out and kill anyone who attempts to hurt us or our allies. The Borneans must also deal with the local insurgency, so neither of us are in for a fun fight. A three-way war between a well-trained and well-equipped conventional enemy nation and a local insurgency who is convinced God sent them to kill Americans is nothing anyone hopes for... but if there's one Unit who can handle it it's on the ground right now. Reinforcements are on the way, but I don't think I'm the only one who says we don't need them. We can take care of this mess. Let's do so and go home, and leave the Army to clean it up after us. Ooh-rah. -Col Penny MEU CO
  4. OP 02-18 OPFOR Issues

    Attention All Hands, 'Furious' and 'spitting mad' are phrases that can perfectly encapsulate the response to the OP 02-18 actions, and yet still not even come close to understand exactly how angry very nearly everyone - including myself - were at what occurred that night... or rather didn't occur. Because of this I thought it would be good for you to all understand what happened, and what will be happening going forward for the rest of this deployment. OP 02-18 was intended to be the consummate COIN operation. GCE would have been searching the structures that they did, but they would have found something. The intelligence found would have represented very important repercussions to the main story line plot (of which many of you have been grossly under-informed about) and had lasting and damning consequences for our stay on Tanoa. This was directed, however it was failed to be relayed to the Zeus Guide, and thus failed to be executed. During your search GCE was intended to take constant harassing fire by local insurgents. This was not a large force. At most there would have been 10 enemies total, but in most occasions no more than a team, constantly stalking GCE and harassing them with small mortars and small arms fire. It would have been frustrating and yet interesting, because it would have been exactly what is encountered in the real world. This was relayed, however it was not executed. Both TFA and TFB experienced, and return, no gunfire at all. In some case no enemies were spawned at all, and in some cases small amounts of enemies were spawned, but in no areas nearby of GCE for them to actually engage and... you know... matter. After stomping around the H&S Channels finding out who I was going to fire, or at the very least NJP, the following courses of action are being implemented to ensure a productive and enjoyable Sunday operation is had by all parties: COIN is done. This is not just because of the storyline, but by know I hope you all understand that COIN in ArmA is not only not fun, but highly difficult to execute without a system like ALiVE - which no one wants to get into. Beyond that almost every here is here for fun and action. COIN Operations provide this for very few people, and that is only those who get to actually operate. The 'vote' held previous to this deployment which showed COIN was heavily favored and wanted prompted the course of action the first few operations of this deployment have taken. You all should know finally see and understand why this is terrible, and why most of our deployments (and all of our successful ones) have been fully kinetic ground wars. This Unit emulates the Marine Corps, but we do not simulate it. Our deployments will be highly kinetic ground wars with focus on action and fun. I hope you all now understand this... we will revisit it in two years when the new blood clamors for it and the old new bloods forget. The 'chess match' of S-2 versus S-3 is done. The last successful 'chess match' was between MSgt Phillips and I when we were directing operations, however it was less departmentalized and closeted than it is currently. S-2 and S-3 will now be working hand-in-hand to direct the OPFOR and BLUFOR movements to insure a healthy and fun operation. Some of these may be lighter operations than others, but these days of 'oh you moved to an empty square, no enemies there, sorry' are over. OPORDs and all S-3 movements will be approved by MEU HQ prior to publication. MEU HQ will work hand-in-hand with S-3 to ensure movements are realistic and provide a fun and dynamic atmosphere for everyone. Failure to follow through with this work will result in formal disciplinary action, and possible replacement. S-2 Intel Reports and OPFOR movements will be approved by MEU HQ prior to publication or enaction. MEU HQ will work hand-in-hand with S-2 to ensure all movements and actions are realistic and provide a fun and dynamic atmosphere for everyone. Failure to follow through with this work will result in formal disciplinary action, and possible replacement. All Zeus Guides will be reviewed and approved by MEU HQ prior to publication. These guides will be filled with plenty of action, dictating realistic movements of the enemy, and will provide a fun and dynamic atmosphere for everyone. Failure to execute these guides properly will result in formal disciplinary actions, and possible replacement. I am further preparing other actions which will dictate next year's deployment. I am not prepared to divulge those actions yet, as they are still in the infantile brainstorming stages, but they could end up involving other units, with our units and other existing on the same universal plane. These will not only involve dynamic story elements all over the world, but open avenues for joint operations with other units during deployment. OP 02-18 was beyond unacceptable by the standards and expectations of not only MEU HQ, but every individual in this Unit. It is the last in a string is miscues and lack of execution that starts with MEU HQ. It will not be repeated. -Col Penny MEU CO
  5. Servers - A Breakdown

    Attention All Hands, The last few weeks we have been testing and changing many settings and possibilities with our servers, which have not been working in the year of 2018 as we expect them too. These can be drawn back to a multitude of reasons, most especially mod and ArmA updates, but that doesn't really tell the whole story. I will attempt to break that down somewhat, as best I can. Updates There is really not much we can do here. We are all at the mercy of the updates to ArmA, and any changes they do are effective to everyone immediately, and there is no stopping it. In ArmA 1 and ArmA 2 we were able to tell people to hold off of updates until those updates had been vetted, and any possible hotfixes had been made, if needed. Unfortunately the nature of ArmA 3 and Steam makes this impossible now. As such we are at their mercy. We have recently switched to Steam distribution of our major mods (CUP Terrains, ACE, RHS) in order to keep us in line with these major updates. If a major update is applied to ArmA, we are able to follow the immediate update of these major mods through their Steam distribution, without worry of missing them because it's too late to update our repo or to get people to update. Unfortunately there is nothing much more we can do on this front. We can be more diligent on the types of mods we add to our pack (ie. the SU-34 that was added to the OPFOR pack and was explicitly told not to be used... but why was it added in the first place in that case? Or the invisible MiGs) but the updating and any possible instability from those updates are something we cannot do anything about until it happens, really (like the cTab memory leak). Hardware Many people have brought up concerns of hardware. Allow me to give you a breakdown of our server hardware: 1 Gbps Dedicated Port Bandwidth Unlimited (10TB Full Speed) 16 GB DDR4 RAM Intel Core i7 6700K 256 GB Primary SSD Drive Windows Server 2012 R2 Standard DDoS Protection 20 Gbps DDoS Protection This is a very powerful server, more than suitable for ours, or anyones needs. This is not a question of hardware. However. We have, regardless, purchased a secondary server for testing purposes, on the hypothesis that there is an issue with the data center. This server is what Task Force Bravo was operating on during OP 02-18. While the server performed well, it was inconclusive as to whether or not this new server is the/an answer. That will not be clear until after OP 03 or OP 04, depending on the outcomes of tests during those operations. Settings We have talked a lot about server settings during this fiasco. A lot of care and attention has been paid to these settings, being tweaked here and there to attempt to get that sweet spot. I could get in to what we've done with 'Max Guaranteed Bandwidth' and 'Minimum Messages' and a whole bunch of crap.. but I won't. Mostly because it's boring and I don't even understand it all personally. Suffice to say in the majority of settings we have what is required and needed, but we need to talk about one specific setting: Max Ping and Desync. I spoke about tests earlier. Many of you know that for the past few operations we have been using the MSOT server box to load balance our servers in attempt to see that the issues are. In OP 01-18 Task Force Alpha operated on the Unit Server Box, while Task Force Bravo operated on the MSOT Server Box. Both servers ran the exact same settings, with the exception of this ping/desync kick setting. TFA did not have this enabled. TFB had this enabled for all pings over 450, and desync for over 9000. TFB ran at 45 FPS all night, with no issues. TFA crashed. Catastrophically. This is when Maj Thomas purchased a new server box (hereafter referred to as the Thomas Server Box). OP 02-18 saw TFA operating on the MSOT Server Box, and TFB operating on the Thomas Server Box. Both servers had the exact same settings, including the ping/desync kicker. Both servers ran at 45 FPS all night. However because of the lack of OPFOR, this is an inconclusive test, though one that does draw some very concerning conclusions. OP 03-18 is going to see a follow-up tests. Company HQ and 1stLt McNeely are already aware of this impending test, as well as anyone who read my post in the Tun Tavern (forums or Discord). OP 03-18 will again see TFA on the MSOT Server Box, running the same settings. TFB will be operating on the Thomas Server Box, however we will be removing the ping/desync kicker. There are two possibilities of the outcome: 1) TFB runs with no issues. This points to either an issue with the Unit Server Box or the specific personnel makeup of Task Force Alpha, with a handful of individuals causing the lacking server performance 2) TFB runs with many issues. This points to a fundamental change in the netcode of ArmA, no longer being so forgiving to those with higher desync and ping. In the case of outcome #1, we will in OP 04-18 be placing TFB on the MSOT Server Box with the 'control' settings, and TFA on the Thomas Server Box without the ping/desync kicker. If it performs without issue, then we know the Unit Server Box was an issue, and it will be cancelled, and MEU HQ will foot the bill for the Thomas Server Box and an additional server box to compensate (the Thomas Server Box is a smaller VPS that is less able to run two full-sized Task Forces at once) until September, when donations were collected through. If it performs with issues, then we know it is a specific personnel composition to Task Force Alpha. In the case of outcome #2, we will be forced to permanently implement the ping/desync kicker on our Task Force Servers. This will lead to many of our Asian, Australian, Eastern European, and some Western European members being unable to join us anymore, and close off that avenue for a long time to come. If it comes to this, we will be discussing the opening of a sister/child unit catering specifically to these regions, or directing those interested to other units with which we already have close contact that cater to these regions. This will be a public discussion for all of those affected. I understand you are all frustrated. Believe me, so am I. Most of you understand that we have been working on this furiously, however there are some of you who would like to ignore that fact. This Unit has been through many such trials and tribulations that ArmA likes to throw at us. You can cower and point fingers and cry and quit if you like, lacking the fortitude and will to weather issues like your brothers and sisters of the Unit deserve; or you can buckle down and raise one another up. We all come here for Sundays, obviously, and we will always do everything we can to make those enjoyable and memorable experiences. But we all stay here for the ones beside us. Don't forget that. We are on the cusp of having this fully solved. It may be May, basically June now, but this has been a more... interesting... year that ArmA has given us. So let's make the second half our little bitch, shall we? -Col Penny MEU CO
  6. 15th Pack - 24MAY18 Update

    Attention All Hands, Please take notice of the 24MAY18 15th Pack Update and update your packs accordingly. Repo will be updated soon. -Col Penny MEU CO
  7. Teamspeak 3 Update

    Attention All Hands, Update to Teamspeak 3.1.9 is now authorized and required. Please update your clients. -Col Penny MEU CO
  8. CH-53 Detachment Re-designated

    Attention All Hands, Effective immediately the CH-53 Detachment will be re-designated from HMH-466 "Wolfpack" to HMH-465 "Warhorse". -Col Penny MEU CO
  9. New Cadet Corps HQ

    Attention All Hands, Given I have no had half the time I expected to have, and what effort I am able to focus here must be focused on the Main Unit, I have gone ahead and found a new HQ element for the Cadet Corps, and the timing could not be better. Effective immediately: Sgt Riggenti will be taking the role of Senior Cadet Corps Instructor. Mr. Riggenti has been with the Cadet Corps for a long time now as Basic Training Instructor, and assisted/replaced me as Task Force Commander for their recent FTX's. He has great vision on what the Cadet Corps is intended to do and needs to do to be successful. LCpl Siddiqui, newly transferred from the Cadet Corps, will be taking the role of Cadet Corps Instructor. Mr. Siddiqui has been with the Cadet Corps very nearly since the beginning, and has suffered through all its throes of membership, and has been leading it by merit of himself as its squad leader for some time now. He knows the Cadets and its program inside and out, and is looking forward to his next step of making the Cadet Corps successful. Congratulations, gentlemen. I look forward to working with you. -Col Penny MEU CO
  10. 15th MEU Realism Unit This is to certify that the Command Staff has awarded the Navy Meritorious Unit Commendation To: All members that participated in combat training exercises or in support of those exercises during SOCEX 2018. (Complete list in following post.) for Participating in at least one official combat training exercise during SOCEX 2018. Given this day, 01 May 2018 Signed, Col Penny MEU CO NOTE: The list following is a list of eligibility. If you have already received the Navy Meritorious Unit Commendation previously you will not be awarded twice. Abernathy Ackles Adam, S. Akif Aleksic Alexander, M. Allington Anderson, G. Aoto Apollo Arana Bahnasy Bajor Baker, M. B. Banks, L. Bashore, S. Bass Bayless Beach, J. Bell, J. Berry Biggs Bisarra Bison Blackburn, A. Blackwood Bliss Bowman Breach Bridger Bruce, R. Burton, C. Bushwig Caesar, P. Calais Cariddo Carlton Caron, T. Carr Ceasar, P. Chan, C. Charboneau Chevy Christian Cloma Coffield Cohrs Collins, M. B. Conway Costello Cuendis Currier Davis, B. Davis, S. Davis, T. M. De Lacy De Landelles De Munck Deaza DeSol Drew Elkin Estes, W. Evans, J. P. Faigin Faulkner Fiore Flavin Fly Frable Franzen Frey Frost, N. J. Gage Galen Gall Geare Genge Gentile Giles, T. Glenn, J. Glenn, W. Goin Gorleer Graff Grant, R. Greene, K. Greene, P. Grimson Grivas Guerrero, E. H. Hansen Hable Hampton, B. Hansel Hansen, A. Hansen, H. Harris, B. Harris, H. Hawk, P. Heckman, T. Henry, C. Hernandez, N. Hetzel Hoagland Hodos Hoffman, T. Holcomb Holiday Horta Hunter, M. Husted Imya Isaacs Jackson, N. James, C. Jefferies Johansen, D. Johansson, P Johnson, A. B. Johnson, D. Johnson, R. Johnston, C. Karelia Khairi Khil Kingsley Kline Krima Krisanits Lacey Lacey, J. LaFave Lamb, E. Lane, N. Latham LaVigne Lebowski Lee, D. R. Lee, J. I. Lewbowski Lockworth, S. Loh Loveless Lowther Lucier M. Osborn Mahlum Marcaeus Marik Martinez, S. Matousek May Mays, C. McArdle McCoy McCoy, J. McDonald McGregor McLaughlin McNeely Medina Melnyk Merc Michaels Miller, J. Milne Mitchell, H. Moore, J. Moore, T. Moser, C. Muffie Muir Mumm Muniz Murphy, J. Nagato Nguyen, T.T. Nissen O'Connor Oelschlager Olivella O'Regan Osborn, M. P. Caesar Padgett Page Penny Petersen Phillips Pole Prochniak R. Johnson Raines Reed, P. Riske Roark Rodriguez, A. J. Rush Russell, C. Rust Saint Santiago, B. T. Sareema Schirf Schultz, D. Scullion Sharon Shelton, C. Shipman, S. Shum Sicuro Simons Smith, C. Smith, J.D. Smith, T. Smithee Smoles Sobchak Stearns Stevens Stevens, J. D. Stewart, B. Stewart, B. D. Stryker Sullivan Sweet T. Smith Taylor, H. Teed Thomas, D. A. Towers Turner, J. D. Underwood Uno Updegraff Usi Velten Verta Watkin Watson, C. C. Whelan Whitcome Wilkins Wilson, M. Wilson, Z. P. Wright, N. Wulff Young, W. Zahj Ziegler
  11. New Server Launch Method

    Attention All Hands, This Sunday (06MAY18) we will be attempting a new method to launch the Task Force servers. Previously we have always started the mission and had Zeus setting up while people join in progress. Instead we will be holding the server at the role selection screen, loading everyone in (using normal joining scheme), and then starting the mission with everyone in their role and at the screen. This new method does not get rid of this order. Zeus is familiar with this methodology, all most personnel need to know is that you will join the role selection screen and select your role, then wait. -Col Peny MEU CO
  12. Col Penny

  13. New Disciplinary Article

    Attention All Hands, We are adding a new article to the Disciplinary Articles of the Unit Policy Manual: 10-7.11 Pattern of Misconduct Any member that commits repeated violations of policies in which each violation by themselves only amount to minor disciplinary action; however, the violations together show a pattern of misconduct. Simply put: There have been identified previous issues of individuals displaying regular conduct of detrimental activity which individually do not fall under any major violation or require heavy steps; however when put together they create a picture of a member who is simply here to disrupt the activities of others. In the past we have been forced to ignore this or simply file the issues under an umbrella of 'General Article'. This was insufficient. This new article should make it possible for the Unit and subordinate commands to take steps to protect their sections and the Unit as a whole more effectively. -Col Penny MEU CO
  14. Unit Counselors Applications

    Attention All Hands, For some time now we have neglected the role of the Unit Counselors, leaving them sitting empty. We are now taking effort, by prompting of 1stLt Graff, to revitalize the program and get it effective again. Thus we are taking applications for: 1x Unit Counselor to represent ACE 2x Unit Counselors to represent the Supporting Assets (AAVs, Tanks, LED, MSOT) A Unit Counselor can be summarized as a couple things.. they are experienced and well-respected members of the unit to whom the members of the section(s) they represent can approach about issues with Command Staff or their Chain of Command (it's meant to complement the Chain of Command, however, not replace it), guidance for one's 'career' within the Unit (S-Shop or primary billet opportunities), and an assistant representative for disciplinary actions (they are not LAWYERS, but they can accompany a member to a Disciplinary Hearing to hear the issues and recommend courses of action for that member). If you would like to apply to be a Unit Counselor you must send an application to @Col Penny, @LtCol M. Alexander, @SgtMaj Hoagland, and @1stLt Graff detailing why you should be selected to be a Unit Counselor, why you want to be a Unit Counselor, and at least two recommendations from members of the section you are going to be representing (to be clear.. these representatives must come from that section; a GCE member cannot represent ACE, for instance). Any questions regarding the role of counselors may be directed to any of those four individuals directly. @1stLt Graff as the current sole Counselor, and previous Senior Counselor, will have the most information. -Col Penny MEU CO
  15. XML Fixed

    Attention All Hands, Thanks to the efforts of @LCpl Bass our Unit Squad XML script has been fixed and is now back in action. Command and S-1 will be uploading a new version of this XML every operational weekend Saturday (the morning of LED operations). As a reminder for those of you who may not know: The Squad XML is considered a part of your uniform and is required for all operations. This means: If you still have the old ArmA 3 Units as your 'display' XML it should be removed. You can still remain a part of the group (it's still used for recruitment purposes) but it is not to be used for display for operations. It is easy to identify: The Squad XML will display a tag of '15th MEU(SOC)' while Units will display '15th MEU'. Also the Squad XML will not show a unit patch, while the Units will display the subdued 15th logo. Your in-game name should display the rank you are currently. DO NOT update this rank after promotions during platoon briefing, before the promotions are officially posted. This will cause your XML to break, spout a server RPT error, and cause you to be out of uniform. E-1s and SNAs may occasionally notice their name not make it on the XML. This will not be common, but it is a possibility. All other grades have zero excuse. If you believe your XML may not be working contact S-1 Personnel. Beginning the first deployment operation (06MAY18) any personnel found to be out of uniform with their XML will be subject to points removal by NJP. This is a very simple thing to rectify that goes a long way to displaying our unit pride and looking professional. Take responsibility for your in-game 'uniform' in the same manner you do everything else. -Col Penny MEU CO