Articles of Organization for Crimson Fortune Merce
1 Crimson Fortune Mercenary Fleet, hereafter referred to as the squadron, was founded to create and maintain an active community of commanders in Elite Dangerous: Odyssey. A community that is not tied to any single Commander or game mechanic. The leadership of this organization is based upon activity in game and can and will be changed as player availability changes. The members have the ability and right to challenge the leadership of the squadron.2 Code of Conduct.
2.1 General
2.1.1 In the words of Wil Wheaton, don’t be a dick.
2.1.2 Be respectful to one another, we set the example for others to follow.
2.1.3 Help your fellow CMDRS.
2.1.4 Don’t be afraid to ask for help.
2.1.5 Have fun!
2.2 Combat
2.2.1 NO COMBAT LOGGING. In combat, terminating the game, interrupting the game’s network connection, or any other way of disengaging that is forbidden by the game ToS, is strictly prohibited.
2.2.2 Any wanted commanders flying in space controlled by the squadron who are neither a member of the squadron or any of the allied squadrons are valid targets as such activity is part of protecting our interests.
2.2.3 Any PvP activity when not protecting the interest of the squadron should be agreed to by both parties, and with clear criteria on victory conditions (for example down to 20% hull or shields drop).
2.2.4 Ensure that any PvP fights are recorded.
2.2.4.1 This will provide protection for any subsequent claims of griefing or combat logging.
2.2.5 In self-defense, only 2.2.1 is relevant.
2.3 Bounty Hunting - The following points on bounty hunting, are about bounty hunting against players, only.
2.3.1 If you choose to engage in PvP bounty hunting, it is recommended to do so in the squadron’s systems or at the Community Goals. Take care engaging in this activity outside of those areas.
2.3.1.1 The Wil Wheaton law, “Don’t be a dick.” Apply.
2.3.1.2 No griefing apply.
2.3.1.3 Remember, you are representing the squadron in each encounter.
2.3.2 No bounty hunting of squadron members or allies. When in doubt, hold your fire.
2.3.3 The squadron flies in defense of its own rather than hunting down a known ganker. Don’t feed the trolls.
2.3.4 Please be aware that some bounties may be unintentional, and thus a commander (particularly an inexperienced one) may not be expecting any interdiction.
2.3.5 Exercise judgement first before interdicting — i.e. does the ship appear to be fitted for combat? What is there in game combat rank?
2.3.6 Ensure that any interdictions are recorded. This will provide protection for any subsequent claims of griefing or combat logging.
2.4 Piracy - The following points on piracy, are about piracy against players, only.
2.4.1 By definition, pirates do not aim to kill but to obtain cargo. You can be a pirate, not a griefer. Don’t intentionally kill targets under the pretense of piracy.
2.4.2 Ensure that you communicate with your targets at all times – explain to them clearly what is happening, and what their options are.
2.4.3 No piracy of the squadron members or allies. If you have any doubt over squadron membership, then do not interdict.
2.4.4 No piracy within space controlled by the squadron or its allies.
2.4.5 No piracy in Engineer/PowerPlay HQ systems.
2.4.6 No piracy in Shinrarta Dezhra.
2.4.7 If you engage in piracy, you’re on your own if you get attacked.
2.5 PowerPlay
2.5.1 The squadron is an independent faction and does not actively or collectively participate in PowerPlay. Any participation in PowerPlay by squadron members is not a reflection of the squadron in any way.
2.6 Dual Membership
2.6.1 We request that commanders fly exclusively for the squadron. That is, if you have both PC and XBox accounts, you will need to be a member of the squadron on both platforms.
2.6.2 Exclusive membership is a requirement to access the following:
2.6.2.1 In-game squadron.
2.6.2.2 Inara membership.
2.6.2.3 Private Group access.
2.6.2.4 Full Discord status.
2.6.2.5 Faction Simulation missions.
2.6.3 Any commanders identified as being non-exclusive will first be contacted by their Wing Commander and be asked to decide which group they wish to be a member of.
2.6.4 If you have a specific reason to fly as part of another wing/squadron on a different platform, then please contact a member of the Commanders Council.
2.7 Doxxing is not permitted.
2.7.1 The term “doxing” comes from the word documents. 1990s hacker culture shortened the term to “docs” and then “dox,” with “dropping dox” referring to collecting personal documents or information (like someone's physical address) and publishing them online.
2.8 Hacks and Bots are not permitted.
3 Commander membership requirements for the squadron are based on in-game activity.
3.1 Commanders who are inactive in the game for a period of 6 months or more with-out a formal notice of a leave of absence will be dismissed from the squadron.
3.2 Commanders who are leaving the game for an extended period may request and be granted a leave of absence.
3.2.1 To request a leave of absence, notify your wing commander or the next highest squadron rank member above you in your chain of command. The individual above you will in turn notify the next level of command.
3.2.2 Commanders who are placed on a leave of absence will be recorded and placed into the Leave-of-Absence role on all digital platforms until they return to the squadron.
3.2.3 When a commander returns from a leave of absence, they will resume their position in the squadron provide they still are able to meet the requirements of the rank they held prior to their leave of absence.
3.2.3.1 A Squadron Commander who has taken a leave of absences will be demoted to the rank of Former Squadron Commander as per the guidelines in that rank.
4 The squadron has (5) five active duty ranks and (2) non-active-duty ranks. These ranks and their requirements and responsibilities in the squadron are defined below.
4.1 The active duty ranks of the squadron are provide below and make up the bulk of the membership.
4.1.1 The highest rank in the squadron is the Squadron Commander.
4.1.1.1 The individual who holds this rank must meet the following criteria.
4.1.1.1.1 Must be the owner and operator of a capitol class vessel.
4.1.1.1.1.1 This vessel will be recognized as the flagship of the squadron and will be the meeting location for official squadron council meetings.
4.1.1.1.2 Must be active in the squadron for a period of 4 months or more.
4.1.1.2 Only one individual may hold the rank of squadron commander at any given time.
4.1.1.3 The individual holding this rank is responsible for the following.
4.1.1.3.1 The Squadron Commander is responsible for ensuring that the squadron is content and active.
4.1.1.3.2 The Squadron Commander will conduct a Commander’s Council meeting at least once a quarter to ensure that all wings and commanders are performing their assigned tasks and duties. The Commander’s Council is detailed in (Paragraph 5)
4.1.1.3.3 The Squadron Commander will conduct no less than (1) wing up events per month.
4.1.1.3.4 The Squadron Commander will ensure that recruitment of pilots is conducted regularly through official channels.
4.1.1.3.5 The Squadron Commander will monitor all pilot activity in the squadron.
4.1.1.3.6 The Squadron Commander will accept/send in-game friends requests to all pilots in the squadron. These will be used to monitor the members of the squadron for in-game activity.
4.1.1.3.7 The Squadron Commander will ensure that the squadron has a BGS oriented activity for the members to participate in.
4.1.1.4 The Squadron Commander is responsible for participating in (1) Wing-up per month.
4.1.1.5 The Squadron Commander position is a will and pleasure positions. They lead only by the collective will of the Commander’s Council and may be removed by the council via a vote of the Commander’s Council.
4.1.1.5.1.1 A Squadron Commander who has been removed from the position has (1) one week to surrender all of the controls for their position.
4.1.1.5.1.1.1 Access to the Inara Website.
4.1.1.5.1.1.2 Access to the in-game squadron.
4.1.1.5.1.2 A Squadron Commander who has been voted out of the leadership position may remain in the squadron and on the Commander’s Council. They will officially be recognized as Former Squadron Commander.
4.1.1.5.1.3 Former Squadron Commanders do not have a vote in the Commander’s Council unless they fulfill the rank requirements of one of the other Commander positions, i.e. Carrier Commander or Wing Commander.
4.1.2 The second highest rank in the squadron is that of Carrier Commander.
4.1.2.1 The individuals who hold this rank must meet the following criteria.
4.1.2.1.1 Must be the owner and operator of a capitol class vessel.
4.1.2.1.2 Must command a wing of pilots in the squadron or recruit a wing of pilots to fly from their carrier’s deck.
4.1.2.2 The Carrier Commander is responsible for the for ensuring the Commanders that fly from their carriers’ decks are happy and content.
4.1.2.2.1 The Carrier Commander will conduct at a minimum (1) one wing up event per month with the pilots who fly from their carrier’s decks.
4.1.2.2.2 The Carrier Commander will monitor pilot activity in the wings that fly from their carrier’s deck.
4.1.2.2.3 The Carrier Commander will accept/send in-game friends requests to all pilots in the wings flying from their carrier’s deck. These will be used to monitor the members of the squadrons in-game activity.
4.1.2.2.4 The Carrier Commander will support the overall BGS activities of the squadron by crafting wing up and other events for the pilots operating from their decks.
4.1.2.2.5 The Carrier Commander will work in concert with the Squadron Commander to determine the best BGS oriented activities for the Squadron.
4.1.2.3 The Carrier Commander is a seated member of the Commanders Council and should attend all meetings of this group.
4.1.3 The Carrier Commander is responsible for participating in (1) Wing-up per month.
4.1.4 The third highest rank and the first of the command ranks in the squadron is Wing Commander.
4.1.4.1 The individuals who hold this rank must meet the following criteria.
4.1.4.1.1 Recruit one to three pilots to fly under their command.
4.1.4.2 The Wing commander is responsible to ensure the Commanders that fly in their wing are happy and content.
4.1.4.2.1 The Wing Commander will conduct at a minimum (1) one wing up event per month with the pilots of their wing.
4.1.4.2.2 The Wing Commander will monitor all pilot activity in the squadron.
4.1.4.2.3 The Wing Commander will accept/send in-game friends requests to all pilots in their wing. These will be used to monitor the members in-game activity.
4.1.4.2.4 The Wing Commander will support the overall BGS activities of the squadron by crafting wing up and other events for the pilots operating from their decks.
4.1.4.2.5 The Wing Commander will work in concert with the Carrier Commander to determine the best BGS oriented activities for the Carrier and the Squadron.
4.1.4.2.6 The Wing Commander is a seated member of the Commanders Council and should attend all meetings of this group.
4.1.4.3 The Wing Commander is responsible for participating in (1) Wing-up per month.
4.1.5 The first rank in the squadron is Commander. This rank represents the pilots that makes up the various wings of the squadron.
4.1.5.1 The individuals who hold this rank must meet the following criteria.
4.1.5.1.1 Must join the in-game squadron.
4.1.5.1.2 Must join the squadron on INARA.
4.1.5.1.3 Must send an in-game friends request to the squadron commander, their carrier commander, and their wing commander.
4.1.5.2 The Commander is responsible for participating in (1) one Wing-up per month.
4.1.6 The Recruit rank is the lowest member of the squadron and represents the newest member.
4.1.6.1 The individuals who hold this rank must meet the following criteria.
4.1.6.1.1 Must join the discord server.
4.1.6.1.2 Must agree to the squadrons code of conduct outlined in section 2 of this document.
4.1.6.1.3 The recruit is responsible for preparing themselves to become a member of the squadron. They should familiarize themselves with the structure of the squadron on discord and determine if they feel we are a good fit for their playstyle in Elite Dangerous: Odyssey.
4.2 The in-active-duty ranks are provided below and make up a much smaller portion of the squadron.
4.2.1 The Leave-of-Absence rank is a position held by any member of the squadron who has voluntarily stepped away from squadron leadership for an extended amount of time.
4.2.1.1 Members who wish to request a leave of absence may do so by contacting a member of the Commanders Council and requesting this change in their role.
4.2.1.2 A Commander who has been placed on a leave of absence will be moved into the leave of absence server designation on the squadron discord server.
4.2.1.3 A Commander on a leave of absence is relived of all duties and responsibilities of their rank in the squadron during the leave of absence.
4.2.1.4 A Commander who returns from a leave of absence will be reinstated to their previous squadron rank; provide they are able to fulfill the duties of that rank.
4.2.1.5 A Commander returning from a leave of absence will contact a member of the Commanders council and reactivate their membership.sd
4.2.2 The rank of Former Squadron Commander is reserved for those commanders who held the rank of Squadron Commander. This rank is granted to Squadron Commanders who have departed the role.
4.2.2.1 The rank of Former Squadron Commander has all the responsibilities of the Carrier Commander.
5 The Commander’s Council is the governing body of the Squadron and is made up of the leadership ranked members.
5.1 Commanders who carry a squadron rank of Squadron Commander, Carrier Commander or Wing Commander are seated member of the Commanders Council.
5.2 Commander’s Council meetings must be held at a minimum of once a quarter.
5.2.1 All Commander’s Council sessions must be announced via the Squadron discord server twice before the event may be held.
5.2.1.1 Announcements must be made (1) one week ahead of the event and (1) one day ahead of the event.
5.2.1.2 An agenda for the event must be included with the announcement.
5.2.2 Commander’s Council meetings are held in a voice channel and aboard the flagship of the fleet simultaneously.
5.3 All decisions of the Commander’s Council are made by vote.
5.3.1 All seated members of the council may vote.
5.3.1.1 A vote may only be called when a quorum of the Commander’s Council is present.
5.3.1.1.1 A quorum of the Commander’s Council is defined as (4) four or more seated members present excluding the Squadron Commander.
5.3.1.1.2 The Commander’s Council may only vote on agenda items.
5.4 If the Commander’s Council feels that the current Squadron Commander is not fulfilling their obligations as the leader of the Squadron, they may call for a Vote of No-Confidence in the Squadron Commander.
5.4.1 A vote of no confidence can only be held at a meeting of the Commander’s Council.
5.4.2 A vote of no confidence requires a quorum of the Commanders Council to perform.
5.4.3 A vote of no confidence must appear on the agenda of the Commanders Council.
6 Disciplinary Actions
6.1 COMBAT LOGGING: If judged to have combat logged, your first offense will receive a formal warning from the Commanders Council. If the attacker demands it, you must accept a rebuy; otherwise, you will be expelled from the Squadron. Second offense is an immediate expulsion from the Wing.
6.2 GRIEFING (including Piracy): You will receive a warning on your first offense and expelled on your second offense.
6.3 Disruptive / Anti-social behavior, violation of other parts of the CoC: You will receive a warning on your first offense and expelled on your second offense.
6.4 Any warning given with a warning already on record may be cause for expulsion.
6.5 Any member in a leadership position that receives a warning will be subject to demotion in the ranks.
6.6 In addition, actions that are cause for immediate removal include: acting for another group considered hostile; making real life threats to any other player; engaging in any illegal behavior (such as DDOS or doxxing).
6.7 Particularly egregious violations as well as any actions outside of those listed above will be dealt with on a case-by-case basis at the discretion of the Commanders Council.
7 Recruitment will be conducted at a minimum on the following platforms.
7.1 Discord.
7.1.1 https://discord.gg/89gdN7mGCd
7.2 Reddit.
7.2.1 https://www.reddit.com/r/EliteWings/
7.3 Frontier Forums.
7.3.1 https://forums.frontier.co.uk/forums/elite-dangerous-groups-squadrons-factions/
7.3.2 https://www.elitedangerous.com/community/squadrons
8 A Background Simulation (BGS) narrative will be used to help shape the events and activities that the squadron participates in. These events may be linked to larger Community Goals or other Squadrons activities.
9 It is recognized that as the Squadron grows the need to modify, extend or clarify the Articles of Organization will be needed. This section outlines the procedures of accomplishing this task.
9.1 All changes to the Articles of Organization must be voted on by a quorum of the Commanders Council in a regularly scheduled meeting.
9.1.1 Changes to the Articles of Organization must appear on the agenda for the Commanders Council meeting as a recognized topic.
9.2 Items removed from the Articles are indicated with a strike thru and the new or replacement material is added to the document directly after the strike through or where appropriate.
9.3 The updated Articles will be posted to the squadron’s media site with-in one week of the official approval.