While I was on the test server I saw something called view overmap. What is the overmap? Is it how traveling to multiple planets is made possible because I remember seeing something like that. 

So questions:

1. What is the overmap

2. How does it work

just need to join in eh

Here is a reasonably comprehensive guide for the full workflow I've developed from start to finish based on our current code. You will need intermediate skill at mapping (or basic skill and a little help), very basic skill with spriting and very basic skill with coding. I'm writing this up so that mappers can get an idea of the full process and we can make contributing a little easier in all areas to hopefully encourage a little more contribution. This is a multidisciplinary process but if you follow the steps carefully and ask for advice/help at different stages along the way anyone can learn to do the full thing. It's also a long guide so you may want to take it in stages, or split the work up between a couple of people.

1. Decide the kind of ship or station you want to make, its size and its purpose. For performance reasons we want to minimise the number of things using 2 or more zlevels (separate decks) by themselves but don't be afraid to make something bigger if you want to. Engines are props and there's no other ship mounted machinery like weapons, comms antennae, sensors etc at the moment but leave space for them as they'll get added eventually. Covenant turfs aren't in the code yet so stick to human ships. Space stations and asteroid bases are basically the same as capital ships but a little bit simpler. In the code stations and asteroid bases are treated identically. Anything larger than 20x20 must be either a capital ship or station (not a shuttle) and can use one or more zlevels.

2. Map the internal layout. Size guidelines for some possible ship/shuttle types are:

- Small shuttle, dropship, personnel lighter, escape pod: up to 6x6 tiles (shuttle class)
- Large shuttle, tug, gunboat, heavy dropship, small yacht: up to 20x20 tiles (shuttle class)
- Stealth vessel, light freighter, transport ship, patrol boat, sub-prowler/sub-corvette, luxury yacht: 1 zlevel (capital class)
- Corvette, light frigate, medium freighter, personnel transport: 2 zlevels (capital class)
- Frigate, light destroyer, heavy freighter, refinery ship: 3 zlevels (capital class)
- Destroyer, heavy frigate, light cruiser, light carrier, colony ship: 4 zlevels (capital class)
- Heavy cruiser, carrier: 5 zlevels (capital class)

Space stations and asteroid bases can be anywhere from 1-5+ zlevels depending on their purpose. Shuttle class ships are able to physically move around inside and dock with capital class ships. We can theoretically make shuttles up to around 50x50 or larger, but any larger than 20x20 and gameplay/performance issues crop up. There are also specific turfs you need to use for shuttles. Capital class ships and space stations occupy entire zlevels and have static layouts. On the overmap both type of ships work near identically but should be given different sized sprites to represent their size difference. Place a minimum 50 tile margin of empty space around the edge of anything occupying one or more zlevels.

Map your shuttles facing north (up) and map your capital ships facing east (right). Don't ask me why because I was probably drunk at the time. I might get drunk and make them the same someday but forget to tell anyone so all the ships suddenly start flying sideways. Spacestations and asteroids can do whatever they want. Make sure that the map z dimension is always 1 and split separate decks off into separate mapfiles labelling then myship-1.dmm myship-2.dmm etc.

2(a). Shuttle specific stuff

The shuttle code requires that the only turf type used internally are of type /turf/simulated/shuttle/hull (for the shuttle) and /turf/unsimulated/blocker (for any empty space around it). To achieve a desired visual effect, you will need to modify the icon and icon_state of the turf in the map editor to match what you want. To do this right click on the turf, go to the dropdown for it and select "Edit..." then scroll down to where it says icon in the left column. In the right column enter the path of the icon you want to use inside single brackets (eg 'icons/turf/space.dmi') then press "OK". Go to the edit menu again, and this time scroll down to where it says icon_state in the left column and put the name of the icon state you want in the right column in double brackets (eg "plating"). To find a list of possible turf sprites to use, navigate to icons/turf inside Dreammaker.

For floor turfs (ie are non-dense and non-opaque) use /turf/simulated/shuttle/hull/floor and for windows (dense and non-opaque) /turf/simulated/shuttle/hull/window the parent hull type /turf/simulated/shuttle/hull function as walls (dense and opaque). Don't worry about maglocks, they don't use specific turfs for now.

Do not map out any areas, but make sure you place exactly 1 APC somewhere (SMES and cabling are optional but there if you want them) and at least 1 /obj/machinery/computer/shuttle_helm to fly the shuttle. Lighting is also required, and you can use ordinary airlocks as normal to divide internal cabins and rooms. Place some /obj/machinery/door/airlock/external/shuttle to allow players to enter and exit the shuttle while it is in flight (not maglocked). Putting the machinery for a cycling airlock is not necessary as most shuttles will be flying to and from hangars or planets with atmosphere, but you can do it if you want (eg for a salvage or SAR shuttle).

The map file containing this layout should use the exact same dimensions. Eg if your shuttle is 12x15 then the map should be 12x and 15y.

Nothing other than shuttles should use these turf types.

3. Get an overmap sprite for your ship or station

Shuttles: the sprite should be around 16x16 from one end to the other (use a standard 32x32 dmi size) with a little bit of leeway either size (eg you could do a 10x10 or 20x20 sprite). Create it as an state in code\modules\overmap\overmap_vehicles\icons\overmap_vehicles.dmi and call it whatever you want but remember it for the next step (4). Make sure the sprite is facing north and don't bother creating directional states.

Capital ships or space stations: The overmap sprite should be 32x32 for things that are 1 full zlevels, 64x64 for things that are 2 full zlevels, 96x96 for things that are 3 zlevels, 128x128 for things that are 4 or more zlevels. Also include icon states for thrusting and braking (reverse thrust). For the dimensions larger than 32 you will need to use an external editor then import it into Dreammaker, I recommend Paint.NET as it's free, small and fast but with loads of features. Place it as a new icon inside the folder code\modules\overmap\ships and name the icon states "base" "thrust" and "brake" for ships. Make sure all 3 icon states exist (if ship), but just reuse the base sprite if you don't have the extra ones. Make sure the sprites are facing north and don't bother creating directional states. 32x32 station sprites can go into code\modules\overmap\ships\sector_icons.dmi or just as new icons into code\modules\overmap\overmapobj (sorry it's a little bit disorganised). Remember the icon name and icon_state for the next step (4a and 4b and 4c).

3(a). Shuttle top-down sprites

The top-down sprite is used for the shuttle when it is in flight (eg docking with or leaving a hangar) and the dimensions need to match the full pixel dimensions of the internal layout so an external editor is required. To calculate the size required, count the x width and y-height of the shuttle excluding any empty space then multiply by the standard Byond turf size of 32x32. For example, a shuttle that is 5 turfs wide and 10 turfs high will need a top-down sprite with dimensions 160 (5 x 32) by 320 (10 x 32).

Once you figure out the required dimensions either obtain the services of an artist or map out the "roof" in Dreammaker using whatever turfs you like then take a screenshot and scale/crop it to the required proportions. Place the image into its own DMI (ensuring it is facing north) and call the icon state "shuttle". Call the icon itself whatever you want, but remember it for the next step (4a).

3(b). Sensor HUD images

Everything the size of a fighter or larger needs a unique sprite to quickly identify it when it pops up on a player's sensor HUD. The sprite should be 32x32 and grayscale (because it is coloured in according to its faction or light blue for environmental stuff like asteroids and stars). Place the sprite in code\modules\overmap\overmap_vehicles\icons\overmap_vehicle_hud.dmi and name it whatever you want but remember it for the next step (4).

4(a). Implementing shuttles in code

Open up code\modules\overmap\overmap_vehicles\instances\shuttles.dm then scroll down to the bottom of the file and copy paste the following code at the end:

I have been looking through the Game mode concept posted by Cael and all of them sound fun. So I was wondering if the development team has agreed to add any of those concepts or other game mode idea's.

I also have some questions

1. In certain game modes will there be escape pods?

2. Will there be ODST's 

3. Will there be a way for Marines to enter open space

4. How detailed will the medical system be

5. What level of role play will be expected on the server. (I hope medium-heavy)

6. Probably the most important: When can we expect the open Alpha and public server to go live?

Keep up the great work, I see a lot of potential here! 

I loved flying these in Halo:Reach could you guys add them?

Hello, My name is Soultaker123 (Jack Goodson).
I really like helping people, sometimes coding, and I REALLY love mapping.
I am very good at mapping, and mapping is the most thing I do in SS13.
I am familiar with the -tg- code, but it seems I like halo station more, looks more fun.

What position are you applying for (Development or Staff)? Staff


How old are you? I am 15.



Known IC Names Or Ckey: Jack Goodson, Soultaker123


What timezone are you in? Israel.


How long can you be active on the server everyday? I can be active everyday depending on what I do.


How long have you been playing Space Station 13? Alot of time. Started in 2015 or 2014 probably.


Have you ever been banned in the past? Yes, I have been banned for griefing.


Do you have any past experience as a moderator? Yeah, I was a mod once but shit owner removed me for no reason.


*If you are applying for development, What skills do you have?( Mapping, coding or spriting etc.)  I am good at mapping.


*If you are applying for development, How long have you done Space Station 13 development? Not really that long.


*If you are applying for development, How long have you been coding and how well do you understand it?Not that long, but I understand it good.


*If you are applying for development, What codebase are you familiar with?-tg-


*If you are applying  for development, How long have you been a Mapper and how well do you understand it? I am very good at mapping. It's like my building lessons.


*If you are applying for development, How long have you been a Spriter and how well do you understand it?I suck at spriting. Though, I can make shadows and other stuff, but I really suck.

So after looking through all the game modes or idea's for them at least i see Pelican's are important part of many of them so i have some questions.

1. In Stranded and other game modes it sounds like Pelican's come in as a scripted event when certain objectives are completed or time limits are up to come save the marine. My question is do these Pelican's work like Pelican's that would spawn on a ship at the start of the round or are they restricted to just NPCS flying, also can these Pelican's be shot down and if so what happen's in the round then if the Pelican's sent to pick up the marines are not there how would the round continue.

2. If Pelican's can get shot down in-game (which I am assuming they can) and there are marine's in the Pelican is it a possibility some of the marines can survive the crash and if so what does this depend on. For example if the pilot is a player (and again i am assuming players can pilot pelican's) does the pilot still have some control on the Pelican even if it is going to crash and could this effect if marines or anybody else in the Pelican  survives the crash.

3. Can Pelican's from a planet in-game go to space . I ask this because I can think of some fun situation's where Spartan's jump out of a Pelican in the middle of a battle in space between UNSC and Covenant forces. This lead's to my next question.

4. In-game do Spartan's have airtight suits of armor?


2.2. This is really apart of question two but when going from orbit down to a planet or anything else  that has a atmosphere can Pelican's be shot down while doing this. I am guessing not because of the BYOND engine's limitation's. Also if your on say a Forerunner Installation with a ground to orbit super weapon (if they exist in game) can you fire at warships and do damage?


5. What code are you using. I thought it was a modified bay code but i would like to know for sure.

Well that's all keep up the great work can't wait to try out the open Alpha.

Concept: The players are the crew of a Covenant warship and are tasked with reclaiming 5 human colonies in an outlying system. First they must locate and retrieve any Forerunner artifacts, then glass the planet. UNSC warships will periodically spawn to attack, and prowlers will try to sneak up and deploy Spartan-II boarding teams.

Retrieving Forerunner relics: Each planet must be carefully searched for Forerunner installations. Human dwellings should be searched as well in case they have stolen any artifacts. Naturally, they will defend their homes with marines and vehicles so work as a team and use your own vehicles.

NPC squads and vehicles: NPC squads and ground vehicles will be available for deployment from your cruiser but you don't possess unlimited amounts so don't squander them by throwing them away to assault enemy strongpoints. Remember to retrieve them before glassing the planet.

NPC fighters: NPC seraph fighters will be available as well, to help keep your ship alive. Keep them back in reserve and to screen your ship, and remember to recall them to hangars before entering slipspace or they'll be lost.

Engaging UNSC warships: These will constantly spawn and hunt you down so try to draw them away from the colonies while your ground forces are searching for relics. Employ hit and run tactics as they will often outnumber you, attacking when you have split them up but retreating to repair and recharge your shields.

Glassing the colony: Once you have finished your search for relics, start the process of glassing. The power draw will disable some of your weapons and you won't be able to move while it's going on (10-30 minutes) so you'll be vulnerable and have to defend yourself as best you can.