Kaed

I suppose I'd be complaining about your lack of clarity about that in your original comment. If you recently fixed an issue, you should put that out in the thread so people know the issue is resolved, that their information is out of date, instead of just calling them wrong with no further details. It is indisputable that at one point the flash blind extension was not working properly, so in the future if you have corrected an issue someone pointed out in a suggestion, clarify that instead of expecting everyone to have read PRs and changelogs and know what you know. It saves this whole tedious conversation about 'but it's broken' 'no I fixed it idiot' from happening. I haven't played in over a week. It's possible that Burger hasn't been flashed in over week, especially if people are still under the impression that flashes are in a state of uselessness. In any case, if it does in fact work as you intended it now, I see no reason to change it further at this time.

Perhaps [mention]ParadoxSpace[/mention] should rephrase their opener to 'create an enhanced trait system, here is an example from polaris' so that there will be more potential receptivity here. Though it's a little laughable to expect that everyone would rather create an entire system from the ground up rather than picking apart someone else's work to get juicy titbits for their own.

Absolutely untrue. Run a watch and it's up to 10 seconds of a blind through a direct flash and 7 seconds with an AOE flash. You greatly underestimate the value of it. I have already come to you and explained that it does not last the extended time you claimed it does. Unless you have recently fixed it, you need to stop disregarding player feedback.

Invoking an unrelated server with a sour reputation to bolster your argument without really adding any substance? Geez, come on. Put in a little more effort if you don't like something. Adding additional character creation options isn't going to turn the station into a fetish pit. Frankly speaking, I sort of like the idea of a traits system because on a roleplaying-intended server, having more character customization is bueno. Why we'd want to 'keep things simple' when there is a whole array of potential mechanical complexities to add for flavour I can't fathom. I'm not entirely sure what that bit about not porting bay over is, though. I think I heard somewhere that a some devs were against porting content, but in an open source setting I'm not really sure why? Most ideas are stolen over from somewhere else anyway, even if we add our personal flair to things when we code them.

Fucking why To cut back on whining about no engine I guess.

Sure.

Sometimes game balance is more important than realism.

It's a much wanted change, which is in no way the same as much needed. It's just another further attempt by IAA players to give themselves more power over the crew. I'm more of the opinion that the role should be removed from the server entirely, but that's not relevant to this thread. I'm just here to express my displeasure with the idea.

That's some pretty broad generalizations there pal. The people who vote extended generally aren't relevant to this thread. I kind of like the idea of the round-controlling antagonists being whitelisted, myself.

It's incredibly frustrating that people continue to handwave illogical and inconsistently immoral regulations because 'they provide conflict' and hold up whitelisting as if it is a special shield that protects us from people being irresponsible idiots or assholes. This continued insistence that being whitelisted gives carte blanche for people to be trusted with all sorts of decisions is essentially turning a blind eye to potential abuse under the assumption that no one would actually do it and if they do it'll be handled on a case by case basis. It is just baffling to me to hear someone say they'd prefer that command staff didn't abuse this power but they'll trust that if we leave things the same there won't be any problems. The problems are already there. They happen. That is the entire reason I made this thread. And post-round stripping of whitelisting does 0 to help about you being cyborged for trumped up charges in the round it happens in. I also hear people in this thread sweep aside the moral and interstellar diplomatic consequences of being the only system in currently known space that treats cyborgification as not an execution with arguments ranging from 'it's just a game' to 'it makes this system speshul and unique'. You can't just have legalized atrocities exist in a vacuum. The only reason this law still exists as a blatant example of sophistry and is not being pressured by all their neighbors to fix it is that people are refusing to examine it because they think it 'provides some interesting roleplay'. Hell, unathi in particular have a reason to be vehemently opposed to being cyborged because many of them believe it destroys their soul, and it's about the most horrible thing you can do to them. There should be outrage from the Hegemony if they found out their migrated people are being cyborgified. But no one ever considers that, or the species or beliefs of the accused. I guess I can assume this is another example of 'the lore team can just eat shit' mentality that floats around here and there?

Let It fo, Fowl Anyway, it might be easier just to split the engineer slots in half and make two of them just engine setup engineers in the other two maintenance technicians/electricians

I'm sorry, I know it frustrates you that your security-bashing channel is getting D-listed, but... why would a private corporate research station have to enforce freedom of press regulations? There's no benefit to them to having their security team or command stuff blatantly mudraked, and it makes perfect sense for them to censor news articles posted only within the corporate station and views by employees they have jurisdiction over. The newscasters are owned by NT, if you are making the company look bad, it's going to get censored. Perhaps journalists need to find an inoffensive way to report issues or not directly take on security by passive aggressively claiming their corruption.

This is what was suggested for the Bridge and Command access; how come "having to ask for permission" would work for Medical but not for the Bridge? Is a CMO's authority over an IAA somehow greater than the Captain's? The IAA doesn't inspect the captain. =/ There's no office in the bridge that falls under their jurisdiction, unlike the argument made for basic departmental access.

It's not about the whitelist, it's about the position itself. Also, whitelists mean very little except that you filled out an application and managed to string some coherent sentences together. It doesn't mean you're trustworthy, necessarily. There are whitelisted people that I find trouble grasping how they became whitelisted. Especially since you only need to clear the whitelist once then you can play any role you want, even outside of what you applied to be.

I can get behind a lot of this, but I have a single concern here with this idea, and it involves medical. There is already kind a frustration with medical that people wander in without asking to come in or actually having a reason to be there, and since it's supposed to be a kind of sterile, private environment for patients, giving IAA free access to medical could possibly cause situations where they wander in and disturb the doctors by being a nosy bureaucrat without asking to be invited. So I'd say if we're going to give them basic department access, they still have to ask if the medical department can admit them before they walk in uninvited. If they need to, and the department actually needs to be investigated, they can escalate the issue.

I don't see why this responsibility shouldn't be passed over to security, since they're the ones that handle the on-station regulation enforcement. The bureaucratic division doesn't need more reasons to feel inflated self worth. We already have IAA who feel they are allowed to give orders to crew members than have them charged with 'failure to execute an order' when they ignore them. They also aren't CCIAs, they don't have the same powers or responsibilities.

Also fixable. So this isn't even something that you worked hard for after all. It's just an accident. Hmmm.

I can very easily add security records to the IAA office. They also have, behind each of their desks, A requests console, which I believe is capable of making announcements they're just not loud 'priority announcements' that make a big DING sound. These aren't hard changes to make, because these functions don't require them to be on the bridge. In any case, if you want to move this to policy, you can. That doesn't work. There is a significant sense of 'why does it matter' to a lot of people who actually have the authority to shoo away an IAA who is getting a little bigheaded, and for players who don't, the IAA tends to snootily ignore them entirely. They benefit from this access only because their office lacks certain facilities they occassionally need.

Clearly, someone needed to step up to the plate and lobby for an alternative viewpoint, then. Hello! Anyway, I get it. You don't like it. Thoughts noted. I want to hear from other people than the exact person whose behaviour incited this thread, and there's no need for this to turn into a bickering contest between us.

Make a radio announcement. Walk to departments yourself and introduce yourself to them. Be a person, instead of relying on large messages to attract people to your dark office cave. You don't need an announcement to be noticed. You can advise the captain over the radio, or if you need to talk in person, ask to come in. Learn to mingle with the crew instead of being feeling obligated to special privilege. Also, 'worked hard to get this access'? Sorry, what? You were given it from the start and didn't have to work for anything. It would also be nice to hear from some people who don't play IAAs and have an immediate prebuilt bias to keeping their lofty status quo.

I see a number of IAAs wandering into the command area, sitting in the bridge, making announcements using the command computers. At the end of the round, many they feel obligated to the right the shuttle to slip into the command bridge and take a seat, sometimes even when we have a full head roster and there isn't room. Sometimes, they even get mouthy with other command members. I feel that this is a sign that some of them are starting to get an inflated sense of their own importance and need to be reigned in a bit. They aren't command members. There's no reason they should be allowed to walk in and out of the command and bridge areas at will, or utilized command-locked NT computer functions. There is no reason they shouldn't have to ask to come in like the other non-command crew members. Asked why they are on the bridge, their answer is inevitably just 'I have access so I'm allowed here'. Their duties lie entirely outside the command sectors and with the crew at large, and I die a little inside every time I see them making a station-wide 'priority announcement' about their bureaucratic duties. Now, this isn't to say they have no reason to have access to the command CHANNEL via radio. There are plenty of valid reasons for them to talk to heads directly. So I'm gauging interest in this change, because I'd be happy to make the PR myself.

if there is a problem like this there are better ways to encourage them to work together than silently doing this and expecting the interdepartmental animosity to evaporate without warning over a week.

Haven't you heard? Mining is science's bitch. If you take away their dependency on science, then they might start thinking things about independence! In all seriousness, they should be encouraged to bring back some materials to science before they get anything particularly good.

What if I put this one here with special Poncho designs for my head of personnel character, and add the generic one to the load out?

And I'm agreeing with you.