Departmental operating procedure proposal#293
Conversation
This is to be changed
github-actions
Bot
added
Design
|
fucking love this idea man, hope it gets accepted |
murphyneko
left a comment
murphyneko
left a comment
There was a problem hiding this comment.
I find this proposal a bit... interesting? It doesn't really go into detail about any specific details. However, it does propose some interesting ideas, like making guidebooks that read like actual guidebooks IC and aren't links to the OOC guidebook.
|
|
||
| ## Core Idea | ||
|
|
||
| My intention with a DOP is to encourage Roleplay but not to enforce it with server rules, this instead is a set of in-character books and guidebook entries that will push players into a more RP centric enviorment. This proposal is more focused towards MRP servers but these guidelines can still be found and used within LRP servers. |
There was a problem hiding this comment.
According to this, DOP is basically a flavor document without anything being enforced. Isn't this just an attempt in official lore of sorts?
There was a problem hiding this comment.
It largely is just a lore thing at this point. I would like for it to be more like the original sop in terms of needing to be followed but I am doubtful that would be approved.
| * Flavor Text | ||
| - Nanotrasen themed guides that offer more fun than actual advice, think of things like "Interogation 101" which will feature an interogation guide complete with responses to certain answers, pretty much useless in terms of advice but is a fun bit of lore that is distrubted to security teams across Nanotrasen stations | ||
| * Guidelines | ||
| - Think of these as the original SOP, a set of straight forward points and guides to explain how a department is to be run, but do not limit roleplay and instead encourage more. With things like medical evaluations and alert procedures. These could be appended with 'guideline' or just left as is such as "Alert Procedure" instead of "Alert Procedure Guidelines". |
There was a problem hiding this comment.
Same as above. Guidelines, but not enforced? Then which mechanic prevents people from ignoring it?
There was a problem hiding this comment.
I don't believe anything prevents people from ignoring it. In it's current form this is largely a self-policed "standarized" roleplay.
This is much like the last issue where I would like enforcment of some guidelinese but I feel it would have to be limited to MRP or jobs like command and sec (which I am trying to avoid as I don't enjoy an operating procedure that only covers two departments).
I will try to mention MRP ammendments or something similar to certain guidelines
| style idG fill:#5ce65c,stroke:#333,stroke-width:4px | ||
| idCC1-->idC1[Captain]; | ||
| idC1-->idHOP1[Head Of Personnel]; | ||
| idHOP1-->idG1[All head of staff are equal below HOP]; |
There was a problem hiding this comment.
This is conflicting with roundstart briefing. According to it, all heads respond to captain directly.
There was a problem hiding this comment.
That is true. I will have to fix that.
I am fairly certain the old SOP also made HOP the second in command.
I will work something out
|
|
||
| ### Service | ||
|
|
||
| Service will not have it's own Operating Procedure and will instead have guidelines and more lore focused text for each job I.E. Chef, Janitor, and Barkeep. |
There was a problem hiding this comment.
I mean, if you want it to be so, then so be it, but I find it rather strange that the most roleplay-focused department does not get their procedures that are, well, roleplay recommendations.
There was a problem hiding this comment.
That is a good point. I will work on something for service.
It is essentially me throwing the kitchen sink at a wall and hoping something sticks. I think specific details would be hard to get into without just fully implementing a DOP example (which I am now planning to do). I do enjoy the idea of IC guidebooks that encourage RP in one way or another. I will respond to all the issues raised and make adjustments and changes where needed. |
|
I am now working on a major rewrite of this that will be a lot more specific in how best to pull off a DOP |
|
Closing this as well. I don't play the game enough now to warrant me working on this. |
3 participants
This is my attempt at adding back a "SOP" with my own idea. The "DOP"! Or the "Departmental Operating Procedure"
Do note this is a bit more than just a name change, my intention with this is create a simple operating procedure within each department that will encourage roleplay and more believable in character interactions. This is more targeted towards MRP servers but it also has its uses on LRP.
I plan for this to incorporate actual in character guidelines and handbooks much like an actual workplace would. Things like "Interogation 101", or "Chain of Command".
My example
I think anyone who attempts this will have numerous ways of trying to do this. The example I integrated into the design doc is what I am planning on working on. I hope that once this doc is approved, if it is, I will go headfirst into writing handbooks and guides, and lore pieces that will fit in with this DOP.
I also noticed most docs don't feature an example like I had and the reason I did this was to give a good idea of what this would look like and my intentions with this proposal.
Thank you,