Conversation
|
So, what I personally suggest is giving the IAA Diamond and the NTR emerald, a magistrate on station is quite rare and this would also be quite confusing, why would the spacelaw person do contracts instead of the person specifically send for paperwork? And the IAA should have the power to suggest contact changes and see crew contracts. And ERT should probably have sapphire and the ERT leader still have emerald Quick second question, would there also be a CC contract tier for payment? |
|
IAA can and should be able to see them, like all command and CC members can, but can not change them. The reason that I decided that way is that the amount of authority they have on the station. I was told in Discord that the IAA has no real power to enforce anything and is more of a CC lawyer. Additionally, the reason that the NRT does not have an emerald ID is that they should go to the captain for immediate action. The Captain or HoP should always have final say on on-station matters. If the NTR does not like that, they can send a report to CC to be approved automatically after some amount of time, but they should not approve it themselves. The reason the magistrate gets emerald is that they have the authority to uphold spacelaw and need access to the systems to do so. The magistrate should always have final say on spacelaw matters. I will look into the ERT suggestion tho I can make a CC contract, but I figured a command contract would work for simplicity, since they would probably be close enough. |
Yeah uh... I might've forgotten to read the CC part about they'll be able to read contracts, but a CC contract would be great because CC VIPs obviously need more pay than those station people! |
Added cargo pay stuff and some clarity on stuff
corresp0nd
left a comment
There was a problem hiding this comment.
this is really cute and seems like a lot of fun, plus it pretty much perfectly fits into the type of world we're looking to try and communicate. i honestly don't have a lot to say about it, though when you start implementing some things you might run into some nitpicks from me. i would work on the security ticket and scanner stuff later, though. i think there's a couple other folks who have their own takes on the direction security should go and it's probably good to talk with them about stuff like this
This doc is to expand on some of the ideas of Unions and Scrip docs and overhaul some current systems to pull them into a more unified vision before attempting implementation.
Let the class disparity begin.