Jump to content

Sirryan2002

Admins
  • Posts

    521
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by Sirryan2002

  1. This feels like its in the same realm as putting a collar/name tag on a terror spider. I would be against a feature like you're suggesting and there's a few reasons for this: 

    1. A need for a snowflake in a check for both proposed solutions
    2. If you take xenomicrobes it, it's intentionally designed to change a crew member into an unidentifiable horror space alien. The proposed change goes against the idea of xenomicrobes being a horrifying bioweapon that traitors can use against their targets or unsuspecting explorers ingest which results in them being hunted by their own colleagues and possibly causing station panic.
    3. Explorers will be more inclined to take xenomicrobes because they know they're less likely to be killed; being able to be named validates this behavior
    4. Dying Permanently because you made a rare lethal mistake or choice with heavy consequences for your own biology is perfectly fine and should be more accepted
    • Like 3
  2. update it's merged :D, feel free to leave suggestions for what could be added in the future, tweaked, or improved. The second part I eventually want to do with the library will come sometime later, probably not for a few months. But when it does I'm hoping to add a few things

    • The ability to specify the type of cover you want your book to have
    • Ability to edit certain attributes of your book once it's uploaded so you don't have to delete and reupload
    • Ability for librarians to edit checkout times + apply fines for delinquent books
    • A way to hook the library into the economy
    • Like 2
    • explodyparrot 1
  3.   

    2022 April Wiki Update:

    Happy (belated) April everyone, solid and consistent work this month, give yourselves pats on the back. Progress baby! As always, we've got a lot of work to do still. Keep writing those pages and helping me hit our development goals. Speaking of our 2022 development goals, we're really beginning to see some progress towards them. This month especially we've placed a special focus on expanding those portal pages and now expanding our wiki contributor resources. Even though I'm getting fucked exams, Buckle up for a funky fresh update!

    ---------------------------------------------------------------------------------------------------------------

    Revision Requests & Changelog

    What needs to be done on the Wiki:

    Keep knocking out those revision requests mis compadres!

    April Change Log:

    Thank you to all of our contributes I haven't specifically mentioned yet: @PopeDaveThe3th @Zydras @Charliminator  @skybluegill@Qwertytoforty @AzuleUtama @Miraviel @BrickTheHooman @roarbark @AffectedArc07

    As you can clearly see, it takes A LOT of contributors to keep the wiki chugging, I encourage all of you who have may <5 edits to continue learning and contributing! I'm always here to support and guide. Those of you who do not contribute (but still read this :D ) this is the perfect time to start learning and becoming a part of our awesome team. Soon enough it will be much easier to get in contributing, just you wait (or start now >:D)

    ---------------------------------------------------------------------------------------------------------------

    2022 Development Goals - How we can/are meeting them!

    Alright lets revisit those development goals and see how they're cooking.

    Finish Every Portal Page - A.K.A Wiki Navigation

    So far we've been making progress. Most notably through the use of portal pages. These portal pages are the bridges between our main page and literally all knowledge on the wiki, they link together one topic and all articles pertaining to its topic. So far we have established three categories of portal pages: Contributor Portals, Game Mechanics Portals, and Department Portals. All Department, most contributor, and no game mechanics portals have actually been established. What we need to do is continue developing these and expanding them. It's pretty simple, just replicate the format of the other ones, I trust you!!! @ me if you need help or guidance.

    Current State of Portal Pages

    • Job Portals 
      • General - FINISHED
      • Service - FINISHED
      • Supply  - FINISHED
      • Medical - WIP
      • Security - WIP
      • Engineering - WIP
      • Research - WIP
      • Command - WIP
      • Antagonist - WIP
      • Legal  - WIP
      • Special Role - NEEDS TO BE MADE AND ADDED TO NAVBAR
    • Contributor Portals
      • Wiki Contributor - WIP/FINISHED
      • Github Contributor - WIP/FINISHED
      • Technical Troubleshooting - WIP
      • Hosting - NEEDS TO BE MADE
    • Game Mechanics Portals
      • New Player - NEEDS TO BE MADE
      • Server Systems -
      • Mobs  - NEEDS TO BE MADE
      • Game Objects  - NEEDS TO BE MADE
      • Game Rounds  - NEEDS TO BE MADE
      • Lore  - NEEDS TO BE MADE

    Development of a Manual of Style

    This is a long-term project, I have made a lot more progress with it. I encourage y'all to suggest things but ultimately this falls upon me to write since it's setting the standards for our wiki writing. What you can do to help this, is start reading through them and learning how to edit articles using our standard format (it also has a couple essay-esque parts that assist with making them better for the reader).

    Current State of MOS:

    • Typography - FINISHED
    • Prose  - WIP
    • Content  - FINISHED???
    • Layout  - very WIP
    • Templates  - NEEDS TO BE MADE
    • Files - WIP
    • Accessibility  - NEEDS TO BE MADE

    Wiki Team Improvement

    Big plans here this and next month! Here's what's done:

    • Wiki Contributor Portal
    • Partial Rewrite of Guide to Wiki Editing

    Here's what we're gonna do:

    • Complete rewrite to our Guide to Wiki Editing
    • Writing of an article for the sole purpose of telling contributors where and how they can contribute
    • Looking into possible incentives for wiki contributors to encourage editing

    Content Expansion

    This has been an alright month for content expansion. As I said before a few pages have seen some increases in their quantity of content. You can all help out here by continuing to populate item/object/mob pages that are missing information. Additionally, rewriting or improving guides to be up-to-date and more user-friendly is always beneficial. Not my penultimate goal in May but I'd like to see contributors step in here and really take hold of an article as their own and completely bring it up to speed <3

    ---------------------------------------------------------------------------------------------------------------

    Conclusion

    if you were @'d on this post it means that you contributed meaningfully to our wiki in some aspect and I'd hope you are willing to stay around another month to keep doing so. If you want to get involved with editing the wiki and don't know how, @ me on the discord and I'll happily sit down and teach you stuff when I get the chance. I hope to continue doing this every month. Here is a syntax guide for those who are curious

    As always, thanks for the hard work everyone!

    • Like 4
  4. Wizard is meant to be a very high chaos round so a bunch of polymorphed mobs isn't a bad/unbalanced thing for that round type. That being said, some feedback to polymorphed players about what they're supposed to do especially in relation to our advanced rules ruling on it would be very helpful.

  5. 2022 March Wiki Update:

    Hey hey folks, I know it's been a few months since I've made a monthly update but it's never to late to start it up again. Quite frankly, we've got a lot of work to do still, however instead of catching up with the github, we're focused on expanding our content. You know what they say, new year new wiki update formats. This year I'd like to expand how our monthly wiki updates are formatted: I will still proceed with the changelog, however it will only be for SIGNIFICANT changes; Needed changes will remain the same; I will include a section for how were are meeting our 2022 wiki development goals; I will include a section specifically guiding our players on how to contribute to the wiki!

    ---------------------------------------------------------------------------------------------------------------

    Revision Requests & Changelog

    What needs to be done on the Wiki:

    Keep knocking out those revision requests y'all. 

    March Change Log:

    Thank you to all of our contributes I haven't specifically mentioned yet: @peter103@Vulkoras@maxfromsweden@Arkhip0v@Qwertytoforty@Krossarn@Generaldonothing@LightFire53@thorium90cent@Meow19@Zydras@whataboutism@Miraviel@Aligote@Abigail886@Agatasa@Beo208@Vilshen@Chapitito

    As you can clearly see, it takes A LOT of contributors to keep the wiki chugging, I encourage all of you who have may <5 edits to continue learning and contributing! I'm always here to support and guide. Those of you who do not contribute (but still read this :D ) this is the perfect time to start learning and becoming a part of our awesome team.

    ---------------------------------------------------------------------------------------------------------------

    2022 Development Goals - How we can/are meeting them!

    Alright lets revisit those development goals and see how we're farin!

    Finish Every Portal Page - A.K.A Wiki Navigation

    So far we've been making progress. Most notably through the use of portal pages. These portal pages are the bridges between our main page and literally all knowledge on the wiki, they link together one topic and all articles pertaining to its topic. So far we have established three categories of portal pages: Contributor Portals, Game Mechanics Portals, and Department Portals. So far only a few of the portals have actually been established EX: Engineering Portal. What we need to do is continue developing these and expanding them. It's pretty simple, just copy the format of the other ones, just @ me if you need help.

    Current State of Portal Pages

    • Job Portals 
      • General - FINISHED
      • Service - FINISHED
      • Supply  - FINISHED
      • Medical - WIP
      • Security - NEEDS TO BE MADE
      • Engineering - WIP
      • Research - NEEDS TO BE MADE
      • Command - NEEDS TO BE MADE
      • Antagonist - NEEDS TO BE MADE
      • Legal  - NEEDS TO BE MADE
      • Special Role - NEEDS TO BE MADE
    • Contributor Portals
      • Wiki Contributor - NEEDS TO BE MADE
      • Github Contributor - WIP
      • Technical Troubleshooting - NEEDS TO BE MADE
      • Hosting - NEEDS TO BE MADE
    • Game Mechanics Portals
      • New Player - NEEDS TO BE MADE
      • Server Systems -
      • Mobs  - NEEDS TO BE MADE
      • Game Objects  - NEEDS TO BE MADE
      • Game Rounds  - NEEDS TO BE MADE
      • Lore  - NEEDS TO BE MADE

    Development of a Manual of Style

    This is a long-term project, I have made some minor progress with it. So far I have developed the guidelines for files/typography n' stuff but that is still very much a work in progress. I encourage y'all to suggest things but ultimately this falls upon me to write since it's setting the standards for our wiki writing.

    Current State of MOS:

    • Typography - WIP
    • Prose  - NEEDS TO BE MADE
    • Content  - NEEDS TO BE MADE
    • Layout  - NEEDS TO BE MADE
    • Templates  - NEEDS TO BE MADE
    • Files - WIP
    • Accessibility  - NEEDS TO BE MADE

    Wiki Team Improvement

    This goal is a bit more grey in terms of completion/where-to-go. My goal this month has been to restart our forums activity and get you guys involved again here. Otherwise I hope to just keep poking and prodding y'all to help contribute.

    Content Expansion

    This has been a great month for content expansion. There has been a large amount of progress with documenting objects on the wiki, specifically Firearms, HUDs, and Simple Mobs. You can all help out here by continuing to populate item/object/mob pages that are missing information. Additionally, rewriting or improving guides to be up-to-date and more user-friendly is always benificial.

    ---------------------------------------------------------------------------------------------------------------

    Conclusion

    if you were @'d on this post it means that you contributed meaningfully to our wiki in some aspect and I'd hope you are willing to stay around another month to keep doing so. If you want to get involved with editing the wiki and don't know how, @ me on the discord and I'll happily sit down and teach you stuff when I get the chance. I hope to continue doing this every month. Here is a syntax guide for those who are curious

    As always, thanks for the hard work everyone!

    • Like 3
    • Thanks 3
    • fastparrot 1
  6. I had some ideas for this.

    Obviously cultists may permakill officers more often if officers can be brought back to sharding, however that's at the tradeoff of giving up a possible construct which is a choice the cult now has to make. I was thinking that upon death, constructs would deform into a "broken construct" or something along those lines and could be brough back through a timed ritual done by the chaplain. 

  7. I'll throw my two cents in here.

    I think Xenos are going to need more than a small rework to be put back into rotation. You offer a lot of good micro changes and a few good major changes. Thankfully for aliens they have a cool concept with cool features already coded in, they just do not mesh well at all with todays balance standards. I'd be happy to work with you (code) for this rework (after I finish my library rework PR this month) but I had some ideas for a few features added in:

    • Egg-sac based queen that slowly becomes more immobile as it gets more egg sac (but increases production speed + upgrade abilities) and therefore is a mobile then stationary hive
    • Plasma farming system where captured mobs are still "alive" in resin nests and produce plasma for the hive (player still gets ghosted temporarily)
      • Non-carbon or dead mobs give a one time lump-sum plasma boost
      • Idea is that players aren't gibbed and permanently removed from the round so easily and gives a large incentive for xenos to defend their hive to the end instead of just running around like terrors
    • Queen can spend plasma on stuff
      • Warrior Alien Egg - 100 Plasma
      • Drone Alien Egg - 100 Plasma
      • Facehugger Alien Egg - 50 Plasma
      • Evolution/Ability Point - 100 Plasma
      • Tier 1 Evolution - 1 Evolution Point
      • Tier 2 Evolution - 2 Evolution Points
    • Facehuggers no longer plant eggs inside of carbon. No longer insta-sleep but will slow down and then stun target after some time
      • Prevents really quick snowballing from spamming facehuggers and abusing insta-stun mechanics
    • Evolution points are a way to "Evolve" alien types and give the hive special abilities
      • early on, abilities are about mobility and survivability
      • overtime the hive evolves to be more offensive and hive-centric
        • eventually xenos grow to be too large for vents and can no-longer vent-crawl, they're much more beefy at this point and shouldn't linger around the station in vents if their queen goes kaput.
    • I'd also like to see the queen evolve into an empress/queen mother as an end goal kind of like you were suggesting
      • gives direction to the antag rather than "kill the crew"
    • Also actually utilizing praetorians, Royal Facehugger, and runners as well somewhere in the mix for xeno type diversity
      • form of investment for the queen to either use low-health cheap/quick runners vs beefy expensive praetorians.

    I don't mean to hijack your post to throw in my entire idea of a xenomorph rework. I think you have a lot of combat balance ideas (especially avoiding stun mechanics) which I haven't really thought out which do need to be implemented, however it would be cool to see large-scale changes to antag strategy that also hope to address issues with xenos and make the roles more fun. lmk if you're at all interested.

    • Like 1
    • eyes 1
  8. Hello everyone, I've been drafting up and beginning the first code reworks of our library system. Library code has been around for.... a very very long time. The Library and Librarian as a role are very underutilized due to Librarians having very little to do, not to mention the UI and library system being pretty out of date. With this proposed refactor I'm hoping to tackle the issue of outdated code and UI. Later down the road (part 2?) I'd like to give the library more functionality with scanning in documents and possibly contributing to research or a knowledge system that would allow crew to learn things like different languages or possibly even light magic.

    Proposed Changes

    Library Computer

    • Remove the Public/Checkout computer and replace it with a single computer
    • Port browserUI to TGUI
    • Tabs for Library System
      • Patron Management - Place where book checkouts are managed and fines are handed out against peoples accounts who do not bring books back in time. Barcode scanner will perform most of the work for checking out books but it can all be done from this tab aswell.
      • Book Archive - Search player-made library books with a much more fleshed out search system. You can now see short book summaries, ratings of books, and up to three categories for books. Additionally, the flagging system has been made much more clear that it is an OOC action
      • Programmatic Books - All hardcoded Manuals/SOP/Religious books will be populated in here separate from the player archive.
      • Book Upload - Where books can be uploaded to the archive. Selected books will show up here, allows editing information about books before uploading them.
      • Possible Security Log screen for any actions (fines, checkouts, etc) taken during the shift
    • Library Computer will have a login screen
      • Librarian Access - All library management tools available
      • Public Access - Can only view player/programmatic book archive and can't order anything

    Barcode Scanner

    • Chat Output from changing modes will be significantly cutdown to a single line
    • User feedback is much more clear (with sounds)
    • Will no longer stores information in barcode object, instead it just relays information directly to the library computer
      • Allowing for on-the-go library work 
    • Will be able to Swipe ID's on the barcode to get crew member information for checking out books.

    Bookbinder

    • Will have a TGUI menu
    • Will be able to print multiple books at a time
    • Option to choose book cover + decorations

    Books

    • Will remain BrowserUI (this is something non-negotiable due to security issues)
    • Will be able to have up to 3 editable Pages
    • Books will open to a "cover page" with the book summary, title, and author available to read. Additionally this page will show if the book is checked out and/or a part of the stations library system.
    • More Book Information
      • Books can now have a short few sentence summary denoting what the book is written about
      • Books will now have a X/5 star rating which is determined by players through the library system
        • This is to help sort through good and shit books
      • More covers + cover decorations (overlays) will be available (I'm hoping to sprite a few more)
      • Examining books will yield extra information such as the book rating on the side as well as if the book

    RFID Scanners

    • Goes off when player walks through it with a non-checked out book
      • Makes a log in the librarians computer
    • Special Punishments for Book Thiefs
      • Lights people on fire when emagged if they steal a book
      • When fully upgraded it stuns the crew member and launches the crew member back into the library
    • Has an R&D circuit board

    Bookcases

    • Hope to resprite these
    • Make them rotatable

    Administration Tools

    • Will remain browserUI, however it will have a significantly improved interface
    • Players now get a yes/no popup before flagging books warning them that they are performing an OOC action
    • Players now have options to choose from for flagging a book so that staff have an idea of what they're looking for
    • Viewing flagged books is much easier and the raw HTML is not dumped in a window

    Database Changes

    • Adds a few columns to the library table
      • Rating *#/5 integer rating of book
      • RatingNumber *integer number of rating reviews left by patrons
      • Summary *string
    • Modifies how data is stored on a few columns
      • flagged column now stores a JSON list of player flags based on report IDs
      • content column now stores a JSON list of book pages

    Thoughts, questions, concerns?

    • Like 7
    • Thanks 1
  9. Greetings everyone!

    As some of you've noticed (at least I hope you've noticed) that I haven't written a monthly wiki update in 3 months. This is for a few reasons: I'm busy with college; I've been focusing more on interacting with the community through events and adminning; It is not healthy to lead development on a wiki and not takes breaks. Now that I've said that, I have been working on plans for this year and even past that in terms of where we can improve our wiki.

    Our wiki in its current state is far from perfect. While our content is up to date and our templates look pretty, there are still some basic principles and structures our wiki is missing. Normally I like to do a changelog but that is not the purpose of my forum post today. This is a brain dump of a lot of thinking I've done. It's not perfect. However, I want to provide direction for our contributors because what "wiki-development" is becomes a bit muddy after everything has been brought up-to-date with the codebase.

    What are the issues we need to tackle?

    As I’ve pointed out, our content is far from lacking, it’s almost completely up to date with the codebase excluding location based information. I will start with the larger (in scope/size) and the most important issues first and then work my way down from there. I know our wiki has made a lot of progress but I'm going to tear apart and criticize our wiki to the fullest extent possible. Please bear with me.

    Wiki Navigation

    Problem: This is the issue I view most in need of attention. What is wiki navigation you may ask? When someone opens our wiki, they see our main page with the cutsie splash and plethora of navigational divs outlining the many sections of our wiki our reader can explore. If you find the right link you can jump into a breakdown of our role pages, antags, guides, lore, and a bit more. We do a solid job linking most pages in our main page and it’s child pages. However, It’s just simply not enough. 

    I should be able to take a brand new player who has never seen the wiki, tell them to find info on a specific topic, and expect them to find that exact page/info without external assistance. In addition, a player with some experience should be able to navigate from an end-node page (see tree chart structures) to another end-node page in a completely different category in only a few (3-5) page jumps.

    Solution:

    • Portal pages with proper intersectional navigation with links to all relevant articles that would fit under the portal’s category.
    • Category tree: every page has a minimum of one static category and a max of 3 static categories. Of those categories there should be a page type(guide, SOP, location, job, etc), if needed-> department (supply, service, etc), and misc categories (out of rotation, archived, etc). Not this does not include variable maintenance categories.
    • Smart naming, use of anchors, and redirects to allow complete and full use of the search bar. File names need to have uniform naming, any reasonable search term needs to redirect, and any specific item on a table should have an anchor associated with it.

    Commentary: Why is this the most important you may ask? Well, what is any of our work worth if a player cannot find it.

    Article Quality and Structure

    Problem: How we write each article can be wildly different. Currently if one was to take a gander at the Guide to Engineering, Exosuit Fabricator, and the Guide to Genetics articles they would find that the prose and style of them is wildly different. How the information is structured and presented, how other articles are linked, how much humor is used, how sentences are bolded and italicized, the objectivity of the article, how templates are used, how the article introduces itself, and how friendly it is to new players varies to such an extreme degree between articles that it would be hard to say that most of our articles follow similar standards at all. 

    As it stands, trying to read through articles one after another can be nauseating. When a reader goes into an article expecting like-structure from another similar article only to encounter a totally new style/prose their brain is immediately boggled and at a disadvantage for learning. In addition, when we don’t set these uniform standards for our articles, basic important knowledge is not included and much transitionary/body/meaty information is left out.

    Solution:

    • This falls mostly on me to push. We need to establish a proper multipage Manual of Style and Guide to editing the wiki portal. This extends to everything: Templates, Files, Articles, Categories, and much more other nuanced things.

    Commentary: By establishing standards in a document, teaching our contributors proper technique, syntax, and style is much easier and it would allow our writers to attain a higher ability in wiki editing much quicker. 

    Wiki Contributor Team

    The Problem: At the beginning of 2021, the wiki contributor team was dead outside of 2-3 people that periodically updated the wiki. Since then, it has been rebuilt into a group of roughly 6-8 people (although losing steam this year again) that regularly update the wiki to varying degrees. Some people are better at grammar, some are versed in images, and some people are good at styling. It’s a good balance but we can always get more contributors. I want to address two issues in this category: our atmosphere and contributor training.

    First, our atmosphere. I was ignorant of this when we were first developing as a community but we’ve adopted (and since have gotten better at avoiding) some bad behaviors. When someone comes to our channel with a wiki-issue/error we cannot just say “go fix it then.” This is the same as telling someone “when you code it” (WYCI) and then providing no guidance as how to code it. Our goal as wiki contributors when interacting with the community is always first and foremost to be receptive in ways to improve our wiki and second to enable outsiders to join our community and learn how to edit our wiki. I will never be negatively critical of anyone's work and neither should anyone else. Going forward I will absolutely not tolerate hostility. That is not to say you cannot criticize others' work or point out errors, but there are ways to constructively do this.

    The Solution

    • Call out bad behavior. If someone leaves out important information or is clearly missing something, your first action should be to ask more questions and politely provide clarification where needed. If someone is being an unabashed dick, @ me immediately and I’ll sort them out.

    Files

    The Problem: An inherited issue from years of bad file organization has been biting us in the ass. Mediawiki has an awful search algorithm. If someone named an image of Xeno Meat Bread something like “xenobread” or god forbid “xbread” you will never and I mean never find it through the search engine. You have to type the exact name. This is why we have duplicate images and why when we write new articles we cannot find relevant images that already exist on the wiki.

    In addition, the quality of our files varies. While we have nailed down the standard 64x64px we haven’t nailed down what state the item needs to be in, if it should be a gif it has multiple states, and the frames/sec for those gifs.

    Solution:

    • As part of the Manual of Style we need to develop guidelines for files on our wiki. A.K.A what size is ok, what quality, gif or png, naming scheme, etc.
    • Once the guidelines have been ALL WRITTEN DOWN we should be going through all of files and standardizing them as much as possible

    The Plan for 2022

    Alright I’ve had enough fun nitpicking our wiki, here’s how we can make it the best in the SS13 Community.

    Finish Every Portal Page

    What is a portal page? It is where EVERY job, location, guide, misc article for a specific topic is linked. This is important because if I'm looking for information about a feature but I only have a general idea/don't know the name of the feature it will be very difficult to locate it. Instead if I know it's related to a specific department I can begin looking in its portal. Not to mention this will allow us to identify holes in wiki where information/articles are missing.

    Each portal page has a uniform structure to it, it should be simple enough to set up. Every department portal page should list the roles, guides, and locations of the category it’s designed for. For other misc portals like the new player, wiki contrib, troubleshooting, and github contrib portals there will be a slightly different structure (with the same design however). Here are all the portals that need to be finished/made:

    • General
    • Service
    • Supply
    • Medical
    • Security
    • Engineering
    • Research
    • Command
    • Antagonist
    • Legal 
    • Special Role
    • Wiki Contributor
    • Github Contributor
    • Technical Troubleshooting
    • New Player
    • Game Mechanics
    • Lore 

    Development of a Manual of Style

    We need to develop a fully fledged manual of style. The following pages will need to be created and written for it:

    • Typography - Italics, Bold, Strikethrough, font size, underscores, colors
    • Layout (By Page Type):
      • Introductory Paragraph
      • Body Paragraph
      • Heading Naming
      • Splitting articles up by sections
      • When, where, and how to use images
      • Where and what templates to use
      • What Information to Include
    • Templates
      • Wikicode Standards
      • <noinclude> documentation
      • Styling Standards
    • Files
      • Images
      • Gifs
      • Naming Scheme
    • Prose
      • Objectivity/Bias
      • Guiding vs. Telling
      • Humor
      • Writing Perspective (1st, 3rd, etc)
      • Paragraph Structure
    • Content
      • Quality and Quantity of Information
      • Readability
      • Flow of Information
      • Over/under-use of Interlinking
      • Article Size and Scope
    • Accessibility
      • Categories/Category Trees
      • Portal Pages
      • Disambiguation Pages

    File Standardization

    While non-admin contributors cannot delete pages, what they can do is mark them for deletion as well as move them. By moving a file they “rename” it. Just make sure to go through each page where that file is referenced and fix it.

    • Capitalization of Files
    • Spacing of Words (A.k.a SecurityOfficer (wrong) vs. Security Officer)
    • Naming of Files (Xeno Meat Bread instead of Xbread)
    • Gif Speed must almost always be 1 frame/second. However guns should be 2 frames per second, actual DMI gifs should be their native speed, and misc gifs like changelings should be whatever works best.

    Going through pages one-by-one

    Once a manual of style is developed, every single page on the wiki needs to be gone over with a fine-comb. This is by-far the heaviest lifting objective. This is something that would have to be done gradually over time. This is not my priority and is something that is very very long-term.

    • Current Rating of articles on a C, B, A and Good Article scale
    • Go portal by portal and fill in any missing gaps + rework articles

    Development of the Following Pages

    I’m just going to list the pages that need to be created or completely rewritten (or the rest of the content filled out)

    • Command Pages
      • Guide to Leadership
      • Guide to Problem Solving ???
    • Service
      • Guide to Cleaning
    • Github
      • Completely Rewrite Guide to Spriting
      • Completely Rewrite Guide to Mapping
      • Completely Rewrite Guide to Coding
      • Write Guide to TGUI
      • Guide to Setting up the Code Environment
      • Guide to Making a PR
        • Technical process
        • Idea to PR process
        • Understanding how to write a good PR
        • When to not make a PR
      • Guide to Bug Fixing and PR Testing
    • All the Manual of Style pages (Listed in another area)
    • Misc
      • Theta Station Researcher
      • Heads Up Displays
      • Starter guide to admin tools
      • Mechs
      • Guide to Regex




     

    • Like 4
    • Thanks 2
  10. Thank you all for those who participated or watched. It was a lot of fun to put on and I love to see players bring out their creative side.

    Here are some screenshots I've collected from players. Feel free to post some if they haven't already

    Spoiler

    Ai_Fashion.thumb.png.bbaf7474579190f5e2ca5ef9e55ad4bb.pngFashionShow.png.2f03fd4987f102c266e2d050ca33a303.pngmy_damn_cane.thumb.png.a504253f12d0faa8bf3f051e1f3b1173.pngchrome_d1cDTVe0PK.png.b30b171c41d12ac8b19aa857b7d5beaa.pngParadise_Station_NSS_Cyberiad_2022-03-05_220921.png.448a0bea01a8dea740bd7d01b5fe0c5a.pngshion_competition.thumb.png.1e08b76d06387ce95dac449939e91ef9.pngunknown.thumb.png.73c9e6be0f9d4beb6f328d4a3ae1c290.pngVIP_pool.thumb.png.75d9ff79a89afe7347012c8cdc5d74ec.png

    It particularly amazing to watch Honkcrates the great (one of the models) walk on stage and light themselves on fire after hurtling a wine bottle into the ground (he later died from unrelated injuries). There was a lot of cool and creative outfits and the crew did an excellent job preparing the venue and being audience members.

    • Like 3
  11. My recommendation? Temporarily retire the character (a month or two minimum). You don't control how other players act but as long as staff don't step in and stop this shit, by continuing to play this character you will be enabling the behavior you just witnessed. It sucks ass to make a character change but it may open up some new front in which to roleplay/enjoy the game differently than you did under you 900 hour character.

    Frankly, as an admin, if I saw players harassing/targeting someone because they're not doing a great job at replicating another players IC persona as a changeling I would be immediately warning them. Toxicity isn't cool and that's not the kind of community we're building here. That being said, this seems like a community issue and you either need to talk to those involved and ask them to cut this shit out or to work with a staff member to make a community announcement.

    I do not know what kind of rules you have on the server you play on, but if this were to happen on Paradise and I witnessed it, bans would be handed out.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use