Kyet

Host & Head of Staff
  • Content Count

    1592
  • Joined

  • Last visited

  • Days Won

    23

Kyet last won the day on November 11

Kyet had the most liked content!

Community Reputation

470 Excellent

7 Followers

About Kyet

  • Other groups Head of Staff,
    InGame Verified
  • Rank
    Nerd

Personal Information

  • Byond Account
    kyet

Recent Profile Visitors

2257 profile views
  1. Plasmamen did not RP more when their karma price was 100. Plasmamen did not suffer a reduction in RP levels when their karma price was reduced. Based on those facts, I don't think that changing the karma price of Vox, or other races, will affect the RP level of Vox players. I'm skeptical about the karma system in general. We do not review, moderate, or otherwise verify the effects of the karma system. We just take it for granted that it works. I've never seen any evidence to prove it works. I've never seen any evidence that karma totals measure RP ability/willingness better than pure playtime does. At times, I've been tempted to just abolish the karma system entirely and just use playtime for everything that's currently karma-locked.
  2. Nov 11th: brandonsacawv has returned to the staff team as Game Admin.
  3. Nice idea. Unfortunately, gateway maps require a LOT more effort to create than you think.
  4. I've done a major upgrade to the wiki. As of today: Logging in to the wiki now uses your forum username/password. You no longer have to remember a separate username/password just for the wiki. Creating a wiki account is now automatic, when you log in via a forum account which doesn't have a wiki account. No more manually registering separate wiki accounts. Logging in will now synchronize your email, email verification status, displayname, etc with the forum, so it won't get out of date on the wiki. Game Admins now automatically get moderator permissions on the wiki, including the ability to view the list of unpatrolled edits, and to mark edits as patrolled. This enables game admins to keep an eye on the wiki. Players can no longer send each other email via the wiki. This had the potential to be annoying.
  5. Updates made today to our Patreon integration: Fixed a bug that was causing people with expired pledges to still get Patreon perks as if they were current patrons. Patron status now synchs from your forum account to your Discord account, the same way that other roles do. This eliminates the need for Patrons to separately connect their Discord account directly with Patreon. It also prevents situations where the forum thinks someone is a patron, but the Discord doesn't, or vice versa. It also ensures that ex-patrons have their patron tag in Discord removed. Patrons of the $1-4 tier are no longer counted as patrons anywhere. They don't get the Patreon Supporters group on the forums, the role/tag in Discord, or any ingame perks. This is a strictly token tier which does not grant anything, per the tier description. To make sure your patron status is correctly updated: If your forum account needs to be activated (you'll see big red text at the top of the page if this is the case) then activate it. Link your Patron account to your forum account here Link your forum and discord accounts here Your benefits should be synched everywhere (on forums, ingame, and on Discord) within an hour.
  6. Today, I reworked how the forum handles member ranks and titles. Short version: The forums no longer give you extra permissions after you've posted once. Instead, they give you extra permissions after you verify your forum account ingame. Patreon supporters no longer have their names displayed in cyan, but they still have "Patreon Supporter" listed on their posts, and unlike previously their supporter status won't cause problems if they are also an admin/mentor/etc. Since this update required a LOT of work on the backend, I urge all staff/mentors/donors/etc to double-check that their forum accounts work correctly. If you notice any issues, message me.
  7. This list is very comprehensive, but it would be even better if it distinguished how important each upgrade was. The most important upgrades are: ORE machine (matter bin multiplies ALL minerals you get) Robotics fabs (manipulator reduces mineral consumption of the #1 most mineral-consuming machines) R&D Machines (same reason as 2, plus enables you to print more upgrade parts if you upgrade protolathe first) Medical Cloner (clones faster, phasic scanner enables autoprocess, may even let you scan people not previously scannable. Overall, huge boost to medical's ability to keep crew alive, and enables easy cloning of people whose bodies are not recoverable, e.g: gateway explorers) When doing science upgrades, you need to do those first. After those the next most useful set is: Robotics Cyborg Rechargers (faster recharging, self-repair, makes cyborgs more useful) Medical sleepers Kitchen appliances Xenobio machines All autolathes (both cargo and science lathes) Teleporter (to stop people spacing themselves)
  8. Certain in-game roles (Captain, NT Rep, IAA, Magistrate, etc) are expected to be played with some level of seriousness. When playing one of these roles, if you photograph your ass and fax it to CC, you're probably not playing the role with the appropriate level of seriousness. It is appropriate for the Clown, or a random Civilian, to try pranking CC in this manner. It isn't appropriate for the IAA, Captain, or other crew trusted with fax access, to be doing it. Previously, we've handled this via strictly IC means, like demotions, or BSAs. Now, I'm going to start considering butt-faxes like this as Captain/NTR/Magistrate/IAA as a sign you're not taking the role with the required degree of seriousness. This means that if I see an IAA butt-fax CC for no reason within a couple minutes of shift start (as I saw yesterday), henceforth I'm going to consider that a good reason to job ban the player from the role, until they start treating the role with the higher level of seriousness it requires. Roles like Captain, IAA, NTR, Magistrate, etc are intended to be taken somewhat seriously. While we understand and expect some antics, treating them completely non-seriously will get you job banned.
  9. https://nanotrasen.se/wiki/index.php/Internal_Affairs The IAA's job includes: Conduct investigations and write reports Ensure SOP is followed Ensure Space Law is upheld This means: For them to be able to conduct an investigation, either they have to witness a problem, or someone has to come to them with a complaint For them to ensure SOP is followed, they have to work with the department heads, who in practice have more authority and knowledge than they do, which makes them largely redundant For them to ensure Space Law is upheld, they need to work with Security. Problems: Few people bring complaints to the IAA, for various reasons. The IAA rarely work with the heads of department. If there's a problem and the head is willing/able to fix it, no reason for the IAA to be involved. If they're willing but not able, IAA involvement is pointless. If they're able but not willing, that's when the NT Rep gets involved. The IAA usually don't work with Security effectively. For example, they usually don't check on processing enough to notice when someone is in there longer than they should be. The IAA is generally considered a joke role. I've lost count of the number of butt faxes I've got from IAAs who don't take their role with even an ounce of seriousness. Solutions: IAAs need to take the job more seriously. This really is the fundamental requirement. If they won't take the job seriously, nobody else will take them seriously either. This means I shouldn't be seeing cases of IAAs buttfaxing centcom as much as I do. Every time you buttfax CentCom as the IAA, you make even admins less willing to take IAAs seriously. IAAs need to remind heads that they exist, and are available to help with investigations. For example, they could adopt a policy of faxing a short note to every head, or sending them it via PDA, at the start of each shift. Simply to remind the heads that they exist, and they're here to serve, by assisting the heads with investigating potential violations of SOP and/or Space Law. For example, the head can contact them to ask about the status of members of their department who have been convicted of crimes. The head can contact them to ask for help in investigating members of their department for doing stupid things. Etc. IAAs need to actively put in the time to monitor Security. This means paying special attention to them in the hallways and reminding them not to run around with tasers out. This means paying attention to brig timer notices and double-checking that the time given matches space law. This means checking on processing often and making sure nobody sits there forever. And so forth. Above all else, IAAs need to ensure they aren't sending pointless faxes to CentCom. CentCom doesn't give a flying hoot if a single officer hits a prisoner with a baton once. That is NOT CentCom worthy. That's the sort of thing the HoS is expected to sort out themselves, assuming it wasn't an accidental misclick. Just about the only time the IAA should be sending faxes to CentCom is if there's a serious problem with the Captain, Magistrate, Blueshield, HoS, or similar high-ranked position. If we want to actually change the game to make the IAA's job easier: Add a timer in processing which generates an alert over sec radio when someone is held in there with no charges for more than 10 minutes. Improve the documentation available to IAAs, to make writing GOOD faxes easier, and to discourage bad faxes. Make it easier for heads to work with IAAs. For example, create a 'private radio kit' which has 5 radio keys all set to the same, random frequency. Have the IAAs start with this kit. The IAAs could then hand out these keys to heads or other informants who want to work with them, giving the IAA eyes and ears throughout the station and a much better chance of detecting problems they can then investigate. Another example would be making it easier for IAAs to be granted access to departments. Usually when I see IAAs in a department now, its because the Captain or HoP gave them the access without even asking the head... which tends to annoy the head and make their co-operation much less likely. Heck, just move their office right next to prisoner processing (separated by shutters) so they can always see who is being processed. Make their boss the NT Rep, rather than the magistrate. The NT Rep can manage them and advocate for them better than the Magistrate can, anyway. Create a new crime "obstructing an investigation", which can be applied to people who completely ignore the IAA while they're trying to ask them about the subject of an investigation. Allow IAAs access to records that allow them to check that SOP is being upheld. E.g. HoP's records of job transfers, Coroners records of who is in morgue trays, Science's records of R&D levels, Cargo's records of what is being ordered, etc. Basically make them record central - bring the information to them.
  10. Updates: The prompt to link your forum/ingame accounts is now easier to read. A new prompt has been added to link your forum/discord accounts, for people who haven't yet. This prompt can be dismissed. It is never shown to people who are banned ingame.
  11. When giving feedback to our staff, please: Cite Examples. E.g: if your issue is that two supposedly similar cases were handled differently, you need to cite both cases in enough detail for us to examine them. For forums, this means providing the URL of the threads. For stuff that's only in-game you need to provide the date it happened, and the name of the admin who handled it. "Sometime last week" is usually not enough for us to go on. Be Prompt. If you see something that you think is an issue, report it IMMEDIATELY. Do not wait! Reporting something in the round that it happens (via ahelp, typically) is better than waiting until next round to ahelp it. If it is serious enough to go to the forums (ban appeal, admin complaint, or whatnot) then do it as soon as possible after the round is over. The longer you wait, the less reliable everyone's memory gets, and the harder it becomes to gather all the relevant facts. Be Clear. E.g: if your issue is X, stick to talking about X in your report. Don't offhandedly bring in other things unrelated to X. Stay on topic. Be Concise. Most issues brought to our attention need no more than a paragraph to explain them. If you find yourself going much over a paragraph, you probably need to edit it down, summarize, and focus on the key thing. Be Direct. If you have an issue to raise, raise it directly with the relevant person. E.g. Hosting/backend issues should be sent to me, mentor issues should be sent to the CMs, code bugs should be logged as Github issues, etc. Don't ask a third party to deliver your feedback for you. Similarly, if someone complains to you about something, and you are not responsible for that thing, tell them to take it up with whoever is responsible for that thing. Don't Over-Generalize. Any comment like "most of the playerbase <insert anything here>" is probably over-generalizing. If you feel that other people agreeing with you is significant to your point, cite those people by name. Anyone can say "lots of people who I won't name agree with me" about virtually anything. As a result, such claims are meaningless. If you want someone's endorsement of your opinion/claim/etc to have weight, you must name them, and you must be prepared for us to ask them to confirm that they support what you said. Be Willing to Offline PM. It is better to leave the right person a message, even if they are offline, than it is to go asking other people because the right person wasn't online at that exact moment. Staff are used to signing on to a bunch of messages. It is okay. We'd rather you just contacted the right person at the start, even if they are not online at that second. For roles which commonly get a lot of feedback (like the Community Managers, who are in charge of everything related to Mentors) there are multiple people in that role, so there is usually at least one of them online who you can contact. Remember: Staff Are Volunteers. None of us get paid for this. While we work very hard to deliver you the best SS13 server out there, remember, we're volunteers, we have real lives, jobs, etc, and sometimes, ban appeals/etc can take a week or two to process. This is especially true for situations that are complex, require very specific people, etc. Those can take longer. Your patience is appreciated.
  12. The following changes have been made to how our website integrates with Discord: You can now register on our forum directly using Discord. Registration no longer asks you for your discord nickname or name preferences.
  13. Vox raiders just walk up to command, trade for what they want, and leave. They only require one person to deal with them (often the Captain or HoP). They're not engaging for anyone outside of Command, and they don't make a good event, let alone a good game mode.
  14. Kyet

    Wiki Changes

    Reminder: Our wiki is at: https://nanotrasen.se/wiki/index.php/Main_Page Anyone can edit it, just register a wiki account. Some good places to start editing: https://nanotrasen.se/wiki/index.php/Category:Work_in_Progress https://nanotrasen.se/wiki/index.php/Category:Revision_Requests Coordinate your changes with other editors using the #wiki_development channel on Discord. Changes Made Today: The "Wiki Curator" role and the "#wiki_curator" channel in public discord (restricted to wiki contributors) have been retired. They were almost never used, and anything posted in that channel would be better posted to the public #wiki_development channel. The "Wiki Contributor" role now has a special color in Discord, and is ranked above normal members. The idea is to encourage people to help out on the wiki by giving them a color for doing so. We will continue giving out this role to people who are actively helping out with the wiki.