# Goonstation Mapping Guide Goonstation doesn't have any specific mapping guide for our version of the game, however there is another highly detailed pair of guides made by san7890 of /tg/station. *Some elements of these may not apply to Goonstation code or practices. They also might not explain things necessary for our code.* [The first](https://hackmd.io/@tgstation/SyVma0dS5) is a comprehensive quick-start guide for anyone wishing to get their toes started in mapping but have absolutely zero idea where to start. [The second](https://hackmd.io/@tgstation/ry4-gbKH5) is more of a reference for those who already know how to map. If you are creating a new map for Goonstation, we have the following mapping guidelines that must be adhered to: ## Goonstation Mapping Guidelines {%hackmd @ZeWaka/dark-theme %} ## :heavy_exclamation_mark:Required:heavy_exclamation_mark: ###### These are fundamental map features that need to be checked to be working prior to submission. If these features do not work in the current codebase then your map PR will be **rejected** and ineligible for resubmission for a full calendar month. - Crates should be able to be ordered and sold from cargo, and arrive where expected **without player intervention**. Sitting in a few-tile conveyor "airlock" is fine, when waiting to come in or out (see Destiny), sitting outside/inside because the door did not open at all is not; missing the conveyor entirely is definitely not fine. - **Access levels** (for both doors and machinery, e.g. NanoMeds, AI turrets) should be correct. Missing a small handful is acceptable, but if excess access levels are incorrect (at the coders' discretion) the map will be rejected. Using the new access_spawn objects is required. :door: - Wiring and pipes (disposals, mail, brig, and morgue/crematorium, if present) should be **complete and error-free** for the most part. Obviously, it is okay if you are missing a single wire or something. - Note to above: SpyGuy and Haine made a wonderful tool to test disposal networks, it is included in the maps/ folder. - The disposals crusher blast door should be **closed** at round start (i.e. anything put down disposals at round start should not be crushed without someone opening the door). - **All areas** on station should be powered. APCs should be able to be charging if the appropriate SMES are set to output. :control_knobs: - Networked equipment should be **functional**. Specifically: telescience teleporter, communications consoles/dishes. - A tested and **functioning engine**, either thermo-electric or singularity. Please provide a screenshot of the engine output if thermo-electric (not necessarily at hellburn levels, but enough to meet the station/ship's power needs) - A **tested and functioning** toxins, if there is a toxins on the map. :biohazard_sign: - **Working** shuttles, for the escape shuttle, mining and visiting traders. Some maps can have different facing traders which are not present in the release. If so, please let the coders know when you are submitting your map. - **Correctly placed spawn points** for all present jobs, late-joiners, observers and so on. Failing to place these will result in players being dropped in to 1,1, which is a Bad Thing. - A **correctly linked** up syndicate listening post (i.e. nuclear operatives should be able to teleport there), and the airlocks should absolutely be correctly configured. - A **Correctly placed** landmark for the Map at 1,1. - **Windows** should be placed using the `obj/wingrille_spawn` spawners. - Non-full-tile windows ('thindows') should not be used, as they are being phased out. - **Firedoors** should be placed using the `obj/firedoor_spawn` spawners. - **Drains** scattered around, the path is `/obj/machinery/drainage`. ## Recommended ###### These are generally recommended map features that should probably be present in your map. If they are present, please ensure they work as intended. - An owlery or aviary. - Monkeys spawn landmarks (including a place for Stirstir in the brig) - Functioning buddy-paths. Including a tour guide written for Murray/Tour Buddy. - If you are using perspective walls, try to minimize placing objects on the south side of rooms. - Blobstart, peststart, and halloweenspawn landmarks. - Medbay and Security should be well-thought out, daresay more so than other departments. - Arrivals should have more than one exit, to prevent people from being unable to join the game. - Cloning should follow the style of modern maps and be mostly public access. - Feel free to take inspiration from other maps, but please don't copy paste large parts of them. - If you use random item spawners, try using the types of them that create specific numbers of items. This way you don't risk accidentally overloading rooms with items because RNG decided it to be so. - Spacemas ornaments are now automatically generated as appropriate. You must only manually add the tree somewhere, specifically the ephemeral subtype. ## Less critical but still important - **Make departments easily recognisable!** Use unique floor designs, wall signs, colored tiles, lines, and "doormats" to highlight to players where they are. Try to avoid big plain floors: spice things up with some checkered patterns or symbols. Different departments have different colours that they generally go by, so try to stick to those (blue for medbay (with black accents in robotics, and purple in pharmacy), purple for science and research, yellow for engineering, mining and mechanics and so on). Inside departments, use unique floor designs, coloured tiles, lines, and "doormats" (little spots of a department's colour outside their door). It just makes everything look nicer and more organised. - Break up empty hallways with things that seem realistic to have on that station. Donut2 is kind of old, so it has random tables and chairs, food and writing things. Things that make it feel lived in, stuff that adds flavour. - **Keep some crime in mind!** Maybe make some areas with less camera coverage, back rooms that are a little odd and musty. Maintainence especially should have little to no camera coverage. Give antags places to play with. Toilets and shower rooms in particular should not have cameras. - **Windows are important**. Walking through hallways shouldn't feel like a prison. People like to peer in and spy on the 'hard working' department workers, plus, it makes the shape of the map and layout of departments easier to interpret. It's easy to forget when you fly around in ghost mode, but visibility is quite important for hallways. The opposite applies too though, obviously don't make every wall out of glass. - **Choke points.** Try not to make entrances to important places like medbay and escape too narrow (unless you're making tiny maps on purpose, of course). It just makes everyone unhappy and then you'll end up engineers removing walls every round then someone pull requests a change-- just save yourself the hassle. In medbay especially, most people get treated right in the lobby or in the main foyer, don't make it too small. - Use default maintenance floors under windows (`/turf/simulated/floor/plating`). You gotta. - Don't forget to install toilets and showers! RP server enjoyers have gotta clean themselves, you know. - At the moment, admins are not really accepting maps unless they offer a big gameplay change (like Nadir). If you do decide to make a full map anyway, make sure you have dev support as early as possible. They like to have input on the way maps are made, and ones they had a hand in making are much, *much* more likely to get added to rotation than ones that pop up, fully made and realised, with not much room for changing. If you feel like your map does fill a niche, you still have to check with admins to see whether they think so too. And to be honest, if they needed a niche to be filled, they'd ask for map submissions outright, so... yeah. - That said, it's good habit to start out by making smaller rooms in order to get used to wiring, APC placement, pipe placement, door permissions and such before tackling a larger project. A lot goes into even small rooms, and they're still important. ## Tips and Tricks ###### These aren't one hundred percent necessary to make maps, but they might make your life a bit easier - **Cable spawners** `/obj/cables/auto` autoconnect to neighbouring cables pointing at that tile and other auto cables, placing multiple cables if necessary. It has reinforced and coloured variants and if you want to make it create nodes for terminal connections and whatnot, you can use the `/node` subtype. When needing something pretty and/or handcrafted (like cable art, or two non connected but crossing networks) it's probably best to just use regular cables placed manually; cablespawners are for convenience in places where you don't care. - **Pipe spawners** are similar to cable spawners, but they can't be used to make junctions (you'll have to set directions and priorities manually). Still, they're handy for drawing very long stretches of disposal/mail/cargo/morgue/transport pipe. Do be warned that you'll have to use the `/obj/disposalpipe/auto/regular` for ordinary disposal pipes, otherwise it'll try to connect itself to ALL subtypes, which will runtime and make you sad. - **Auto Catwalks** and **Auto lattices** similarly are useful. Auto catwalks are now the default placement method of catwalks, and auto lattices are stored under `/obj/lattice/auto` (Like cable spawners and pipe spawners, auto lattices will break if placed alone). There's different connection options too, for auto connection with turfs or just walls. - **Palettes** are small rooms with assortments of walls, floors and such in different arrangements, available for you to copy over to your projects. Palettes are available at the #immapper channel on the [goonstation discord](https://discord.com/invite/goonstation), and get updated every so often. You'll have to link your byond account with your discord account first, though. - In StrongDMM, "ctrl+1,2,3 to toggle layers, shift click to highlight thing, ctrl shift click to delete thing, 1 2 3 to switch between placing a singular thing, placing multiple things in the area via clickdrag and selecting an area without placing things" ~ Caro, in the #immapper pins - Conveyor belts can have *corners* now (quite incredible). Try them out! - When placing **items on tables**, `var/rand_pos` being true means that the pixel position will be randomised. Otherwise, `pixel_x` or `pixel_y` will be used.
Last changed by  
 
Goonstation
Developers for the classic flavor of SS13
5701

Read more

Goonstation Spriting Guidelines

So, you want to contribute sprite art to Goonstation. Great! This set of guidelines details what's generally expected out of sprite contributions for Goonstation, and aims to provide helpful advice on the implementation and creation of sprites. As a disclaimer, this isn't a guide on 'How All Good Pixel Art Should Be Drawn', it's how sprites contributed specifically to Goonstation should be drawn.

4/16/2024
Goonstation Contributor Guidelines

Codebase Expectations The question this section aims to answer is: "What can I reasonably expect about this codebase, my contributions, and the maintainers?" Essentially, this is more of a FAQ section. Maintainers / Developers The Goonstation codebase maintainers/developers are a part of the general admin team for the Goonstation servers. They are The People Who Decide What Goes In The Game. You can identify these people on the Discord by their red/amaranth name. On GitHub, they'll also show up as a member of the Goonstation organization: . Please do not unnecessarily ping us directly unless someone explicitly says it's ok. If you have a question for developers, you can generally reach us (or perhaps a fellow contributor can answer your question) in the #imXYZ discord channels, like #imcoder.

11/3/2023
Goonstation Code Guide

General Operators Don't use goto. Bad. Don't use the : operator to override type safety checks. Instead, cast the variable to the proper type. Don't use del, it's horrendously slow. Use qdel(). Don't use <>, it's completely unused in the land of SS13. Use != instead, as it's infinitely more sane. Stuff To Use Use SPAWN() instead of spawn() Use TIME instead of world.timeofday

9/12/2023
Goonstation Development Guide

:exclamation: Disclaimer This guide is the one to follow to get started developing and making changes to Goonstation.<br> It's also the one to follow if you just want to host a local server to run around in by yourself.<br> Following this guide will get your local development environment set up to do whatever you want. It will also familiarize you with the basic process of contributing to Goonstation. However, you must follow the guide in its entirety.<br> No skipping, even if you think you have a good reason. <ins>There are no optional sections.</ins><br> Help and support is not offered whatsoever if you skip portions of the guide. :question: So, how do I get started?

8/18/2023
Read more from Goonstation
Published on HackMD