Jump to content

StealthCT

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by StealthCT

  1. These are all excellent points, thank you! I especially like @nokko's observations on "player marriage" and its relation to the wider game and other systems. At the end of the day, "does this improve the synergy and operation of the station as a whole?" - likely not. My proposal of these mechanic changes was aiming to tie up what seems to be a partially implemented feature (as per this code from @Fox McCloud). Whilst I'm a big fan of mechanic improvements and micro-objectives within the station (especially if they may lead to some sort of persistent reward that suitably reflects the challenge overcome), I can't dispute that the mechanic we're improving here is one that doesn't contribute to the working of the station, and this is important. If there was any way in which player marriage did contribute to the station, this might be a different story. Right now I don't see that, so I concede on the idea of introducing a mechanic around this. What I might suggest to help those simply wanting to point to their ring for character backstory (long lost partner, etc.) would be fixing up names & descriptions, and offering these in loadout for that simple purpose. That at least covers the separate goal of giving these items purpose and meaning (when they are chosen to be used).
  2. And to clarify the purpose of this feature request, in as little detail as possible: Blessed rings already exist in ParadiseStation, but are unfinished. This finishes them with descriptions and properties, and the Chaplain's ability to bless them. Within session RP, some players have desired persistence of aspects of their RP. Adding wedding rings to CUI loadout helps solidify that side of RP for involved players, and adds purpose behind having blessed rings to begin with. Automating CUI (based on above strict conditions to reduce abuse and create a sense of objective fulfillment) aims to put the onus of achieving this objective on the RPing players, and removing any and all requirement for admins to have to be pro-actively involved in wedding ring CUI management (outside of removals as normal).
  3. Addressing some of the excellent points raised in Discord on this idea: So that idea could be up for debate! I like the idea of botched weddings, and more the reason to reattempt them. Think of cartoons - persistence is rarely granted, and only with certain conditions met. If the world got blown up but exists in the next episode, that shit never happened. Also, significantly simplifies implementation and attempts to counter any abuse potential. Fair, but this keeps the implementation of CUIs and the potential for abuse to a minimum. Also, whilst polyamory isn't outlawed, marriage in law often struggles to implement this cleanly. A space station is no exception. That's why I'd like any implementation to be minimalistic as possible. Blessed rings already exist in ParadiseStation, but are unfinished. This aims to finish them in a minimalistic approach, with the additional end goal of "having a ring in your loadout", as desired by some prevalent station RPers (and without negates any meaning of having these items in the game in the first place) The SOP is already loosely defined, but the desire behind mechanic is to introduce a practical objective to that session: Get in Get married Get out alive despite how simple this is in concept, weddings, and space station shifts, always have hitches. Giving players something to achieve to solidify their partnership adds to the fulfilment and enjoyment of that in RP. And the purpose of this proposal is to provide players with what's been asked about - CUI wedding rings. Those limited objectives are likely the bare minimum to allow for generation of CUIs of a practical session wedding, to avoid abuse/misuse. as @Chapitito points out, it also adds to the mechanic set of what Chaplain's can do. Weddings have always been RPable - this proposal isn't about that. It's about covering what RPers have asked for - having that signifying item (the ring), validating your achievement making it through a session successfully, including getting married, and pointing to that saying "look, I've been to hell and back for this person". Not everyone on this station would avail of this opportunity, but for those who play for this RP - this might provide them with a fun, and meaningful objective to do once on a session. After all - not all features implemented are for the sole benefit of all station crew. This is for those players who desire more mechanics surrounding their RP.
  4. Weddings have always been possible onboard the NSS Cyberiad, however I've noted that many would like a more concrete way of representing their marriage (post-wedding) in-session, for RP opportunities and station drama. An admirable goal not without caveats or considerations. This thread aims to be a feature suggestion to implement this, and facilitate discussion on how ParadiseStation members would like to see this implemented. Current problems Blessed rings are only partly implemented, and do not currently signify any meaning There currently isn't any (automatic) way of persisting these rings post-session Chaplains (AFAICT) have no mechanic involvement in blessing rings MVP scenario outline example Two characters wish to get married, and start a session with each other's ring of choice (perhaps with a preferred chaplain to officiate) The couple (and the guests) make it to the ceremony unharmed The chaplain successfully makes it through the ceremony opening, outlined in "Chaplain's Guide to Marriage" runbook, part I Chaplain takes each ring, and "blesses" it against the other partner, returning the rings to same partner Vows are exchanged ("I give this ring", etc.), giving the ring to the other partner Chaplain pronounces the marriage official, celebrations ensue, and the after-party held in Cargo's "break room" follows Both marriage partners finish the session alive, in possession of their ring, and with continued commitment to each other through time and space Post-session processing adds the ring to their respective loadouts via the CUI implementation In order to implement this with minimal complexity, hands-off admin approach, and tackling abuse potential, I've a few proposal ideas to cover this: Blessed rings implementation Blessed rings as implemented by @Fox McCloud gain a few additional properties: 'blessed_by' (for admin trail), 'bearer' (who should wear it), 'partner' (who the ring signifies commitment to), and have more descriptive text (similar to what I outlined here, with templating) Chaplain's bless ability (or additional spell) gains the ability to transmorgify rings, applying these properties. (to combat rogue Chaplains) Chaplains cannot target themselves for 'bearer' or 'partner' properties (cannot officiate their own wedding) Persistence implementation During round post-processing, any blessed rings that exist in the session are checked. If the ring is in the possession of (or in the glove slot of) the same player as 'bearer', a custom item of the same (base) type with flattened 'name' and 'desc' is added to that player's CUI loadout. (to combat rogue Chaplains) both ring pairs need to exist with this rule at the end of the session to be processed for automated CUI. (to combat polygamy - Space Law) existing wedding ring CUIs are replaced by presence of a new blessed ring. Try explaining that one to your previous spouse. Round summary includes any successful (or botched) weddings. Cue wedding MIDI, I dunno, have fun :D I'm interested in alternative takes or implementation ideas, especially around the concern of automated CUI implementation. My desire behind this (if considered) is to allow relatively unknown or less prominent players to RP marriage on this station, and reduce the hands-on approach admins would need to take in the current state of affairs.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use