The Consortium

[Lobster]

STRATEGIC COORDINATOR: Strategic co-ordinators function similarly to tactical co-ordinators, abeit on a larger scale. Directly commanding full fleets or divisions of troops (although more commonly smaller units) and relaying Overwatch's instructions to tactical co-ordinators and lesser rank structures, similarly to military Generals or Admarals.

SHIPMASTER/SHIPMISTRESS (CS-CSHM#)

Shipnodes in command of Consortium capital ships. They typically answer to Coordinators and higher ranking members, and ensure the function and operation of the ship they are assigned to.

REGULATOR (CS-CRG#)

Regulators are part military-police, part technicians, part mechanics. They are tasked with internal affairs, and maintianing Consortium military forces and industrial output. Diffrent subtypes exist, but all are interchangable. Regulators are tasked with, ensuring no dissent or behavioral anomalies arise (and dealing with those that do), repairing or overseeing and coordinating the repairs of damaged equipment, and often interrogating captured enemy combatants before Augmentation. They typically have even less emotional capability then other Consortium personel.

ENGINEERING (CS-CENG#)

These are analog to any combat engineering personell of any other army, abiet with more wide-ranging . Handling both direct military projects, Industrial operations, repair of Consortium and allied hardware, analysis of technology (alongside research division), and any other engineering or technical related duties within the Consoritum. While technically able to fly any strike-class Consortium warship, individuals with engineering skills are often assigned to utility vessels or internal crews on capital ships.

Engineering is also tasked with augmentation of newly captured personell for Consortium use.

RESEARCH (CS-RCH#)

As their name would suggest, Research Division is specialised to anylise any captured technology, from the most primitive to the beyond futuristic, to find means of using it for Consortium use. Usually closely allied with Regulators and Engineering, they usually stay behind the lines, but it isn't unheard of for them to be deployed forward in certian circumstances. They are almost always secondary crew on larger ships, though their operational status would allow them to command specialised research ships.

BLACKWATCH (CS-BW#)

Blackwatch units are effectively special forces shock troops. With the best possible military training (that which can only come from experiance, as opposed to neurocyte uploads), equipment, and an unmatched ruthlessness to get the job done. While their types of operations vary, and are usually highly classified even amongst Consortium personell, some of their more common tasks include intelligence gathering, covert ops, surgical strikes on critical targets, infiltration of enemy populations and factions, and anti-Exogen operations.

SPAHI (CS-SPK#)

The meat of the Consortium. While generally expendable, Spahi are nonetheless important both for their use as labourers, military forces, and as intelligence assets. The men on the frontlines are as much a part of the chain of command as the ranking Co-ordinators and Shipmasters. Hundreds of subtypes exist, too numerous to list here, as individuals may recive diffrent training for ground combat, space dogfighting, or military support occupations.

Spahi are divided up into 1st, 2nd, and 3rd class. Ship denominations are granted based on seniority.

---

Spahi cls-3

Class 3 Spahi are essentially raw recruits under evaluation. They are not permitted high-end ships to prevent losses should their combat skills prove unsatisfactory.

Allowed ships

Drones: Civilian Shuttle
Fighters: Dagger, Stiletto, Kingfisher
Bombers: Mafic
Freighters: Dromedary, Civ-freighter
Transports: Gull
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: none
Misc: Startracker, Starflier

Currently Assigned Personnel: ??? (Reavengitair), ??? (Turkish)

***

Spahi cls-2

Class 2 Spahi have proven competant enough to be allowed more significant weaponry and superior ships.

Drones: none
Fighters: Scimitar, Switchblade, Kingfisher, Sabre
Bombers: Mafic, Falcata
Freighters: Dromedary, Civ-Freighter
Transports: Armored Transport, Gull, Albatross
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: none
Misc: none

Currently Assigned Personnel: \CS\-Nekekami (Death's Overture)

***

Spahi cls-1

Class 1 Spahi are the ranking slave-soldiers in the Consortium which have not been placed on other assignments.

Drones: none
Fighters: Scimitar, Switchblade, Kingfisher, Sabre
Bombers: Mafic, Falcata
Freighters: Dromedary, Civ-Freighter
Transports: Armored Transport, Gull, Albatross, Borderworld Transport
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: none
Misc: none

Currently Assigned Personnel: \CS\-Regent (Alexander), \CS\-Tacitus (Taro), \CS\-Helkos (Sivran)

***

Airwatch

Tactical units are dedicated space combat personnell and are mainly assigned the majority of combat operations. These personell are usually drawn from the best captured enemy pilots or Spahi who prove proficient. They outrank all other units except Overwatch during combat operations.

Allowed ships

Drones: A.I. SHF (with special permission and RP)
Fighters: Scimitar, Switchblade, Kingfisher, Sabre
Bombers: Mafic, Falcata
Freighters: none
Transports: Prison Liner
Gunboats: Outcast Gunboat
Destroyers/Cruisers: Outcast Destroyer, A.I. Cruiser (with special permission and RP)
Battleships: Decided on Case-by-Case basis
ComLog: none
Misc: none

X.O: Juliet.November (Nathrael)

Currently Assigned Personnel: \CS\-Interceptor.Shield (Watsas), \CS\-Skyshield (Shag'o'had), \CS\-Shelldrake (Tidomann), \CS\-Enforcer (Watsas), \CS\-Tactical-Hk1/2/3 (Enko), \CS\-Darak.Ti (shared, mostly Watsas), \CS\-Kuudark (Kikatsu), \CS\-Tactical-21 (Alex<3net), \CS\-Khamun (Watsas), \CS\-Shamshir (<3net), \CS\-Eskaluur (Ktayn), \CS\-Carla (Bobafett), \CS\-Artificier (Ktayn again), \CS\-Codex.Control.Unit (N@thrael)

*note, Guard ID required for Capital Ships

***

Combat Logistics

Logistics Units catagorize all level of combat support assets, including transport ships, repair vessels, mining ships, and space stations. These are critical for support of all other arms of Consortium Operations.

Allowed ships

Drones: Civilian Shuttle
Fighters: CSV, X-Shuttle
Bombers: none
Freighters: Dromedary, Civ-freighter
Transports: Armored Transport, Gull, Albatross, BW transport, Train (any non-faction type), Prison Liner, Slave Liner
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: none
Misc: Barge, A Yacht (with special permission)

X.O: \CS\-Ryosei.Yonekura (<3net)

Currently Assigned Personnel: \CS\-Basul-Re (Watsas), \CS\-Logistics-23 (Alex), \CS\-AT-## (mostly shared or <3net), \CS\-Storage.Barge (shared)

***

Hunter-Abductor

Hunter-abductors are sub-type of military logistics which deal in Capture and Assimilation. Essentially Consortium equivelents to Slavers.

Allowed ships

Drones: none
Fighters: Virage
Bombers: Mafic
Freighters: Dromedary
Transports: Armored Transport, Borderworld Transport, Slave Liner, Prison Liner
Gunboats: none
Destroyers/Cruisers: OC Destroyer (only in the case of \CS\-Tiishalon)
Battleships: none
ComLog: Heavy Lifter
Misc: none

X.O: \CS\-Nihilaus.Clark (Shagohad) & \CS\-Zio.Internecine (Bobafett) [both temporarily]

Currently Assigned Personnel: \CS\-Tiishalon (also Bobafett)

***

Combat Engineering

Engineering units are a sub-type of Logistics spikes and largely subordinated to them, but may be subordinated to Airwatch in combat situations.

Allowed ships

Drones: Civilian Shuttle
Fighters: CSV
Bombers: none
Freighters: Dromedary
Transports: Armored Transport, Gull, Albatross, BW transport, Prison Liner, Slave Liner
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: Repair Ship, Mining Ship, Heavy Lifter
Misc: none

X.O.: N/A

Currently Assigned Personnel: \CS\-Shipwreck (Taro), CS-YMD-21 (shared), \CS\-SALCAP-1/2 (shared)

***

Blackwatch

Allowed ships

Drones: Civilian Shuttle
Fighters: Scimitar, Switchblade, Kingfisher, Sabre, Virage, X-Shuttle
Bombers: Falcata, Mafic
Freighters: Dromedary
Transports: BWTransport, Armored Transport, Prison Liner
Gunboats: none
Destroyers/Cruisers: none
Battleships: none
ComLog: none
Misc: none

X.O. \CS\-James.Dacker (Watsas)

Currently Assigned Personnel: \CS\-Chikako.Asano (<3net), \CS\-Ishimaru.Kaito (Austin Goodwoman)

***

Overwatch

Overwatch may or may not command a ship directly, but is typically well away from the front-lines commanding and overseeing Consortium activity as a whole.

Allowed ships

Drones: none
Fighters: none
Bombers: none
Freighters: none
Transports: none
Gunboats: none
Destroyers/Cruisers: none
Battleships: Morningstar*
ComLog: none
Misc: Barge

Currently Assigned Personnel: \CS\-Ironwatsas (watsas)

(*as the Morningstar does not actually exist ingame, it is mentioned mainly for referential purposes)

---

RECRUITMENT POLICY

(//this section is written in OOC, for an inRP explanation, see 'Capture Policy: Augmentation and Assimilation methods above')

As a faction, the Consortium is on lookout for individuals with exemplary RP skill and competent PvP capability (though the latter is secondary) who may possibly be willing to join. If someone is willing to join, or seeks to join, the following prerequisites however, must be met.

1: First and foremost, RP skill. Specifically, ingame RP. Forum RP is also to some extent necessary, but Ingame is the real deal-breaker. Competent PvP is welcome, so long as it is conducted in line with faction doctrine. A recruit could be the worst shot in the history of the server, but if he has excellent RP, we'll train him over time or put him in a trade/logistics ship.

2: New Recruits must have an active Forum account, and Skype. The latter is necessary for co-ordination of operations, as briefings, planning, and updates are typically conducted there. The former of course is needed for Message Dump posts and forum RP.

3: While sheer length of time spent on the server is largely irrelevant, new recruits should have a high degree and depth of knowledge and understanding about the server, it's factions, and history. Understanding how to interact with and respond to other factions is key to cohesive Roleplay.

4: A firm understanding of the English language and ability to take orders is also important. We acknowledge that English is a retarded language and those who developed it must have been on crack at the time, but it is the language of this server and nearly all of our members. If you are not a native english speaker, that is fine (and could possibly be taken advantage of with creative RP), but for practical reasons, it is important to be able to read and write competently.

5: Keeping up activity is important, so members should be willing and able to dedicate atleast SOME time every now and then to the faction, participate in events, or just make their presence known on the server.

---



---

Consortium personnel usually speak in military code, with a medical nomenclature. This serves mainly as an aesthetic touch. The current dictionary of Consortium terminology is listed here http://bradiuscaesar.com/CS/dictionary.html

Our augmentation and Cyborg RP, aside from being one of the faction's core principals, is also the RP means to our recruitment. While we rarely Augment the actual characters we encounter, we do get a better idea of what players would make better members for the faction. As well, other players get atleast a rough idea of Consortium role play. This logic applies to both allied and enemy factions.

---

NAMING CONVENTION

All spacecraft belonging to the Consortium bear the \CS\ prefix. For fighters, bombers, freighters, or non-combat transports, This is typically followed by a codename or character name.

Examples being.

\CS\-Enforcer
\CS\-Ishimaru.Kaito

codenames can have more then 1 word such as:

\CS\-Interceptor.Shield

In some cases, these names will have special suffixes designating either rank or assignment.

\CS\-James.Dacker-[B]

Suffixes for small ships are as follows (these will be gradually phased-in for older ships. Spahi, Airwatch, and Overwatch do not use these suffixes)

[B] = Blackwatch
[E] = Engineering
[L] = Logistics
[H] = Hunter

Naming Conventions for capital ships and large logistics ships are slightly diffrent. The normal procedure is \CS\ prefix, shipname, followed by a hull code designating shipclass and number. These hull codes are based on real life Hull Classification Symbols (the link provided should be used for referance to these).

Example.

\CS\-Khamun-[FFG-21]

in which FF = Frigate (consortium refer to Gunboats and Gunships as such), G = Guided Weapons Supportm and 21 being the identification number.

All Gunboats, Capital Ships, Liners, or Combat Engineering ships should use appropriate hull designators. (improvisations may be made if a certian shiptype has no maritime naval analog or obviously compatable hull code).

In some cases, names of utility ships may ONLY consist of hull codes. E.g.

\CS\-YMD-23

YMD = Mining ship, Drone

Typically, unnamed ships using only codes are ancillary or ships or unmanned logistics ships, or simply 'not important' enough to receive proper names, or generic ships on shared accounts. Such ships include storage freighters, armories, bank ships, etc. Many of these ships CAN use proper names or a code, with the ultimate decision left to player preference.

---

The aesthetic nomenclature for Consortium naming isn't clearly defined at this point. The most common naming conventions currently in use are...

English/American military lingo (or something similar): E.g. Interceptor Shield, James Dacker
Japanese (to partially fit the Kusari theme): E.g. Hoshinokatana, Nekekami, Ishimaru Kaito
Indian/Middle Eastern (often mythological): E.g. Khamun, Vajra, Al-Khalid
Names that are aesthetically similar to the above, but not necessarily actually from the above languages

However, some diversions can be made from these, depending on the individual character in question.

---

[url="http://img39.imageshack.us/i/csimperitivesbar.png/]
[/url]

(//this section is also written in an OOC context)

The Consortium has existed as an RP group since about sometime in the Fall of last year (2008), and was at that time basically the joint RPs of myself, Enko, Ktayn, and Bobafett combining and turning into a full blown faction.

In the Discovery community as a whole, the Consortium fills several niches which no other faction has yet filled. The main themes of the faction (Techno-Parasitism and de-humanization, the simultaneous conquest of humanity to perhaps save humanity, the 'Outside Context Problem', and mass abduction and forced human engineering.) are thus far, not occupied by any other faction in the same manner as us, though some similarities may exist.

There may also be some similarities to other entities from outside Discovery and Freelancer. While the Consortium is by no means an import faction (despite some, occasionally intentional similarities, most of the faction's background is original). However, some outside influences are relevant. The most obvious are the Combine from half-life, as evidenced by our adaptation of Combine's medical newspeak to fit our context.

The main reasons for this are simply because 1: It sounds really cool, 2: It fits and emphasizes the 'dehumanization' theme of the faction, 3: most of that terminology is adapted medical terminology.

Other influence like Quake, Ghost in the Shell, Homeworld, Angels Fall First, are also apparent. Much of this is aesthetic (e.g. character representations and screenshots of various stuff), but this is no different then other factions such as the Phantoms, Mandolorians, and individual characters doing the same.

---