Discovery Gaming Community
SRP Request: INS-Klaxon - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Rules & Requests (https://discoverygc.com/forums/forumdisplay.php?fid=6)
+--- Forum: Player Requests (https://discoverygc.com/forums/forumdisplay.php?fid=244)
+---- Forum: Special Roleplay Requests (https://discoverygc.com/forums/forumdisplay.php?fid=45)
+----- Forum: Approved Special Roleplay Requests (https://discoverygc.com/forums/forumdisplay.php?fid=403)
+----- Thread: SRP Request: INS-Klaxon (/showthread.php?tid=197937)



SRP Request: INS-Klaxon - Petitioner - 07-19-2023

1. Forum name of the owner:
@Petitioner

2. What exactly are you requesting?
- Rename of ship (currently ingame as LNS-Cascadia since I can't continue the Klaxon's roleplay in any form without this request) to INS-Klaxon
- SRP ID named Battleship Klaxon with the same lines as the current Insurgency ID
- Insurgent IFF
- Full red rephack to all Liberty and Bretonia lawfuls
- Teleport to whatever Insurgent base I can buy Insurgency BS turrets on.
- Tech core set to 85% to represent the difficulty of maintaining it with the Insurgency's crumbling supply lines.
- Battleship Harmony's red engines.

3. Exact name, identification and affiliation of the character:
Currently LNS-Cascadia, for gameplay reasons.
If the request is granted, the name will be INS-Klaxon with an SRP ID and an Insurgent IFF.

4. Why is this request necessary for the continuation of this character's roleplay?
The Insurgent ID cannot use the Overlord. The Klaxon is an Overlord dreadnought that was part of the original battle between Harmony+LSF vs LN, on the side of Harmony, and has since then been unable to continue its roleplay as I've never been a member of Harmony or the Insurgent player factions.

5. What short-term and long-term goals are you planning to achieve on this character?
I want to continue the story of the battleship and its crew, exploring the logistics of maintaining a battleship without a military-industrial complex fueling its supply lines. The crew of the Klaxon is thoroughly convinced that the Liberty Navy is either nomad infested or corrupt to the core to the point that they're willing to throw entire battlegroups under the bus for no apparent reason, and as the Insurgency crumbles they intend to continue the fight somehow once they're able to secure resupply and maintenance for the Klaxon's advanced technical equipment.

6. Provide links to the relevant forum roleplay.
1) https://discoverygc.com/forums/showthread.php?tid=196914&highlight=Klaxon
2) https://discoverygc.com/forums/showthread.php?tid=139923&highlight=Klaxon
3) https://discoverygc.com/forums/showthread.php?tid=141935&highlight=Klaxon
4) https://discoverygc.com/forums/showthread.php?tid=141515&highlight=Klaxon
5) https://discoverygc.com/forums/showthread.php?tid=141519&highlight=Klaxon
6) https://discoverygc.com/forums/showthread.php?tid=141517&highlight=Klaxon

7. Provide a cliffnote/summary for the links provided above.
1) Ship info thread for the Klaxon.
2) Outreach to BAF during the Gallic War to request a Bretonian missile turret.
3) Message from Admiral Knight after the initial conflict outside West Point between the Liberty government forces (where the Klaxon was present and sided with Harmony, turning its guns onto the [LN]).
4) Commander Howe of the Klaxon reaching out to LSF director Eva Adenauer trying to coordinate resupply and further anti-Navy operations.
5) The Navy identifies the Klaxon as a rogue vessel to be destroyed.
6) Another instance of the above.

8. How long has this character been building its backstory?
Since 2016.

9. If you feel that you would like to provide us with character references, specify whom.
@Kauket, @Reeves, and former admins who granted my only previous SRP (for the ship Unacceptable.Behavior which is no longer active) can attest to my dedication to quality roleplay.


RE: SRP Request: INS-Klaxon - Connor - 08-30-2023

Approved


SRP Change: INS-Klaxon - Petitioner - 12-20-2023

1. Exact name of the character:
INS-Klaxon

2. Link to the request to be amended:

3. What exactly do you want changed?
I would like an IFF change to Bundschuh, along with all the expected rephacks. I also need, of course, some ID changes.

Currently, the ID is literally just the old Insurgent ID with some find-and-replacing done. It reads as follows:


I would like the new ID to be this:

In the case of the Bundschuh ID receiving any changes in the future, I would also like them to apply to the Klaxon's ID -- basically, I am requesting a Bundschuh ID, but with the added ability to attack Liberty forces anywhere. I do not intend to abuse this in any way, and I do not see the Klaxon going anywhere it is likely to encounter the evil enforcers of the illegitimate M*nhattanite government Liberty's forces, but as essentially an AWACS/EW/support ship, being sent on recon missions outside of Rheinland's space is a possibility, and on the off-chance that I run into Liberty forces there, I think it only makes sense that the personnel aboard would try to take their revenge on those who took everything from them.

Lastly, I would like a name change from INS-Klaxon to (=)BFS-Klaxon.

4. Why are these changes necessary?
With its current ID, the Klaxon is confined to Liberty -- somewhere it hasn't been anywhere near since the Fall of Veracruz -- and its practical gameplay (beyond saying words at people, which anyone can already do anywhere) would be limited to acting like the Insurgency still exists, basing off of Fontana and Junker bases. This makes no sense, as everyone on those bases would want to see any remaining Insurgent "loyalists" thrown out an airlock.

As for why the Klaxon sought refuge with the Bundschuh in particular, Erich Klugmann is a famous (or infamous) man among anyone who paid attention to Rheinland politics in the past twenty years. Howe (the captain of the Klaxon) is an educated man, and one who fundamentally believes in human decency despite all he has been through, explaining why he reached out to Klugmann. The crew held a vote and tenuously agreed to use the Klaxon's jump drive to move to Rheinland, essentially throwing themselves at the Bundschuh's mercy.

Unfortunately, the unannounced three-year timeskip sort of threw a wrench in my original plan of seeking out potential allies in the Order (who would actually have the resources necessary to properly maintain a dreadnought) or elsewhere, and so given that circumstance, the direction the roleplay has taken is the most logical one in my view.

All that being said, at this point, I cannot progress the Klaxon's story without reflecting its Bundschuh affiliations. The mood aboard the ship -- the worldbuilding of which has involved many other people at this point -- is now entirely defined by the romantic emotional and ideological clashes of the Klaxon's history of unwittingly participating in antidemocratic actions (the Insurgency overthrowing the Commonwealth's civilian government), the loss of their home, and their desire to genuinely fight for freedom and democracy in Sirius. The requested changes are the only way that this story can possibly continue to play out ingame in accordance with the roleplay which has already happened.

5. Provide possible links to the relevant forum roleplay.
To: Insurgency Captains -- the Corsair company "Deterrence" offers all Insurgent captains and crews a very suspicious out from their fate. Posts 12, 13, and 16 include Howe's communications with the Deterrence representative.

Military Democracy -- The story of what has happened aboard the ship itself. Howe institutes a unique consensus-based system of voting aboard the ship in the hopes that that even if democracy dies in Liberty, it lives aboard the Klaxon. The peculiarities of this democratic system foreshadow the deep internal clashes between practicality and ideology that will eventually define the overall vibe of the Klaxon's crew. Posts 2 thru 10 detail the crew's rejection of the Cretan offer of asylum.
Military Democracy as a roleplay thread is an experimental approach to storywriting on Discovery, wherein I permit anyone and everyone in the community to act as a member of the Klaxon's crew and vote on the direction the story takes. In this way, I have attempted to involve the entire community in this story, even if they don't want to invest themselves in it greatly over time -- and as you can see, various people have participated, and their votes have impacted the direction the Klaxon took. I intend to continue with this, as I believe allowing the community input into the most critical junctures of the Klaxon's story is something unique among SRPs in the past. In a way, it also makes the entire story more "meta"; using real democracy to simulate in-world democracy, and allowing both the good and bad parts of democracy to truly make themselves known and visible via however the Klaxon's storyline plays out.

History Repeats -- Howe personally reaches out to Klugmann in a desperate attempt that, even if Klugmann can't help directly, he can at least forward them to somebody who can. Klugmann offers the Klaxon safe harbor, including food, water, and oxygen (commodities which are desperately low aboard the ship at this point) in exchange for Howe's insider perspective of what the hell the Insurgency was even fighting for.

Military Democracy -- Posts 11 thru 14 detail the vote to resupply with the Bundschuh.

Survey Commission -- Howe reaches out to the Starfliers, known for their political neutrality, to commission survey coordinates for the Klaxon's jump to Rheinland. To his pleasant surprise, the commission is free -- and the Klaxon has just enough fuel to make the jump.

Military Democracy -- Posts 15 thru 23 recap the situation the Klaxon has been in for the past three years, and detail the vote to join forces with the Platform.

Platform Recruitment -- Post 6 is Howe's application for himself and on behalf of the battleship's crew. Post 7 is the man, the myth, the legendary Kloog himself welcoming these seasoned revolutionaries into the fold.



RE: SRP Change: INS-Klaxon - Wildkins - 02-14-2024

Approved, all changes should take effect by next restart