Guide to contributing to the wiki: Difference between revisions

From Yogstation-13
Jump to navigation Jump to search
imported>LiamLime
No edit summary
 
(29 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== Welcome ==
== Foreword ==
Welcome to contributing to the Yogstation Wiki - we're happy to have you here. This wiki would not be possible to maintain without the help and dedication of players and staff alike. In a game as complex as Space Station 13, having an up to date wiki is critical to properly enjoy it. Thank you for taking your time.
== Getting Started ==
=== Your account ===
As a first order of business, in order to edit pages a wiki account is '''required''' - this is a method to reduce the possibility of grief showing up on the wiki itself. To obtain a wiki account, use the '''Create account''' button at the top right of the page. You will need to confirm your email address before you will be able to make changes to the wiki.


We're happy you've shown interest in contributing to the wiki. This is a quick guide to how you can help
In order to both maintain a minimum level of quality on the wiki and to limit the damage of grief, edits made by new accounts will not be immediately visible, once you save an edit, the wiki staff will get a notification of your edit so that your edit may be reviewed, potentially edited and then approved or rejected. During the review process, you will still be able to further edit the page while your edit is being reviewed but try to avoid submitting incomplete edits. The wiki staff patrols change logs to correct small errors and combat intentional misinforming edits, so please be mindful and be ready to explain your edit if it raises a red flag. The best way to prevent misunderstandings is adding proper summaries for all your edits. Once you've created your account, don't be afraid to jump in and start correcting and adding to pages.


== [[Wikicode]] ==
Once you have a few edits under your name, feel free to apply to join the wiki team at https://forums.yogstation.net/forums/wiki-team-applications.290, this will allow you to create new pages and bypass the need to have your edits manually reviewed by the wiki staff.


Wikicode is the strange syntax used by all wikipedias including this one. If you don't know it and are prepared to learn, you can read the internal wikicode page [[Wikicode|here]], or read the Wikipedia page [http://en.wikipedia.org/wiki/Help:Wiki_markup here]. If you don't want to spend your life learning this markup, then fret not, you can still help.
=== [[Wikicode]] ===
Wikicode is the syntax used by all Wikipedias, including this one. It is not hard to pick up: Don't hesitate to read [[Wikicode|our internal guide]] or the [https://en.wikipedia.org/wiki/Help:Wiki_markup wikipedias official article]. The syntax and options might seem daunting at first, but remember that you can edit allmost all articles with this 5 minute crash course:
{| class="wikitable mw-collapsible mw-collapsed" width="800"
! colspan="3"| Most used wikicodes
|-
! Formatting
! Code
! Example
|-
! Bold
| <pre><nowiki>Quite a '''bold''' move, Mr Bond</nowiki></pre>
| Quite a '''bold''' move, Mr Bond
|-
! Italic
| <pre><nowiki>Do you ''really'' want that drink?</nowiki></pre>
| Do you ''really'' want that drink?
|-
! Italic & bold
| <pre><nowiki>No! '''''Please'''''! NO!</nowiki></pre>
| No! '''''Please'''''! NO!
|-
! Sections
| <pre>= Level 1 =
== Level 2 ==
=== Level 3 ===
==== Level 4 ====
===== Level 5 =====</pre>
| [[File:Wiki header example.png]]
|-
! Link (Internal)
| <pre><nowiki>Check [[Wikicode]] or [[Wikicode|click here fore more]]</nowiki></pre>
| Check [[Wikicode]] or [[Wikicode|click here fore more]]
|-
! Link (External)
| <pre><nowiki>http://en.wikipedia.org/wiki/Help:Wiki_markup</nowiki></pre>
| [https://en.wikipedia.org/wiki/Help:Wiki_markup http://en.wikipedia.org/wiki/Help:Wiki_markup]
|-
! Link (External, Custom)
| <pre><nowiki>[http://en.wikipedia.org/wiki/Help:Wiki_markup click me]</nowiki></pre>
| [https://en.wikipedia.org/wiki/Help:Wiki_markup click me]
|-
! List (Unordered)
| <pre>* Talk shit
* Get hit</pre>
|
* Talk shit
* Get hit
|-
! List (Ordered)
| <pre><nowiki># Stop
# Drop
# Roll</nowiki></pre>
|
# Stop
# Drop
# Roll
|}
Wikicode is what salt is for food. Of course you can cook without salt, but well-prepared foods and texts are clearly more enjoyable. Instead of having a page be a long meandering paragraph, Wikicode allows information to be broken up and changed in appearance for greater clarity, such as the section headings shown in this guide.


It is allright if you really don't want to deal with wikicode. You can still help by writing and correcting texts and have the wiki staffers add the formatting later. Just add something like <code>TODO - NEEDS FORMATTING</code> in your edit-summary to make it easier to detect.
=== Questions? ===
There are a few concepts that drive Wiki functionality, and this guide will attempt to touch on the very basics that you'll need to get in and get going. If you have questions regarding more advanced topics, you are allways welcome to ask in the above mentioned [{{Constant/Discordurl}} #wiki-public].
== What needs doing? ==
== What needs doing? ==
The Yogstation Wiki is an utterly massive project, and the [[Contributors#Wiki_Staff|active wiki staff team]] is small, comparatively. Most everywhere you look there is out-of-date information, duplicate guides, broken links, unintelligible references. The Wiki Team attempts to keep core pages up to date and patrolled, but there are many pages on the periphery in dire need of attention.


=== New pages ===
A good place to start is by analysing your strengths and the completeness of your knowledge within the context of Space Station 13, and then attempting to revise or update material relevant to that. If you are a person who plays Roboticist every round, then take a moment to look over the [[Roboticist]] page and verify the information there - add tips and tricks that you've picked up; publish a new guide page for some advanced facet of the position - in short, play to your strengths when editing and contributing, otherwise information can be left worse off than when it started.
 
New content is constantly being added to ss13 which needs tutorials and such. Before you start to write a page, search for it and if you can't find it, start one yourself. If you wish to work on a page uninterrupted, make it in your personal [[Special:MyPage/Sandbox|sandbox]] area or anywhere in your own pages. If you don't know wikicode, you can create a unformatted page and ask someone else to format it for you.
 
=== Content revisions ===
=== Content revisions ===
Once you are done reviewing your favourite articles / randomly browsing the wiki, check its list of pages which need revisions: '''[[:Category:Needs revision]]'''. Revision flags on Jobs or Guides tend to take highest priority, as these are the pages utilized the most by Wiki visitors.


A list of pages which need revisions can be found [[:Category:Needs revision|here]]
As a recommendation, if you wish to work on a page uninterrupted and not worry about other users editing the same thing while you are working, you can mirror the page in to your personal [[Special:MyPage/Sandbox|sandbox]] area or anywhere in your own pages. This will create a "localized" copy that you can change unfettered by interference by others.


Updates are frequent and we need people to update the information on the wiki. To do this simply edit the page with new information. If you don't know wikicode you can write the new, updated content on the discussion page without formatting.
'''Additionally, if you are revising a page, PLEASE put a summary in the Summary section of your editing window towards the bottom of the page. This will help Wiki Staff immensely when patrolling the moderation queue.'''
=== Mark articles ===
Whenever you find a page that needs some work you can't do / you want to do later, make sure to mark it. Marking an article will not only insert a nice obvious note, it will temporarily add the page to a category. These categories serve as todo-lists, which is very convenient. As long as you don't mark every single page in existence, this alone will be helpful.


=== Images ===
When tagging articles, make sure to use <code><nowiki>~~~~</nowiki></code> wherever possible, since this will automatically insert your post-details like this: '''[[User:Helpful Herbert|Helpful Herbert]] ([[User talk:Helpful Herbert|talk]]) 23:30, 24 April 2020 (UTC)'''.
 
{| class="wikitable"
If you have relevant images then upload them and add them to the page they're intended for. It is appreciated if the pictures of items you add have a blank background and are in the .gif or .png format. The easiest way to add images of items is to download the [[Downloading the source code#Downloading|source code]], open the icons .dmi files and export images as .gif's or .png's from there.
!Category
 
!When to mark
=== Marking for revision and deletion ===
!How to mark (insert anywhere in the article)
 
|-
If a page is '''up to date''' when you read it, please put the following tag at it's top (with the correct date):
|[[:Category:Candidate for deletion]]
 
|Article is not needed anymore
<code>
|<code><nowiki>{{Delete|to set an example|~~~~}}</nowiki></code>
<nowiki>{{Lastrevision | date = 15. 1. 2012}}</nowiki><br>
|-
</code>
|[[:Category:NPA]]
 
|The article '''N'''eeds '''P'''ictures '''A'''dded
If a page is '''out of date''' or doesn't have a reason for existing, add one of the following tags to the top of the page:
|<code><nowiki>{{NPA}}</nowiki></code>
 
|-
<code>
|[[:Category:Citation needed]]
<nowiki>{{Needs revision}}</nowiki><br>
|Rarely used, as this wiki doesn't have a very academic style
</code>
|<code><nowiki>{{Citation needed}}</nowiki></code>
<code>
|-
<nowiki>{{Needs revision | reason = Out of date.}}</nowiki><br>
|[[:Category:Needs_revision]]
</code>
|Something is wrong, needs to be checked, rewritten or any other kind of work like formatting
or<br>
|<pre><nowiki>{{Needs revision
<code>
|reason=Full review required
<nowiki>{{delete}}</nowiki>
|user=~~~~
</code>
}}</nowiki></pre>
 
|-
==Talk Pages==
|[[:Category:Needs_critical_revision]]
When write on a page or user's '''talk page''' (for example [[Talk:Main_Page]]), there are a few things you need to know.
|Large rewrites needed
 
|<pre><nowiki>{{Needs critical revision
===Signature===
|reason = The guide on this page is out of date.
Always end of your message with your signature, so everyone knows who wrote what (without checking the edit history).<br>
|user = ~~~~
This can be done easily by using <code><nowiki>~~~~</nowiki></code> after your message. You can customize your signature on your [[Special:Preferences|user preferences page]].
}}</nowiki></pre>
 
{|class="wikitable" style="font-size:90%; border: 2px solid darkgrey" cellpadding="3" cellspacing="0" colspan="2" ||
|-
|-
!Code:
|[[:Category:Stub]]
||
|For articles without content / barebones structure.
<nowiki>Look. ~~~~</nowiki>
|<code><nowiki>{{Stub|to set an example|~~~~}}</nowiki></code>
|-
|-
!Result:
|[[:Category:Outdated images]]
||
|Image is outdated
Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET)
|<code><nowiki>{{Outdated}}</nowiki></code>
|}
|}
 
{| class="wikitable mw-collapsible mw-collapsed" width="100%"
===Indentation===
! Example: Needs revision
When replying to another user's message, be sure to ''indent'' your message so it is visibly a reply to the above message.<br>
This is done by simply adding <code><nowiki>:</nowiki></code> at the start of the line will cause this effect.
 
{|class="wikitable" style="font-size:90%; border: 2px solid darkgrey" cellpadding="3" cellspacing="0" colspan="2" ||
|-
!Code:
||
<nowiki>Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET)</nowiki><br>
<nowiki>:At what? ~~~~</nowiki>
|-
|-
!Result:
|{{Needs revision|reason=REASON}}
||
Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET)
:At what? - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:40, 30 November 2013 (CET)
|}
|}
 
{| class="wikitable mw-collapsible mw-collapsed" width="100%"
===Headline===
! Example: Flag for deletion
If you are starting a new topic, add a headline with the name of the topic. If a talk page is used a lot, it can become confusing if the topics aren't separated with headlines. It also allows for section editing, which makes editing long talk pages a lot easier.<br>
This is one of the most basic things on a wiki, and are used by typing <code><nowiki>==Topic==</nowiki></code> on the line above your message.
 
{|class="wikitable" style="font-size:90%; border: 2px solid darkgrey" cellpadding="3" cellspacing="0" colspan="2" ||
|-
|-
!Code:
|
||
{| width="60%" bgcolor="#ff6666" align="center"
<nowiki>==Look at this tutorial==</nowiki><br>
|align="center"|[[File:Dead.png]] <font size='4'>'''THIS PAGE HAS BEEN MARKED FOR DELETION'''</font> [[File:Dead.png]]
<nowiki>Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET)</nowiki><br>
<nowiki>:At what? - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:40, 30 November 2013 (CET)</nowiki><br>
<nowiki>::This tutorial I made. ~~~~</nowiki>
|-
|-
!Result:
|align="center"|For the following reason: ''{{{1|REASON}}}''. Tagged by: {{{2|NAME}}}[[Category:candidate for deletion|{{FULLPAGENAME}}]]
||
|}
<font size="4">Look at this tutorial</font> <nowiki>[</nowiki><span style="color: blue">edit</span><nowiki>]</nowiki>
----
Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET)
:At what? - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:40, 30 November 2013 (CET)
::This tutorial I made. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:45, 30 November 2013 (CET)
|}
|}
=== New pages ===
New content is constantly being added to Space Station 13, which requires new tutorials and guides and information. Before you begin a new page, '''please search thoroughly and completely for an existing or similar page to avoid creating duplicate guides or pages'''. If you can't find it or anything related to it, you are clear to start a page yourself! This can be done simply by plugging in the title of the page you would like to create in the Search Bar in the top right - if nothing is found in the Wiki databanks, you will be prompted to create a new page under that title; this will generate a blank page that you can begin formatting and filling in with your information. It is highly recommended that you first assess the type of page you are trying to make, i.e. is it a new guide? is it a new job? and then navigate to pages that exist within that same familial typing and copy the formatting over to your new page. This will save you a lot of work in the end, as well as standardize the formatting across your new page and existing ones of the same type.
=== Give Me Moar ===
Still not enough huh? Well here we go: [[:Category:WikiCoordination]] is a used as an internal starting-point for coordinating things in need of doing. At this point you might want to have a talk with the wiki staff about coordinating your efforts with them.
Other useful links include:
* '''Categories:''' [[Special:Categories|Used]], [[Special:UnusedCategories|unused]] and [[Special:WantedCategories|wanted]]
* '''Templates:''' [[Special:MostLinkedTemplates|Used]], [[Special:UnusedTemplates|unused]] and [[Special:WantedTemplates|wanted]]
* '''Files:''' [[Special%3AListFiles|All]], [[Special:UnusedFiles|unused]] and [[Special:WantedFiles|wanted]]
* '''All pages:''' [[Special:AllPages|All existing pages]] and [[Special:WantedPages|Wanted pages]]
== [[Styleguide|Guidelines]] ==
As often in life, ''what'' you do is as important as ''how'' you do it. These are not ''enforced'' rules, but use your best judgment (or preferably just ask) when to divert from these suggestions.


== Jokes ==
Really, '''[[Styleguide|READ THEM]]'''
== Advanced Topics ==
The following guides should eventually be moved to separate articles to not overload this guide.
=== Guide to Writing and Revising a Guide ===
Always keep in mind what the guide pages on this Wiki are for. They are so new players can quickly glean relevant information about the role they have chosen, or been chosen for, or about mechanics of the game on the whole.


Some pages are intended to be entertaining but when writing guides, remember that a newbie might not realize something is a joke or sarcasm, even if it's blatantly obvious to the rest of us. Think where jokes fit and where they don't. Also, if you're updating someone else's joke, think whether yours is actually funnier.
'''A good guide generally consists of:'''
* A brief introduction or overview of what the guide is going to be describing or accomplishing.
* A detailed run down of the various topics mentioned above, with sectioning and sub-sectioning for clarity and ease of access.
* Images and visual information where needed and appropriate.
* Reference links or further reading material to give a grasp of content adjacent or connected to the topic at hand - for example, the Cook job page has links to the Guide to Food and Guide to Drinks, as these are relevant.
* A conclusion which ties together all the above information and seeks to reiterate the material covered prior.
Poorly formatted or written guides can make it hard to convey relevant information and may be discouraging to newer players.


== Guide to Writing and Revising a Guide ==
'''Extra tips:'''
Always keep in mind what these guides are for; they're so newbies can quickly skim across them so they can have half an idea what they've just been selected for.
* Keep your facts correct and as the primary focus.
 
* If you are writing a basic guide, '''keep it basic''', and put the advanced topics on a separate page.
'''A good guide needs, by order:'''
* Make use of formatting, tables, white space, headings, and other methods to draw attention and give direction to critical points of information
* A brief one-two paragraph description of what the mode is.
=== Images ===
* A bullet point list of short to the point key points of key mechanics, these should be no longer than two sentences each. And remember: key points means the important shit you need to know to atleast bumble fuck your way around at round start, you should be able to read and understand it within 5 minutes.
What would articles be without proper icons of things like ingame-items.
* A more meaty section detailing the game mechanics in depth (this is where you explain what all runes and talismans do, including the ones that are barely used), it should still be clear and concise.
* A summary of the key points, yes - one at the start and one at the end. Reiteration helps to hammer things home. This one will more or less be simple list to remind the reader of things, it wont explain them.
* Further reading - this is where you link to the pages that detail advanced strategies for fighting for and against the cult. No you don't put them on the main page because that will clutter it.
* Links! Remember to add links to [[modes]], [[Guides#Antagonist Guides|antagonist roles]], [[jobs]], items and [[guides]] you mention! Simply do it when you re-read your content before submitting.
 
 
A bad guide is one that's a giant wall of text that's overly fluffed up and full of opinionated bullshit.<br>
A newbie is going to take one glance at it and shit their pants out of fright, and advanced player is just going to go "Yeah.... I'm not reading someone's sperg page".
 
[At the moment]{{citation needed}} [[Guides#Security guides|Security's guides]] are good. [[Space Law]] is unfluffed and tells plainly the basics of what a [[security officer]] needs to know to start patrolling and robusting greyshirts. The [[Guide to security]] is more fleshed out and explains things more in depth and lists strategies to counter antags.<br>
[[Cult]], [[Malf]], and [[Traitor]] are bad because they're giant imposing walls of text that reads like a newspaper: squished up text that obscures the facts with needless opinions and blurbs that you don't need to know off the bat.
 
'''So remember:'''
* Facts good, opinions bad.
* Keep your facts clear of irrelevant fluff and other bullshit.
* Keep the basic guide basic, keep the advanced stuff on a separate page.
* Important stuff first, depth and explanation and unimportant things second.
* White space, tables, sections, and formatting are essential for ease of reading. We're not print media, space isn't at a premium so use it freely.
* Links!
* I just used the above template to write this guide.
 
== Useful pages ==
 
'''Categories:''' [[Special:Categories|Used]], [[Special:UnusedCategories|unused]] and [[Special:WantedCategories|wanted]]
 
'''Templates:''' [[Special:MostLinkedTemplates|Used]], [[Special:UnusedTemplates|unused]] and [[Special:WantedTemplates|wanted]]
 
'''Files:''' [[Special%3AListFiles|All]], [[Special:UnusedFiles|unused]] and [[Special:WantedFiles|wanted]]
 
'''All pages:''' [[Special:AllPages|All existing pages]] and [[Special:WantedPages|Wanted pages]]
 
== /tg/station wiki specific markup ==
 
To create a BYOND hyperlink, use the <nowiki><byond></nowiki> tags. The specific syntax is <nowiki><byond server=servername.com port=4000>Link text here</byond></nowiki>.


The wiki also supports the features of the [http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions ParserFunctions] extension.
If you have image files to attach, you can upload them via the [[Special:Upload|Upload File]] link on the left toolbar (also accessed by Alt-Shift-U keyboard command), and then add them to the page they're intended for.  


== Spambot protection - Security question ==
For item images, it is appreciated if the image has a blank background and is in the .gif or .png format.


To create an account you will need to provide the answer of one of two questions. One being about the game engine (byond) and the other about the chan board (tg). The answers to the questions are in brackets.
For most ingame assets, the easiest way to add images of them is to download the [[Downloading the source code#Downloading|source code]], open the icons .dmi files and export images as .gif's or .png's from there.
[[File:DreamMaker_opened_environment.png|thumb|alt=Dream Maker with opened yogstation.dme|Dream Maker with opened yogstation.dme]]
==== Simple Icons ====
Here is a short guide of how to extract, upload and use icons:
# [[Downloading the source code|Download the source code]]
# Start the program '''Dream Maker''' (was installed with BYOND)
# Menu > File > Open Environment > ''your_path_to_the_code''/'''yogstation.dme'''<br>
# Navigate the filestructure on your left to your icon, for example '''icons\obj\hydroponics\harvest.dmi'''
# Rigclick your image on the right, for example '''firelemon''' > Export
# Make sure to save as '''*.png''' for normal icons and '''*.gif''' for animated icons
# Go to the [[Special:Upload|Upload]] of the wiki
# Select your file and upload it. Make sure to leave a comment like "Extracted from icons/obj/.../xxx.dmi"
# Write down the name of your uploaded file. In this example File:Firemelon.png
# Go to the article you want to edit and insert your image with <nowiki>[[File:Firemelon.png]]</nowiki>
==== Animations of combined icons ====
Some icons are used together to create animations. Do this to combine them into an animated gif:
# Open the appropriate *.dmi like explained for simple icons. We will use '''icons/obj/hydroponics/growing.dmi''' as an example
# Select multiple images with Ctrl-Leftclick
# Rightclick > Combine > 1 direction (The other options are used for things like walking-animations for different directions)
# If the images are not in the right order: Rightclick > Edit Pixels/Movie
# Use Shift+Drag to swap the images on the bottom into your preferred order
# Exit the editing view via the Back-button (right bottom)
# Rightlick > Export > Safe as gif
# (optional) Revert the Image-combination with Rightclick > Split > Split animation frames
# To adjust the animation-speed of your gif you have to edit it. In this example we will be using https://ezgif.com/maker
## Upload your gif
## Change the delay of the frames (I usually go for 50)
## Set a tick at 'don't stack frames'
## Make and download the gif
## View it to make sure it works as needed
==== Auto extraction of icons ====
You can extract all icons of a *.dmi (as png) with this little python-tool: https://github.com/alexkar598/DMIExport/releases/tag/1.0.0
Animated icons will be extracted by frames as separate images.


You will need to provide the answer to the question every time you make an edit as an unregistered user. The question is just above the edit content field.
'''Beware:''' Make sure to review the results, as icon names can get mismatched.
==== Images of locations / maps ====
There are multiple ways to make proper images of locations and maps:
* '''DreamMaker:'''
** Select File (like _maps/RandomRuins/LavaRuins/lavaland_surface_ash_walker1.dmm )
** The view automatically switches from the File-tab to the Object-tab
** Overwrite all areas with '''area/space''' to get a better view
** If some things like '''no_lava''' are bothering you: '''Select all tiles > rightclick > Find replace in Selection''' to replace "no_lava" with ""
** Take screenshots
* https://fastdmm2.ss13.io/ Very useful if you intend to do multiple locations. You can pan the view with the middle mouse button or the arrow-keys.
** Open with Chrome / Firefox. Microsoft Edge does not work as of 2020.05.04
** Load up the repo
*** Make sure the repository is specified in the top textfield: <code>yogstation13/yogstation</code>
*** Click on '''Open Github repository'''
*** Choose the branch <code>master</code> and click on '''Ok'''
*** Wait for '''yogstation.dme''' to load. This might take a minute
** Open the map file you want: '''File > Open > _maps > ...'''
** Set the settings you want to show on the left hand side by clicking on the eye-icons next to the nodes
*** You can also <kbd>ctrl</kbd> + <kbd>shift</kbd> click on items to jump to them on the left panel
*** Only have to do this step once since it saves your setting between the maps you load
*** Disable '''Options > Frame Areas'''
*** You will most likely want to disable a bunch of things to make adding transparency easier:
**** '''/area'''
**** '''/obj/effect/mapping_helpers/no_lava'''
**** '''/turf/open/space'''
** Take screenshots
** Open screenshot in [https://www.gimp.org/ GIMP]
** Layer-window >Rightclick on your layer > add alpha layer
** Colors > Color to Alpha
*** Color: #444488
*** Both sliders to 0
** Image > Trim to content
** (optional) Save (<kbd>Ctrl</kbd> + <kbd>S</kbd>)
** Export as png (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>E</kbd>)
* '''Dream Daemon:''' Very tedious, but it will look better, since sprites for chasms etc. will properly connect.
** Start your local server
** Join with your '''BYOND client'''
** '''Tab Admin > Aghost''' to start ghosting (Shortcut: <kbd>F5</kbd>)
** Adjust your view
*** Disable the ingame-ui
*** '''Tab Admin > Stealth Mode''' to turn your ghost invisible
*** Set '''Tab Ghost > View Range''' or '''Tab Special Verbs > Change View Range''' to increase your field of view
*** Adjust the shadows by repeatedly clicking '''Tab Ghost > Toggle Darkness'''
** Go places or spawn in your maps / locations with '''Tab Debug > Map template - Place'''
** Take screenshots (Shortcut <kbd>F2</kbd>)
==== Images of people ====
Getting images of people is more difficult than for objects, since people consist of all kinds of parts. This means you need ingame-screenshots:
* Start a local server with '''Dream Daemon'''
* Join with your '''BYOND client'''
* (optional) Pick a jobs with the clothes you want for your screenshots
* (optional) Build a 3x3 of tables and climb on them. The best place to do this is the lockerroom near arrivals. The even background of the tables will make it so much easier to crop out the background later.
* Rightclick your mob > Your name > View Variables
* Use the '''"select option"-dropdownmenu''' to change your mobtype
** Set species
** Make cyborg
** Other options include "Make alien" and "Make slime"
* Use the '''"select option"-dropdownmenu''' to modify your body
** Modify bodypart
** Modify organs
* Make sure the area is well-lit
** '''Tab Admin > Secrets > Fix all lights'''
** '''Tab Admin > Secrets > Make all areas powered'''
* Take screenshots (Shortcut F2)
=== Checking the game-code ===
So somebody told you to ''"RTFM"'' or ''"do a code-dive"''? Congratulations, you managed to either ask a rude person a really obvious question, or you breached into advanced territory. It is hard to find someone knowledgable of everything in the game, and even skilled players might have outdated information. The only way to be sure is to read the game-code. Yes code, like in programming. You don't need to be able to program yourself, but it '''really''' helps.  


The easiest way to read the code is using the searchbar on [{{Constant/Giturl}} github].
[[Category:Guides]] [[Category:Game Resources]]
[[Category:Guides]] [[Category:Game Resources]]
{{Contribution guides}}
{{Contribution guides}}

Latest revision as of 20:16, 28 September 2023

Foreword

Welcome to contributing to the Yogstation Wiki - we're happy to have you here. This wiki would not be possible to maintain without the help and dedication of players and staff alike. In a game as complex as Space Station 13, having an up to date wiki is critical to properly enjoy it. Thank you for taking your time.

Getting Started

Your account

As a first order of business, in order to edit pages a wiki account is required - this is a method to reduce the possibility of grief showing up on the wiki itself. To obtain a wiki account, use the Create account button at the top right of the page. You will need to confirm your email address before you will be able to make changes to the wiki.

In order to both maintain a minimum level of quality on the wiki and to limit the damage of grief, edits made by new accounts will not be immediately visible, once you save an edit, the wiki staff will get a notification of your edit so that your edit may be reviewed, potentially edited and then approved or rejected. During the review process, you will still be able to further edit the page while your edit is being reviewed but try to avoid submitting incomplete edits. The wiki staff patrols change logs to correct small errors and combat intentional misinforming edits, so please be mindful and be ready to explain your edit if it raises a red flag. The best way to prevent misunderstandings is adding proper summaries for all your edits. Once you've created your account, don't be afraid to jump in and start correcting and adding to pages.

Once you have a few edits under your name, feel free to apply to join the wiki team at https://forums.yogstation.net/forums/wiki-team-applications.290, this will allow you to create new pages and bypass the need to have your edits manually reviewed by the wiki staff.

Wikicode

Wikicode is the syntax used by all Wikipedias, including this one. It is not hard to pick up: Don't hesitate to read our internal guide or the wikipedias official article. The syntax and options might seem daunting at first, but remember that you can edit allmost all articles with this 5 minute crash course:

Most used wikicodes
Formatting Code Example
Bold
Quite a '''bold''' move, Mr Bond
Quite a bold move, Mr Bond
Italic
Do you ''really'' want that drink?
Do you really want that drink?
Italic & bold
No! '''''Please'''''! NO!
No! Please! NO!
Sections
= Level 1 =
== Level 2 ==
=== Level 3 ===
==== Level 4 ====
===== Level 5 =====
Wiki header example.png
Link (Internal)
Check [[Wikicode]] or [[Wikicode|click here fore more]]
Check Wikicode or click here fore more
Link (External)
http://en.wikipedia.org/wiki/Help:Wiki_markup
http://en.wikipedia.org/wiki/Help:Wiki_markup
Link (External, Custom)
[http://en.wikipedia.org/wiki/Help:Wiki_markup click me]
click me
List (Unordered)
* Talk shit
* Get hit
  • Talk shit
  • Get hit
List (Ordered)
# Stop
# Drop
# Roll
  1. Stop
  2. Drop
  3. Roll

Wikicode is what salt is for food. Of course you can cook without salt, but well-prepared foods and texts are clearly more enjoyable. Instead of having a page be a long meandering paragraph, Wikicode allows information to be broken up and changed in appearance for greater clarity, such as the section headings shown in this guide.

It is allright if you really don't want to deal with wikicode. You can still help by writing and correcting texts and have the wiki staffers add the formatting later. Just add something like TODO - NEEDS FORMATTING in your edit-summary to make it easier to detect.

Questions?

There are a few concepts that drive Wiki functionality, and this guide will attempt to touch on the very basics that you'll need to get in and get going. If you have questions regarding more advanced topics, you are allways welcome to ask in the above mentioned #wiki-public.

What needs doing?

The Yogstation Wiki is an utterly massive project, and the active wiki staff team is small, comparatively. Most everywhere you look there is out-of-date information, duplicate guides, broken links, unintelligible references. The Wiki Team attempts to keep core pages up to date and patrolled, but there are many pages on the periphery in dire need of attention.

A good place to start is by analysing your strengths and the completeness of your knowledge within the context of Space Station 13, and then attempting to revise or update material relevant to that. If you are a person who plays Roboticist every round, then take a moment to look over the Roboticist page and verify the information there - add tips and tricks that you've picked up; publish a new guide page for some advanced facet of the position - in short, play to your strengths when editing and contributing, otherwise information can be left worse off than when it started.

Content revisions

Once you are done reviewing your favourite articles / randomly browsing the wiki, check its list of pages which need revisions: Category:Needs revision. Revision flags on Jobs or Guides tend to take highest priority, as these are the pages utilized the most by Wiki visitors.

As a recommendation, if you wish to work on a page uninterrupted and not worry about other users editing the same thing while you are working, you can mirror the page in to your personal sandbox area or anywhere in your own pages. This will create a "localized" copy that you can change unfettered by interference by others.

Additionally, if you are revising a page, PLEASE put a summary in the Summary section of your editing window towards the bottom of the page. This will help Wiki Staff immensely when patrolling the moderation queue.

Mark articles

Whenever you find a page that needs some work you can't do / you want to do later, make sure to mark it. Marking an article will not only insert a nice obvious note, it will temporarily add the page to a category. These categories serve as todo-lists, which is very convenient. As long as you don't mark every single page in existence, this alone will be helpful.

When tagging articles, make sure to use ~~~~ wherever possible, since this will automatically insert your post-details like this: Helpful Herbert (talk) 23:30, 24 April 2020 (UTC).

Category When to mark How to mark (insert anywhere in the article)
Category:Candidate for deletion Article is not needed anymore {{Delete|to set an example|~~~~}}
Category:NPA The article Needs Pictures Added {{NPA}}
Category:Citation needed Rarely used, as this wiki doesn't have a very academic style {{Citation needed}}
Category:Needs_revision Something is wrong, needs to be checked, rewritten or any other kind of work like formatting
{{Needs revision
|reason=Full review required
|user=~~~~
}}
Category:Needs_critical_revision Large rewrites needed
{{Needs critical revision
|reason = The guide on this page is out of date.
|user = ~~~~
}}
Category:Stub For articles without content / barebones structure. {{Stub|to set an example|~~~~}}
Category:Outdated images Image is outdated {{Outdated}}
Example: Needs revision
Pen.png This page needs revising!

The following page is out of date and/or needs to be revised. If the page's guide needs revision, see here for an example.
The revision reason is: "REASON"
Marked by: "Unknown"



Example: Flag for deletion
Dead.png THIS PAGE HAS BEEN MARKED FOR DELETION Dead.png
For the following reason: REASON. Tagged by: NAME

New pages

New content is constantly being added to Space Station 13, which requires new tutorials and guides and information. Before you begin a new page, please search thoroughly and completely for an existing or similar page to avoid creating duplicate guides or pages. If you can't find it or anything related to it, you are clear to start a page yourself! This can be done simply by plugging in the title of the page you would like to create in the Search Bar in the top right - if nothing is found in the Wiki databanks, you will be prompted to create a new page under that title; this will generate a blank page that you can begin formatting and filling in with your information. It is highly recommended that you first assess the type of page you are trying to make, i.e. is it a new guide? is it a new job? and then navigate to pages that exist within that same familial typing and copy the formatting over to your new page. This will save you a lot of work in the end, as well as standardize the formatting across your new page and existing ones of the same type.

Give Me Moar

Still not enough huh? Well here we go: Category:WikiCoordination is a used as an internal starting-point for coordinating things in need of doing. At this point you might want to have a talk with the wiki staff about coordinating your efforts with them. Other useful links include:

Guidelines

As often in life, what you do is as important as how you do it. These are not enforced rules, but use your best judgment (or preferably just ask) when to divert from these suggestions.

Really, READ THEM

Advanced Topics

The following guides should eventually be moved to separate articles to not overload this guide.

Guide to Writing and Revising a Guide

Always keep in mind what the guide pages on this Wiki are for. They are so new players can quickly glean relevant information about the role they have chosen, or been chosen for, or about mechanics of the game on the whole.

A good guide generally consists of:

  • A brief introduction or overview of what the guide is going to be describing or accomplishing.
  • A detailed run down of the various topics mentioned above, with sectioning and sub-sectioning for clarity and ease of access.
  • Images and visual information where needed and appropriate.
  • Reference links or further reading material to give a grasp of content adjacent or connected to the topic at hand - for example, the Cook job page has links to the Guide to Food and Guide to Drinks, as these are relevant.
  • A conclusion which ties together all the above information and seeks to reiterate the material covered prior.

Poorly formatted or written guides can make it hard to convey relevant information and may be discouraging to newer players.

Extra tips:

  • Keep your facts correct and as the primary focus.
  • If you are writing a basic guide, keep it basic, and put the advanced topics on a separate page.
  • Make use of formatting, tables, white space, headings, and other methods to draw attention and give direction to critical points of information

Images

What would articles be without proper icons of things like ingame-items.

If you have image files to attach, you can upload them via the Upload File link on the left toolbar (also accessed by Alt-Shift-U keyboard command), and then add them to the page they're intended for.

For item images, it is appreciated if the image has a blank background and is in the .gif or .png format.

For most ingame assets, the easiest way to add images of them is to download the source code, open the icons .dmi files and export images as .gif's or .png's from there.

Dream Maker with opened yogstation.dme
Dream Maker with opened yogstation.dme

Simple Icons

Here is a short guide of how to extract, upload and use icons:

  1. Download the source code
  2. Start the program Dream Maker (was installed with BYOND)
  3. Menu > File > Open Environment > your_path_to_the_code/yogstation.dme
  4. Navigate the filestructure on your left to your icon, for example icons\obj\hydroponics\harvest.dmi
  5. Rigclick your image on the right, for example firelemon > Export
  6. Make sure to save as *.png for normal icons and *.gif for animated icons
  7. Go to the Upload of the wiki
  8. Select your file and upload it. Make sure to leave a comment like "Extracted from icons/obj/.../xxx.dmi"
  9. Write down the name of your uploaded file. In this example File:Firemelon.png
  10. Go to the article you want to edit and insert your image with [[File:Firemelon.png]]

Animations of combined icons

Some icons are used together to create animations. Do this to combine them into an animated gif:

  1. Open the appropriate *.dmi like explained for simple icons. We will use icons/obj/hydroponics/growing.dmi as an example
  2. Select multiple images with Ctrl-Leftclick
  3. Rightclick > Combine > 1 direction (The other options are used for things like walking-animations for different directions)
  4. If the images are not in the right order: Rightclick > Edit Pixels/Movie
  5. Use Shift+Drag to swap the images on the bottom into your preferred order
  6. Exit the editing view via the Back-button (right bottom)
  7. Rightlick > Export > Safe as gif
  8. (optional) Revert the Image-combination with Rightclick > Split > Split animation frames
  9. To adjust the animation-speed of your gif you have to edit it. In this example we will be using https://ezgif.com/maker
    1. Upload your gif
    2. Change the delay of the frames (I usually go for 50)
    3. Set a tick at 'don't stack frames'
    4. Make and download the gif
    5. View it to make sure it works as needed

Auto extraction of icons

You can extract all icons of a *.dmi (as png) with this little python-tool: https://github.com/alexkar598/DMIExport/releases/tag/1.0.0 Animated icons will be extracted by frames as separate images.

Beware: Make sure to review the results, as icon names can get mismatched.

Images of locations / maps

There are multiple ways to make proper images of locations and maps:

  • DreamMaker:
    • Select File (like _maps/RandomRuins/LavaRuins/lavaland_surface_ash_walker1.dmm )
    • The view automatically switches from the File-tab to the Object-tab
    • Overwrite all areas with area/space to get a better view
    • If some things like no_lava are bothering you: Select all tiles > rightclick > Find replace in Selection to replace "no_lava" with ""
    • Take screenshots
  • https://fastdmm2.ss13.io/ Very useful if you intend to do multiple locations. You can pan the view with the middle mouse button or the arrow-keys.
    • Open with Chrome / Firefox. Microsoft Edge does not work as of 2020.05.04
    • Load up the repo
      • Make sure the repository is specified in the top textfield: yogstation13/yogstation
      • Click on Open Github repository
      • Choose the branch master and click on Ok
      • Wait for yogstation.dme to load. This might take a minute
    • Open the map file you want: File > Open > _maps > ...
    • Set the settings you want to show on the left hand side by clicking on the eye-icons next to the nodes
      • You can also ctrl + shift click on items to jump to them on the left panel
      • Only have to do this step once since it saves your setting between the maps you load
      • Disable Options > Frame Areas
      • You will most likely want to disable a bunch of things to make adding transparency easier:
        • /area
        • /obj/effect/mapping_helpers/no_lava
        • /turf/open/space
    • Take screenshots
    • Open screenshot in GIMP
    • Layer-window >Rightclick on your layer > add alpha layer
    • Colors > Color to Alpha
      • Color: #444488
      • Both sliders to 0
    • Image > Trim to content
    • (optional) Save (Ctrl + S)
    • Export as png (Ctrl + Shift + E)
  • Dream Daemon: Very tedious, but it will look better, since sprites for chasms etc. will properly connect.
    • Start your local server
    • Join with your BYOND client
    • Tab Admin > Aghost to start ghosting (Shortcut: F5)
    • Adjust your view
      • Disable the ingame-ui
      • Tab Admin > Stealth Mode to turn your ghost invisible
      • Set Tab Ghost > View Range or Tab Special Verbs > Change View Range to increase your field of view
      • Adjust the shadows by repeatedly clicking Tab Ghost > Toggle Darkness
    • Go places or spawn in your maps / locations with Tab Debug > Map template - Place
    • Take screenshots (Shortcut F2)

Images of people

Getting images of people is more difficult than for objects, since people consist of all kinds of parts. This means you need ingame-screenshots:

  • Start a local server with Dream Daemon
  • Join with your BYOND client
  • (optional) Pick a jobs with the clothes you want for your screenshots
  • (optional) Build a 3x3 of tables and climb on them. The best place to do this is the lockerroom near arrivals. The even background of the tables will make it so much easier to crop out the background later.
  • Rightclick your mob > Your name > View Variables
  • Use the "select option"-dropdownmenu to change your mobtype
    • Set species
    • Make cyborg
    • Other options include "Make alien" and "Make slime"
  • Use the "select option"-dropdownmenu to modify your body
    • Modify bodypart
    • Modify organs
  • Make sure the area is well-lit
    • Tab Admin > Secrets > Fix all lights
    • Tab Admin > Secrets > Make all areas powered
  • Take screenshots (Shortcut F2)

Checking the game-code

So somebody told you to "RTFM" or "do a code-dive"? Congratulations, you managed to either ask a rude person a really obvious question, or you breached into advanced territory. It is hard to find someone knowledgable of everything in the game, and even skilled players might have outdated information. The only way to be sure is to read the game-code. Yes code, like in programming. You don't need to be able to program yourself, but it really helps.

The easiest way to read the code is using the searchbar on github.

Contribution guides
General Hosting a server, Setting up git, Guide to GitKraken, Downloading the source code, Guide to contributing to the game, Reporting issues, Game resources category, Guide to changelogs
Database (MySQL) Setting up the database, MySQL
Coding Understanding SS13 code, SS13 for experienced programmers, Text Formatting
Mapping Guide to mapping, Room Structure, Map merger
Spriting Guide to spriting
Wiki Guide to contributing to the wiki, Wikicode, Styleguide