BF Code

Black Flag CODE - Abbreviated 

All members of our alliance will honor this code of conduct in all interactions with other alliances and players.

I.                    Play with integrity.  Treat each other with respect and courtesy. 

II.                  Fight for profit and/or glory. Defend & Protect our own and our friends/allies. 

III.                Abide by universal ROE & the Server 24 Mining Accords (see bottom of page).   

IV.                Armadas – Share with the team, don’t poach from others, don’t attack active armada ships.

V.                  Raids – Do not poach except by invite. Do not intervene except for our own and allies.

VI.                Floaters – only attack with cause  

VII.              Retaliation should always be direct and exact  

VIII.            Avoid General Chat

IX.                Attempt to resolve your issues with other players through polite PMs.

X.                  Participation in events and contribution to the team 

Black Flag CODE - Verbose

I.                    Play with integrity.  Treat each other with respect and courtesy.  We have zero tolerance for insults, misogyny, defamation, discrimination, threats, malicious remarks, or harassment. 

II.                  Fight for profit and/or glory. Defend & Protect our own and our friends/allies. 

III.                Abide by universal ROE & the Server 24 Mining Accords (see bottom of page). 

a.       Conditions that preclude ROE: Being in a state of war or having a player KOS

b.      Declarations of War and KOS can be made by the Admiral

IV.                Armadas: BF does not attack another team’s active armadas.  We should avoid poaching another team’s armada (check if it is already damaged, if there are other ships surrounding it, ask if the other team plans to make another attempt).  Also we should not give opportunities for others to poach our damaged targets – Kill them in the first shot. 

V.                  Floaters:  Attacking idle or in route ships is discouraged except with cause such as retaliation, defending our bases, or protecting a miner/node. 

VI.                Raids: Do not impose on another team’s raid.  Do not join the raid except by invitation (Ask first).  Do not defend against a raid unless it is BF or a BF Ally. 

VII.              Retaliation: If a player attacks your combat ships (floaters), BF retaliates as a team against the offending player. 

VIII.            General Chat: Use of general chat is discouraged, especially involving controversial matters. Do NOT post player base coordinates into GC.

IX.                Player to Player Issues: If you have an issue with another player, attempt to resolve the issue one on one through polite PMs.  If no resolution can be reached, then escalate to an officer for further assistance. 

X.                  Contribute towards Competition in Alliance events: Alliance event rewards can be used to purchase among other things station shields.  Where possible players are encouraged to participate and contribute towards ranking in alliance events. 

ARMADA Code (NO Armada-drama) 

The following code for Armadas has been established to promote sharing and fairness in how we execute our armadas.  The intent is to give every alliance member the opportunity to participate in and enjoy the benefits of Armada combat.   

1)  Share Armada participation with others.  If you have enlisted in an armada already, give the next opportunity to other members of the team. 

2)  The HOST coordinates and should use STARS.  Announce your armada in AC.  Establish your guidelines.  Specify required ship strength and select your team.  Use STARS confirm your team. 

3)  Armada Participants should CALL IN.  Do not impose on an armada by kicking a lower strength player.  If the Armada is already full, wait for the next opportunity. 

4)  Multiple Hits:  The best case scenario is to always kill the armada target in the first shot.  If an armada target requires multiple hits then the team that started the first attack should be prioritized during the final / successful assault.  This insures that those who have worked on the target get the benefits.  Do NOT poach. 

BASE Protection / SHIELD Discipline

SHIELD DISCIPLINE IS PRIORITY 1!  We suggest the following guidelines to safeguard your base and protect your resources. 

A.  BF will attempt to make contact with you thru discord to alert players to shield if their base is being raided.  We will also make best effort attempt to defend a base that is under attack.  

B.      BOOT & LOOT:  If defense becomes costly or futile we may kick the player from the alliance and “counter-raid” in order to keep the resources within the alliance. 

B.      It is suggested that bases are never located in high traffic systems.  High traffic systems are those that sit as a hub in the center of spoke systems, 3* & Latinum mining systems.  For example:  Rator, P’Jem, Morska, Opla, Kepler, Ahza, Midnight.

C.      Shields should be your first line of base defense.  Always guard your base especially when you are away from the keyboard.  We suggest that all players always keep at least one strong ship docked to defend the station especially when not actively playing in the event your shield lapses. 

D.      Bases should be guarded / shielded even if you do not have resources above your protected levels.  A base under attack triggers a defensive response from our members which in turn consumes resources.  Consider that you are protecting more than just your resources.  We are a strong alliance that ranks well in events and has wide visibility amongst other alliances and players.  Our preference is that our bases do not become easy targets for other players to hit and/or raid. 

E.       HIVES – We discourage the establishment of large HIVES due to the risk. 

The Current Senate Mining Accords