Участник:E25/Sandbox

https://tgstation13.org/wiki/User:E25/Sandbox?action=purge

Welcome

So you want to contribute to the wiki, eh? Welcome to our humble, outdated, broken and mostly coblled together wiki of the TerraGov Marine Corps fork of CM. Whether you're only wanting to do a few sections here and there or (dare I say) become a full on wiki maintainer, this guide will hopefully give you a general idea of how wreched eldrich abomination wikicode works.

Before that there are a few rules to keep in mind about Wikicode:

1. Things will sometimes break for no reason.
2. Some edits will take time and break the whole page or more. (See later on)
3. Anything advanced WILL require workarounds.
4. Wikicode is the BYOND of web development.

Now with that acknowledged, here's how to start:

First, you will need to link your byond account to your forum account to be able to edit the wiki. Instructions are on the forum. (This is due to us, you know, using their wiki as a base.)
In summary:

1. Create a Byond account (if you haven't).
2. Create a tgstation13 forum account.
3. Link those accounts. Linking can be done in-game by clicking the OOC tab and "Link Forum Account", or with the link https://tgstation13.org/phpBB/linkbyondaccount.php .
4. You should now be able to see "edit" buttons on the wiki.

Concerns

Can my poor single-cell organism of a brain comprahend Wikicode? - If you know a bit of basic HTML and CSS you should be more than ready to go. Even if you have no prior experience some guy in his last summer break/holiday was able to learn it before becoming offically unemployed.
Does contributing to the wiki requires constant, long term dedication? - Pff, as if. People will be greatful if you get anything done, plus once the wiki gets to a usable state it's likely that most work will be just changing icons for updated gun designs and whatnot, with the rare addition here and there. CIMEX IS NOT REAL, CIMEX DOES NOT EXIST

Wikicode

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 here, or read the Wikipedia page here. If you don't want to spend your life learning this markup, then fret not, you can still help.

What needs doing?

New pages

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. We welcome all contributions to the wiki and trust all edits to be made in good faith. As a recommendation if you wish to work on a page uninterrupted and not worry about other users edits while working, make it in your personal 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

A list of pages which need revisions can be found here

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.

Images

Uploading new images

If you have new, 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 source code, open the icons .dmi files and export images as .gif's or .png's from there.

Then upload them here: https://tgstation13.org/wiki/Special:Upload

Updating existing images

It is possible for an image to become depreciated following an update to the source code. To update an existing, obsolete image you can visit the upload page, upload your new image, and then add the filepath of the old image you want to substitute. You can also visit its page on the wiki (by either clicking the image itself or searching for its name using the "File:" prefix in the searchbar), click on "upload a new version of this file" under "File history", and selecting your new image on the upload page.
All depreciated versions of the image will remaing in the File's history page for posterity.
IMPORTANT: Images can only be updated with files of the same format: .png images cannot be updated to .gif, and viceversa. This is because files are saved on a page which include their format in its name.

Tabs

Any page can have tabs added to it through the <tabs> function. This function has the known problem of displaying correctly in a page edit preview, but incorrectly once an edit is applied. To fix this, the page's cache has to be flushed; One easy method is adding ?action=purge at the end of a page's URL. If the problem persist, leave a post on the forum.

Marking for revision and deletion

If a page is up to date when you read it, please put the following tag at it's top (with the correct date):

{{Lastrevision | date = 15. 1. 2012}}


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:

{{Needs revision}}
{{Needs revision | reason = Out of date.}}
or
{{delete}}

Talk Pages

When writing on a page or user's talk page (for example Talk:Main_Page), there are a few things you need to know.

Signature

Always end of your message with your signature, so everyone knows who wrote what (without checking the edit history).
This can be done easily by using ~~~~ after your message. You can customize your signature on your user preferences page.

Code:	Look. ~~~~
Result:	Look. - Deantwo (talk) 10:35, 30 November 2013 (CET)

Indentation

When replying to another user's message, be sure to indent your message so it is visibly a reply to the above message.
This is done by simply adding : at the start of the line will cause this effect.

Code:	Look. - [[User:Deantwo|Deantwo]] ([[User_talk:Deantwo|talk]]) 10:35, 30 November 2013 (CET) :At what? ~~~~
Result:	Look. - Deantwo (talk) 10:35, 30 November 2013 (CET) At what? - Deantwo (talk) 10:40, 30 November 2013 (CET)

Headline

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.
This is one of the most basic things on a wiki, and are used by typing ==Topic== on the line above your message.

Code:	==Look at this tutorial== 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. ~~~~
Result:	Look at this tutorial [edit] Look. - Deantwo (talk) 10:35, 30 November 2013 (CET) At what? - Deantwo (talk) 10:40, 30 November 2013 (CET) This tutorial I made. - Deantwo (talk) 10:45, 30 November 2013 (CET)

Jokes

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.

Guide to Writing and Revising a Guide

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.

A good guide needs, by order:

• A brief one-two paragraph description of what the mode is.
• 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.
• 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 game modes, 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.
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]} 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.
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: Used, unused and wanted

Templates: Used, unused and wanted

Files: All, unused and wanted

All pages: All existing pages and Wanted pages

/tg/station wiki specific markup

To create a BYOND hyperlink, use the <byond> tags. The specific syntax is <byond server=servername.com port=4000>Link text here</byond>.

The wiki also supports the features of the ParserFunctions extension.

Cimex strains

	Name: Chrager	Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris molestie ante vel urna ultrices, sit amet aliquet ex sodales. Nunc fringilla neque sit amet urna tempus, quis porttitor justo tincidunt. Phasellus lacinia viverra cursus. Sed ultricies placerat eleifend. Vestibulum velit dui, consectetur sed ultrices non, lacinia ut eros. Nulla sit amet sem nec ligula fermentum tristique id sit amet ipsum. Fusce ut elementum tellus, eget imperdiet arcu. Praesent ac tristique nisi. Maecenas auctor elit enim, eget sodales lorem molestie vestibulum. Nullam congue tortor ut tellus gravida, non facilisis nisl pharetra. Nunc tincidunt massa quis justo pretium, vitae dignissim erat viverra.
	Stats: Health: 100 Armor: 100 Melee damadge: 100

	Generic Cimex Health: 100 Armor:Hover here Slashes to gib a muhreen: One Jiheisho's wet dream? Yes	Uuuuuuuh its a cimex bug thingy Uuuuuh.... Totally not stolen from EDF with Natural selection 2 and Zerg combined.
Copy paste field
A		B	C

Gun Template

Weapon:	Description:
T-12 assault rifle	The T-12 assault rifle used to be the TerraGov Marine Corps standard issue rifle before the T-18 carbine replaced it. It's however still used widely despite that. The gun itself is very good at being used in most situations however it suffers in engagements at close quarters and is relatively hard to shoulder than some others. Ammo: T-12 assault rifle magazine Holds fifty(50) 10x24mm caseless rifle rounds.
Gun name	Looks like someone failed to write a description Ammo: {{{mag_name}}} Holds X number of boolets, make you go 'Ow'.

Meaning of Parameters

image is the icon for the gun
image_size is the size of the gun icon, 128px by default
name name of the weaon
anchor anchor point for linking
desc description for the weapon
mag_image icon the for magainze
mag_image_size icon size for the magainze, 64px by default
mag_name name for the magazine
mag_anchor anchor for the mag mag_desc description for the magazine