Star Wars Roleplay: Chaos

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Codex Denied ESDF-Eriadu System Defense Force

Status
Not open for further replies.
wOXIiCt.png

OUT OF CHARACTER INFORMATION
  • Intent: To create an autonimous planetary| System Defense force for the Eriadu system to work in conjunction with the Confederate Defense Force of the Confederacy of Independent Systems at the behest of Viceroy Credius Arcosius Nargath.
  • Image Credit: Created by Credius Credius with [X]
  • Role: Planetary| System Defense force
    The Eriadu System Defense Force will act as a localised army, completely dedicated first and foremost to the Viceroy of Eriadu and the Territories | System which they govern. Though usually, a planetary defense force is more of a militia rather than a military, the ESDF will fill in various roles usually maintained by the Confederate Defense Force as a means to have a constant, military presence at the ready at any given crisis. Though the ESDF essentially functions with the Viceroy as supreme commander, command can be transferred to the CDF at any given time during crisis.
  • Permissions:

  • Links:


    GENERAL INFORMATION
    • Unit Name: Eriadu System Defense Force
    • Affiliation: Viceroy of Eriadu, Confederacy of Independant Systems
    • Classification: Infantry, Navy, Engineers, strategic command, civil operations, security detail.
    • Equipment:
      • See Eriadu System Defense Army
      • See Eriadu System Defence Navy
      • See Valkan Guard

      • m9iV36K.png
    • Description: [ Give a brief overview of this combat unit. Notable appearance, if they have a unit emblem, general mindset and behavior, etc. ]
  • COMBAT INFORMATION:The combination of Unit Size and Availability below is the indicator of how numerous your unit is. Stormtroopers for instance would be considered Large/Common, while Rogue Squadron would be a Small/Unique unit. Majority Force User Units are prohibited from being Common or Large. The stronger and more specialized your unit is (FU or NFU), the smaller and less common it should be.
    • Unit Size: [ This is how many individuals make up a single unit. Choose from Small (each unit is small, comprising a dozen members or less), Medium (moderately sized units, often specialized), Large (many individuals, often compromising the rank and file). ]
    • Unit Availability: [ This is how many units are available for deployment. Choose from Unique (only one), Rare (very few, difficult to replace, may have long training times), Uncommon (some, replaceable, enough to support), Common (many, easy to replace, likely with more always in training). ]
    • Unit Experience: [ How experienced is this unit? Choose from Rabble, Recruit, Trained, Veteran, Elite. Veteran and Elite are more appropriate to smaller, less common units with lower casualty rates than the rank and file, while Trained and lower are appropriate for larger, more common units with higher replacement needs. You are encouraged to update the units, as they grow through RP in experience, through the submission modification thread. ]
    • Combat Function: [ Describe this unit’s general function in combat. Put things like tactics, habits, goals, how they interact with other parts of a larger army, do they need support or are they the support, etc. ]
  • Strengths:
    • [ Provide, in list format, some strengths of this submission. 2 recommended. ]
  • Weaknesses:
    • [ Provide, in list format, some weaknesses of this submission. 2 recommended. ]
  • HISTORICAL INFORMATION
    [ Include a description of the unit’s history here. How they were formed and by whom, past noteworthy battles, moral affecting defeats, where they are stationed if applicable, etc. ]
 
Last edited:
Credius Credius

What is the status of this submission? As per the rules of the pre-codex, which can be found here, submissions may only remain in the pre-codex for one month before being archived. Unfortunately, your submission has been in the pre-codex for longer than a month, if you could please update us on if you still intend to complete it, or if you would rather the submission be moved to the archives till you're ready to work on it.
 
Status
Not open for further replies.

Users who are viewing this thread

Top Bottom