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!

Status
Not open for further replies.

OUT OF CHARACTER INFORMATION
PRODUCTION INFORMATION
TECHNICAL SPECIFICATIONS
  • Classification: Battleship.
  • Role: Flagship, Battleship, Pocket Dreadnaught, Starfighter Carrier, Superheavy Tractor Tug, Planetary Assault Carrier, Military Transport, Etc.
  • Length: 3,000 Metres.
  • Width: 750 Metres.
  • Height: 1,200 Metres.
  • Armament: Very High Rating.
    • [3] Heavy Tractor Beam Projectors, with Magnite Crystal Enhancements.
      • [1 Fore, 1 Port, 1 Starboard, and 0 Aft.] (Equatorial Trench Placement.)
    • [12] Octuple Barbette Super-Heavy Turbolaser Batteries.
      • [4 Fore, 4 Port, 4 Starboard, and 0 Aft.] (Ventral: 6, Dorsal: 6.)
    • [12] Octuple Barbette Super-Heavy Ion Cannon Batteries.
      • [4 Fore, 4 Port, and 4 Starboard, and 0 Aft.] (Ventral: 6, Dorsal: 6.)
    • [8] Turreted Flex-tube Launchers, with Variable Payloads and Warheads.**
      • Four Projectors per Turret; ~600 Warheads.
      • [2 Fore, 2 Port, 2 Starboard, and 2 Aft.] (Ventral: 4, Dorsal: 4)
    • [10] Deck-mounted Flak Cannons.
      • [0 Fore, 5 Port, 5 Starboard, and 0 Aft.] (Equatorial Trench Placement.)
    • [90] Dual Heavy (Kyber Crystal - Enhanced) Turbolaser Cannon Turrets, with Laser-Reflective Barbettes.
      • [20 Fore, 30 Port, 30 Starboard, and 10 Aft.] (Ventral: 45, Dorsal: 45.)
    • [90] Dual Heavy Ion Cannon Turrets, with Laser-Reflective Barbettes.
      • [20 Fore, 30 Port, 30 Starboard, and 10 Aft.] (Ventral: 45, Dorsal: 45.)
    • [120] Automated Quad Laser Cannon Turrets, with Laser-Reflective Barbettes.
      • [30 Fore, 30 Port, 30 Starboard, and 30 Aft.] (Ventral: 60, Dorsal: 60.)
    • [120] Automated Rotary Point Defence Cannons, with Laser-Reflective Barbettes.
      • [30 Fore, 30 Port, 30 Starboard, and 30 Aft.] (Ventral: 60, Dorsal: 60.)
    • [120] Automated Antimissile Octets, with Laser-Reflective Barbettes.
      • [30 Fore, 30 Port, 30 Starboard, and 30 Aft.] (Ventral: 60, Dorsal: 60.)
    • [120] Automated Nanomissile Blister Pods, with Seeking Anti-missile Interception Protocols. (Thirty Nanomissiles per Blister.)
      • [30 Fore, 30 Port, 30 Starboard, and 30 Aft.] (Ventral: 60, Dorsal: 60.)
  • Defences: High Rating.
    • Heavily Reinforced, and Ablative Armour and Hull Plating.
      • Honeycombed Skeletal Structure, with Internalized Anticoncussion Field Generators, Laser Reflective Paneling, Animated Metal Sealant, and Redundant Armour Plating, Etc.
    • Primary Deflector Shielding Array (Ray, Particle and Concussion Barriers; Overlaid.)
      • Redundant Deflector Shield Emitters and Generators; Miniaturized.
    • Secondary Deflector Shielding Array (Ray, Particle and Concussion Barriers; Overlaid.)
      • Redundant Deflector Shield Emitters and Generators; Miniaturized.
    • Tertiary Deflector Shielding Array (Ray, Particle and Concussion Barriers; Overlaid.)
      • Redundant Deflector Shield Emitters and Generators; Miniaturized.
    • Reinforced Ionic Shielding.
    • Standard Emergency Thrusters (Chemical Propellant and Lateral Thrusters.)
    • Advanced Reactionary Pressor Beam Emitters - Maximum Coverage Layout.
    • Advanced EWAR, Electronic Countermeasures, Chaff, Flare Launchers, Etc.
    • Standard Internal Defenses.
  • Hangar Space: Average Rating - Sixteen Squadrons.
  • Hangar Allocations:
    • Starfighters: Six Squadrons (Seventy-Two Attack Craft; Two Starfighter Wings - New Republic Style.)
    • Support Craft: Two Squadrons (Twenty-Four Auxiliary Craft.)
    • Capital Ships (Corvette Class): Four Corvette - Class Starships
      • Eight Squadrons Exchanged for Four Corvettes (<150 Metres in Length.)
      • External Hangar Platforms with Magnetized Surface; Located Behind the Frontal Hatchet Superstructure.
  • Maneuverability Rating: 60 DPF - Average Rating.
  • Speed Rating: Low Rating.
  • MGLT: 45 MGLT.
  • Maximum Atmospheric Speed: 800 Km/H.
  • Engine Unit(s): Ion Engines - Twelve Drive Units.
    • Eight Primary, with Four Secondary.
  • Secondary Propulsion Method: Integrated Repulsorlift Engines, with Turbofans; Retractable Cowling.
  • Primary Power Plant: Hypermatter Reactor.
  • Secondary Power Plant(s):
    • Localized Compact Fusion Reactors.
    • Solar Ionization Conversion Module(s) with Retractable Agrinium Collection Arrays.
  • Hyperdrive: Equipped.
  • Hyperdrive Class:
    • Primary Rating: Class 1.0
    • Secondary Rating: Class 8.0
  • Passengers:
    • One Thousand Soldiers - Shipboard Security Complement
    • Four Thousand Soldiers - Planetary Assault Brigade.
  • Crew Complement (Optimal): 2,750 Officers, Enlisted Personnel, and Integrated Droid Brains.
  • Crew Complement (Skeletal): 1,450 Officers, Enlisted Personnel, and Integrated Droid Brains.
  • Escape Craft: Innumerable Saviour Pods and Ejectable Lifeboats.
  • Cargo Capacity: 120,000 Metric Tonnes
    • Including Vehicles, Misc Cargo, Munitions, Fuel, Etc.
  • Consumables: Five Years.
STANDARD FEATURES
  • Advanced Sensor Systems and Targeting Systems.
  • Standard Avionics Package.
  • Standard Navigation System.
    • Dedicated Precision MicroJump Computer.
  • Standard Life Support System.
    • (Automated Barrack Deck(s,) Integrated Training Centres, Mess Halls, Recreational Facilities, Etc.)
    • Trans-binary Deflector [Anti-Cosmic Radiation] and Rad-Dampening Energy Shields.
  • Standard Damage and Hazard Control Systems.
  • Standard Tractor and Pressor Beam Emitters.
  • Standard Anti-Ion Emission Tracker (Anti-Hyperspace Tracking.)
  • Standard Communication Systems, with Encrypted Military Keys.
  • Standard Shift and Relativistic Shielding.
  • Standard Magnetogravitic Shielding (Internal [Cargo Bays] and External [Concussion Shield Reinforcement: Particulate Debris.])
  • Standard Thermal and Atmospheric-Friction Shielding.
  • Standard Force Cylinder Transit Conduits.
  • Standard Animated Metal Sealant, with Automated Repair Drones.
ADVANCED SYSTEMS
Strengths:
  • Pocket Dreadnought - Heavily Armed and Armoured; Devastating Super-heavy Weaponry.
  • Highly Automated, with Animated Metal Sealant, Automated Repair Drones, and Minor Regenerative Properties.
  • Reinforced Defensive Capabilities on External Emplacements, and within the Skeletal Structure.
  • Shieldception - Multiple Layers within Layers of Deflector Shielding Inhibit the Capabilities of Individual Field Disruptors; Making Each Projected Layer Harder than the Previous One to Breach.
  • Advanced Countermeasure Suite; Internal and External Systems.
  • Lateral Thrust Vents (Increased Maneuverability.)
  • Magnite-Enhanced Heavy Tractor Beams - Capable of Pulling Enemy Starships Apart.
  • Dual Engine Placement; Limited Combat Capabilities when Connecting Spar is Severed.
Weaknesses:
  • Limited EMP and Ionic Resistance (Proximity Dependant.)
  • Limited Firing Arc’s (Heavy Focus on Bow, Port and Starboard Sections.)
  • Limited Capital-Grade Weaponry (Aft Section.)
  • Limited Heavy Tractor Beam Placement (Bow, Port and Starboard Sections.)
  • Turreted Warhead Projectile Tubes (Explosive Chain Reaction.)
  • Dual Engine Placement; Limited Combat Capabilities when Connecting Spar is Severed.
  • Exposed Primary Command and Observation Deck(s.)
  • Limited Self-Repair Properties (Full Restoration Requires Sufficient Drydock Time.)
DESCRIPTION
Initially commissioned by the nascent New Republic, and built from the disassembled Imperial warships captured during the Battle of Endor, the Starhawk-Class Battleship was one of the first non-Mon Calamari warships that served within the New Republic Defence Force. As materials were scarce, and budgets were tight, the New Republic Senate found itself finally coming to an agreement in regards to re-purposing Imperial war material to take the fight to what remained of the Emperor's ever-lasting legacy. From this new initiative, the conceptual origins of the Starhawk were born. While it's uncertain what inspired those ancient technical architects, or how many variants they rifled through to achieve their final result; what is known, was just how powerful these battleships were. Heavily armed, and equipped with tractor beams - allegedly ten times more powerful than the Imperial-standard, the Starhawk was truly a juggernaut amongst the stars.

It was this legacy that the Republic Engineering Corporation sought to reignite with a warship that would become the Starhawk's spiritual successor. However, to embark on such a project with the materials on hand would've been ludicrous. The Republic Engineering Corporation never made a warship of that size before. Sure, they've done refits on several former First-Imperial battlecruisers, but those were warships that were already built and didn't require them to be built from scratch. They needed raw materials and the proper facilities in which to house this new, and prosperous endeavour. The latter was easy enough, as there were many scattered facilities drifting out in the depths of space - waiting for new masters to lay claim to them.

In their quest to find the required material needed to create the first generation of what would eventually be called Starhawk III's - the nascent Shipwright looked to the remnants of the First Order, and their once-proud navy. Due to the collapse of their government and subsequent withdrawal into exile, there was a plethora of derelict warships and salvage populating their former spheres of influence. Precisely what the Corporation would need, not only to adhere to the storied legacy of the Starhawk - but for the production of their successors as well. To that end, the Republic Engineering Corporation contracted nearly a dozen salvage teams, alongside elements of the Golden Company to act as their security detail - and additional transport if required.

With several wrecks and derelict hulks in tow, the twinned shipwrights began disassembling their newfound prizes into their component parts and materials, before reforging them anew with the intent of making them better. The First-Imperial technology - what wasn't destroyed or damaged beyond repair - was folded into a blessed technological union with Thyrsian and Coruscanti brilliance. Their finished product, in many ways, was considerably larger than originally intended as the actual dimensions of the first generation Nadiri battleships were nebulous at best. However, such a feat of engineering was made possible due to the amount of material provided by the captured Resurgent - Class Star Destroyers that made their way into the shipwrights' possession.

From the ashes of the First Order's Navy, and of the various Imperial Warlords that came after, came the Starhawk III - Class Battleship, or more colloquially known amongst the Coruscanti as the Mark Three Starhawk.

Utilizing the same "hatchet"-like sensor profile of the Original Starhawk, the twinned shipwrights did their best to replicate the ancient warship's design; albeit with several minor, quality of life changes. The first of these notable changes was the laser-reflective panels that shrouded the myriad turrets dotting the warship's frame, and the critical systems (aside from the communications and sensor towers) that couldn't be mounted internally. With that reflective armour in place, the warship would find itself more than adequately protected from nimble strike fighters - should they manage to weave through the impressive and comprehensive point defence network. The second of those notable changes was the Carbon-Durasteel hull plating with the secondary layer of Turadium plating, which would ensure that the Starhawk III - Class Battleship would live up to - and eventually surpass - their predecessors legacy.

The rest of the changes were hidden behind armoured bulkheads and bright - clean curves that formed the vast majority of the warship's interior corridors. Warm and inviting lights were fitted throughout the vessel in an attempt to become the polar opposite of a standard Imperial starship. While many would consider it a foolish design choice - it was believed that the pseudo-ivory bulkheads would significantly improve morale among the personnel stationed aboard the battleship. However, that was mere speculation in the grand scheme of things, but one couldn't deny the positivity felt by staring at a blank, well-lit canvas. In addition to the interior spinal corridors appearing as the polar opposite of standard seen in most Imperial warships, a majority of the warship's systems were entirely automated; effectively cutting down on the required personnel and increasing the quality of life for those that resided aboard. With a majority of the warships systems governed by automation, the Starhawk II came with a central computer core - which permitted the installation of an artificial intelligence; which in turn would guide and direct their subservient systems at the Captain's behest.

Thus, with the impressive complement of weapons, defences, and internal systems the Starhawk III - Class Battleship was poised to become one of the most advanced pocket dreadnoughts to ever serve within the Alliance Navy - and the select clientele of the Republic Engineering Corporation.

 
Last edited by a moderator:

Runi Verin

Two pounds shy of a bomb.
Republic Engineering Republic Engineering

As much as I hate to pull up what is an otherwise exception submission over the sake of five meters, I've got to ask that you bump the 'hawk up to at least 3000m if you want the average hangar rating to equate 16 squadrons.

The alternative is to drop the count to 14 in line with the average rating of the 2500m we would currently round it down to.

Other than that, as I said, another fine example of a submission and the kind we've come to expect from you.
 
Prefactory Request:
  • Submission Name: Starhawk III - Class Battleship [ Model Three Starhawk. ]
  • Link to Submission: [ Click. ]
  • Reason for Pre-Factory Request: Updating the Formatting and Adding in New Canon Functionalities.

Moved to pre-factory per OP request.

Please remember to include a list of changes made when you tag a member of factory staff to move the submission to live judgement.
 
John Locke John Locke - Submission Modifications are complete.

Modification Summary:
Old Modification List:
  • Updated Formatting, and Template to match Factory 5.1.2 Standards.
  • Added Links to Primary Sources.
  • Updated Affiliation and Manufacturing Fields.
  • Updated Materials Field.
  • Updated Rating Values on the Manvuerability and Armament.
  • Updated Hangar Values to better represent new Information.
  • Updated Tractor Beam Functionality to better represent new Information.
  • Fleshed out Defences, Standard and Special Features.
 
Republic Engineering Republic Engineering I'll be your judge for this submission.

  • Affiliation: The Galactic Alliance.
    • Galactic Alliance Defence Force; Alliance Navy - Admiralty Authorization Required.
  • Model: Mark Three Starhawk - Class Battleship.
  • Production: Limited-scale Production.

Just to make sure I understand this correctly, how does the "Admiralty Authorization" request work to further limit the scope of this deployment from the entire faction for a "limited" production ship?

  • Shieldception - Multiple Layers within Layers of Deflector Shielding Inhibit the Capabilities of Individual Field Disruptors; Making Each Projected Layer Harder than the Previous One to Breach.

This is conceptually solid, though perhaps the wording might need a little tweaking? The word "inhibit" used in the sense of restraining or making something more difficult (and even possibly impossible) I think would be appropriate here, but another potential meaning of "inhibit" means to "prevent completely". Is there a way we can state this concept while explicitly giving opponents a little bit of room to possibly board this ship?
 
Gir Quee Gir Quee - As the Rank of Admiral requires the Permission of Faction Staff within the Galactic Alliance, they need to be "Authorized" to utilize this Ship in Open RolePlay Threads. So, it'll be limited to a small handful of writers, and "limited" even further by the Naval Structure of that faction.

As for the use of "Inhibit" - I'd wager the supplementary part of the sentence - "Making Each Projected Layer Harder than the Previous One to Breach." -would imply that the former definition of the word takes precedence over the secondary. With that said, it's not impossible to board this vessel - just extremely difficult.
 
Republic Engineering Republic Engineering

As the Rank of Admiral requires the Permission of Faction Staff within the Galactic Alliance, they need to be "Authorized" to utilize this Ship in Open RolePlay Threads. So, it'll be limited to a small handful of writers, and "limited" even further by the Naval Structure of that faction.

I'm not so sure about this, largely on the principle in that it seems to be based on internal faction rules (which are subject to change at any time). Additionally, it seems to me that there is some ambiguity here for a single admiral PC to employ an undisclosed amount of these in a single engagement. I personally don't see much of an issue with a PC admiral deploying a small number of these in a large engagement, but there's an obvious issue if a single admiral keeps up showing to the every engagement and spamming them in large numbers - it defeats the purpose of a "limited" production.

This is one of the few instances where I think a straight number might be more useful (something like "Up to three Starhawk III-class Battleships per PC admiral"). I'm sure that you can think of an alternate solution that could work to address this issue, of course.

As for the use of "Inhibit" - I'd wager the supplementary part of the sentence - "Making Each Projected Layer Harder than the Previous One to Breach." -would imply that the former definition of the word takes precedence over the secondary. With that said, it's not impossible to board this vessel - just extremely difficult.

That works for me, especially since you're being explicit here that it's not invulnerable.
 
Gir Quee Gir Quee - To be fair, any rule on this website is capable of being changed at any time, but the Site Staff is simply being nice by providing us with updates after the fact. While this doesn't have any bearing in regards to the submission, the point being raised does. With that being said, however, if things do change within that faction where they don't require permission for Admiral ranks - we'll likely be back at this again as I'll be making another modification to account for said changes. Especially since the Limited production rating has varying perceptions and concerns from One judge to another.

And when it comes to Naval Engagements on Chaos, production rating usually isn't really considered in how people structure or utilize their fleets outside the purview of the Codex unless it's Unique. Sadly, that's something we can't control without opening a huge can of worms, even if we go out of our way to say that this Rank only gets this - or that. People will write what they want to write - even when most Fleet Battles on Chaos are easily compared to, and erroneously mimick the Battles of Endor or Exogol in terms of scope. In addition to that, as most logistical infrastructure doesn't exist outside of a Faction's headcanon on Chaos - that very same Admiral could keep respawning their Starhawk if and when it's destroyed between Battles, which breaks the immersion and sense of realism from the RolePlay thread, but that wouldn't be in violation of the rules.

And if that Admiral shows up to a thread and spams these in large numbers - that's on them - as they'll undoubtedly reap what they sow from their opposition and their supposed allies/fellow faction members. lol

So, I don't think that's a very fair suggestion to make in gatekeeping my submission, especially since it more than complies with the current Factory Standards in regards to Limited production items.

Quoting for Posterity.
Limited (Only one small group of characters. IE: A Single Minor Faction, Company, or Group within a faction.)

To help curb the possibility of ambiguity in terms of numbers that can be deployed, the best and most sensical route forward that I can see - is adding Closed-Market to the submission - as that'll leave the Submitter of this submission, and the Faction Staff of the GA to act as a form of "quantity control" in the use of the Starhawk III outside Codex Fleet Submissions.
 
Republic Engineering Republic Engineering , how we've been regulating limited production ships with their affiliations has certainly been (and likely will continue to be) a topic of discussion.

It's perfectly valid to simply use "Closed Market" for this. However, with that said, as it accordance with the current production and affiliation guidelines, please remove "Galactic Alliance" from the affiliation. Alternatively, if you can find a different way to restrict usage within the GA, that would be fine.
 
Gir Quee Gir Quee - Yeah, I don't think you'll approve of any restrictions I've come up with since it's pretty clear that it's your way or the denial pit. So, in that vein, I've removed the faction affiliation(s) as well as the previously established restrictions that you believed were going to cause issues and replaced them with Closed Market.

If there are any other issues, please say so now, so that they may be amended.
 
Republic Engineering Republic Engineering , this is approved then.

For the record, there are multiple ways of getting a limited production sub made for use within a major faction, but it does have to have clear, unambiguous delineation of who can have access to it - keeping in mind that "limited" doesn't only apply to PCs, but NPCs (including NPC admirals in this case) as well. Things that tend to work well for limited production ships like this are specific fleets, specific commanders, or specific locations of a faction's territory. This has been fairly consistent not only with me as a judge, but with the current Factory Administrator as well (another example here).

As always, you're welcome to modify this submission at a future date if you have a different idea for affiliation.
 
Status
Not open for further replies.

Users who are viewing this thread

Top Bottom