Discovery Gaming Community

1 Million Credits reward if you can point out ways to be a dick and work against the spirit of the rules without technically breaking the rules below (check the “spoilers” Info bar too). I believe section 3 “Hired Guns & Bounties” could be the best place to find loopholes atm. EDIT: Also, don't act it out ingame. Just post it here.

2 Million Credits reward if you can find a difference to the rules (found here LinkRules LinkBounties LinkFactionCreation LinkOFs LinkPOB LinkClassifications) currently in effect (in meaning, not wording or numbering or organization), if it matters with the game mechanics we have today. I know of 2 minor things and the first person to find them will get paid anyway because Karlotta is magnanimous like that.

3 Million Credits for someone who can suggest a good addition or change to these rules. For examples moving certain things into or out of the spoilers. The rules in this post should be visible to anyone ingame, the spoilers only on the forum.

1 Million Credits for someone who can point me to instances where the current Faction Right 6 (OFR 4 in this post) is still practiced today.

Same goes for the forum-only rules in the second post.

DO NOT post ways to cheat that aren’t listed in section 6. If you know of any that aren’t described here, PM them to admins.

DO check what others posted before you because you won’t get paid for posting something someone else already posted.

And DO give the char name you want the credits to be transferred to.

Go!!!

---

Click the Info bar for explanations and examples.

1. COMMUNITY RULES

1.1 This is a Freelancer-based role-play community. Character names and behavior must be realistic in the Discovery Freelancer universe (no player nationality tags, memes, pop-culture references, or direct imports from other universes like Star Wars). Realistic role-play also means that characters can’t use information they didn’t receive in the game universe.

Info

Name regulations:
- no swear words
- no indicating of player origin
- no faction tags if you're not a member
- no excessive use of random symbols, capital letters, numbers, symbols, leet speak, emoticons
- no references to real-life atrocities
- no memes

Examples:

No Little Ponies, Furries, Care Bears, Ewoks, Luke Skywalkers, Jean Luc Piccards, supergamer72, |\/\/\$N00P-DAWG/\/\/|.

No using Outcast characters to tell the identities of cardamine smugglers to law enforcement.

No using information from a communication channel that a character has no access to.

No using of cloaked nomad ship to acquire information for enemies of Nomads.

1.2 Don’t insult, harass, or threaten players outside of role-play. Don’t use racist, graphic, pornographic, obscene, or law-violating materials in or out of role-play. Don’t repeatedly target specific players or groups with the intention of ruining their game experience. Don’t mislead players about rules or pose as an admin or “admin friend” to gain an advantage.

Info

No insulting or degrading real people. For example "you stupid lolwhut", "go kill yourself", "people of X nationality/ethnicity/religion are sub-human")

No using Discovery to promote political views or historic/scientific revisionism. Not even in role play, or disguised as role play.

No pornographic role play or links to sites that feature pornography or propaganda. Keep in mind that there are people of all ages playing here.

No systematic attacking or public smearing of certain player(s) with the intention of removing them as players from the community or from what you consider "your turf".

You may remind players of rules and point it out if they are violating them. However, be careful not to misrepresent them, because misrepresenting them to threaten with sanctions will get you sanctioned.

1.3 Everything must be in understandable English. Some non-English words can enhance role-play, but the meanings should be kept understandable to English-only speakers.

Info

Allowed: "Hola, victim! Give me two million credits, or you shall die!"
Not allowed: "¡Dame dos millones de créditos o muere!"

2. SERVER GAMEPLAY

2.1 Out-Of-Character (OOC) chat should be avoided in local and system chat. Using // in front of OOC messages is recommended.

Info

Try to restrict non role-play chat to PM or group chat. If people in your group ask you to role play in the group, stop OOC.

2.2 A character/ship must use one single ID and follow the permissions and restrictions of ID, ship, and equipment infocards.

Info

You may travel and engage in role play only if you have one, and only one, ID on your ship. You may buy an ID for another player to help set up up a character, but it should be done quickly, should not involve traveling, and not be done while role-playing is taking place within radar range.

2.3 Players using Recruit ID and players below level 30 may not be attacked unless they: attack first, fire cruise-disruptors, refuse to stop stalking, carry a codename weapon, or take active part in role-play.

Info

This rule is there so people don't target new players who have no way of defending themselves and little understanding of the rules and game mechanics. It shouldn't be abused by using low level or recruit ID in order to bother others.

2.4 All attacks must be a result of roleplay. Players must say more than one line and give reasonable time for the opponent to react before initiating an attack. Non-Nomads may always attack Nomads, but role-play is still required. See rule 5.1 before attacking a Player Owned Base.

Info

This rule exists so people don't just go around shooting everyone out of the blue. Leave your opponent enough time to at least notice you, and give him a chance to react to you before you open fire. You don't have to give up the element of surprise completely, as you don't have to state your intention of attacking someone before attacking. You can, for example, have a friendly conversation out of radar range (system chat or pm), use an IFF that doesn't arouse suspicion, and then surprise-attack him after you won't be suspected of wanting to do any harm.

2.5 If you die in any way during PvP, you must leave the system the fight took place in and not re-enter it on any characters for two hours. You may not carry cargo, engage in player interactions, or be attacked while leaving. You also can’t attack the player(s) you died to on any of your characters for two hours.

Info

Without this rule, battles would be endless and pointless, so please obey it. Instead of taking revenge by re-engaging with the same or another character before two hours are up, you have much better options available: Put up an IRP bounty on who ever killed you. Play on another character in another corner of Sirius. Go to Connecticut and train your combat skills. What ever you do, don't break the rules while you're angry. You'll only end up harming yourself and giving your opponent more ways to harm you. Revenge is a dish best served cold.

2.6 The same as 2.5 applies if you dock within 15K of your enemy while in PvP, with the exceptions that you may re-enter the system to trade, keep your cargo, and players may attack you while you're leaving the system.

Info

If you dock while in PvP and you are flying any ship (fighter, miner, or transport), you are permitted to leave the system keeping your cargo. However, players are permitted to attack you again, for example for piracy, while you leave. You will also not be allowed to engage players in the system you died even for the purpose of defending an allied ship. You may only re-enter the system in a transport or freighter, and the only thing you'll be allowed to do is trade (no following people around and no initiating role play with anyone). These restrictions last for two hours after the moment you docked during PvP.

2.7 Demands should be reasonable and only one monetary or cargo demand can be issued during each piracy interaction.

Info

An unreasonable demand is a demand that only serves as an excuse to destroy the other player because no player (or character) would realistically obey it. An example would be asking for credits that exceed the total value of a transport's cargo. Another example for an unreasonable IRP demand is for the transport to reply "Just kill me so I can re-spawn where I bought my cargo and resume trading." A better alternative to the later is to die in a fight.

2.8 Don’t disconnect in space to escape interaction. If you get disconnected, log back on immediately and apologize to the players you were interacting with. If you can’t apologize ingame, do so in the forum thread titled "DISCONNECTED". Don’t rejoin a fight without permission from your adversary after getting disconnected.

Info

When a ship loses connection, people within its radar range will see a green message that says it's trying to disconnect. It will drop its shield and stay in space for a certain amount of time, often long enough for it to be destroyed by an enemy. No matter the circumstances, the safest way to avoid a sanction for disconnecting during interaction is to apologize for disconnection ingame or on the forum.

2.9 Connecticut is a system where players aren’t required to role-play and may only attack with the adversary’s consent. Bastille is a system that imprisons rule breakers until they agree to obey server rules.

Info

Players may also train combat as a "simulation" in the role play universe, where they won't be considered "PvP dead" upon defeat. This may only be done if all involved parties agree to it and not abused to circumvent PvP rules.

3. HIRED GUNS & BOUNTIES

3.1 All contracts and bounties must be justified within roleplay and conform to IDs. A character may be hired ingame or on the forum by non-generic IDed (non Freelancer, Pirate, or miner) players, for a minimum of 1 million credits per target. Targets must be informed of the contract/bounty originator before the attack. The reputations of employer and employee must be neutral or friendly to each other, and they must both be hostile to the target.

Info

"Justified within roleplay" means that Bounties should result as a logical consequence from actual ingame interaction between the person placing the bounty and the target. They shouldn't be purely motivated by OORP player relations or abused to be able to blow up transports without demand.

Bounties must be placed before, not after, they're fulfilled.

Spying/scouting bounties must conform to rule 1.1 and reputation rules of 3.1, but it's not required to inform the target on the server if no attack occurs.

3.2 Bounties and contracts made while the employer is offline or PvP-dead must be posted in the "Bounty Offices" sub-forum. Employers must specify their name and affiliation, and also specify and verify the affiliation of those who may claim the bounty. A limited payout number, expiry date, or exclusivity to pre-registered bounty board members may be specified beforehand. Players may not hire exclusively their own characters.

Info

Role play motivating a bounty may be posted anywhere, but every bounty must be documented in the Bounty Board forum section.

If someone is hired to attack someone ingame, the attack may only be initiated if the employer is still online. If the employer is offline while hiring, the contract must be documented with a forum bounty post. An already started engagement may continue if the employer dies during the engagement.

You may claim bounties that your character placed using another one of your characters, as long as the Bounty can also be claimed by other characters than your own and is publicly placed and claimed on the forum.

3.3 Forum-Bounties on factions instead of named individuals (blanket bounties) may only be issued (or sponsored within roleplay) by official factions and governments. These may also be compensated through flat rate payments of at least 30 million credits per month to individuals or factions. Non-generic IDed unofficial factions may sponsor internal blanket bounties for members of their player or NPC faction only.

Info

The flat rate contract contract and all acts under it must be posted.

Sponsoring a bounty means that the payments are guaranteed to be made by the sponsor.

Every official faction may only sponsor one unofficial faction bounty.

3.4 Attacking someone for non-existing contracts or non-claimable bounties, as well as not visibly claiming payment within 3 days of an alleged forum-bounty kill, will result in sanction. Payments must be made within two weeks of a legitimate claim.

Info

If several employers placed bounties on the same target, it's permitted but not required to claim payment with more than one of them.

4. FACTIONS

4.1 Players may create a faction for any publicly available ID they want, if the faction uses a single ID, IFF, and tag. Every faction must have one leader and at least one second-in-command who speak for it. It’s recommended but optional for unofficial factions to post descriptions in the Unofficial Factions and Groups sub-forum, explaining their background, diplomacy, goals, and to ask for community feedback. It’s also recommended to create roleplay message logs on the forum.

Info

All ships in the same faction must follow common diplomacy.

Having faction ships that don’t use an IFF or tag is acceptable.

4.2 Official status is awarded following the "Achieving Official Faction Status" post on the forum. Official Factions (OFs) must have a public feedback thread they answer to on the forum. They have the following Official Faction Rights (OFRs). All instances of OFR use must be documented by forum roleplay.

-OFR 1: OF leaders ranked first or second in command have in-roleplay authority over characters of the same NPC affiliation, regarding diplomacy and strategic/tactical direction. They may not require anyone to follow non-canon or unreasonable roleplay. Disobeying legitimate orders may result in roleplay consequences such as ingame arrest, court-martial, and in extreme cases ingame force.

-OFR 2: OFs who planned an event with at least 24 hours notice on the forum can restrict the participation of others in that event. It shouldn't severely limit another faction’s activities in their own ZoI or provide unfair protection from logical roleplay consequences.

-OFR 3: OFs may request that the reputation of a player's ship be set hostile towards their NPC faction, by posting in the appropriate Violation Reports sub-forum. They must provide evidence of forum roleplay and interaction between the OF and the character. Ships subjected to OFR3 may treat ships of the issuing faction (except transports) as hostile targets.

-OFR 4: OFs may bounty or attack a player who uses their affiliation's technology without the faction ID nor official permission, regardless of their diplomacy with the user's faction. Permissions may only be given by an OF affiliated with the manufacturer of the technology, and must be documented in roleplay on the forum.

Info

In cases where affiliated OF leaders disagree on exercising any OFR, server administrators will decide the course of action, for example by making OF leaders vote.

Irresponsible use of OFRs may result in warnings or sanctions, including removal of official status.

5. PLAYER OWNED BASES

5.1 Dealing more damage to a Player Owned Base (POB) than needed to prevent a ship from docking must be preceded by forum roleplay and a post in the Attack Declaration Thread at least 8 hours (core 1 bases) or 24 hours (core 2 and higher) prior to the attack. Attack declarations are valid for 2 weeks.

5.2 No roleplay is required prior to building a Core 1 base, but it must make sense in roleplay. Name, location and IFF of bases are permanent and can’t be changed after construction. Bases within 15k distance of mining fields may not advance beyond Core 2. Core upgrades have requirements listed in the "Player Owned Base Upgrades" forum thread.

5.3 POBs are destructible when unprotected, so it's recommended you inform yourself about House laws and fees and local diplomacy in order to build in a well protected location. POBs in systems bordering House space may not be engaged by House forces for lack of payment of fees, but can still fall prey to other factions.


6. CHEATING

The following cheats and exploits are forbidden:
6.1 Modifying your Discovery Freelancer installation, using third-party tools, or abusing glitches/bugs in order to gain advantages over other players.
6.2 Running the game with framerates above 155fps. Computers running uncapped framerate must use a third party program to limit the FPS to below 155.
6.3 Using cruise disruptors or missiles in order to track a ship that has successfully cloaked.
6.4 Intentionally ramming a capital ship in order to ''flip'' it or ''catapult'' your ship away from it.
6.5 Suicide trading and intentionally self/team-killing during Combat-Event-Plugin battles in order to prevent the opponent from scoring points.
6.6 Connecting to the server with more than one character at a time (Multiboxing). Players sharing a network connection may not engage in trading/mining at the same time.


7. SANCTIONS

7.1 Administrators will impose sanctions on players who violate rules or harm server gameplay. Admins are obliged to:
-Safeguard the community, server, and forums.
-Be fair and treat all players equally.
-Not mix server roleplaying with server administration in any way.
-Not ignore reported rule violations.

Info

- No teleporting players to give them an IRP advantage

7.2 Depending on severity and amount of rule violations, sanctions can range from a warning, credit fine, loss of equipment, probation periods with removal of certain privileges, and bans of varying duration. Sanctions will appear in forum threads detailing the offenses and punishments.

Info

A "permaban'' is a sanction where the punished player and all his assets are removed from the community for an indefinite amount of time. Permanent bans will only be lifted if a ban appeal is submitted and positively voted on by the administration team. If the vote fails, the player may not submit another appeal for another six months.

When players are "permabanned", their ingame assets are frozen. Shared characters are included in the freeze to avoid situations where shared banks and expensive ships are saved/bumped by a third party Member. The only ships not hit by the freeze are shared Faction ships that have a been shiplocked. Requests to unban them will be viewed on case-by-case basis.

Please only share access to your accounts with people you trust, as losing these accounts is within your own responsibility.

7.3 If someone shows disregard for the rules even after being informed of rules and violations, players can file a rule violation report in the appropriate sub-forum. Playing Discovery Freelancer as a community is less anonymous than other games, and therefore things are often taken more personal. Don’t attempt to use violation reports for personal revenge. If you’re angry, take time to gather and present the evidence properly and make sure you’re not mistaken when you’re calm.

Info

Fair play, a level head, and consideration for others are paramount. The rules are not a sword or shield to be used for or against someone, but are there to ensure that the server environment has structure and allows everyone to have fun. If you make a mistake apologize. Attempts to intentionally bait someone into violating rules or attempts to exploit loop holes will not be tolerated.

Forum Rules

1. When replying to a roleplay post or using the information within in roleplay, be sure your character has access to it (check receivers/participants and message encryption). Don't mix role play and non-roleplay when posting.

2. When choosing to participate in an out-of-roleplay discussion, read the original post carefully and make sure you understand it properly before you answer. Try to avoid off-topic, logical fallacies (straw-man, ad-hominem, appeals to authority, false equivalences), as well as mindless spam posts.

3. No commercial advertising of services or products, and no posting links to to things that violate community rules.

4. Embedded pictures can't be wider than 700px. Signatures can't be larger than 700*250px and 1mb.


Achieving Official Faction Status

1. After a player faction has three or more active members and posted a faction description, ID status, RP story, member list, and diplomatic relations with relevant factions, it can request to become official in the Faction Creation Requests sub-forum. The request may be discussed by other players and administrators, but only administrators can approve or reject official status.

2. To start the approval process, the faction has to provide the admin team with 500 million credits. The amount will only be refunded if the faction gains official status. Once the process starts, the faction tag will be added to the faction activity tracker. Tag-less ships and ships in Connecticut don’t contribute tracker time.

3. The request will remain open for discussion for two months, during which faction performance on both server and forums will be reviewed. The status request will then undergo an admin vote and the result will be posted in the request thread. If rejected, the reasons will be explained and you may still be given a chance to improve and get approved.

4. Upon approval, the faction will receive its own sub-forum in the official factions section, and a free CAU 8 upgrade. Moderation requests for faction sub-forums should be posted here, by the faction leader or a second in command, preferably using the faction forum account. At this point you must also create a faction feedback thread.

5. Once the faction has gained officialdom, it’s required to fill out a Faction Status Report once a month in the Faction Activity sub-forum. It must shed light on the faction's goals, roleplay efforts, and in-game activity.

6. Official factions may request their own ID based on the one of their NPC faction, to allow for specialized roleplay or remove certain restrictions. The faction ID can be requested from the admins if the faction's roleplay, or that of a sub-group in the faction, can't be fulfilled within the original ID. If restrictions are lifted for only a sub-group, it will be specified in the ID.

7. If an official player faction’s activity sinks below the required threshold, its status is changed to “suspended”. It will have 4 weeks to either rebuild activity or lose officialdom and associated rights.


Player Owned Base Upgrades

POBs built in House space are subject to House laws and fees.

Core upgrades can only be done after fulfilling requirements depending on core level and by then requesting the necessary blueprints. Requests must be posted in the appropriate subforum, and are invisible to non-admins. The blueprints given upon successful request are non-transferable. Abuse will result in loss of the base.

Ugrade requirements:

Core 2: Post the name, IFF, system, and purpose of the base.

Core 3: Provide more detailed roleplay and demonstrate responsible behavior for at least one month as Core 2. Base may not be within 15k of a mining field.

Core 4: Provide proof of responsible and productive roleplay for at least two months as Core 3.

Core 5: The base must be owned by an official faction for at least three months as Core 4. Only one Core 5 base per official faction is permitted. Wear & tear damage is disabled at Core 5, and food/water/oxygen consumption can be disabled through a special roleplay request.


System Classifications

Factions are bound by server rules as well as ID restrictions and allowances. In case of conflict, IDs over-ride server rules.

House Space

-Sovereign Space: This is called "House Space" in ID docking rules, quasi-lawful piracy, and quasi-lawful house law enforcement. House Military, Police, and Intelligence Factions (MPIFs) may enforce roleplay consequences on players, factions and POBs found breaking House Laws here.

-Controlled Space: MPIFs may enforce roleplay consequences on players, factions, and POBs found breaking House Laws, only if they personally witnessed the legal infraction while uncloaked.

-Outer Region: Like Controlled Space, except that MPIFs may not enforce roleplay consequences on non-hostile POBs, whether they break House Laws or not.


Liberty
-Sovereign Space: New York*, Alaska, California, Colorado, Ontario, Texas, Virginia.
-Controlled Space: Alberta, New Hampshire, Pennsylvania, Cortez, Hudson, Magellan
-Outer Region: Cassini, Kansas

Bretonia
-Sovereign Space: New London*, Cambridge, Manchester, Newcastle
-Controlled Space: Dublin, Poole, Omega-3, Cortez, Magellan
-Outer Region: Edinburgh, Leeds

Rheinland
-Sovereign Space: New Berlin*, Frankfurt, Hamburg, Munich, Stuttgart
-Controlled Space: Bremen, Koeln, Omega-7, Hudson
-Outer Region: Dresden

Kusari
-Sovereign Space: New Tokyo*, Hokkaido, Honshu, Kyushu, Shikoku
-Controlled Space: Hiroshima, Nagano, Tohoku, Rishiri
-Outer Region: Chugoku, Tottori

Gallia
-Sovereign Space: Ile-de-France*, Burgundy, Dauphine, Orleanais, Picardy
-Controlled Space: Auvergne, Languedoc, Lorraine, Lyonnais, Tau-23, Tau-31, Orkney, Edinburgh, Leeds
-Outer Region: Champagne, Provence

*House Capital


Independent Systems

See House Space for independent systems that are also house-controlled.

Border Worlds: Bering, Coronado, Drake, Galileo, Kepler, Humboldt, Inverness, Puerto Rico, Unknown, Vespucci
Taus: Tau-23, Tau-29, Tau-31, Tau-37, Tau-44, Baffin, Orkney, Rishiri, Roussillon
Omegas: Omega-3, Omega-5, Omega-7, Omega-9, Omega-11, Omega-41, Omega-47, Omega-49, Omega-54, Omega-55, Omega-58, Cayman
Sigmas: Sigma-13, Sigma-15, Sigma-17, Sigma-19, Sigma-21, Sigma-59, Okinawa
Omicrons: Omicron Alpha, Omicron Beta, Omicron Gamma, Omicron Delta, Omicron Epsilon, Omicron Theta, Omicron Iota, Omicron Kappa, Omicron Mu, Omicron Xi, Omicron Rho, Omicron Sigma, Omicron Tau, Omicron Phi, Omicron Chi, Omicron Psi, Omicron Omega


Ships Classifications

Unless specified differently by their infocards, ships are classified as such:
Fighters/Snubs: Light Fighters, Heavy Fighters, Very Heavy Fighters, Super Heavy Fighters and Bombers
Freighters: Trader ships with cargo holds smaller than 650 units
Transports: Trader ships with cargo holds larger than 650 units, including Liners
Cruisers: Destroyers, Cruisers and Battlecruisers
Battleships: Battleships, Dreadnoughts, Juggernauts and Carriers
Capital Ships: Gunboats, all Cruisers and all Battleships

---

I think you want Impy on this project.

>5.1 Dealing more damage to a Player Owned Base (POB) than needed to prevent a ship from docking must be preceded by forum roleplay and a post in the Attack Declaration Thread at least 8 hours (core 1 bases) or 24 hours (core 2 and higher) prior to the attack. Attack declarations are valid for 2 weeks.

Some important difference in dealing damage to prevent dock. Even if nobody not sanctioned for this actions,in current rules nothing said about it and this really confused people. Really should be writed especially.

>5.3 POBs are destructible and not safe when unprotected. It's recommended you inform yourself about House laws and fees and local diplomacy before construction. POBs in systems bordering House space may not be engaged by House forces for lack of payment of fees, but can still fall prey to other factions.

Last line important too. Some peoples really dont realise, that their bases can be demolished even by small groups of pirates, if it dont have shield for defence, and dont realise about existing of big amount of BS in indie property of some unlawful factions. Should be writed, yes.

Another PoB rules maden more compact, and this is right direction i think.

Post a bounty on someone under Forum account "A" and then watch the player list and wait for your victim to show up. Usually works best during trade events, hunt him/her/it down....play out the necessary one line of lame RP such as " Oh what do we have here?....you have a bounty on your head...time to die...McDick sends his regards." and vaporise the helpless sap.

Then go back to the forum and claim that bounty placed with Forum Account "A" but claim it using Alternate forum account "B". You must remember to pay yourself.

(03-25-2018, 12:14 AM)Mephistoles Wrote: [ -> ]I think you want Impy on this project.

If you can convince him to come on board with it, I'll pay you 10 mil.

(03-25-2018, 01:38 AM)oZoneRanger Wrote: [ -> ]Post a bounty on someone under Forum account "A" and then watch the player list and wait for your victim to show up. Usually works best during trade events, hunt him/her/it down....play out the necessary one line of lame RP such as " Oh what do we have here?....you have a bounty on your head...time to die...McDick sends his regards." and vaporise the helpless sap.

Then go back to the forum and claim that bounty placed with Forum Account "A" but claim it using Alternate forum account "B". You must remember to pay yourself.

I guess I could add the word "justified" in

"All contracts and bounties must be justified within roleplay and conform to IDs."

to prevent abuse of that possibility.

Thank you. What char would you like the credits to be transferred to?

(03-24-2018, 11:32 PM)Karlotta Wrote: [ -> ]Freighters: Trader ships with cargo holds smaller than 650 units
Transports: Trader ships with cargo holds larger than 650 units, including Liners
Cruisers: Destroyers, Cruisers and Battlecruisers
Battleships: Battleships, Dreadnoughts, Juggernauts and Carriers
Capital Ships: Gunboats, all Cruisers and all Battleships

(03-24-2018, 11:32 PM)Karlotta Wrote: [ -> ]Freighters: Trader ships with cargo holds smaller than 650 units

Freighters: Trader ships with cargo holds up to 650 units
Also, 204-ARKM-B10 "Ragnar" Rheinland Armored Transport does have 850cargo and although it is by name transport, it is considered freighter by the game, in many aspects. It can be jumped for example. Then you have Base Construction Platform, with 750cargo.

(03-24-2018, 11:32 PM)Karlotta Wrote: [ -> ]Capital Ships: Gunboats, all Cruisers and all Battleships

Capital Ships: Gunboats, Destroyers, Cruisers, Battlecruisers, Battleships, Dreadnoughts, Juggernauts and Carriers
Although it is longer, I think it is much clearer. It shows, that some ships fall under more than one class.

That being said, some ships are hybrids: Junker GB for example has 1100cargo and needs to use Transport Cloak. Junker Frigate is GB/Transport hybrid too. And what about the Bustard? Is it liner? Is it carrier?

Ragnar is a freighter, not a transport. The infocard is misleading, it's a class 2 ship which are freighters.