Guide to contributing to the game
This is more of an index to contributing to the game. Note that your solutions might not be used and it is possible for them to even be ridiculed. Please do not take offense and try to get as much constructive criticism out of it as you can. If your work does get put in, then congratulations!!
I hope this covers everything, if not, join coderbus on our Discord and ask there.
So you have an idea and don't know where to post it? Simple... check if it's already been submitted and if it hasn't, post it on our Git.
Icons, glyphs, sprites, animations... images
For an overview on spriting see our Guide to spriting.
You have what it takes to make a 32x32 pixel image actually look like something? We're always on the lookout for good spriters. Mention some admins on our Discord server with examples of your work and you'll be well on your way!
Development and contribution guides
FTL13 is an open source project, so anyone can contribute to it. Here are a few guides to help you if you're interested in contributing.
- Guide to Contributing to the Game
- Setting up Git (TG13 Source Control)
- Guide to working with /tg/station as an upstream repository
- Downloading the Source Code
- Understanding SS13 Code
- SS13 for Experienced Programmers
- Text Formatting
- More dev guides
Helping with SS13
See Setting up git to see how to commit your code, images, map updates or anything else to the repo.
|General||Hosting a server, Setting up git, Downloading the source code, Guide to contributing to the game, Reporting issues, Game resources category, Guide to changelogs|
|Database (MySQL)||Setting up the database, Working with the database, MySQL|
|Coding||Coding standards, Understanding SS13 code, SS13 for experienced programmers, Binary flags, Getting Your Pull Accepted, Guide to SNPC's, Text Formatting|
|Mapping||Guide to mapping, Map merger|
|Spriting||Guide to spriting|
|Wiki||Guide to contributing to the wiki, Wikicode|