Guide to mapping - Revision history

Sergeirocks100: 37 revisions imported

2022-01-19T16:35:23Z

37 revisions imported

← Older revision

Revision as of 16:35, 19 January 2022

tgstation>Vire: Details on working with multi-z, earned through suffering

2021-03-18T20:20:27Z

Details on working with multi-z, earned through suffering

← Older revision		Revision as of 20:20, 18 March 2021
Line 90:		Line 90:
	=== Power ===		=== Power ===
	* Each area (which requires power) should have exactly one APC. For areas with a high roundstart power draw (engineering/cargo), one of the highcap subtypes can be used.		* Each area (which requires power) should have exactly one APC. For areas with a high roundstart power draw (engineering/cargo), one of the highcap subtypes can be used.

	~~=== Multi-Z ===~~
	* If you are building station rooms on a lower Z level, ensure that a floor of some type is mapped on the Z level above the room. You can check the coordinates in the mapping editor to ensure you floor over the correct dimensions of the room. When running the server in Dream Daemon to test the map, you can go to the Debug tab and hit show debug verbs, go to Mapping tab and hit Show ATs, if the list is empty, you are good.

	== Atmospherics ==		== Atmospherics ==
Line 293:		Line 290:
	* <code>{\W\bsomething = [^;]+?\W}</code> => nothing		* <code>{\W\bsomething = [^;]+?\W}</code> => nothing


			== Multi-Z ==

			Multi-Z is a feature which allows a station map to have multiple Z-levels layered on top of each other, behaving as a single station with multiple floors. This feature is currently in use on the [[Tramstation]] and [[IceboxStation]] maps. A station's multiple levels can be bundled into one map file, or in several seperate files. The traits section of the map configuration json tells SS13 how to link the maps together.

			* If you are building station rooms on a lower Z level, ensure that a floor of some type is mapped on the Z level above the room. You can check the coordinates in the mapping editor to ensure you floor over the correct dimensions of the room. When running the server in Dream Daemon to test the map, you can go to the Debug tab and hit show debug verbs, go to Mapping tab and hit Show ATs, if the list is empty, you are good.

			* Earlier versions of multi-z did not require a baseturf to be defined under each z-level's traits in the config json. Each level must now have a baseturf set.

			* The maploader '''will not''' load and link a map file without areas or turfs defined. An empty space (nothing but baseturf) map will runtime. If you are adding a Z-level to an existing map, be aware of this.

			* SS13 will cache a map's configuration json file in data\next_map.json. If you alter a map's configuration json locally, you must also clear this file by using the change-map verb in game, deleting the file, or replacing it with your updated json file.

	{{Contribution guides}}		{{Contribution guides}}

tgstation>Nari Harimoto: adds a section for Multi-Z mapping so people are aware on how to prevent ATs because of upper Zs not being floored off

2021-01-21T00:36:38Z

adds a section for Multi-Z mapping so people are aware on how to prevent ATs because of upper Zs not being floored off

← Older revision		Revision as of 00:36, 21 January 2021
Line 90:		Line 90:
	=== Power ===		=== Power ===
	* Each area (which requires power) should have exactly one APC. For areas with a high roundstart power draw (engineering/cargo), one of the highcap subtypes can be used.		* Each area (which requires power) should have exactly one APC. For areas with a high roundstart power draw (engineering/cargo), one of the highcap subtypes can be used.

			=== Multi-Z ===
			* If you are building station rooms on a lower Z level, ensure that a floor of some type is mapped on the Z level above the room. You can check the coordinates in the mapping editor to ensure you floor over the correct dimensions of the room. When running the server in Dream Daemon to test the map, you can go to the Debug tab and hit show debug verbs, go to Mapping tab and hit Show ATs, if the list is empty, you are good.

	== Atmospherics ==		== Atmospherics ==

tgstation>SpaceManiac: Remove "Game Resources" category

2020-12-04T03:45:34Z

Remove "Game Resources" category

← Older revision		Revision as of 03:45, 4 December 2020
Line 292:		Line 292:

	{{Contribution guides}}		{{Contribution guides}}
	~~[[Category:Guides]]~~
	~~[[Category:Game Resources]]~~

tgstation>SpaceManiac: Add ninjanomnom's "Useful regexes for coding" from the GitHub wiki

2020-12-01T05:21:09Z

Add ninjanomnom's "Useful regexes for coding" from the GitHub wiki

← Older revision		Revision as of 05:21, 1 December 2020
Line 274:		Line 274:
	If you are adding a map to the game, you need to ensure it has a JSON file under _maps, and is included in the maps config file.		If you are adding a map to the game, you need to ensure it has a JSON file under _maps, and is included in the maps config file.

	[~~[Category~~:~~Guides]] [~~[~~Category:Game Resources]~~]		==Helpful regular expressions==
			Everything in the code blocks is a regular expression, most decent text editors are able to use regex in their searches.

			Replace the regex proceding <tt>=></tt> with what follows.

			=== Pesky var edits for the `something` var are all over my map ===
			Replace <tt>something</tt> with the var that needs to be removed. You need to run both replacements to catch all cases.

			For standard dmm format:
			* <code>\bsomething = .+?; *</code> => nothing
			* <code>{\W\bsomething = [^;]+?\W}</code> => nothing

			For TGM format:
			* <code>^\W+\bsomething = .+?;\n</code> => nothing
			* <code>{\W\bsomething = [^;]+?\W}</code> => nothing


	{{Contribution guides}}		{{Contribution guides}}
			[[Category:Guides]]
			[[Category:Game Resources]]

tgstation>Cartographer-D at 03:00, 12 September 2020

2020-09-12T03:00:14Z

← Older revision		Revision as of 03:00, 12 September 2020
Line 1:		Line 1:
	Other related guides: [[Understanding SS13 code]], [[SS13 for experienced programmers]] and [[Map Merger]]		Other related guides: [[Understanding SS13 code]], [[SS13 for experienced programmers]], [[Guide to door access]] and [[Map Merger]]
	== Map Merger ==		== Map Merger ==
	It is important that you use the [[Map Merger]] tools before commiting any changes to a map. See [[Map_Merger\|here]] for how.		It is important that you use the [[Map Merger]] tools before commiting any changes to a map. See [[Map_Merger\|here]] for how.

tgstation>PixelShader: /* Access */

2020-07-06T05:36:49Z

Access

← Older revision		Revision as of 05:36, 6 July 2020
Line 192:		Line 192:

	=== Access ===		=== Access ===
	''' <span style="color:#FF5238"> Refer to \code\__DEFINES\access.dm for door access values.</span>'''		''' <span style="color:#FF5238"> Refer to ..\code\__DEFINES\access.dm for door access values.</span>'''

	Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.		Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.

tgstation>PixelShader: Adding a note, stating where door access values exist.

2020-06-24T16:08:27Z

Adding a note, stating where door access values exist.

← Older revision		Revision as of 16:08, 24 June 2020
Line 192:		Line 192:

	=== Access ===		=== Access ===
	''' <span style="color:#~~ff0000~~"> Refer to \code\__DEFINES\access.dm for door access values.</span>'''		''' <span style="color:#FF5238"> Refer to \code\__DEFINES\access.dm for door access values.</span>'''

	Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.		Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.

tgstation>PixelShader at 16:06, 24 June 2020

2020-06-24T16:06:37Z

← Older revision		Revision as of 16:06, 24 June 2020
Line 192:		Line 192:

	=== Access ===		=== Access ===
			''' <span style="color:#ff0000"> Refer to \code\__DEFINES\access.dm for door access values.</span>'''

	Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.		Access to doors is handled by req_access values. There are four when editing a door - req_access, req_access_txt, req_one_access, and req_one_access_txt. The one's we're concerned with are '''req_access_txt''' and '''req_one_access_txt'''.

tgstation>Hughgent at 01:56, 22 November 2018

2018-11-22T01:56:45Z

← Older revision		Revision as of 01:56, 22 November 2018
Line 21:		Line 21:
	The first step, then, is to be able to create your first few rooms. Select a turf (floor) from the generic simulated floors. These will start with the right make-up and pressure of air on them, which is how you'll want it. Surround these floors with walls, and hey presto you have a room. Try sticking some tables in there, perhaps a vending machine or two.		The first step, then, is to be able to create your first few rooms. Select a turf (floor) from the generic simulated floors. These will start with the right make-up and pressure of air on them, which is how you'll want it. Surround these floors with walls, and hey presto you have a room. Try sticking some tables in there, perhaps a vending machine or two.

	If you want to add some chips to your new den but are unhappy of how they neatly stack on top of eachother, you can change their "pixel_x" and "pixel_y" values in the "edit" rmb-menu to arrange them as you want! (Remember to start and end the value with doublequotes! Also, all custom values are '''bold''' so it's easier to identify them.) In fact, most wall-mounted machines on stations are shifted like this, and while they APPEAR to be on a wall, they are actually on the tile in front of it. Just don't go overboard with this, as every new instance of an object is added as its own entry in the menu, and when there are dozens of them it can get hard to remember which one you wanted. ~~One~~ you've made your room you'll want to put lights in.		If you want to add some chips to your new den but are unhappy of how they neatly stack on top of eachother, you can change their "pixel_x" and "pixel_y" values in the "edit" rmb-menu to arrange them as you want! (Remember to start and end the value with doublequotes! Also, all custom values are '''bold''' so it's easier to identify them.) In fact, most wall-mounted machines on stations are shifted like this, and while they APPEAR to be on a wall, they are actually on the tile in front of it. Just don't go overboard with this, as every new instance of an object is added as its own entry in the menu, and when there are dozens of them it can get hard to remember which one you wanted. Once you've made your room you'll want to put lights in.

	{\|		{\|