Commander Whitelist Application
Byond ID? forest2001
Player Name You Use Most? Charles Edwinson - CE & Command, Percival - Synthetic, Arthur Edwinson - Enlisted & Others
Make a list of links to all of your applications and (job)ban appeals, including whitelist and staff apps, within the last year. Also, provide "Ban reason; Verdict" beside each (job)ban link
Have you received any ban within the last month? How long was it and what for? No
Do you understand that any player - even donors or staff members - can have their whitelist status revoked should they break our Server Rules or Roleplay Guidelines? Yes
How do you view the tool of Battlefield Execution to be used? What circumstances do you think it would be necessary to BE a member of the crew? Where do you think the Battlefield Execution Mechanic Differs from regular Execution and why? My view of the Battlefield Execution is that it is a complete last resort and I believe it is currently overused. Whilst I agree that most situations it is used are completely valid, I would personally prefer to attempt to find an alternative to execution.
The circumstances I believe would require a Battlefield Execution is when for example a lieutenant is deliberately aiding the enemy forces (sedition) and I haven't the time to wait for MPs to detain and proceed for a formal execution. Or alternatively someone is killing my crew and I'm nearby. If their being removed is crucial, I'll do it myself. If I can afford to have MPs handle it, I will.
The Battlefield Execution differs from the regular execution because it is a rapid and final resolution of a critical situation. Where a formal execution can take some time and is rarely possible for matters of extreme urgency.
How will your Commanding Officer run his/her ship? Provide a detailed explanation on how he would handle situations that might commonly occur such as, a insubordinate Req, Engineering, MP, or Command Staff I intend to run the ship with a much more administrative approach to ensure I am effectively delegating tasks to my subordinates, where possible I intend to leave the majority of the operational action to the rest of the CIC team and oversee the running of the operation and ship from a more withdrawn position. My decisions are final, but I am more than happy to take advice from my officers and crew and want to encourage free thinking and letting the CIC team garner more experience.
I am very aware of what falls within IC and OOC purviews (e.g. OTs bombing the ship being a no go), however I wish to answer all the potentials from an IC perspective regardless.
Requisitions:
Requisitions is the lifeline of any operation, an efficient Req team can help turn the tide of a failing mission, and a poor one can cripple the operation.
Due to this, it would be a priority of mine to ensure Requisitions is functioning effectively. I’ve seen a lot of Req teams abused and mistreated by both command teams and/or marines and I don’t intend to allow that, however I have also seen plenty of rounds where Req have pushed their limits far beyond what they should be allowed to get away with.
If the Requisitions team is being insubordinate I would have them arrested or talk with them directly where possible if I believe that would help instead. Fortunately, as requisitions is not something limited by skills I would appoint 1-2 marines or other crew to take the place of whomever I have arrested.
Engineering:
With the new OT updates engineering is an extremely dangerous department if it were to cease supporting the operation for whatever reason. Considering the dangers of potential rogue explosive devices being used aboard the ship I would be quite eager to ensure they’re brought back in line.
It’s also very circumstantial to what the actual issue is. If an OT is refusing to follow a deployment order and we desperately need engineers I would either forcibly have them deploy with an MP escort or have them detained. The issue with this is that they’re no more use to me in the brig than they are if they refuse to deploy, indeed even less so.
If engineering is instead spouting seditious remarks or other such actions that go against the operation directly I would take a harsher approach. I would rather not take any chances and would have the MPs detain the perpetrators and charge them accordingly.
Ordinance Tech built explosives are valuable assets, but they are not crucial to mission success. And due the reactors no longer requiring maintenance the engineering team is not a critical asset anymore. With this in mind it is safer to detain and punish those that pose a threat than to provide concessions in favour of having more explosives.
With all that said however, diplomacy and discussion is the first step to resolving any conflict. If diplomacy fails, force is used.
MP(s):
The MPs are my eyes, ears, and hands around the ship. If they turn against me for whatever reason the first action I would take is to inform High Command via fax. If a standard MP is insubordinate, I would talk with them as to why they are refusing to obey my orders, and unless their answers are satisfactory, I would pursue a legal response and have the CMP detain them. If it is the CMP themselves that is insubordinate, I would be less forgiving. I hold officers to a much higher standard than the enlisted forces. I would give the CMP a second chance to obey my orders and then failing to obey then I would order their immediate arrest and fax High Command for their demotion and court martial.
Command Staff:
As I plan to give the Command Team a lot more liberty than many COs, insubordination is more troublesome and not something I will be very tolerant of. If someone countermands my orders, or otherwise orders people to do something I have told them not to, it had better be for a damn good reason or there will be consequences. Everyone has second chances, I do not want to judge people by one bad decision, but beyond that it will be the cells. If I have no MPs available then I’ve little choice but to be a bit more tolerant. If they become a risk to the operational integrity however, then I have only one alternative.
Medical:
Where Requisitions is the metaphorical lifeline of the operation, medical is the literal one. The only time I intend to intervene in medical is if people are refusing to perform surgeries or revive people. I do not care if chemicals are not being made, they are a privilege not a right. But if they are endangering the lives of my marines, I will take necessary action to force them to do their jobs. A doctor in a cell is no use to me. Unless they are breaking serious laws and causing actual harm through their actions, and not inaction, I would prefer to keep them out of the brig. I may station an MP or an officer if one is otherwise free, to oversee medical and make sure duties are being carried out. Persistent refusal however will just land the perpetrator(s) in the brig. If they absolutely will not do their duties, then I am not going to let them faff around doing what they please.
What do you think is the job of a Commander? I believe the role of a Commanding Officer is to improve the round by providing unique RP opportunities. I do not believe they are integral to the round nor operational success. I think that a Commanding Officer should attempt to make the round more enjoyable for all players by experimenting and trying new tactics and approaches to the round rather than the standard "its Team Deathmatch and I want to win" route.
As a player what do you think could be added for Commanding Officer to benefit the role? I think it would be nice if the CO had more ways to reward the excellency of his troops rather than just medals. An idea that occurred to be would be to implement a functional Echo Squad and have this be a medal tier reward. To explain better, allow the CO to appoint marines to positions within Echo Squad which could give them some perks such as cheaper gear or rarer weapons? I'm well aware that this could and likely would lead to round start making all of a squad into Echo Squad and powergaming it as best as possible, but I think having a way to coordinate and utilise a squad specifically of the proven best of the round would offer a unique approach rather than having the medal recipients and dedicated, brave marines, scattered around and left to die by their fellows.
Another idea I had is if the CO had a vendor for rank pins, so they can field promote marines for good work. This might require a slight change on how the rank prefix is determined, but otherwise would allow for some interesting opportunities. Although a limit to stop anything higher than Ensign or Lieutenant would probably be wise.
What do you think you could contribute by being whitelisted? I think I could contribute an alternative RP scenario to most existing COs. I know that my intended approach is not unique, and others have done or have attempted to do the same. I have a strong liking of RP and want to be able to encourage it instead of the typical rush to win the round. Failure is an inevitable part of life. Through failure you gain perspective, through perspective – success.
Your story (potential topics listed below) Note:
I have chosen to write the history of my character in the form of a dossier rather than a traditional story as I struggle writing dialogue as has been proven in my last two WL applications.
Weston-Yamada Personnel Archives
Lead Synthetic Technician – Charles Edwinson
Medical Information:
Date of Birth: August 7th, 2155
Ethnicity: White British
Vision: 20-20
Build: Average
Bloodtype: AB+
Allergies: N/A
Medical Conditions: N/A
Employment History:
March 2175 – Inducted into the Weston-Yamada Synthetic Laboratories to train as a service technician.
July 2176 – Graduated from WYSL as a Synthetic Technician.
September 2176 – Dispatched to REDACTED in the REDACTED system and received the position of Deputy Colonial Synthetic Technician.
2180 – Upon special recommendation from REDACTED was reassigned as Lead Synthetic Technician at REDACTED.
October 2182 – Armed Forces from the Union of Progressive Peoples attacked the colony of REDACTED, USCM forces were dispatched to retake the colony, and C. Edwinson was rescued.
November 2182 – Formal Resignation from Weston-Yamada Technician Division
Security Information:
July 2176 – Issued Level 1 Synthetic Internal Access
March 2179 – Issued Level 2 Synthetic Internal Access
2180 – Issued Level 4 Synthetic Internal Access
November 2182 – Revoked Level 4 Synthetic Internal Access
May 2186 – Issued Level 3 Synthetic Internal Access in accordance with USCM Treaties.
Important Notices:
August 2181 – REDACTED
October 2182 – REDACTED
May 2186 – Promoted to Lieutenant Commander, Chief Engineer of the USS Almayer.
April 2190 – Field Promoted to Commander, temporary Executive Officer of the USS Almayer.
USCM Personnel Records
Lieutenant Commander
Chief Engineer
Charles Edwinson
Civilian Record:
Joined WYSL in March 2175
Operated as a WY Synthetic Technician 2176-2180
Appointed Lead Technician 2180-2182
Resigned from Weston-Yamada in November 2182
Enlistment:
After a UPP attack on Weston-Yamada Colony REDACTED Charles Edwinson was rescued by the 7th Falling Falcons aboard the USS Almayer responding to the distress call. Immensely gratified Edwinson retired from Weston-Yamada and enlisted into the marines, seeking to join the brigade that saved his life to thank them.
In January of 2183 Edwinson was enlisted into the USCM Engineering Academy to be trained as a Maintenance Technician.
February of 2184 Edwinson was granted the rank of Sergeant and returned to the USS Almayer.
Medal Recommendations:
2185 Recommended for a medal of distinguished conduct owing to his rapid repairs on the heavily damaged USS Almayer Synthetic in a time of crisis.
April 2190 Recommended for a medal of exceptional heroism for actions in Operation Tiberius.
Promotion Record:
Enlisted at the rank of Sergeant.
2185 – Promoted to Staff Sergeant for dedication and quality work.
2186 – Promoted to Lieutenant (Senior Engineer)
May 2186 – Promoted to Lieutenant Commander (Chief Engineer) after the death of his predecessor.
April 2190 – Field Promoted to Commander (Acting Executive Officer) for his actions in Operation Tiberius
Operation Tiberius:
Much of this file is CLASSIFIED. Public record excerpts displayed.
- USS Almayer, USS Kestrel, USS Georgia, USS Waterloo and USS Alaska dispatched to REDACTED.
- Rogue UPP Battlegroup Tiberius engaged.
- USS Kestrel receives critical damage and all hands abandon ship.
- USS Almayer intercepts escape pods and recovers the 5th Brigade and 1st Force Recon Battalion remnants.
- Railgun strike to the USS Almayer CIC renders much of the command team dead or incapacitated. Captain Orlando Blackburn MIA presumed KIA.
- Commander Martin Alvarez deceased.
- USS Almayer Missile Silos damaged and Reactor breach imminent.
- Lieutenant Commander Edwinson risks his life to engage manual shutdown of the reactors before rerouting all reserve power to the sublight engines in an evasive manoeuvre.
- USS Alaska provides covering fire for the USS Georgia, USS Waterloo and USS Almayer to escape.
- USS Alaska, USS Georgia, and USS Waterloo arrive at the evacuation rendezvous. USS Almayer fails to arrive, its engines giving out half way.
- Lieutenant Commander Edwinson and his maintenance team successfully restore the USS Almayer’s reactors to a functional state and communications reactivate.
- Transmission from the USS Almayer to USS Alaska notifying of location and status.
- USS Alaska’s Rear Admiral Moore appoints Lieutenant Commander Edwinson to the temporary position and rank of Commander, Executive Officer.
- USS Almayer reaches the secondary rendezvous and the damaged battlegroup returns to Sol.
END OF PUBLIC RECORD
Do you understand that you cannot advertise your application on any public platform for votes. Do you also understand you may not edit this application 1 hour after it has been posted? Yes