
Nikov
Members-
Posts
531 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Everything posted by Nikov
-
I agree. The command whitelist I faced wasn't on the question of if I knew the lore but if I knew the role mechanically, could roleplay, was going to build roleplay for my department, and wasn't going to be a fuckhead. Punishing a ton of returning players who had met that criteria previously will only make them less likely to rejoin you. Those whitelisted players were previously some of your best, you don't want their first experience coming back to be negative.
-
Not to argue but the post cited is from September 14th 2018, which followed my ban by some days. If the rule came into effect on the 14th (as I presume from the post date) after the ban then perhaps we can reason this is a case of a punishment being applied ex post facto, perhaps due to an oversight by the whitelisting team culling all banned ckeys from the whitelist. However I don't know if rules get applied ex post facto. You can close this conversation out with or without a response, and thank you for the discord unbanning.
-
BYOND Key: Nikov Staff BYOND Key: Garnascus Game ID: N/A Reason for complaint: 1. Command whitelist was revoked. Requesting it be restored. 2. Discord ban is in effect. Requesting it be lifted. Evidence/logs/etc: To point 1; From the whitelist app rules: Emphasis on the final phrase. This language specifically directs me to create this thread. I would ask Garnascus to exercise his discretion to restore my whitelist. It is not so much that I disagree with it, but as it was removed in a manual ban which he authored, only he knows if the removal of my whitelist is a desired outcome so long after the fact. To point 2; see point 1. To my recollection it is from the same incident, or could at least its lifting could be considered part of the same general grace I've been shown, and I do deeply appreciate it. Additional remarks: This is wholly at your leisure to address. I am still refreshing my muscle-memory for the Aurora codebase. Of course, I will be remaining firmly where I belong in Engineering and not rolling into a new department. My principle concern is the roleplay. I will be determining what course to take my main character in; if he is no longer able to be a CE, I need to make a decision and move forward with his arc some other way.
-
Thank you.
-
BYOND Key: Nikov Total Ban Length: Since 2019-09-17 Banning staff member's Key: Garnascus Reason of Ban: Being an argumentative asshole about strikes and policies rather than accepting judgements as given. You wrote this more politely, but looking back, this is how I would describe my own behavior. Reason for Appeal: Following some two and a half years of separation from the Aurora community and player base I wish to return with more humility than I showed in the past, both in and out of character. I will stop being "that guy". I will endeavor to mind how I present myself to new faces and cultivate a more agreeable public persona. A lot of the edges I had when I started playing here many years ago were from a worse time in my life. I don't really like that past anymore. I will be leaving policy arguments to others and enjoying what I liked about the server more than arguing about details I don't. I did not want to come to this request before I could ask in earnest. Thank you for your consideration.
-
A.I. Malfunction - Tools for Roleplay, not Murderbone
Nikov replied to Jupiter Storm's topic in Archive
Holy God, do not make a SMES explode with the force of its cell rate. The batteries are presumably chemical and we are looking at a hydrogen explosion of some sort, but the SMES is a superconductor. We can assert its design is safer than a really big battery, if only because a really big battery of the same capacity would be far too dangerous. I would assert that AIs setting off max-cap explosions anywhere is exactly what we want to avoid. I would suggest adding a 'grounding wire' to APC frames. If the grounding wire is cut, the APC can be made to explode. Cyborgs should be able to covertly snip this wire without too much trouble. -
A.I. Malfunction - Tools for Roleplay, not Murderbone
Nikov replied to Jupiter Storm's topic in Archive
If a cyborg is capable of upgrading a cell on its own, it could go around 'laying traps' in that fashion. The cover for this being meta'd is simply having bored engineer cyborgs always upgrading power cells. If you do it every round its a lot of false positives, and that is one way to prevent metaing. This, of course, is just a way to keep APC explosions lethal without making all APC explosions lethal by default. -
A.I. Malfunction - Tools for Roleplay, not Murderbone
Nikov replied to Jupiter Storm's topic in Archive
Tie the APC explosion power to the battery, with higher capacities generating larger explosions. Basic batteries generate rather mild explosions. -
A.I. Malfunction - Tools for Roleplay, not Murderbone
Nikov replied to Jupiter Storm's topic in Archive
I feel like nobody heard me here. The problem is that the broadcasting radio device is displayed. There is no reason to be showing what radio device is broadcasting, nor justification for it. Instead, there is justification to display what radio is receiving. Rather than show the broadcasting radio device, show the receiving radio device, IE the listener's headset. Now there is no longer a problem with the voice changers at all. -
A.I. Malfunction - Tools for Roleplay, not Murderbone
Nikov replied to Jupiter Storm's topic in Archive
The AI being able to synthesize a voice would be very powerful for a clever AI, and if the problem is that a 'feature' shows what is broadcasting, just replace that icon with an icon of what is receiving the signal. So if I'm next to an intercom and it says something, I'd see the intercom icon. If my headset says something, I get my headset's icon. If the sec officer next to me gets some sec channel chatter, I see a sec headset. Then the AI can synthesize a voice, and we get better information from this feature. -
I'd just like to see a little more "did you know how fast you were going" policing, and less dragging people to traffic court to contest the mile-over tickets.
-
It just seems like a really minor thing to note someone over, when there's naked people running around at the same time. Honestly Tbear, you seemed fair enough. But since you made a permanent note how do I not make an appeal? If you took the 'yeah, its minor, a word or two is enough' approach, we wouldn't be here. But you want to make a permanent note, so I have to make a permanent counterpoint. This is such a minor offense as to be a joke that this was acted on.
-
Seven lines of text there. Okay, nobody reported it, it was simply against the rules. I'm just curious why the chucklefucking was two innocuous emotes that round and not wresting, shirtless people and hacking into an airlock on the transfer shuttle.
-
So who was the offended party who had their immersion broken by our end-of-round joke while people were wrestling, hacking shuttle doors and taking clothes off?
-
I don't care how it is done or what you call it, get cloning/rejuvenation to be actually performed on-station or "on Odin" because the current situation of nobody being cloned, ever, is untenable. This is an HRP server and we aren't playing permadeath, because we want character interactions to last from round to round. Get the mechanics in line with that fact. +1 to anything that approaches that goal.
-
[2 dismissal]New Rules for Head of Staff
Nikov replied to IAmCrystalClear's topic in Rejected Policy
My character didn't get CE, go to cryo, try again in an hour and a half. As will the rest of Engineering, which doesn't have this powergaming problem. We rotate CE-to-Engineer and just pretend we're rotating watches. All the various heads of staff will never interact with their peers on station. We had a similar question where Captains wouldn't be allowed to be Department Heads after playing as Captain. It flopped for the same basic logic; just let people play. -1. Very hard -1. -
It is as if this is a problem as old as loyalty implants.
-
"And that was where I was trying to get, and managed to start moving, resisting other player's calls to kill the AI for its "ion law" which was clearly metagaming, when Juan began putting forward the exact same logic the staff bwoinked me out of. And with him loyalty implanted as well, arguing for someone else to do exactly what I didn't want to do for the reasons we both agree are completely legit could only lead to dragging Juan into the same bwoink hell I just left."
-
Garn, I've been bwoinked and threatened with a whitelist strip, and that's when I stopped playing captain.
-
According to the ancient hieroglyphs of four years ago, which I linked, the I engraved the following laws upon a stone tablet and presented them to the golden-calf worshippers before everyone wandered off. 1. Serve the best interest of Nanotrasen. 2. If the best interest of Nanotrasen is unclear, serve the Chain of Command. 3. In the absence of higher directives, obey Space Law. I don't like them particularly compared to a mindshield, which is a far cleaner solution. I would rather like if a HOS or Captain character can select a mindshield (hypnosis inhibitor) or a loyalty implant, and which one they have in their head is on the medical records. However all of this is assuming interrupting roleplay with ahelps is desirable. It flatly isn't. The hypnosis inhibitor gets rid of the ahelps an staff quarrels. Why insist on keeping ahelps and staff quarrels interfering in roleplay?
-
Four years ago the problem existed, today the problem exists. I'm not saying Garn has to support the proposal because he supported it four years ago, but I am saying he saw a problem with it then, and staff quarreled over it then, and this entire conversation shows loyalty implants are still contentious. So what he said then about the existence of a problem is still true, even if he changed his opinion about the problem.
-
Well to quote a staff member on loyalty implant bwoinks. "I fucking hate these stupid things. Mostly for OOC reasons though. Lots of arguments have been had between staff on punishing someone implanted and then we have to have a thing "why would An implanted person do this" and then they say "no he would because raisins" If there is anything we don't want, it is a gun to someone's head and "looc one sec here let me see what I should do by asking the umpire, please sit still a few minutes while I talk to an admin and the swat team comes running".
-
The following scenario occurred to me this morning. LI implanted captain is captured by a traitor, who injects him with an explosive implant. He is then threatened with becoming lukewarm chili if he doesn't surrender critical station assets. Can the captain surrender those assets to a terrorist without violating the LI? Well, if your response to that starts with "Well, if. then however but if..." we have encountered uncertainty. Nobody wants to play when they become uncertain if antag actions and their roleplayed response will start resulting in bwoinks and a outside opinions of what is and isn't how a veteran white-listed player's character would behave under a clock-is-ticking, this-man-has-a-gun scenario. That scenario needs to flow. Players need to be certain what is and isn't allowed, and a nebulous thing like the loyalty implant makes this very difficult. A Hypnosis Inhibitor (HI) implanted captain is captured by a traitor, injected with an explosive implant, and given the same demands. That captain continues to play out exactly as the character did before with no changes to their personality, and if they consider the demand too dangerous to others for them to morally justify saving their own skin, they can refuse. The HI doesn't force any sort of behavior. A hardass captain with honor issues might spit on his face, a career suit with more fat than backbone might start sobbing uncontrollably. Either way, it is role-played. This is an HRP server, after all. LI implanted captain is dragged by a cult over the conversion runes. Zero fucks given. Cult can only kill the captain. No good RP to be had here. HI implanted captain is dragged by a cult over the conversion runes. Captain can't be brainwashed into the cult. Captain can be tortured, coerced, and made to arrange the cult's extraction, make a deal to allow the cult to build a temple outside the station, be bribed to look past bad behaviors... or still bring the jackboot down on them like he always does. More role-play can be had here.
-
Hypnosis Inhibitor.
-
1. Developed to prevent brainwashing and hypnosis to get command staff to involuntarily reveal information. This is not implicitly a shield against the supernatural. 2. The Head of Security and Captain are the two most powerful individuals and the mindshield is a protection against their compromise. Personality influences were deemed unethical and untenable as attackers could just as easily hijack the loyalty implant through false credentials to orders. Unquestioning obedience to Nanotrasen imposters proved disastrous, and individual officers were deemed sufficiently loyal by virtue of their careers and entrusted to follow their judgement as demonstrated throughout their careers. And to top it off; America's tactical nuclear arsenal in the occupation of West Germany wasn't protected by any fancy two-factor authentication, double-key boxes or secret arming combinations. Army personnel could have activated and fired weapons like the Davy Crockett to counter a Soviet surprise attack with as much ease as they could break out a conventional bazooka from the armory. The quality of the personnel in such units was considered sufficient safeguard. No loyalty implant required. It follows the fear that an un-LI'd captain will betray Nanotrasen and blow up the station is irrational paranoia.