Shadeykins

Community Manager
  • Content Count

    3014
  • Joined

  • Last visited

  • Days Won

    22

Shadeykins last won the day on April 21

Shadeykins had the most liked content!

Community Reputation

351 Excellent

4 Followers

About Shadeykins

  • Rank
    The Lowest Common Denominator
  • Birthday 06/18/1992

Personal Information

  • Byond Account
    Shadeykins

Recent Profile Visitors

1932 profile views
  1. You were given an extensive period (6 months) with constant requests for feedback on lore. Vulpkanin went without lore for about eight months initially because you refused to provide any input on the matter whatsoever despite having joint authority over it (you were even told a simple yes/no to the proposed lore would have sufficed--there was three different lore documents floating around at the time as well). You declined to give any feedback after being asked on four separate occasions by myself, by Flattest at least two or three times (to my knowledge), and by headministration once or twice at the time. A lore team was later established which you also did not apply for or offer any feedback. The new revised lore produced by the lore team was then announced publically at multiple junctures (five times to the community) for feedback to be given. The lore then sat for another six months during a feedback period where we were actively collecting input from members of the community and people who were interested in the lore (quite honestly anyone was welcome to provide input and spitball at this time). You didn't give any feedback/input at this time either. People wanted your feedback on the lore and actively tried to include you in the process. I am glad you've actually stated a few of your original ideas (they're valuable if the lore gets revised again), but this is an incredibly unfair statement to anyone who worked on it. People repeatedly tried to involve you in the process and framing it as though you were patently glossed over is completely untrue. If you--as the creator of the species--write something, I can guarantee you that it would be incorporated. As for lore discussion, it's always welcome; idea generation is valuable. The only thing to keep in mind is that lore mirrors mechanics, not the other way around. This is probably the biggest reason why none of the lore is terribly bold or adventurous for the species as nobody wants to implement active contradictions between the lore and the game server.
  2. Administratively it would be a bit more for us to enforce, but it's a nice idea. It would be a little canned, but a selection of prompts (pre-filled responses) would nip any potential issues in the butt (you could select roleplay, antag, helpful, etc., basically to let people know why you karma'd them).
  3. The change was deliberate because you shouldn't get arrested for drawing with crayon on the floor. If the person is anything but a civilian, you could always just get them fired.
  4. Crime stacking is a horrible can of worms that should never be opened. Needless complication + easy abuse. Sparking a Manhunt was already a crime in the past and was abused to the nth degree. It very easily amounts to "security had to find and arrest you, therefore you get charged even if you weren't aware you were under arrest." Lower times in cells encourages repeat offenses (since each crime matters little, 1-5 minutes isn't even worth sentencing someone over most of the time hence why minor crimes already have an optional warning system). Repeat offender based off getting brigged again might work, but mostly repeat offender is to deal with that one shit who keeps disarm spamming people.
  5. The term you're using originates from the original practice of anthropology which advocated for categorization of peoples based on ethnicity (different ethnicities are "different" humans) and is responsible for the proliferation of subhuman ideologies (anthropometry and the association between ethnic groups and intelligence specifically). It exists as a slur precisely because of its associations with subaltern peoples and, yes, is levied as an insult against east and southeast asians (which includes Vietnam, Bengal, etc.). Much like the word "gay" came to be a pejorative because of its associations with homosexuals, so too did this word become associated with down syndrome because of its ethnic associations. Etymologically, the term was initially used to describe people with down syndrome because they had folded eyes similar to southeast/eastern asian peoples. This should be a pretty big giveaway to the racial motivations behind the word's usage. It became especially popular as a pejorative in the Vietnam war era by certain groups and saw a revival in the post-war period (along with a handful of other colourful slurs nobody has any business using). So yes, it is mostly levied against Vietnamese peoples (in an American context) despite having wider ranging associations. tl;dr the term is not acceptable and discussion of bans outside of the ban appeal section is not acceptable whatsoever (we especially don't want discussions on slurs either). A good rule of thumb is that if your insults rely on the denigration of a group of people based off of uncontrolled characteristics (ethnicity, sexuality, etc.), you probably should find better insults. /thread
  6. Both of these words are actually derived from botanical categories. Tomato being a vegetable is actually the action of grocer's unions demanding its classification as such rather than a natural evolution of language. The common usage is actually derived from the misapprehension of political worker's groups who apparently have nothing better to do. If you've ever worked at a unionized grocery and read its agreement, there's almost always a section in the CBA about tomatoes being fruit. It's real dumb. ?
  7. Ketchup is a preserve/dressing (like Mayo). You could make tomato jam/jelly w/ sugar and pectin. It would be closer to a chutney, presumably. Tomatoes are indeed fruit! This has to do with the orientation of the epicarp, endocarp, and mesocarp and the fact that it originates from the 'mammary' of the plant.
  8. Stims making you drop an item wouldn't balance this out to be fair, it would just make tasers/batons have an even bigger edge in combat. The real issue is instastun in general.
  9. Attack them on harm intent?
  10. Multiple people witnessing you EMPing your surroundings with no clear source of that EMP is more than enough testimony. Non mind-shielded personnel can still testify, the only difference is that their testimony is not true by default. Your blatant misreading of Space Law and SOP is not grounds for an argument. You have been told by three admins as to the actual interpretation of Space Law thus far, one of whom actually wrote the document itself. If you bothered to actually read Space Law, you would be well aware that you can't brig people during a station-wide emergency when there's an imminent threat to the health of prisoners. Space Law > SOP. Follow the server rules. /thread
  11. Laws do not overrule one another. There are several exception clauses for "Use of Deadly Force" so Security isn't hamstrung. This is not "overruling other laws," it's quite literally to allow security to do their job. Guillotine/Incinerator are not valid means of execution. The incinerator is literally only permissible because of the Changeling Enemy of the Corporation clause. If you do not follow through on proper execution standards, it's considered murder. This includes improperly executing prisoners. This is Rule 10. Intentionally violating the rules will get you warned/disciplined/job-banned. It is absolutely within the rules that security should be following Space Law. Additional adherence to SOP is expected for security because it handles things like brigging procedures, trials, and execution standards (which are not inherently part of Space Law). The override is inherent in Space Law. Space Law is not under SOP. SOP is complementary to Space Law, not the other way around. Space Law > SOP
  12. https://nanotrasen.se/wiki/index.php/Guide_to_Editing_the_Wiki
  13. We're currently maintaining 363 content pages, 2400+ files, and over 200 redirects. Of this, only 46 pages are labeled for updating (36), expansion (7), or deletion (3) and in active need of attention. This means roughly 9/10 (88%) pages are (to my knowledge) up to date. Most wiki-development work occurs either silently (anonymous/personal contribution) or is discussed on the #wiki-development channel on our wiki. The forum section here is sadly deprecated and only really serves as a quick reference for the wiki-contributor tag guidelines at this point. If there are pages not clearly marked by a templated header stating "OUT OF DATE" but updates are required to the page, please inform me of the relevant pages/reasons so they can be tagged for updates. As TDS mentioned, you are also welcome to contribute to the wiki yourself and make emendations where needed.
  14. https://github.com/ParadiseSS13/Paradise/pulls?utf8=✓&q=is%3Apr+maint+drone Many issues get resolved on the GitHub or even on the Discord/server. Not everything is noted down on the forums. Asking administration to copy-paste a response on every single pertinent thread/venue in every location (when we may not even know about the thread's existence) is not feasible. If you have a concern about the current status of drones, you are more than welcome to create a new and relevant thread about it. Necroing a thread that has been dead for four months to try and make a critique about the coding team is not the way to do it. Reasoning is already supplied on the pertinent pull request.
  15. This was done and dealt with, as you yourself mention, four months ago. Don't necro threads, please.