Skip to content

Rulebook

Synergy of Steel · As of June 2026

The Alliance's supreme goal is achieving our shared objectives. "Synergy first." The foundation for this is mutual respect among pilots, based on honesty and mutual support. Alliance rules always take precedence over Corp rules. Corps may introduce their own rules, as long as they do not contradict the Alliance rules.

Section 1 · General

1.1 · Admission Requirements

Every Corporation in the Synergy of Steel alliance must demonstrate active participation in Alliance fleets. The evaluation is based on the respective last 3 months, using the following two criteria, both of which must be met:

  1. Participation rate: At least 50 % of a Corporation's real pilots must have taken part in fleets.
  2. FAT points: The Corporation must reach a minimum number of FAT points. The target is calculated as follows: Number of real pilots × 15 More information on FAT points: see Section 6

1.2 · Code of Conduct

  • Respectful conduct is mandatory.
  • Personal attacks, threats, and insults are forbidden.
  • Disputes are first clarified privately or through your own Corp Leadership.

1.3 · Infrastructure & Communication

Registration Requirement

All characters in Synergy of Steel and Synergy of Support must be fully verified on the Alliance Portal as well as WinCo Auth / SeAT. Alt characters must be assigned to a Main.

  • CEOs record their Corps (NS and HS) in the Portal under "Corp Statistics".
  • CEOs record their Structure ESI under the Structures and Moon Mining modules.
  • All characters in use must be entered completely and correctly in the Character Audit Tool.

Channels & Availability

  • Discord: Ping, info, and leadership channels are mandatory reading (Alliance and Coalition). Muting is at your own risk.
  • Verification for the Discord server is done via the Auth Portal.
  • TeamSpeak is mandatory as soon as any in-game activity is being carried out.
  • Alliance mails are intended exclusively for important announcements. CEOs and Directors have posting rights; third parties only with their express permission.

1.4 · Conduct in Space

Smacktalk and information-bearing statements in local chat are forbidden.

Section 2 · Taxes

2.1 · PvE Tax

The Alliance levies 7 % on all PvE activities. As soon as a pilot has at least one character in the Null-Sec alliance, this tax also applies to characters in the High-Sec alliance.

Taxable transaction types:

  • agent_mission_reward | Agent - mission reward
  • agent_mission_time_bonus_reward | Agent - mission time bonus reward
  • bounty_prizes | Bounty payout
  • ess_escrow_transfer | ESS - escrow transfer
  • corporate_reward_payout | Corporate reward payout

Loyalty points are likewise subject to the 7 % tax.

2.2 · Mining Tax

The Alliance levies 7 % on mined ore, ice, gas, and R4/R8 moons — regardless of the security status of the system (Null-Sec, Low-Sec, High-Sec, Wormhole).

2.3 · Payment Terms

Taxes are issued to each Corp via contract by the Alliance at the start of the month. The Corp must pay the contract within 7 days of issuance.

Section 3 · Fleets & Fleet Rules

3.1 · CTA and HomeDef

Mandatory participation for all online pilots. Ping channel: #important-pings. Reward: FAT + SRP.

  • Participation in CTA and HomeDef fleets of Synergy or Phoenix is mandatory.
  • Any form of ISK-making is forbidden during these fleets.
  • Exception: members/Corps that have been in the Alliance for less than 30 days.

3.2 · Strat-OPs

Recommended participation for a strong fleet presence. Ping channel: #important-pings. Reward: FAT + SRP.

3.3 · Home Defense Patrol

Recommended participation to protect your own space against neutrals. SRP is granted if the lost ship was used sensibly for the action.

3.4 · OPs / Roaming

Ping channel: #general-pings. Reward: SRP.

  • Extended PvP activities: roams, ESS-robbing, etc.
  • For roams, the FC decides whether to provide ships or grant SRP — at the FC's own expense.

3.5 · Doctrine and Fittings

  • Current doctrines and fittings are posted on the Alliance Bulletin Board.
  • The common doctrines must be trained as a priority.
  • Every pilot keeps at least one undockable-ready fitting per doctrine in the Stagings.

3.6 · Loot from Fleets

Loot and salvage from SRP fleets must be handed over via contract to Leean Otsolen.

Section 4 · Upwell Structures & POS

Deploying structures outside of Synergy sov is forbidden without the consent of the Alliance Leadership.

4.1 · Approval Requirement

  • Athanors and Metenoxes may only be deployed at FAT moons with approval. Others can be deployed without prior consultation.
  • Structures of size L and XL require the approval of the Alliance Leadership.

In the system J7YR-1, activating a service module for Reactions of any kind is forbidden.

4.2 · POCOs & Skyhooks

  • Structures of this type are fundamentally the property of "SYN Holding".
  • Structures of this type owned by other Corps must be sold to SYN Holding upon request.

4.3 · Access Rights (ACLs)

  • The predefined ACLs (Access Control Lists) are to be used for all structures.
  • ACLs are located in the CEO channel in-game; invitation is done by the Alliance Leadership.
  • Docking ACLs apply to docking, cyno beacons, bridges, offices, and clone bays.
  • Gunnery ACLs must include SYN Defense and WinCo Defense.

4.4 · Unanchoring & Decommissioning

  • Advance notice: an Alliance mail must be sent two weeks before unanchoring or decommissioning.
  • Unanchoring the last docking structure in a system requires coordination with the Alliance Leadership.
  • Unanchoring L and XL structures requires the approval of the Alliance Leadership.

4.5 · Mercenary Dens

  • Pilots in the top 19 of fleet activity are each assigned 1 planet.
  • Planets may be rented out to other pilots; responsibility remains with the assigned pilot.
  • Every 2 months, a re-evaluation with reassignment takes place according to the current top-19 ranking.
  • Responsibility includes: no negative impact on the Workforce; when the owner changes, the new owner removes the previous owner's Den.
  • Failure to meet this responsibility automatically results in the loss of the planet to the next-ranked pilot.

Section 5 · Activity Rules

Intel channel: mandatory to join and actively use (link in the Alliance MOTD). Language in Intel: English.

5.1 · Ratting / Crabbing

Basic Rule

  • The entire Alliance space as well as Shared Space may be used for ratting.
  • Guest conduct applies in the Coalition space of other alliances; instructions from the system owners must be followed.
  • "First Come, First Served" (FCFS) generally applies to all ratting sites.

Site Usage

  • The owner of a site is whoever starts it first — this carries the claim to loot, wrecks, and salvage.
  • The owner's right automatically lapses upon leaving the site.
  • MTUs may only be deployed in your own sites. Foreign MTUs may be destroyed.

Priorities Under High Load

  • AOE fleets have top priority on Havens.
  • Ishtars/Battleships → Hubs
  • Marauder → Sanctums
  • AOE → Havens

CAP Ratting

  • Capitals must have an available cyno and be adequately secured.

5.2 · Mining

Don't be an ass.

5.3 · Scanning

Scanning sites are to be fully cleared whenever possible.

5.4 · Rorqual Mining

  • Only pilots who can fight and communicate with an FC may mine with a Rorqual.
  • A cyno ship (ideally also a FAX) is expected to be on standby, and pilots are expected to contribute to organizing a HomeDef.
  • In the event of a tackled Rorqual: inform your own FCs first.

5.5 · Alliance Moon Mining

  • Holding moons are available to all Alliance members when entered in the calendar. Other Holding moons may only be mined with the approval of the Alliance Leadership.
  • Only modules and drones with a 0 % residue probability may be used.
  • Mining Alliance moons is taxable. Payment is made exclusively in ISK.
  • Via the "Moon Mining Pay" Auth module, an invoice is automatically generated every Wednesday, based on the taxable mining amount of the past billing period.
  • Tax calculation: Jita Buy of the Refining Value.
  • The module also states the respective payment deadline ("Due Date"). The invoice must be paid in full by this date.
Moon type Tax
R64 50 %
R32 35 %
R16 20 %
R8 7 %
R4 7 %

Cherry-Picking Rules

Option A: The belt must be mined in its natural ratio. At the latest by the end of the belt's lifespan, each player's mined ratio must match the natural ratio.

If more R64 ore is mined than permitted, an additional tax of 25 % applies.

Option B: The belt is mined in the naturally occurring ratio. R4 and R8 are exempt: instead of 7 %, R4/R8 ores of the respective moon worth 15 % of the R64 tax amount must be handed over. If no R64 is mined, the standard 7 % applies again for R4/R8.

5.6 · Corp Moons

  • The Athanor owner decides who mines the moon and in what way.
  • All deployed Athanor/Metenox drills factor into the moon rating and influence the FAT-based distribution.
  • Corps are entitled to a proportional share of R16+ moons according to their FAT ratio. Details and calculations are provided by the Alliance Leadership; dashboard insight for CEOs via Grafana.
  • R16+ moons awarded via FAT activity are tax-free.
  • Corps receive Magmatic Gas for the fuel of every deployed Metenox at an R16+ moon.
    • Magmatic Gas is distributed monthly via contract, free of charge, from the Holding to the Corps, for every Metenox at an R16+ moon. The Alliance reserves the right to continue this for as long as the supply lasts or until adjustments are made by CCP.

5.6.1 · R64 Moons

Corps that field, on average, at least 5 active pilots per official Alliance fleet (CTA, HomeDef, Strat-OP) over three consecutive months receive exclusive access to R64 moons.

  • The Athanor remains the property of the Holding. Due to name-tagging (C), it is no longer publicly accessible.
  • The claim to regular R16+ moons via the FAT system remains unaffected.

5.7 · Market

  • Use of the market in all Stagings is expressly permitted.
  • Scamming and relisting are forbidden.
  • For the Market channel on Discord, the pinned rule applies.

5.8 · ESS

Main and reserve ESS banks may under no circumstances be hacked in your own or allied systems.

Intentional violations result in ISK fines payable to the Holding.

5.9 · Drag/Stop Bubbles

  • If a gate gets a drag/stop bubble, this must be pinged in Discord #intel-homedeff.
  • There must be an up/down spot available from which the gate can be reached directly.
  • When a pilot jumps into the system, the bubble must not block the entry point.
  • Bubbles more than 1000 km from a gate are exempt from these rules.
    • Exception: if it is the only station in the system, a warp spot must be available for it as well.
    • Bubbles are fundamentally forbidden at Fortizars.

Gate bubbles, or fully bubbling gates in other systems, are forbidden without prior coordination with the Alliance Leadership.

5.10 · Faction Warfare

In FW systems, FW-enlisted pilots may attack each other — even if they are blue. Blue status does not protect against PvP in FW systems.

Section 6 · FAT (Fleet Activity Tracking)

FATs are collected in fleets such as CTA, HomeDef, and Strat-OP, for every 3 hours of fleet time (or part thereof). The timing and manner of awarding FATs are at the discretion of the commanding FC.

6.1 · Weighting

Fleet type FAT points
CTA 3 points
Strat-OP / Strat 2 points
HomeDef 1 point
OP / Roam 0 points

6.2 · Multiboxing

  • A maximum of 3 characters per player per fleet are counted toward the base rating.
  • The 1st character counts normally; the 2nd and 3rd are counted additionally; any further characters do not increase the base rating.

6.3 · Capital & Supercapital Bonus

For Capital, Force Auxiliary, Supercapital, and Titan ships, an additional bonus point is awarded per ship deployed — independent of the multiboxing limit.

Example: A player flies in a CTA with 5 characters, 2 of which are Capitals → 3 characters base rating + 2 Capital bonus points.

6.4 · Weighting of Votes

Votes by the Alliance Leadership within the Corp Leadership that affect the Alliance as a whole are subject to a FAT-based vote weighting. This is based on the Corps' participation in official Alliance and Coalition fleets over the last 3 months.

Section 7 · SRP (Ship Replacement Programme)

All ships requested by an official FC in an official fleet (CTA / HomeDef / Strat-OP) are replaced 100 %. Additional ships may be replaced as a courtesy if they were used sensibly (e.g., for home defense). In this case, Junior FCs can create an SRP link and explain the situation to the Alliance Leadership.

Capitals and Supercapitals are exempt from this rule. See the separate Capital SRP rules as well as the supplementary info ping on Discord.

7.1 · SRP Calculation

SRP amount = [ship price incl. fitting] − [Platinum insurance payout] + [Platinum insurance cost]

Payment is made via contract: ship hull + ISK equal to the fitting price (cheapest price in B-9C24 or Jita) minus the insurance payout plus insurance cost (Platinum). Alternatively, the pilot can request ISK instead of the hull — in that case, return the hull via contract (DM to Erzus Fahrtas).

Section 8 · Recruiting / Internal Transfers

  • Internal transfers are forbidden unless both affected CEOs agree.
  • In case of disagreement, the matter can be escalated to the Alliance Leadership or Alliance Diplomats. Evidence and valid reasons must be presented.
  • The Alliance Leadership makes the final decision in case of persistent disagreement.
  • Rejoining a Synergy Corp is only permitted after clarifying the reasons with the former CEO.
  • Admitting players who are on the blacklist is not permitted.
  • A transfer between a Renting/Main Corp within the Coalition is only possible once.

Section 9 · Synergy of Support

Synergy of Support is the support alliance of Synergy of Steel under the same leadership. It is clearly separate from the main alliance. Members with at least one character in the main alliance are fully subject to the main alliance's rulebook.

9.1 · Prohibitions

  • Ratting, mining, scanning, and industry in Null-Sec are strictly forbidden — including resource extraction and use of industrial facilities.
  • Deploying structures is forbidden, in order to avoid making the alliance eligible for war.

9.2 · Benefits

  • Improved standing.
  • Participation in Academy and PvP fleets of the main alliance (incl. SRP access).
  • Mining of Corp moons belonging to the associated 0.0 Corp (the only permitted ISK source with regard to 9.1).
  • Use of the market in the Staging and other Alliance systems. Permanent logged-in presence on stations is only allowed in the Staging system.

9.3 · Transfers Between Corps

Members are permitted up to 2 transfers between Corps. Further transfers require the approval of the Alliance Leadership.

9.4 · Liability

The main alliance's Corps are responsible for their affiliated High-Sec Corps and are liable for compliance with the rules.

Section 10 · Enforcement, Consequences, Amendment

The Alliance places great value on compliance with all rules. In the event of an established rule violation, the following escalation chain applies:

  • Clarification through your own Corp Leadership.
  • Clarification through the Alliance Diplomats.
  • Clarification through the Alliance Leadership.

Vigilantism is forbidden. CEOs are responsible for rule enforcement within their Corp.

10.1 · Alliance Diplomats

The Alliance Diplomats are impartial members of the Alliance. They resolve internal conflicts, always act in the spirit of the rulebook, and relieve the burden on the Alliance Leadership.

Contact via ticket or Discord DM — for:

  • Conflict resolution
  • Questions about the Alliance and its goals
  • Reporting rule violations
  • General support

Current Diplomats:

  • Taurus Highlander (MA)
  • Radiant Dawnseeker (SCG)

10.2 · Consequences for Rule Violations

Various consequences may be determined by the Alliance Leadership for non-compliance with the rules, depending on the severity of the violation and the frequency of the misconduct.

  • Warning: For minor rule violations, a warning is usually issued first. The affected player or Corporation is notified of the violation and asked to correct their behavior.
  • Sanctions: For repeated or serious misconduct, sanctions may be imposed. This can include a temporary restriction of game privileges, such as fleet access, access to certain systems or resources, ISK fines, or even a temporary suspension of Alliance membership.
  • Expulsion: In the event of repeated or serious misconduct, a player or Corporation may be expelled from the Alliance. Expulsion generally follows a thorough investigation of the incident and a weighing of the circumstances.

10.3 · Escalation

Escalation to the Alliance Leadership should be seen as a last resort for resolving conflicts and finding a fair solution. CEOs and members of the affected Corporations are expected to take all reasonable steps to resolve disputes within their own Corp before escalating the situation.

  • If disagreements arise between CEOs of different Corporations within the Alliance and no agreement can be reached, the matter may be escalated to the Alliance Leadership. In such a case, evidence and valid reasons for the disagreement should be presented. The Alliance Leadership will review the evidence and make a final decision that takes into account the interests of all involved parties and the well-being of the entire Alliance.

10.4 · Rule Amendments

  • The Alliance Leadership retains the right and responsibility to amend the rulebook.
  • Changes are communicated transparently — with an explanation of their effects.
  • CEOs have the right to submit proposed changes; the Alliance Leadership reviews these and decides.

Why Alliance PvP Is Mandatory

Anyone who wants to survive long-term in Null-Sec must be able to successfully stand up to the average attackers in Null-Sec. To achieve this, all you need is a fleet strength of 200-300 pilots.

Very few alliances can manage that alone - which is why you need to find friends. Since friends in EVE, and especially in Null-Sec, don't come for free, there are fundamentally two ways to acquire allies for PvP: either you're a renter and pay for them, or you support each other in PvP. The bigger (and therefore also the better) such an alliance is, the more space you have to defend and the bigger you have to plan - if your alliance contributes 10% of the numbers to a fleet, you consequently have to help your allies 10x, until you've earned a fleet of support yourself.

Synergy is a PvP alliance - we pay rent or money to no one, and we work as equals with the allies of our Coalition. Consequently, we pay for our right to exist in the form of fleets - the currency of our Coalition -, just like every alliance in our Coalition.

The Alliance rules are designed to make it as easy as possible for every Corp and every player to support this alliance system. Besides a low tax of 7 %, the only obligation is contributing to the alliance system in the form of fleets (especially CTAs/HomeDefs), which enables our space, our moons, and our freedoms. Through our contribution in fleets, we earn our space and our R64 moons as our primary income, with which we pay for all the infrastructure (access to markets, standings, important stations, SRP, etc.) that makes playing in Null-Sec possible in the first place, no matter what playstyle you prefer.

Pilots who refuse to engage in PvP in Alliance fleets therefore not only contribute nothing to this alliance system, which inevitably also enables their own playstyle, but they let themselves be freeloaded on by the rest of the Alliance. That is unacceptable for all members who do contribute their part, and it does not fit with our Alliance.

All pilots who do make the effort to carry their weight, take part in fleets, and contribute to our existence as an Alliance - regardless of whether these fleets are sometimes boring, since not every PvP mechanic is the most exciting one thanks to CCP - will have a very relaxed life and enormous freedom and opportunities to pursue their own individual playstyle. Naturally, we also try to make PvP as appealing as possible through transparency about our military goals, and to have as many exciting fleets as possible and as few as possible that are more tedious (yet still necessary).