SS220 /tg/station13 (Space Station 13) - Вклад [ru]

Шаблон:TGMC:SpitterPrimordialEvolution

2022-08-23T10:32:46Z

TrashDoxx: Исправил сломанный мною шаблон

|- style="background:#{{ColorPalette‎‎|Xenomorph|Primary}}; color:#{{ColorPalette‎‎|Xenomorph|Header Text}}; font-weight:bold; text-align:center;"
| style="border-style:double; border-width:.2em; border-color:#{{ColorPalette‎‎|Xenomorph|Primary Bold}}; border-radius:.2em;" colspan=4 | Способность эволюционной ветки Primordial
|- style="color:black; background:#{{ColorPalette‎‎|Xenomorph|Very Light}};"
! {{RowHeader|Theme=Xenomorph}} | Пулеметный плевок [[File:TGMC Xeno Spit.gif|64px]] Machinegun Spit
| Эта способность добавляет дополнительный вариант плевка Xeno Spit, имеющий пониженные урон и стоимость, но с очень быстрой перезарядкой. Вы можете переключиться на классический вариант, кликнув по способности.
|Н/Д
|Н/Д

Шаблон:TGMC:SpitterPrimordialEvolution

2022-08-23T10:31:40Z

TrashDoxx: Изменил описание способности примордиала-плевателя

|- style="background:#{{ColorPalette‎‎|Xenomorph|Primary}}; color:#{{ColorPalette‎‎|Xenomorph|Header Text}}; font-weight:bold; text-align:center;"
| style="border-style:double; border-width:.2em; border-color:#{{ColorPalette‎‎|Xenomorph|Primary Bold}}; border-radius:.2em;" colspan=4 | Способность эволюционной ветки Primordial
|- style="color:black; background:#{{ColorPalette‎‎|Xenomorph|Very Light}};"
! {{RowHeader|Theme=Xenomorph}} | Пулеметный плевок [[File:TGMC Xeno Spit.gif|64px]] Machinegun Spit
| Эта способность добавляет дополнительный вариант плевка Xeno Spit, имеющий пониженные урон и стоимость, но с очень быстрой перезарядкой.
| Вы можете переключиться на классический вариант, кликнув по способности.
|Н/Д
|Н/Д

Глоссарий

2022-04-07T21:46:35Z

TrashDoxx: Частичный перевод.

{{Speech
|name=Speaks-His-Mind the Maintenance Dweller
|text=SSSo, lassst I heard the AI wasss helping the Redssshirts in sssome operation to robussst sssome sssort of cult in Aft Maintenance. I sssuggessst you ssstay clear of there, ssstranger. I wouldn't want to be on the wrong end of a ssstunbaton, no no...
|image=[[File:Lizardman.png|64px|right]]
}}

A big bad list of common terminology and slang commonly used by resident Spacemen (players).

===Администрация===
Руководящее звено, которое управляет сервером. Имеют множество кнопок для злоупотребления властью, чтобы игра была как можно менее весёлой.

===Adminhelp/Ahelp===
Команда, позволяющая отправить сообщение [[Administrators|администраторам]]. Доступ к ней можно получить, набрав Adminhelp в игре или нажав <code>F1</code>.

Используйте это (вместо OOC-канала), если вы считаете, что кто-то нарушает правила, или если вам есть о чём спросить администраторов.

Это могут быть вопросы об этикете, правилах или внутриигровых процессах, таких как запуск двигателя и т.д.

Следует отметить, что даже в том случае, если администраторов нет на сервере, все сообщения, отправленные в Adminhelp, записываются в журнал.

===Additional Access===
Under certain circumstances, such as a low server population, admin-toggled, or simply set in the server configuration by the host, jobs may be granted additional access when they join the round.

===Aft===
Морской термин. Он означает заднюю часть корпуса корабля, или, в нашем случае, юг.

===[[ИИ]]===
Искусственный интеллект - станционный компьютер, который может получить доступ ко всему оборудованию станции.

===[[Analyzer]]===
Most often refers to [[Health Analyzer]]s, but can also refer to [[Analyzer|Atmospheric Analyzers]], [[Botanist|Botany]]'s Plant Analyzers, or [[Scientist|Research & Development]]'s Destructive Analyzer.

===Аномалия===
A kind of [[random event#Anomalies]] announced over comms that can cause station damage if not dealt with in time.

===Антаг===
Антагонист. Также "противник" или "враг". Каждый [[Game_modes|игровой режим]] (за исключением extended и secret extended) имеет, по крайней мере, одного.

===[[APC|ЛКП]]===
The Area Power Controller, a square box on the wall that provides power to the room and is the purview of [[Station Engineer]]s.

===[[Asimov]]===
The default laws that the [[AI]]s and therefore the [[Cyborg]]s are held to. Taken from [http://en.wikipedia.org/wiki/Isaac_Asimov Isaac Asimov]'s short stories and the [http://en.wikipedia.org/wiki/Three_Laws_of_Robotics Three Laws of Robotics].

Basically makes robots follow orders and unable to harm people.

===[[Atmos]]===
Either an [[Atmospheric Technician]] (which are also commonly known as Atmos Tech) or the [[Atmospherics]] area itself which deals with the air supply.

===Ayys/Ayyliens===
An [[Abductor]], not to be confused with a [[Xenomorph]].

===Badmin===
Bad Admin, refers to an admin who abuses their powers.

===Бан===
Blocking a person from access to the SS13 server for a period of time. This can happen if a person is not obeying the given [[rules]].

Read the [[guide to evading getting banned]] for further guidelines.

===[[Beepsky|Beepsky/Officer Beepsky]]===
A [[Securitron]] that starts in Security. Will chase, stun, and handcuff anyone set to be arrested in the [[security records]].

===[[Блоб]]===
Can refer to the Blob game mode, or the Blob that spawns in Blob mode and sometimes in random events.

A big green jelly thing that spreads quickly, causes enormous damage, beats the shit out of people and is weak to fire.

===Bolt/Bolted===
A feature of [[Airlock]]s. When the bolts are dropped, the door cannot move from its current position, be it open or closed. They can be lifted by the AI or [[hacking]] the airlock.

===[[Борг]]===
Он же [[Киборг]].

===[[Borging|Боргификация]]===
Making a Cyborg out of someone. Done in [[Robotics]] usually.

===Braindead===
Refers to a player who has logged off or been disconnected. Examining a braindead character reveals the message; "They have a blank, absent-minded stare and appears completely unresponsive to anything. They may snap out of it soon."

While these players are not in-game, they should generally be left alone (or preferably dragged somewhere safe) The rules still apply to braindead characters.

'''NOTE: This person can still come back to the game!''' Who knows, maybe their computer just crashed for a minute.

===[[Bridge|Мостик]]===
The command center of the ship where the heads start. Found in the center of the station.

===[[Brig|Бриг]]===
An area where people are held by [[shitcurity|security]] after being arrested.

===Bwoink===
Receiving an Admin PM, named after the sound effect played when an admin PMs you.

===[[BYOND]]===
The shitty, [[Lagtime|laggy]] platform SS13 was coded on. You need it to be able to play the game, unfortunately.

===[[Cargo|Карго]]===
A shortened version of either the cargo bay, or the whole of the supply section, not including mining dock and mining outpost.

===Catatonic===
A player who has ghosted while alive, disabling them from returning to play. When such a player is examined, it gives a message stating there is no hope of recovery.

These people are as considered corpses and can be taken to the [[Morgue]] or [[Kitchen]].

===[[CE]]===
The Chief Engineer.

===[[CentCom]]===
Short for "Central Command", the administration branch of Nanotrasen which runs SS13. Will periodically send messages to the station which are usually of debatable usefulness.

Also refers to the area the Emergency [[Escape Shuttle]] goes to when it leaves SS13.

===[[Cloning|Clone/Cloning]]===
To revive someone back to life through cloning their dead body. Used to be done in [[Medbay]] until cloning was removed Feb, 2020.

===[[CMO]]===
The Chief Medical Officer.

===[[CO2]]===
Carbon Dioxide, an invisible gas kept in black canisters. Will knock you out and suffocate you.
A small trace amount of it makes up breathable air.

===Comdom===
A derogatory name for an incompetent and abusive [[Captain]].

===Corporate===
A lawset for the [[AI]], which makes it a ruthless profits-maximizing, efficiency-enforcing machine.

===Crew===
This is everybody on [[Space Station 13]] that is not a [[Syndicate]], [[Wizard]], [[xenos|Alien]], or whatever.

Typically what they do is get the station into shape, like setting up the [[Station_Engineer|singularity]] and [[Quartermaster|ordering supplies]]. Oh, and beating the shit out of the other groups of players, of course!

===[[Crit]]===
To be in a critical state. At this point, your character has lost consciousness and will slowly die from lack of oxygen.

===[[Cryo]]===
The big green glass things in Medbay. Putting dying people in here can save them.

===Cuban Pete===
''They call me Cuban Pete, I'm the king of the rhumba beat.''

''When I play my maracas I go''

''Chick chicky boom, chick chicky boom''

A notorious griefer who applied the bomb-making knowledge of a mysterious first scientist mentor who had invented ludicrous sized bombs. The station was turned into nearly dust every round he was on, antagonist or not. Because of him there was a bombcap hardcoded into the game.

===[[Cult]]===
Refers to either the [[Cult]] game mode, or the cultists within.

===Deadchat===
A chat channel dead/observing players speak on using the say command. Can only be seen by other dead/observing players. Deadchat is mostly considered to be out-of-character, and here you are allowed to talk about anything happening in the round (unlike in the [[OOC#OOC_channel|OOC channel]]).

Note that what you learn here is forgotten by your character if you're revived.

===Deadmin===
Most commonly read as dead-min (as in dead admin), but actually stands for de-admin, meaning the action of removing administrative powers from an [[Administrators|administrator]].

===Disk===
Infrequently a science or genetics research disk, but most often refers to the [[Nuclear Authentication Disk]], used in [[nuke|Nuclear Mode]]. If you are the [[captain]], guard it with your life.

If you are a traitor with it as your objective, GET DAT FUKKEN DISK.

===Donk/Bangin' Donk===
[https://www.youtube.com/watch?v=ckMvj1piK58 wait wait hold on, you know what you wanna do with that right? you wanna put a bangin' donk on it]

===Drone===
Either a type of [[alien]] or a [[Drone|player-controlled repair bot]].

===Electrified/Shocked===
Another feature of [[Airlock]]s. If an electrified airlock is touched by someone without insulated gloves, they will receive an electric shock, taking damage and being stunned for some time.

The AI and airlock hacking can activate or disable electrification. Some grilles are also electrified -- cutting a cable without wearing insulated gloves will also electrify you.

===[[Emag]]===
Another name for the [[Syndicate_Items#Cryptographic_Sequencer|Cryptographic Sequencer]] traitor item, which in the past used to permanently open doors and still has a myriad of other uses.

===Emagged/Emaged===
Used either as a verb to describe the action of using an [[emag]] on something, or as an adjective to describe an object that someone has used an emag on.

===[[Emoji]]===
A.K.A. smileys, except smile is not mandatory. [[Emoji cheat sheet|Learn them all!]]

===End of round grief (EORG)===
The practice of killing and/or causing destruction after the end round report has appeared, but before the server restarts. This is traditionally allowed on /tg/station.

===[[Engine]]===
The large area in the south of the station that is used to start and contain a gravitational singularity that provides power to the station.

===ERP===
Erotic Role Play (ERP) is the action of when a player or players engages in roleplaying that is erotic in nature.

An inherently controversial subject, people's reactions to ERP ranges from upset and rage to taking off one's clothes and joining to [[Rules|ding dong bannu]].

===[[EVA]]===
A room where space suits, magboots, jetpacks and the RCD are kept. Stands for Extra-Vehicular Activity.

===Fore===
Nautical term. It means the front of a ship, or in our case, north.

===[[Ghost]]===
Refers to a command you can type when you have died to become a ghost, and to the actual ghosts themselves.

Ghosts can speak on deadchat, move around the station freely, see everything, and can't interact with anything meaningful.

They are used to observe the game after you have died. Cannot be seen directly by living players unless something is very wrong.

===Gibs===
The bloody, torn apart remnants of a former living being. Created by people and monkeys exploding. A cyborg that blows up has its own version of gibs: robot debris.

To gib something is to turn it into gibs, usually by a [[guide to toxins|bomb]] or the Chef's machine that turns people into meat, the [[Gibber]].

===Gimmick===
Can refer to a player gimmick or a gimmick round. Basically a round or player which plays with a certain "theme".

Can be amusing once or twice but doing this regularly runs it into the ground very quickly.

===Grayshirt/Grays===
[[Assistant]]s, named after their signature gray uniform. Not to be confused with ayyliens. AKA grayshits. AKA,

===Graytide===
Originated from a bug in the job selection system, causing the majority of the crew to be roundstart [[Assistant]]s, dressed in gray. This resulted in swarms of Assistants storming the Brig and antagonize [[security]]. Now the word refers to any griefy behavior of that bent.

===[[Greentext]]===
An alternate way of describing a victory as an antagonist. Derived from the green text used for 'success'.

===Grief===
A.K.A. Griefing/Griefer/Griffed/Griff/Griffon/Gruffer/Grover/Shitler/Chucklefuck/(Pulling a) Cuban Pete.

Intentionally ruining the game for others without the metagame pardon of being an antagonist.

Note that this is subjective and up to the admin's interpretation, not yours. Report this using adminhelp to keep the servers tidy!

===Gulag===
The Russian term for the [[Labor Camp]].

===[[Hacking]]===
The act of breaking the security measures on equipment such as Airlocks or APCs by illicit means.

===[[Hand of God|HoG]]===
Abbreviation for the [[Hand of God]] game mode.

===Heads===
The station's [[Chain_of_Command|Heads of Staff]], each in command of a department. They are also the targets of a [[revolution]].

===Honk/Hunke===
[[clown|hh-ho-ooonn-nk-kkk ww-hhh-yy i-iss-s see-ccu-uur-rrttt-yy bb-eeaa-tt-iinn-gg m-mme-ee hh-hoo-oon-nnk-kk]]

===[[Head of Personnel|HoP]]===
[[Head of Personnel]]. Should assign jobs and shit, but usually ends up giving himself Captain-level access, ignoring his job, and acting like a supercop in an [[The Owl|owl costume]].

===[[Head of Security|HoS]]===
The [[Head of Security]].

===Hulk===
Used to refer to the [[genetics|superpower]] or a person in possession of it. People with the Hulk gene turn green and become super strong, being able to punch through walls, windows, and other fixtures. Hurts like hell if one hits you. Hulks are an exception to some killing rules (see the [[Rules]] for details)

===Husk===
A corpse which has turned into a gray, ugly... mummified thing.

This has either happened by extreme heat (fire), extreme cold (space) or liquid suckification (changeling sucked their juices/DNA out). Not a nice thing to witness at first, but you get used to it.

[[Guide_to_medicine#Husk|How to Unhusk]]

===Hypo===
[[High-risk_items#Hypospray|Hypospray]].

===IC===
In Character. Stuff that is happening in the game.

===[[IC in OOC]]===
The act of describing anything happening in the game over the [[OOC]] channel. The rule of thumb is '''if a person not involved in the incident or not observing the game can still tell what's going on''', it's [[OOC|IC in OOC]]. Usually comes with a chastising and a thousand mini-mods squawking out "ICKY OCKY!!!" but excessive use results in a ban. (See the [[OOC]] page for details)

===[[Internals]]===
Usually an [[oxygen tank]] of some sort and a [[gas mask]]. Basically any worn item that lets you breathe when you otherwise can't.

===Internals Box/Survival Box===
That box which comes in a spawned player's backpack, containing a transparent breath mask, one emergency-sized tank of pure oxygen, and an epinehrine medipen.

There's a lot of spare room in there, so it's great place to keep things you don't access a lot but want to keep on you.

===Job Ban===
Similar to a [[Terminology#Ban|Ban]], except in this case you'll be prevented from playing a specific role, such as a [[gang|team-based antagonist]] or a [[Head of Security|head of staff]]. You may even get banned from playing an entire [[Science|department]] if you demonstrate an inability to follow the [[rules]].

===[[Random_events#Space_Vines|Kudzu]]===
Space vines. Can start growing randomly or be planted.

===Lag/Space Lag/Spacetime Distortions===
Concept common to almost all online gaming. Not worth explaining in depth here - basically it's the server (server-side lag) or your own computer (client-side lag) being slow and causing gaps between you doing stuff and it actually happening to grow. Sometimes referred as 'time warp' or something similar when players are in character.

===Lathe===
Short for the [[Autolathe]], located in [[Cargo]]. Could also be [[Protolathe]], located in [[R&D Lab]].

===[[Asimov|Law/Laws]]===
Rules which the [[AI]] and [[Cyborg]]s must follow. Are somewhat open to interpretation by the player, but the majority consensus and badmin rulings are what really count. May be modified or changed at an [[AI Upload|AI Upload Terminal]] using various modules, wiped back to the basic three using the Reset Module, or purged entirely with the Purge Module. Note that core modules cannot be removed by the standard reset module.

===[[Ling]]===
A [[Changeling]].

===[[Malf]]===
Short for malfunction. Can refer to either the [http://nanotrasen.com/wiki/index.php/Game_Mode#AI_Malfunction|AI Malfunction game mode], or to describe the AI in said mode.

===[[Mass Driver]]===
Computer or switch operated devices found in Toxins, the Chapel and arrivals Disposals.

Any objects on them when they are activated will be thrown forward at high speed, either into the bomb testing area (Toxins) or space (Chapel).

===Mini-mod===
Those players without admin or mod powers or responsibilities who chastise other players and list server rule infractions incessantly. They should be ignored.

===[[MMI]]===
A Man-Machine-Interface. Essentially player-cyborg-interface. A [[cyborg]] has one inside it. Enables the brain to speak and see.

Put a brain into an empty MMI, insert the whole thing into an empty [[cyborg]] and you can bring it back to life!

===Mod===
Could be used to refer to Moderator, the rank, or any admin.

===Murderboning===
Going on a killing spree.

===[[N2]]===
Nitrogen, an invisible gas kept in red canisters. Mostly useless but makes up a certain percentage of breathable air. Not to be confused with chemical reagent nitrogen from chemistry.

===[[N2O]]===
Nitrous Oxide, also known as laughing gas or anesthetic. White gas kept in red canisters with a white stripe, that will knock you out and suffocate you at high enough concentrations.

===[[Nanotrasen]]===
The autonomous super-corporation that built and operates the station, according to the [[backstory]].

Common misspellings include NanoTrasen, Nanotressen, Nanotransen, Nanotracer, and You Know That Fucking Company We Work For. (See CentCom for the difference between Nanotrasen and CentCom)

===Nar-Sie/Nar-Nar===
The eldritch deity whom [[cultists]] serve and often wish to summon.

===Notes===
A command which displays "'''Notes'''" kept in your character's memory, which you add with the "'''Add-Note'''" command. Some notes are automatically added depending on the circumstances, such as [[Revolution|revolutionaries]] having the list of rev members memorized, [[Syndicate]] leaders having the nuclear bomb code memorized, or the time of your death. Also refers to the top secret notes [[admin]]s keep on players, usually if they get banned.

===[[Nuke]]===
Can refer to either the [[Game Mode#Nuclear Emergency|Nuclear game mode]] (also known as Syndicate), or the Nuclear Fission Explosive used in said mode.

===[[O2]]===
[[Oxygen]]. Invisible gas usually kept in blue and white [[Canister]]s. Vital for reasons that you should already know, but deadly for reasons you [http://en.wikipedia.org/wiki/Oxygen_toxicity may not].

===One-Human(ed)===
Referring to a custom AI law that designates only one member of the crew as a human. Usually accompanied with an order to purge "non-humans."

===[[OOC]]===
The blue bolded chat channel which is shown to all players. Don't use this to talk about anything going on in the game (until right at the end of the game generally).

Might get switched off occasionally if it gets too idiotic. You can toggle the visibility of the ooc channel by using the corresponding command.

===[[OOC in IC]]===
The inverse of the much more common [[IC in OOC]]. Whenever a game mechanic, metafeature, or player-to-player conversation is referenced in the say or emote channels.

Heavily frowned upon as it ruins MY IMMERSIONNNN!

Talking ((Like this)) is still OOC in IC.

===Ops/Operatives===
Short for [[nuke ops]]. Generally heard over the radio shortly before the station goes boom.

===ORM===
Short for the Ore Redemption Machine, which is used to turn the materials miners bring into usable sheets. Often found in Cargo.

===Paladin===
A lawset for the [[AI]], your stereotypical white-knight good-guy role.

===Parapen===
The [[Sleepy Pen]] was previously called Parapen, short for Paralysis Pen.

===[[PDA]]===
Short for Personal Digital Assistant, a [[PDA|handheld device]] that acts as a pager, flashlight and other useful functions, depending on what cartridge is inserted.

===[[Perma|Perma/Permabrig]]===
The [[Prison Wing]] in the fore section of security, where prisoners are kept permanently.

===[[Plasma]]===
A.K.A. [[Plasma|Biotoxin]]. Purple gas kept in orange canisters. Poisonous and flammable.

Research into uses and properties of plasma is the station's prime reason for existence, according to the [[backstory]].

===Port===
Nautical term. It means the side of a ship on the left when one is facing forward, or in our case, west.

If you're the kind of person who likes mnemonic devices, it's useful to remember that ''PORT'' has the same number of letters as ''LEFT''.

===[[QM]]===
Usually refers to the [[Quartermaster]], but can also mean the [[Cargo Bay]] or the people who [[Cargo Technician|work there]].

===[[R&D|RnD/R&D]]===
Refers to [[Guide_to_Research_and_Development|Research and Development]], or the [[R&D|Laboratory]] that carries it out.

===[[Radio]]===
Normally refers to the headset on your head which can be used with the command '<code>say ";help that faggot traitor is griefing me"</code>', for example. Can also refer to station bounced radios and intercoms. Shows up as green text with a symbol and frequency appended to it. Additional department-specific radios also exsist. To use the equipped department radio's default department frequency use '<code>say ".h Hello Department!"</code>'. (See [[Radio]] for details or how to use the radio when it has multiple department frequencies available)

===[[RCD]]===
[[Rapid Construction Device]]. A piece of equipment that can quickly make and break floors, regular walls, and airlocks.

===[[Research Director|RD]]===
The [[Research Director]].

===Records===
Comes in two flavors, [[Computers|Security and Medical]], both accessible from terminals with red or white screens, respectively.

Medical Records are mostly useless and thus mostly unused, but Security Records contain useful fingerprint information and can be used to have [[Beepsky]] arrest people on sight.

===Redshirt===
[[Security Officer]]s, named for their signature red uniforms and tendency to die at the hands of everything.

===Redtext===
An alternate way of describing a loss as an antagonist. Derived from the red text used for 'fail'.

===Report/Centcom Report/Traitor Report===
A document printed out from communications consoles at the start of most [[Game Mode|game modes]]. Lists who might be the traitor and what might be their targets.

Inaccurate to the point where it's usually false. Do not treat this report as proof of anything.

===[[Rev]]===
Could refer to the game mode [[Game_Modes#Revolution|Revolution]], a member of the Revolution in said game mode, or a [[Revenant]].

===Revhead===
One of the leaders of the revolution in [[Game_Modes#Revolution|Revolution]] game mode.

===[[Robusting|Robust/Robusting]]===
The game's ROBUST COMBAT SYSTEM. To robust someone is to beat the shit out of them or at least win in a fight.

The definition of what exactly makes a crewmember robust varies from person to person, but it's almost universally agreed to mean being skilled despite the inherently clunky interface.

===[[RP]]===
(MY IMMERSION) "Role Play". Basically acting within the mental/emotional confines of your in-game character and not yourself. This is encouraged on our servers.

===[[Shitcurity]]===
A derogatory term for [[Security Officer]]s who are abusive, incompetent or generally shit. Can usually be heard shouted by the guy who just got arrested.

===[[Shuttle]]===
Most of the time refers to the Emergency [[Escape Shuttle]] which shows up at the end of the round. Can also refer to the Arrival Shuttle (where you start if you join late), the [[syndicate]] or [[wizard]] shuttle (which you'll rarely see, if ever), the Supply Shuttle (which brings items to the [[Quartermaster|Cargo Bay]]), or the mining and prison shuttles (which move people between the mining and prison stations, respectively).

===[[Signal]]===
A beep sent from a Remote Signalling Device. "Default Signal" is used to refer to the default setting of the devices, which is Frequency 147.9, Code 30.

Randomly signaling the default frequency/code is a good idea, and will cause nothing bad to happen ever.

===Silicon===
A term for [[AI]] or [[cyborg]] players, contrast with "human."

===[[Singulo|Singulo/Singuloth/Sing]]===
The [[Singularity|gravitational singularity]], what is essentially a black hole that emits radiation, this radiation is converted to power. It '''should''' be contained with a shield, if it isn't, don't stop to take in the view, get those legs moving.

===[[Shadowlings|Slings]]===
[[Shadowling]]s, one of the station's many antagonist types.

===Space Wind===
Shifts in air pressure that can cause players and items they're dragging to be knocked into space.

===Spacing===
The act of forcing or throwing someone out an airlock into space, usually for [[Traitor|malicious purposes]].

===[[SS13]]===
[[Space Station 13]]. Generally used to refer to the game rather than the actual station.

===SSD===
Stands for Space Sleep Disorder or Sudden Sleep Disorder. An in-character explanation for someone that has disconnected or has gone AFK.

===Starboard===
Nautical term. It means the side of a ship on the right when one is facing forward, or in our case, east.

===[[Supermatter|SM]]===
The [[Supermatter]].

===[[Syndie|Syndie/Synd]]===
Can refer to the organization known as the [[Syndicate]], a coalition of companies that execs their hate of [[Nanotrasen]], according to the [[backstory]], or to raid groups and operatives of said coalition. [[Traitor|Traitors]], traitor [[Cyborg]]s and traitor [[AI|AIs]] are Syndicate affiliates and [[Game Mode#Nuclear Emergency|Nuclear mode's]] premise revolves around a direct Syndicate attack. Ingame, they have randomized company names that usually look something like "GeoDyne West Operative #2" or "Waffle Co. Czar" and there are usually at least two of them and up to six. They also have access to a lot of special syndicate gear.

===Tabling===
The act of grabbing someone then clicking a table to instantly knock them down on it, usually followed by a toolbox in the skull or being stripped.

===[[Tele]]===
While usually referring to the [[Hand Teleporter]], it could also be referring to the full-fledged [[Teleporter]] in the [[Teleporter|Teleporter Room]]. Most people have no idea how to use it.

===Tesla===
The [[Tesla Engine]]. An alternative engine that [[Engineering]] can build. Also commonly referred to as the "goofball", so named for the programmer who created it.

===Testmerge===
Trying out new features or significant changes usually means temporarily merging that feature into the server in order to gather bug reports and feedback

===[[Tcomms|Tcomms/Telecomms]]===
[[Telecommunications]], the room holding servers that allows headsets to work. Does not affect [[Intercom]]s or [[Station Bounced Radio]]s.

===[[Thermals]]===
[[Optical Thermal Scanners]]. Green glasses which let you see people through walls and in the dark. The only thing they can't see through is hiding in closets. Generally not available to the crew.

===[[Toxins]]===
That section of the station east of [[Medbay]], better called the [[Research Division]] containing [[Guide to research and development|Research and Development]], [[Xenobiology]], the [[Toxins Lab]] and the [[Research Director]]'s office.

It is very rarely not filled with fire, hot gas, poisonous vapors, blood, acid, foam of all kinds and dangers, or the aftermath of all this destruction.

===[[Traitor]]===
Used to refer to the [[Game Mode|mode]] or an actual [[Traitor]] (assigned by the game mode or by admins).

===TraitorChan===
Used to refer to the [[Game_Mode#Traitor.2BChangeling|game mode]], a combination of [[Traitor]] and [[Changeling]].

===Valid/Validhunting===
Adjective: Someone whom it is allowed under the [[Rules]] to kill, usually on grounds of being a loud traitor. Verb: The act of killing or deliberately seeking out said kill. An inherently controversial subject.

===Voice in Your Head===
A subtle, in-character message from an admin.

===Vote===
A command which lets you call a vote to restart the game or change the game mode (which will restart the game anyway), or a request by other players indicating that the command should be typed. Calling votes when an unruined game is in progress for any reason is looked down upon, but it's not like votes work when the game really is ruined either. All votes are liable to being canceled by admins.

===VOX===
The audio announcement system that the [[AI]] will use to <s>curse at</s> send messages to the crew.

===WGW===
The legendary tale of [[Woody's Got Wood]]. The book obtained from the library. This vile tome is highly forbidden, and someone will eventually print it to spam over the radio any chance they get. Doing so will usually result in a station-wide manhunt, or the admin spawning a Space Carp named "Video Games" outside your hidey hole.

===[[Wormhole]]===
A black swirly portal that shows up during the Space-Time Anomaly random event or the verb used when thrown through a wormhole by an aggressor or your own stupidity. Anything coming into contact with a wormhole will be teleported to a random area on or off the station. They can be fairly dangerous or cause temporary blockades. Not to be confused with portals made from the Handheld Teleporter, which are blue or (more rarely) orange.

===[[Xeno]]===
Can refer to [[Aliens]], or [[Xenobiology]].

===[[Wizard]]===
Usually refers to the [[Wizard]] game mode, or a Wizard player who has access to a number of spells and will probably wreck your shit on sight or die in the first 12 seconds of a Wizard game.

===Z-Level===
Another area/map which the game consists of. Gameplay-wise, it's just a level.

Z-levels are areas you randomly spawn into when you go over the edge of an area. Part of BYOND's functionality. For example, the station, DJ station, Central Command and the [[Derelict]] are all on different Z-levels. Going off the edge of one Z-Level will take you to another.

[[Категория:Руководства]]

Картографические истины

2022-04-07T21:18:52Z

TrashDoxx: Запоздалое продолжение работы.

{{wip
|assign = TrashDoxx}}
== Руководство для страждующих мапперов ==
'''Адресовано как тем, кто имеет хоть какое-то представление о том, как пользоваться редактором, так и для тех, кто не имеет его вовсе.'''

Я понятия не имею, насколько опытен тот, кто это читает, поэтому начну с самых азов. Во-первых, вам нужно получить копию всех файлов для редактирования. Для этого перейдите в требуемый репозиторий (например, [https://www.github.com/ss220-space/tgstation сюда]) и нажмите зелёную кнопку '''Code''', затем, в выпадающем меню выберите '''Download ZIP'''. Если вы пока не имеете представления о том, что делаете - этого будет достаточно для ознакомления. Но конечно, если вы уже умеете обращаться с версиями проектов на '''GitHub''', вы можете использовать привычные для себя инструменты. Когда вы получите архив - распакуйте его куда вам угодно.

Итак, теперь у вас есть папка с последней версией кода и резервная копия в архиве, к которой можно вернуться, если вы всё сломаете. В основной папке вы увидите файл в формате - '''.dme''', который содержит в себе ссылки на всё, что должно быть в игре после компиляции. Фактически, это такая среда с необходимыми ресурсами. Вам необходимо открыть этот файл. Для этого вы можете использовать встроенный инструментарий BYOND'а или внешние редакторы, о которых я упомяну позднее. На данный момент вам достаточно дважды кликнуть по нему. Когда вы откроете программу, вы увидите две вкладки слева: '''File''' и '''Object'''. Во вкладке '''File''' откройте директорию с картами, а затем откройте файл в формате - '''.dmm'''. Именно в этом формате записываются игровые карты. В результате вы получите что-то похожее на это:

[Тут могла быть ваша реклама, но она появится чуть позднее].

Переключитесь с вкладки '''File''' на вкладку '''Object''' и вы увидите '''области (area)''', '''мобов (mob)''', '''объекты (object)''' и '''покрытия (turf)'''. Это четыре основных слоя с которыми вам предстоит работать. Вы можете переключать их видимость, а также более детально настраивать их интерактивную видимость с помощью контекстного меню сверху - '''Layers'''. Я бы посоветовал скопировать эту карту и переименовать ее, скажем, в '''test.dmm'''. Возможно, удалите большую часть или всю станцию по умолчанию и стройте на пустом теперь Z-уровне, где захотите. Чтобы строить, используйте дерево объектов в левой части пользовательского интерфейса для выбора объектов, затем щелкните, чтобы разместить их. Простой щелчок позволяет разместить по одному предмету на плитку из каждой категории, в то время как Ctrl-клик складывает его поверх всех предыдущих, а Shift-клик удаляет самый верхний предмет. Можно открыть несколько карт одновременно - у меня обычно открыта основная карта и её экспериментальная копия, что предназначена для изменений. В таком случае бесстыдно копировать-вставлять вещи гораздо проще. Кроме того, поиск предметов в дереве объектов может быть чертовски утомительным - щелкните правой кнопкой мыши на предмете, который вы видите, и вы увидите его путь в дереве - obj/structure/closet/etc. Это поможет вам найти вещи. С этого момента, действительно, можно приступать к созданию карты.

Вы можете выбрать области для копирования/вставки/удаления, а также войти в режим добавления или заливки при размещении объектов. В общем, просто пощёлкайте по всем меню и вы поймете, как они работают, более или менее. Опции > Увеличение позволяет уменьшить масштаб до 50%, чтобы увидеть больше вещей. Используйте слои, чтобы выбрать, какую область, объекты и территорию вы хотите редактировать. Если вы действительно хотите иметь возможность видеть что-либо, я бы отменил выделение области и поставил галочку "показывать только выделенные слои".

Первым шагом будет создание нескольких помещений. Выберите турфы (пол) из общих смоделированных полов. Они будут иметь нужный состав и давление воздуха на них, что вам и нужно. Окружите эти полы стенами, и вот вам комната. Попробуйте поставить там несколько столов, возможно, торговый автомат или два.

Если вы хотите добавить несколько фишек в ваше новое логово, но вам не нравится, как они аккуратно уложены друг на друга, вы можете изменить их значения "pixel_x" и "pixel_y" в rmb-меню "edit", чтобы расположить их так, как вам хочется! (Не забывайте начинать и заканчивать значение двойными кавычками! Кроме того, все пользовательские значения выделены жирным шрифтом, чтобы их было легче идентифицировать.) На самом деле, большинство настенных автоматов на станциях смещены именно так, и хотя они кажутся расположенными на стене, на самом деле они находятся на плитке перед ней. Только не переусердствуйте с этим, так как каждый новый экземпляр объекта добавляется как отдельный пункт в меню, а когда их десятки, бывает трудно вспомнить, какой из них вам нужен. Как только вы обустроите комнату, вам захочется установить в ней свет.

{|
|[[File:Mystery pipe.png|left|frame|There is one uninvited guest here!]]
|'''Важно:''' Во время строительства вы можете обнаружить, что вам нужен объект с определенным направлением (окна, трубы, кабели и т.д.), который не отображается в вашем меню. Это происходит потому, что BYOND не симулирует экземпляры объекта, кроме его базового состояния, если они не присутствуют на карте. Вы можете создать их, щелкнув правой кнопкой мыши на объекте и выбрав "generate instance from state/direction". Эта функция имеет нежелательную особенность, при которой сгенерированный объект иногда автоматически добавляет метку. Эти метки могут вызывать ошибки в работе некоторых функций игры во время раунда, и их необходимо удалять. Чтобы проверить это, щелкните правой кнопкой мыши объект на карте или в меню, выберите "редактировать" и прокрутите до строки "тег", которая должна быть пустой, за исключением двух двойных кавычек (""). Если это не так (что легко определить, поскольку тег массивный и жирный, его невозможно пропустить даже при прокрутке со скоростью света), измените его. В хорошо поддерживаемых картах таких тегов обычно нет, так что можете смело копировать-вставлять на свое усмотрение. В качестве совета, помните, что все нестандартные объекты имеют свой собственный пункт в меню, а наличие тега вообще не является стандартным для большинства объектов!
|}
{|
|[[File:Editinstance.png|left|200px]]
| So now we get to the basics of making a functioning room. First of all, you'll need to re-enable the area layer. Pick some area from the object tree, and cover your room in it. You can rename this area if you want, we'll do that later. Make sure the area isn't used anywhere else on the map. Each area should have one APC or Area Power Controller in it. Copy one in from the default map or spawn one yourself, then rename its "name" variable through "edit" to something appropriate. If you copied your APC from another map, chances are that cell type and dir are both in bold. Cell type defines how much power the APC can hold, and for your first map you'll want to set this nice and high as you don't have any sort of generator yet - 10,000 ought to do. Dir defines the direction the APC is in with regards to the cell it occupies. Basically, 1 means it is above the cell you place it in, 2 is below, 4 is to the right and 8 to the left.

Note that with APCs, '''dir ''' is the only variable controlling their position. Other objects have their positions defined by '''pixel_x '''and '''pixel_y''' - this changes where APCs appear in the editor, but once ingame they snap to whatever the '''dir''' variable says. Other things, like signs on walls, will only take notice of the pixel variables and not necessarily dir. In a normal power system, you'd connect the APC up to all the others and the station's generator via SMES cells, but we'll do that later. For now you have a basic room that is powered and starts with enough air to breathe happily. You can put an air canister in if you think you'll consume all the oxygen, or somesuch.
|[[File:Directions.png|right|200px]]
|}

'''Important Note:''' There are '''nudge_x '''and '''nudge_y''' variables in the editor, as well as various z-axis variables. Don't ever change these, they're not used in SS13 and break things.

To be able to actually spawn into a room, you'll want to place spawners. You'll see these as the big red X symbols on the default map, for each role. There are also blue Xs for xeno spawn locations and the spawns for all latecomers on the arrival shuttle. Stick in a spawn_late somewhere in your room for now.

To actually play your map and be able to screw around in it as an admin, you'll have to compile it. First, make sure the file tree (on the left like the object tree, click the file tab) is open, and go to maps. Make sure the only one ticked is your own. Then click Build>Compile from the top, and wait for it to finish. This will give you a something like "tgstation.dmb" in the folder containing bot, code, config, maps, etc. Whilst here, quickly go into config, and open 'admins.txt'. Replace everything in there with:

"<yourbyondname> = Game Master", filling in your BYOND name.

This will make you an admin, which is very helpful for tinkering ingame. Now to actually boot up a server so you can run your map! Find 'Dream Daemon' (has a big green icon) in your BYOND folder, and click the 'File' dropdown at the bottom. Select your "tgstation.dmb". Select a port if you want, put security on safe, and visibility to invisible, for now. Click start to start the server, which will take a little while. You can then connect to it through BYOND by putting in either your external IP, shown in Dream Daemon, if that port is correctly forwarded. Otherwise use your internal IP, 192.168.x.x, where x is whatever. If you don't know this, ask and I can help. Once in, go to the admin tab and click 'start game'. By joining after the start, you'll spawn at the late spawn you made, and, being an admin, will be able to make stuff, delete stuff, and other handy admin things (like causing massive explosions).

From there on, you can make whatever you like, really. Copying the default map and working out how everything works isn't too hard and is fairly rewarding. You could just tweak the default one for a bit if you like. The first thing I made was a small shuttle - you can see this at the bottom. Just tweak it and add stuff and you'll work out how almost everything works fairly easily. For explanations of wiring, piping, and atmos, ask away on here. I'll add an atmos guide later on, as well as a power generation and wiring guide. If you're a good engineer in-game, it'll help a lot as a mapper.

If you've managed to get all the way to the end of this before I've added more, fine effort on your part. Have fun screwing around with stuff, and feel free to ask anything you like. I'll add more stuff here soon.

== Pre-commit checks ==

*Are floors with or without air, as they should be? (regular or airless)
*Does the area have an APC?
*Does the area have an Air Alarm?
*Does the area have a Request Console?
*Does the area have lights?
*Does the area have a light switch?
*Does the area have enough intercoms?
*Does the area have enough security cameras? (Use the verbs under Mapping for help)
*Is the area connected to the scrubbers air loop?
*Is the area connected to the vent air loop? (vent pumps)
*Is everything wired properly?
*Does the area have a fire alarm and firedoors?
*Do all pod doors work properly?
*Are accesses set properly on doors, pod buttons, etc.
*Are all items placed properly? (not below vents, scrubbers, tables)
*Does the disposal system work properly from all the disposal units in this room and all the units, the pipes of which pass through this room?
*Check for any misplaced or stacked piece of pipe (air and disposal)
*Check for any misplaced or stacked piece of wire
*Identify how hard it is to break into the area and where the weak points are, and balance the area accordingly (eg. the Vault should be made of reinforced structures and electrified windows, the Kitchen should not)
*Check if the area has too much empty space. If so, make it smaller and replace the rest with maintenance tunnels
*Are there any [[guide_to_mapping#Room Structure|indestructible turfs]] where they shouldn't be?

== General Station-wide Mapping Guidelines ==

=== In general ===
* Don't run pipes/cables/disposals through walls if you can avoid it. Otherwise it's a pain to repair or sabotage them, especially under r-walls.
* Try to connect departments to maintenance through a back or side door. This lets players escape and allows antags to break in. Metastation is a good example for this.

=== Atmospherics ===
* Each area should have EXACTLY one air alarm (Exceptions are only possible if a room has scrubbers or vent pumps on different frequencies).
* Each ROOM (Walled off space) should have at least one vent pump and scrubber, which is properly connected to its respective loop. Keep in mind that scrubbers don't detect gases/pressure; only air alarms do.
* The air supply loop's pipes should be colored blue.
* The scrubbers loop's pipes should be colored red.
* Some areas require special air alarm subtypes: /engine for the SME and /server for tcomms or the RnD server room.

=== 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.

== Atmospherics ==

=== Pipes and manifolds ===

Atmospherics releases it's cocktail of gases into the air supply loop (blue pipes). The station is also equipped with a scrubber loop, which filters unwanted gases and sends them back to atmospherics via the scrubber loop (red pipes).

If you're expanding the air supply loop (blue pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/supply/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/supply/visible and ../hidden.

If you are expanding the scrubber loop (red pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/scrubbers/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/scrubbers/visible and ../hidden.

If you are however building a pipe network which has nothing to do with the air supply or scrubbers loop, you should use the objects in /obj/machinery/atmospherics/pipe/simple/general/visible or ../hidden. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/general/visible and ../hidden.

To add new colors of pipes, you will need add a new subtypes in the appropriate .dm files located in tgstation\code\modules\atmospherics\machinery\pipes

Please refrain from var-editing pipes, as it typically introduces graphical glitches and other issues.

=== Air Alarm ===

Every single area (with scrubbers and/or vent pumps) should have exactly one air alarm. More than one should be placed if vent pumps or scrubbers use different radio frequencies than the default one (1439).

=== Scrubbers (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one scrubber.

The path for scrubbers that start on is '''/obj/machinery/atmospherics/components/unary/vent_scrubber/on'''

And make sure the '''id_tag''' is the default one (null)

Also ensure the scrubber is connected to the scrubber loop!!

=== Vent Pumps (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one vent pump.

The path for vents that start on is '''/obj/machinery/atmospherics/components/unary/vent_pump/on'''

Please make sure the '''id_tag''' is the default one (null)

Also ensure the vent pump is connected to the air supply loop!!

=== Gas tanks and filters ===

Each station should have a full set of these - or at the bare minimum, one for N2, one for O2 and a third tank to filter dangerous gases into.

[[File:Atmos mapping.jpg|right|frame|Left to right: N2, O2, Airmix. The canisters inside are just for decoration.]]

Each gas tank needs:
* '''Outside''': A tank computer and a gas filter to pick what gases will be filtered into it.
* '''Inside''': A gas injector (input), a vent pump (output), a gas sensor and a specific turf.

The tank computer controls the input/output and receives data from the gas sensor.

The specific turf creates the gases that will be inside each tank - the gas canister is just for decoration.

Let's take a look at the MetaStation N2 tank:

* '''Tank computer''': /obj/machinery/computer/atmos_control/tank/nitrogen_tank
* '''N2 filter''': /obj/machinery/atmospherics/components/trinary/filter/atmos/n2
* '''Gas injector''': /obj/machinery/atmospherics/components/unary/outlet_injector/atmos/nitrogen_input
* '''Vent pump''': /obj/machinery/atmospherics/components/unary/vent_pump/siphon/atmos/nitrogen_output
* '''Gas sensor''': /obj/machinery/air_sensor/atmos/nitrogen_tank
* '''Turf''': /turf/open/floor/engine/n2

These objects have all the neccessary vars preset and start switched on - you'll only have to edit the dir if neccessary.

Additionally, you'll want this type of gas mixer for the airmix tank (N2 + O2):

* '''Air mixer''': /obj/machinery/atmospherics/components/trinary/mixer/airmix

== Power ==

=== APC ===
Each new room needs at least one, this will provide all the power for the room (magically). Each piece of machinery inside the APC's area will draw power from either the lighting, equipment or environmental channel.

Any room that is very equipment heavy (for example cargo bay) may need a beefed up APC (apc/highcap) to prevent early blackouts. These start with higher capacity power cells.

=== Wiring ===
Make sure the wires lead from the main power grid, and to the APC(s) of your area. If any equipment in your new area requires a wire under it, line it up, connected to the main power grid, and under the machinery.

Wires are also helpful when making electrical grilles (just dot wire under a grille), make sure the wires touch the main power grid (or they won't shock people).

== Equipment ==

=== Lights ===
Lights take up a lot of power, don't use too many! Make sure to put in just enough so the room is fully lit, but not so many that the equipment will go out in ten minutes of the round starting.

=== Light switch ===
For mood lighting, or to show the room is currently not in use by the primary occupant. These disable the lighting equipment (and power drain associated) in the area, but not desk lamps. Place these on walls, usually by a door.

=== Request Console ===
If a certain room has no need for materials, or produces no materials, do not give it a Request Console. If it does (for either case or both) make sure it has at least one, that is in a place where some one will see it.

=== Intercoms ===
At least every room should have one of these. They should be set to 145.9, and be speaker ON Microphone OFF. This is so radio signals can reach people even without head sets on. Larger room will require more than one at a time.

=== Security Cameras ===
Most areas should have these, enough to see the general area from a Human point of view, but, not bunched together for the AI's sake. Larger rooms may require more than one.

== Room Structure ==

=== Access ===
''' Refer to ..\code\__DEFINES\access.dm for door access values.'''

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'''.

[[File:DoorAccessImage1.png|thumb|left|300px]] This image shows a door on the Arrivals shuttle - since it's a public door, the access is set to "0", as everyone should be able to open it. If we look at the Brig front door, we would set the access to 63, because that's the value for Security front doors - accessible by Security positions, but no one else.

Multiple accesses to doors are handled by adding a semicolon (with no spaces) between access values (eg. "28;31" is for Kitchen and Cargo access). This might seem worthless, but it's useful for small maps, where jobs might need to share access due to cramped spaces.

There's an important difference between the two that you need to pay attention to - req_access_txt requires '''ALL LISTED ACCESSES''' to open the door, while req_one_access_txt lets anyone with '''ONE OF THE LISTED ACCESSES''' open the door. For example - say you want your Brig to be openable by the Detective and Security Officers, we would put "63;4" in '''req_one_access_txt''', because we want the Detective '''AND''' Security to have access. If we used req_access_txt, you would need '''BOTH''' accesses to open the door, meaning neither the Detective or Security could open it.

You can view all of the access values in the code/game/jobs/access.dm file. (Most should be self explanatory or have a label, but if you really aren't sure, you can take a look at Boxstation's map file and check the value on the door you're looking for).

=== Airless Floors ===

Ideal for rooms or chambers that mix gas, and for tiles exposed to space. Not ideal for areas that humans will cross in frequency.

Use these on external tiles (to prevent lag when the game starts) and chambers that will require gas mixing (toxins mix chamber/ furnace). Double check these to make sure you don't suffocate mobs in the new rooms.

=== Fire Alarms and Fire Doors ===
Make sure to put these INSIDE of the boundary of the area, so there is a lock down. Any spot that gets hot as a normal function should not have a fire Alarm right next to the heat source (toxin mix chamber). Make sure there is a fully sealed area (with the exception of maintenance doors for people to escape fires) that can't be open by normal civilians.

=== Weak Points ===
Judge how high security the room will be, if it is high security, reinforced walls and electrified grill windows may be in order. Areas that do not need a lot of security can use basic walls, and windows to your liking (though normal glass windows break very very easy). Each room should have one place that's weaker than the rest (like a back door, side entrance, or a window), just because the main entrance might be out of commission (and realistically, for traitors to break into).

=== Item and Machinery Distribution ===
Be smart about what will go in an area, keep a fine balance between the size of the room and amount of equipment. Large rooms may require multiple APCs to prevent power outages early in game. Second, make sure to place equipment that make sense for the area (security computer in a security area/ Medical vendor in a medical area).

=== Indestructible Turfs ===
Before you finalize a map, check for any indestructible turfs. These turfs ignore things like external damage and are typically meant for things like special ruins/rooms where you want to avoid people trying to circumvent a path. Due to these characteristics, they have no real place on regular station maps and would probably lead to confusion for players more than anything.

== Balance ==

=== Item contents ===
The harder the room is to enter, the more goodies or sensitive equipment there is inside. Make sure to keep this in mind (and don't make an empty room that's covered in blast doors, electrified grills, reinforced walls, and captain level doors).

=== Room security ===
A room is only as secure as its necessity. Public rooms should not have many security functions (other than a fire alarm), but private work space must be more secure (based on job). The bartenders do not need reinforced walls around their storage, but engineers do.

The highest security rooms should utilize the highest security measures. The lowest security rooms should utilize the cheapest security measures.

== Step_x, step_y and the broken movement syndrome ==

So you compiled the map and suddenly whenever you move you no longer get the animation of moving but just 'appear' on the next tile?

So a while back step_x and step_y were introduced to allow pixel based movement. SS13 does not utilize this. Step_x and step_y are variables that each atom has. The way they work is that as soon as you set any object on the map to use one of these variables, the game interprets that you overrode all default movement code and wrote your own - but you didn't (The code that makes the animation from tile to tile).

To fix this problem you need to close dream maker (save the project first, obviously). Open your map (.dmm) file in a text editor, such as notepad or notepad++. Search (ctrl+f) through the file for step_x and step_y and remove any reference to it. Once no more step_x or step_y -es are found in the file, save it and open it in dream maker once again. Compile the code and movement should work fine once more. Go to [[Community|the development IRC]] if you need more help.

==Shuttles==
Basically there's 3 types of shuttle dock stationary, transit and mobile
*stationary == places where the shuttle can dock
*transit == shuttle as it moves
*mobile == the place with the actual shuttle
so you'd have a transit dock in the transit area and 2 stationary docks, one in centcomm and the other one in the station and 1 mobile dock, in centcomm for most shuttles (apart from mining)

The shuttle docks are grouped by id eg id = "cargo_away" id = "cargo_transit"

You need to add the dock types to the map and edit the bounding boxes via varediting the dock, you need to varedit height, width, dheight and dwidth at minimum. These are offset by the dir so do keep that in mind, eg if dir == 2 then width goes from EAST to WEST, if dir == 4 then width goes from NORTH to SOUTH and dwidth/dheight are offsets from the lower-left corner of the plane switched to the dock's dir

You should also ensure the directions face the shuttle or face away from the thing the shuttle docks with.

If a shuttle's mobile docking port direction is different then the stationary docking port's direction, the shuttle and all items on it will be rotated accordingly. (Try it, it works properly for just about everything)

'''Warning the bounding box for the mobile dock must fit inside of the stationary dock (after any rotation)''' Or the shuttle will refuse to move.

If the shuttle's mobile docking port is in an area that is a subtype of /area/shuttle, Only turfs in the bounding box in that same area are moved. Otherwise it moves all turfs in the bounding box. This can be used for odd shaped shuttles. (the area will be transfer over as well)

Also note that the emergency shuttle and cargo shuttle need special subtypes of the dock type eg so /obj/docking_port/mobile/emergency

The other variables of note is traveldir, which defines if the shuttle rotates on transit, it's an angle in degrees (just imagine the shuttle is inside a circle . For example, if you want the shuttle going right to left set it to 270 degrees.

===Dwidth and Dheight in more depth===
dwidth/dheight is the offset of the docking_port obj from the (0,0) bounding box corner. In dir == 1 (north) 0,0 is the bottom left corner? This changes for each direction, For example when dir is 2 it's the upper right corner. so dwidth and dheight identify where the bounding box starts relative to the docking port obj whereaswidth and height determine the actual width and height of the bounding box

'''Note: We count step 0 as a tile, so a height and width of 9 is actually 10 tiles (tile 0 to tile 9)'''

Here is an example for the north facing shuttle dock direction - you can rotate this image to determine where the offset is for each other cardinal direction
[[File:ShuttleBox.png]]

==Other files==
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.

==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

== 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.

== На будущее ==
Other related guides: [[Understanding SS13 code]], [[SS13 for experienced programmers]], [[Guide to door access]] and [[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.

{{Contribution guides}}

Guide to mapping

2022-03-10T17:51:58Z

TrashDoxx: TrashDoxx переименовал страницу Guide to mapping в Картографические истины: Русификация. Вероятно, изменю позднее.

#перенаправление [[Картографические истины]]

Картографические истины

2022-03-10T17:51:58Z

{{wip
|assign = TrashDoxx}}
== Руководство для страждующих мапперов ==
'''Адресовано как тем, кто имеет хоть какое-то представление о том, как пользоваться редактором, так и для тех, кто не имеет его вовсе.'''

Я понятия не имею, насколько опытен тот, кто это читает, поэтому начну с самых азов. Во-первых, вам нужно получить копию всех файлов для редактирования. Для этого перейдите в требуемый репозиторий (например, [https://www.github.com/ss220-space/tgstation сюда]) и нажмите зелёную кнопку '''Code''', затем, в выпадающем меню выберите '''Download ZIP'''. Если вы пока не имеете представления о том, что делаете - этого будет достаточно для ознакомления. Но конечно, если вы уже умеете обращаться с версиями проектов на '''GitHub''', вы можете использовать привычные для себя инструменты. Когда вы получите архив - распакуйте его куда вам угодно.

Итак, теперь у вас есть папка с последней версией кода и резервная копия в архиве, к которой можно вернуться, если вы всё сломаете. В основной папке вы увидите файл в формате - '''.dme''', который содержит в себе ссылки на всё, что должно быть в игре после компиляции. Фактически, это такая среда с необходимыми ресурсами. Вам необходимо открыть этот файл. Для этого вы можете использовать встроенный инструментарий BYOND'а или внешние редакторы, о которых я упомяну позднее. На данный момент вам достаточно дважды кликнуть по нему. Когда вы откроете программу, вы увидите две вкладки слева: '''File''' и '''Object'''. Во вкладке '''File''' откройте директорию с картами, а затем откройте файл в формате - '''.dmm'''. Именно в этом формате записываются игровые карты. В результате вы получите что-то похожее на это:

[Тут могла быть ваша реклама, но она появится чуть позднее].

Switch from the '''files''' tab to the '''objects''' tab, and you'll see '''area''', '''mob''', '''objects''', and '''turf'''. These are the four primary 'layers' that you can see in the editor. You can toggle their visibility and interactivity on and off using the '''layers '''dropdown. I'd advise copying this map, and renaming it to, say, teststation.dmm. Perhaps delete most or all of the default station, and build on the now-empty z-level, wherever you like. To build stuff, use the object tree on the left of the UI to select things, then click to place them. A simple click lets you place one item per tile from each category, while Ctrl-click '''stacks''' it on '''top''' of all previous ones and Shift-click deletes the '''topmost''' item. You can have multiple maps open at once - I usually have the default /tg/station map and mine open, and can then shamelessly copy-paste things far more easily. Also, finding stuff in the object tree can be tedious as hell - right click something you see and you can see its path in the tree - obj/structure/closet/etc. This will help you find things. From this point on, really, you can begin mapping proper.

You can select areas to copy/paste/delete, or enter add or fill mode when placing objects. Basically just click around all the menus and you'll work out how they work, more or less. '''Options>Zoom''' allows you to zoom out to 50% to see more stuff. Use layers to select which of area, objects and turf you want to edit. If you actually want to be able to see anything, I'd deselect area, and tick 'only show selectable layers'.

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. Once you've made your room you'll want to put lights in.

{|
|[[File:Mystery pipe.png|left|frame|There is one uninvited guest here!]]
|'''Important:''' While building your station you might find yourself in need of an object with a specific alignment (windows, pipes, cables etc) that does not appear in your menu. This is because BYOND does not simulate instances of an object other than its base state unless they are present on the map. You can generate them by right clicking an object and selecting "generate instance from state/direction". This function has an '''unwanted feature''' in which a generated object sometimes has a tag added automatically. These tags can cause error with certain features of the game during a round, and need to be removed. To check for it, right click an item on the map or in the menu, select "edit" and scroll to the "tag" line, which should be empty save for two doublequotes (""). If it's not (which is easy to tell since the tag is massive and bold, impossible to miss even scrolling at lightspeed), change it. Well maintained maps don't usually contain these, so you should be safe to copy-paste to your heart's content. As a tip, remember that all non-standard objects have their own entry in the menu, and having a tag is not standard at all for most object!
|}
{|
|[[File:Editinstance.png|left|200px]]
| So now we get to the basics of making a functioning room. First of all, you'll need to re-enable the area layer. Pick some area from the object tree, and cover your room in it. You can rename this area if you want, we'll do that later. Make sure the area isn't used anywhere else on the map. Each area should have one APC or Area Power Controller in it. Copy one in from the default map or spawn one yourself, then rename its "name" variable through "edit" to something appropriate. If you copied your APC from another map, chances are that cell type and dir are both in bold. Cell type defines how much power the APC can hold, and for your first map you'll want to set this nice and high as you don't have any sort of generator yet - 10,000 ought to do. Dir defines the direction the APC is in with regards to the cell it occupies. Basically, 1 means it is above the cell you place it in, 2 is below, 4 is to the right and 8 to the left.

Note that with APCs, '''dir ''' is the only variable controlling their position. Other objects have their positions defined by '''pixel_x '''and '''pixel_y''' - this changes where APCs appear in the editor, but once ingame they snap to whatever the '''dir''' variable says. Other things, like signs on walls, will only take notice of the pixel variables and not necessarily dir. In a normal power system, you'd connect the APC up to all the others and the station's generator via SMES cells, but we'll do that later. For now you have a basic room that is powered and starts with enough air to breathe happily. You can put an air canister in if you think you'll consume all the oxygen, or somesuch.
|[[File:Directions.png|right|200px]]
|}

'''Important Note:''' There are '''nudge_x '''and '''nudge_y''' variables in the editor, as well as various z-axis variables. Don't ever change these, they're not used in SS13 and break things.

To be able to actually spawn into a room, you'll want to place spawners. You'll see these as the big red X symbols on the default map, for each role. There are also blue Xs for xeno spawn locations and the spawns for all latecomers on the arrival shuttle. Stick in a spawn_late somewhere in your room for now.

To actually play your map and be able to screw around in it as an admin, you'll have to compile it. First, make sure the file tree (on the left like the object tree, click the file tab) is open, and go to maps. Make sure the only one ticked is your own. Then click Build>Compile from the top, and wait for it to finish. This will give you a something like "tgstation.dmb" in the folder containing bot, code, config, maps, etc. Whilst here, quickly go into config, and open 'admins.txt'. Replace everything in there with:

"<yourbyondname> = Game Master", filling in your BYOND name.

This will make you an admin, which is very helpful for tinkering ingame. Now to actually boot up a server so you can run your map! Find 'Dream Daemon' (has a big green icon) in your BYOND folder, and click the 'File' dropdown at the bottom. Select your "tgstation.dmb". Select a port if you want, put security on safe, and visibility to invisible, for now. Click start to start the server, which will take a little while. You can then connect to it through BYOND by putting in either your external IP, shown in Dream Daemon, if that port is correctly forwarded. Otherwise use your internal IP, 192.168.x.x, where x is whatever. If you don't know this, ask and I can help. Once in, go to the admin tab and click 'start game'. By joining after the start, you'll spawn at the late spawn you made, and, being an admin, will be able to make stuff, delete stuff, and other handy admin things (like causing massive explosions).

From there on, you can make whatever you like, really. Copying the default map and working out how everything works isn't too hard and is fairly rewarding. You could just tweak the default one for a bit if you like. The first thing I made was a small shuttle - you can see this at the bottom. Just tweak it and add stuff and you'll work out how almost everything works fairly easily. For explanations of wiring, piping, and atmos, ask away on here. I'll add an atmos guide later on, as well as a power generation and wiring guide. If you're a good engineer in-game, it'll help a lot as a mapper.

If you've managed to get all the way to the end of this before I've added more, fine effort on your part. Have fun screwing around with stuff, and feel free to ask anything you like. I'll add more stuff here soon.

== Pre-commit checks ==

*Are floors with or without air, as they should be? (regular or airless)
*Does the area have an APC?
*Does the area have an Air Alarm?
*Does the area have a Request Console?
*Does the area have lights?
*Does the area have a light switch?
*Does the area have enough intercoms?
*Does the area have enough security cameras? (Use the verbs under Mapping for help)
*Is the area connected to the scrubbers air loop?
*Is the area connected to the vent air loop? (vent pumps)
*Is everything wired properly?
*Does the area have a fire alarm and firedoors?
*Do all pod doors work properly?
*Are accesses set properly on doors, pod buttons, etc.
*Are all items placed properly? (not below vents, scrubbers, tables)
*Does the disposal system work properly from all the disposal units in this room and all the units, the pipes of which pass through this room?
*Check for any misplaced or stacked piece of pipe (air and disposal)
*Check for any misplaced or stacked piece of wire
*Identify how hard it is to break into the area and where the weak points are, and balance the area accordingly (eg. the Vault should be made of reinforced structures and electrified windows, the Kitchen should not)
*Check if the area has too much empty space. If so, make it smaller and replace the rest with maintenance tunnels
*Are there any [[guide_to_mapping#Room Structure|indestructible turfs]] where they shouldn't be?

== General Station-wide Mapping Guidelines ==

=== In general ===
* Don't run pipes/cables/disposals through walls if you can avoid it. Otherwise it's a pain to repair or sabotage them, especially under r-walls.
* Try to connect departments to maintenance through a back or side door. This lets players escape and allows antags to break in. Metastation is a good example for this.

=== Atmospherics ===
* Each area should have EXACTLY one air alarm (Exceptions are only possible if a room has scrubbers or vent pumps on different frequencies).
* Each ROOM (Walled off space) should have at least one vent pump and scrubber, which is properly connected to its respective loop. Keep in mind that scrubbers don't detect gases/pressure; only air alarms do.
* The air supply loop's pipes should be colored blue.
* The scrubbers loop's pipes should be colored red.
* Some areas require special air alarm subtypes: /engine for the SME and /server for tcomms or the RnD server room.

=== 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.

== Atmospherics ==

=== Pipes and manifolds ===

Atmospherics releases it's cocktail of gases into the air supply loop (blue pipes). The station is also equipped with a scrubber loop, which filters unwanted gases and sends them back to atmospherics via the scrubber loop (red pipes).

If you're expanding the air supply loop (blue pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/supply/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/supply/visible and ../hidden.

If you are expanding the scrubber loop (red pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/scrubbers/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/scrubbers/visible and ../hidden.

If you are however building a pipe network which has nothing to do with the air supply or scrubbers loop, you should use the objects in /obj/machinery/atmospherics/pipe/simple/general/visible or ../hidden. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/general/visible and ../hidden.

To add new colors of pipes, you will need add a new subtypes in the appropriate .dm files located in tgstation\code\modules\atmospherics\machinery\pipes

Please refrain from var-editing pipes, as it typically introduces graphical glitches and other issues.

=== Air Alarm ===

Every single area (with scrubbers and/or vent pumps) should have exactly one air alarm. More than one should be placed if vent pumps or scrubbers use different radio frequencies than the default one (1439).

=== Scrubbers (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one scrubber.

The path for scrubbers that start on is '''/obj/machinery/atmospherics/components/unary/vent_scrubber/on'''

And make sure the '''id_tag''' is the default one (null)

Also ensure the scrubber is connected to the scrubber loop!!

=== Vent Pumps (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one vent pump.

The path for vents that start on is '''/obj/machinery/atmospherics/components/unary/vent_pump/on'''

Please make sure the '''id_tag''' is the default one (null)

Also ensure the vent pump is connected to the air supply loop!!

=== Gas tanks and filters ===

Each station should have a full set of these - or at the bare minimum, one for N2, one for O2 and a third tank to filter dangerous gases into.

[[File:Atmos mapping.jpg|right|frame|Left to right: N2, O2, Airmix. The canisters inside are just for decoration.]]

Each gas tank needs:
* '''Outside''': A tank computer and a gas filter to pick what gases will be filtered into it.
* '''Inside''': A gas injector (input), a vent pump (output), a gas sensor and a specific turf.

The tank computer controls the input/output and receives data from the gas sensor.

The specific turf creates the gases that will be inside each tank - the gas canister is just for decoration.

Let's take a look at the MetaStation N2 tank:

* '''Tank computer''': /obj/machinery/computer/atmos_control/tank/nitrogen_tank
* '''N2 filter''': /obj/machinery/atmospherics/components/trinary/filter/atmos/n2
* '''Gas injector''': /obj/machinery/atmospherics/components/unary/outlet_injector/atmos/nitrogen_input
* '''Vent pump''': /obj/machinery/atmospherics/components/unary/vent_pump/siphon/atmos/nitrogen_output
* '''Gas sensor''': /obj/machinery/air_sensor/atmos/nitrogen_tank
* '''Turf''': /turf/open/floor/engine/n2

These objects have all the neccessary vars preset and start switched on - you'll only have to edit the dir if neccessary.

Additionally, you'll want this type of gas mixer for the airmix tank (N2 + O2):

* '''Air mixer''': /obj/machinery/atmospherics/components/trinary/mixer/airmix

== Power ==

=== APC ===
Each new room needs at least one, this will provide all the power for the room (magically). Each piece of machinery inside the APC's area will draw power from either the lighting, equipment or environmental channel.

Any room that is very equipment heavy (for example cargo bay) may need a beefed up APC (apc/highcap) to prevent early blackouts. These start with higher capacity power cells.

=== Wiring ===
Make sure the wires lead from the main power grid, and to the APC(s) of your area. If any equipment in your new area requires a wire under it, line it up, connected to the main power grid, and under the machinery.

Wires are also helpful when making electrical grilles (just dot wire under a grille), make sure the wires touch the main power grid (or they won't shock people).

== Equipment ==

=== Lights ===
Lights take up a lot of power, don't use too many! Make sure to put in just enough so the room is fully lit, but not so many that the equipment will go out in ten minutes of the round starting.

=== Light switch ===
For mood lighting, or to show the room is currently not in use by the primary occupant. These disable the lighting equipment (and power drain associated) in the area, but not desk lamps. Place these on walls, usually by a door.

=== Request Console ===
If a certain room has no need for materials, or produces no materials, do not give it a Request Console. If it does (for either case or both) make sure it has at least one, that is in a place where some one will see it.

=== Intercoms ===
At least every room should have one of these. They should be set to 145.9, and be speaker ON Microphone OFF. This is so radio signals can reach people even without head sets on. Larger room will require more than one at a time.

=== Security Cameras ===
Most areas should have these, enough to see the general area from a Human point of view, but, not bunched together for the AI's sake. Larger rooms may require more than one.

== Room Structure ==

=== Access ===
''' Refer to ..\code\__DEFINES\access.dm for door access values.'''

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'''.

[[File:DoorAccessImage1.png|thumb|left|300px]] This image shows a door on the Arrivals shuttle - since it's a public door, the access is set to "0", as everyone should be able to open it. If we look at the Brig front door, we would set the access to 63, because that's the value for Security front doors - accessible by Security positions, but no one else.

Multiple accesses to doors are handled by adding a semicolon (with no spaces) between access values (eg. "28;31" is for Kitchen and Cargo access). This might seem worthless, but it's useful for small maps, where jobs might need to share access due to cramped spaces.

There's an important difference between the two that you need to pay attention to - req_access_txt requires '''ALL LISTED ACCESSES''' to open the door, while req_one_access_txt lets anyone with '''ONE OF THE LISTED ACCESSES''' open the door. For example - say you want your Brig to be openable by the Detective and Security Officers, we would put "63;4" in '''req_one_access_txt''', because we want the Detective '''AND''' Security to have access. If we used req_access_txt, you would need '''BOTH''' accesses to open the door, meaning neither the Detective or Security could open it.

You can view all of the access values in the code/game/jobs/access.dm file. (Most should be self explanatory or have a label, but if you really aren't sure, you can take a look at Boxstation's map file and check the value on the door you're looking for).

=== Airless Floors ===

Ideal for rooms or chambers that mix gas, and for tiles exposed to space. Not ideal for areas that humans will cross in frequency.

Use these on external tiles (to prevent lag when the game starts) and chambers that will require gas mixing (toxins mix chamber/ furnace). Double check these to make sure you don't suffocate mobs in the new rooms.

=== Fire Alarms and Fire Doors ===
Make sure to put these INSIDE of the boundary of the area, so there is a lock down. Any spot that gets hot as a normal function should not have a fire Alarm right next to the heat source (toxin mix chamber). Make sure there is a fully sealed area (with the exception of maintenance doors for people to escape fires) that can't be open by normal civilians.

=== Weak Points ===
Judge how high security the room will be, if it is high security, reinforced walls and electrified grill windows may be in order. Areas that do not need a lot of security can use basic walls, and windows to your liking (though normal glass windows break very very easy). Each room should have one place that's weaker than the rest (like a back door, side entrance, or a window), just because the main entrance might be out of commission (and realistically, for traitors to break into).

=== Item and Machinery Distribution ===
Be smart about what will go in an area, keep a fine balance between the size of the room and amount of equipment. Large rooms may require multiple APCs to prevent power outages early in game. Second, make sure to place equipment that make sense for the area (security computer in a security area/ Medical vendor in a medical area).

=== Indestructible Turfs ===
Before you finalize a map, check for any indestructible turfs. These turfs ignore things like external damage and are typically meant for things like special ruins/rooms where you want to avoid people trying to circumvent a path. Due to these characteristics, they have no real place on regular station maps and would probably lead to confusion for players more than anything.

== Balance ==

=== Item contents ===
The harder the room is to enter, the more goodies or sensitive equipment there is inside. Make sure to keep this in mind (and don't make an empty room that's covered in blast doors, electrified grills, reinforced walls, and captain level doors).

=== Room security ===
A room is only as secure as its necessity. Public rooms should not have many security functions (other than a fire alarm), but private work space must be more secure (based on job). The bartenders do not need reinforced walls around their storage, but engineers do.

The highest security rooms should utilize the highest security measures. The lowest security rooms should utilize the cheapest security measures.

== Step_x, step_y and the broken movement syndrome ==

So you compiled the map and suddenly whenever you move you no longer get the animation of moving but just 'appear' on the next tile?

So a while back step_x and step_y were introduced to allow pixel based movement. SS13 does not utilize this. Step_x and step_y are variables that each atom has. The way they work is that as soon as you set any object on the map to use one of these variables, the game interprets that you overrode all default movement code and wrote your own - but you didn't (The code that makes the animation from tile to tile).

To fix this problem you need to close dream maker (save the project first, obviously). Open your map (.dmm) file in a text editor, such as notepad or notepad++. Search (ctrl+f) through the file for step_x and step_y and remove any reference to it. Once no more step_x or step_y -es are found in the file, save it and open it in dream maker once again. Compile the code and movement should work fine once more. Go to [[Community|the development IRC]] if you need more help.

==Shuttles==
Basically there's 3 types of shuttle dock stationary, transit and mobile
*stationary == places where the shuttle can dock
*transit == shuttle as it moves
*mobile == the place with the actual shuttle
so you'd have a transit dock in the transit area and 2 stationary docks, one in centcomm and the other one in the station and 1 mobile dock, in centcomm for most shuttles (apart from mining)

The shuttle docks are grouped by id eg id = "cargo_away" id = "cargo_transit"

You need to add the dock types to the map and edit the bounding boxes via varediting the dock, you need to varedit height, width, dheight and dwidth at minimum. These are offset by the dir so do keep that in mind, eg if dir == 2 then width goes from EAST to WEST, if dir == 4 then width goes from NORTH to SOUTH and dwidth/dheight are offsets from the lower-left corner of the plane switched to the dock's dir

You should also ensure the directions face the shuttle or face away from the thing the shuttle docks with.

If a shuttle's mobile docking port direction is different then the stationary docking port's direction, the shuttle and all items on it will be rotated accordingly. (Try it, it works properly for just about everything)

'''Warning the bounding box for the mobile dock must fit inside of the stationary dock (after any rotation)''' Or the shuttle will refuse to move.

If the shuttle's mobile docking port is in an area that is a subtype of /area/shuttle, Only turfs in the bounding box in that same area are moved. Otherwise it moves all turfs in the bounding box. This can be used for odd shaped shuttles. (the area will be transfer over as well)

Also note that the emergency shuttle and cargo shuttle need special subtypes of the dock type eg so /obj/docking_port/mobile/emergency

The other variables of note is traveldir, which defines if the shuttle rotates on transit, it's an angle in degrees (just imagine the shuttle is inside a circle . For example, if you want the shuttle going right to left set it to 270 degrees.

===Dwidth and Dheight in more depth===
dwidth/dheight is the offset of the docking_port obj from the (0,0) bounding box corner. In dir == 1 (north) 0,0 is the bottom left corner? This changes for each direction, For example when dir is 2 it's the upper right corner. so dwidth and dheight identify where the bounding box starts relative to the docking port obj whereaswidth and height determine the actual width and height of the bounding box

'''Note: We count step 0 as a tile, so a height and width of 9 is actually 10 tiles (tile 0 to tile 9)'''

Here is an example for the north facing shuttle dock direction - you can rotate this image to determine where the offset is for each other cardinal direction
[[File:ShuttleBox.png]]

==Other files==
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.

==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

== 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.

== На будущее ==
Other related guides: [[Understanding SS13 code]], [[SS13 for experienced programmers]], [[Guide to door access]] and [[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.

{{Contribution guides}}

Картографические истины

2022-03-10T17:48:55Z

TrashDoxx: Начальная стадия работы.

{{wip
|assign = TrashDoxx}}
== Руководство для страждующих мапперов ==
'''Адресовано как тем, кто имеет хоть какое-то представление о том, как пользоваться редактором, так и для тех, кто не имеет его вовсе.'''

Я понятия не имею, насколько опытен тот, кто это читает, поэтому начну с самых азов. Во-первых, вам нужно получить копию всех файлов для редактирования. Для этого перейдите в требуемый репозиторий (например, [https://www.github.com/ss220-space/tgstation сюда]) и нажмите зелёную кнопку '''Code''', затем, в выпадающем меню выберите '''Download ZIP'''. Если вы пока не имеете представления о том, что делаете - этого будет достаточно для ознакомления. Но конечно, если вы уже умеете обращаться с версиями проектов на '''GitHub''', вы можете использовать привычные для себя инструменты. Когда вы получите архив - распакуйте его куда вам угодно.

Итак, теперь у вас есть папка с последней версией кода и резервная копия в архиве, к которой можно вернуться, если вы всё сломаете. В основной папке вы увидите файл в формате - '''.dme''', который содержит в себе ссылки на всё, что должно быть в игре после компиляции. Фактически, это такая среда с необходимыми ресурсами. Вам необходимо открыть этот файл. Для этого вы можете использовать встроенный инструментарий BYOND'а или внешние редакторы, о которых я упомяну позднее. На данный момент вам достаточно дважды кликнуть по нему. Когда вы откроете программу, вы увидите две вкладки слева: '''File''' и '''Object'''. Во вкладке '''File''' откройте директорию с картами, а затем откройте файл в формате - '''.dmm'''. Именно в этом формате записываются игровые карты. В результате вы получите что-то похожее на это:

[Тут могла быть ваша реклама, но она появится чуть позднее].

Switch from the '''files''' tab to the '''objects''' tab, and you'll see '''area''', '''mob''', '''objects''', and '''turf'''. These are the four primary 'layers' that you can see in the editor. You can toggle their visibility and interactivity on and off using the '''layers '''dropdown. I'd advise copying this map, and renaming it to, say, teststation.dmm. Perhaps delete most or all of the default station, and build on the now-empty z-level, wherever you like. To build stuff, use the object tree on the left of the UI to select things, then click to place them. A simple click lets you place one item per tile from each category, while Ctrl-click '''stacks''' it on '''top''' of all previous ones and Shift-click deletes the '''topmost''' item. You can have multiple maps open at once - I usually have the default /tg/station map and mine open, and can then shamelessly copy-paste things far more easily. Also, finding stuff in the object tree can be tedious as hell - right click something you see and you can see its path in the tree - obj/structure/closet/etc. This will help you find things. From this point on, really, you can begin mapping proper.

You can select areas to copy/paste/delete, or enter add or fill mode when placing objects. Basically just click around all the menus and you'll work out how they work, more or less. '''Options>Zoom''' allows you to zoom out to 50% to see more stuff. Use layers to select which of area, objects and turf you want to edit. If you actually want to be able to see anything, I'd deselect area, and tick 'only show selectable layers'.

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. Once you've made your room you'll want to put lights in.

{|
|[[File:Mystery pipe.png|left|frame|There is one uninvited guest here!]]
|'''Important:''' While building your station you might find yourself in need of an object with a specific alignment (windows, pipes, cables etc) that does not appear in your menu. This is because BYOND does not simulate instances of an object other than its base state unless they are present on the map. You can generate them by right clicking an object and selecting "generate instance from state/direction". This function has an '''unwanted feature''' in which a generated object sometimes has a tag added automatically. These tags can cause error with certain features of the game during a round, and need to be removed. To check for it, right click an item on the map or in the menu, select "edit" and scroll to the "tag" line, which should be empty save for two doublequotes (""). If it's not (which is easy to tell since the tag is massive and bold, impossible to miss even scrolling at lightspeed), change it. Well maintained maps don't usually contain these, so you should be safe to copy-paste to your heart's content. As a tip, remember that all non-standard objects have their own entry in the menu, and having a tag is not standard at all for most object!
|}
{|
|[[File:Editinstance.png|left|200px]]
| So now we get to the basics of making a functioning room. First of all, you'll need to re-enable the area layer. Pick some area from the object tree, and cover your room in it. You can rename this area if you want, we'll do that later. Make sure the area isn't used anywhere else on the map. Each area should have one APC or Area Power Controller in it. Copy one in from the default map or spawn one yourself, then rename its "name" variable through "edit" to something appropriate. If you copied your APC from another map, chances are that cell type and dir are both in bold. Cell type defines how much power the APC can hold, and for your first map you'll want to set this nice and high as you don't have any sort of generator yet - 10,000 ought to do. Dir defines the direction the APC is in with regards to the cell it occupies. Basically, 1 means it is above the cell you place it in, 2 is below, 4 is to the right and 8 to the left.

Note that with APCs, '''dir ''' is the only variable controlling their position. Other objects have their positions defined by '''pixel_x '''and '''pixel_y''' - this changes where APCs appear in the editor, but once ingame they snap to whatever the '''dir''' variable says. Other things, like signs on walls, will only take notice of the pixel variables and not necessarily dir. In a normal power system, you'd connect the APC up to all the others and the station's generator via SMES cells, but we'll do that later. For now you have a basic room that is powered and starts with enough air to breathe happily. You can put an air canister in if you think you'll consume all the oxygen, or somesuch.
|[[File:Directions.png|right|200px]]
|}

'''Important Note:''' There are '''nudge_x '''and '''nudge_y''' variables in the editor, as well as various z-axis variables. Don't ever change these, they're not used in SS13 and break things.

To be able to actually spawn into a room, you'll want to place spawners. You'll see these as the big red X symbols on the default map, for each role. There are also blue Xs for xeno spawn locations and the spawns for all latecomers on the arrival shuttle. Stick in a spawn_late somewhere in your room for now.

To actually play your map and be able to screw around in it as an admin, you'll have to compile it. First, make sure the file tree (on the left like the object tree, click the file tab) is open, and go to maps. Make sure the only one ticked is your own. Then click Build>Compile from the top, and wait for it to finish. This will give you a something like "tgstation.dmb" in the folder containing bot, code, config, maps, etc. Whilst here, quickly go into config, and open 'admins.txt'. Replace everything in there with:

"<yourbyondname> = Game Master", filling in your BYOND name.

This will make you an admin, which is very helpful for tinkering ingame. Now to actually boot up a server so you can run your map! Find 'Dream Daemon' (has a big green icon) in your BYOND folder, and click the 'File' dropdown at the bottom. Select your "tgstation.dmb". Select a port if you want, put security on safe, and visibility to invisible, for now. Click start to start the server, which will take a little while. You can then connect to it through BYOND by putting in either your external IP, shown in Dream Daemon, if that port is correctly forwarded. Otherwise use your internal IP, 192.168.x.x, where x is whatever. If you don't know this, ask and I can help. Once in, go to the admin tab and click 'start game'. By joining after the start, you'll spawn at the late spawn you made, and, being an admin, will be able to make stuff, delete stuff, and other handy admin things (like causing massive explosions).

From there on, you can make whatever you like, really. Copying the default map and working out how everything works isn't too hard and is fairly rewarding. You could just tweak the default one for a bit if you like. The first thing I made was a small shuttle - you can see this at the bottom. Just tweak it and add stuff and you'll work out how almost everything works fairly easily. For explanations of wiring, piping, and atmos, ask away on here. I'll add an atmos guide later on, as well as a power generation and wiring guide. If you're a good engineer in-game, it'll help a lot as a mapper.

If you've managed to get all the way to the end of this before I've added more, fine effort on your part. Have fun screwing around with stuff, and feel free to ask anything you like. I'll add more stuff here soon.

== Pre-commit checks ==

*Are floors with or without air, as they should be? (regular or airless)
*Does the area have an APC?
*Does the area have an Air Alarm?
*Does the area have a Request Console?
*Does the area have lights?
*Does the area have a light switch?
*Does the area have enough intercoms?
*Does the area have enough security cameras? (Use the verbs under Mapping for help)
*Is the area connected to the scrubbers air loop?
*Is the area connected to the vent air loop? (vent pumps)
*Is everything wired properly?
*Does the area have a fire alarm and firedoors?
*Do all pod doors work properly?
*Are accesses set properly on doors, pod buttons, etc.
*Are all items placed properly? (not below vents, scrubbers, tables)
*Does the disposal system work properly from all the disposal units in this room and all the units, the pipes of which pass through this room?
*Check for any misplaced or stacked piece of pipe (air and disposal)
*Check for any misplaced or stacked piece of wire
*Identify how hard it is to break into the area and where the weak points are, and balance the area accordingly (eg. the Vault should be made of reinforced structures and electrified windows, the Kitchen should not)
*Check if the area has too much empty space. If so, make it smaller and replace the rest with maintenance tunnels
*Are there any [[guide_to_mapping#Room Structure|indestructible turfs]] where they shouldn't be?

== General Station-wide Mapping Guidelines ==

=== In general ===
* Don't run pipes/cables/disposals through walls if you can avoid it. Otherwise it's a pain to repair or sabotage them, especially under r-walls.
* Try to connect departments to maintenance through a back or side door. This lets players escape and allows antags to break in. Metastation is a good example for this.

=== Atmospherics ===
* Each area should have EXACTLY one air alarm (Exceptions are only possible if a room has scrubbers or vent pumps on different frequencies).
* Each ROOM (Walled off space) should have at least one vent pump and scrubber, which is properly connected to its respective loop. Keep in mind that scrubbers don't detect gases/pressure; only air alarms do.
* The air supply loop's pipes should be colored blue.
* The scrubbers loop's pipes should be colored red.
* Some areas require special air alarm subtypes: /engine for the SME and /server for tcomms or the RnD server room.

=== 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.

== Atmospherics ==

=== Pipes and manifolds ===

Atmospherics releases it's cocktail of gases into the air supply loop (blue pipes). The station is also equipped with a scrubber loop, which filters unwanted gases and sends them back to atmospherics via the scrubber loop (red pipes).

If you're expanding the air supply loop (blue pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/supply/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/supply/visible and ../hidden.

If you are expanding the scrubber loop (red pipes) use the objects in /obj/machinery/atmospherics/pipe/simple/scrubbers/visible or ../hidden depending on if you want it to show above floors or below them. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/scrubbers/visible and ../hidden.

If you are however building a pipe network which has nothing to do with the air supply or scrubbers loop, you should use the objects in /obj/machinery/atmospherics/pipe/simple/general/visible or ../hidden. For manifolds use the objects in /obj/machinery/atmospherics/pipe/manifold/general/visible and ../hidden.

To add new colors of pipes, you will need add a new subtypes in the appropriate .dm files located in tgstation\code\modules\atmospherics\machinery\pipes

Please refrain from var-editing pipes, as it typically introduces graphical glitches and other issues.

=== Air Alarm ===

Every single area (with scrubbers and/or vent pumps) should have exactly one air alarm. More than one should be placed if vent pumps or scrubbers use different radio frequencies than the default one (1439).

=== Scrubbers (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one scrubber.

The path for scrubbers that start on is '''/obj/machinery/atmospherics/components/unary/vent_scrubber/on'''

And make sure the '''id_tag''' is the default one (null)

Also ensure the scrubber is connected to the scrubber loop!!

=== Vent Pumps (Station air supply) ===

Every room (ie. walled off space) except for maintenance hallways should have at least one vent pump.

The path for vents that start on is '''/obj/machinery/atmospherics/components/unary/vent_pump/on'''

Please make sure the '''id_tag''' is the default one (null)

Also ensure the vent pump is connected to the air supply loop!!

=== Gas tanks and filters ===

Each station should have a full set of these - or at the bare minimum, one for N2, one for O2 and a third tank to filter dangerous gases into.

[[File:Atmos mapping.jpg|right|frame|Left to right: N2, O2, Airmix. The canisters inside are just for decoration.]]

Each gas tank needs:
* '''Outside''': A tank computer and a gas filter to pick what gases will be filtered into it.
* '''Inside''': A gas injector (input), a vent pump (output), a gas sensor and a specific turf.

The tank computer controls the input/output and receives data from the gas sensor.

The specific turf creates the gases that will be inside each tank - the gas canister is just for decoration.

Let's take a look at the MetaStation N2 tank:

* '''Tank computer''': /obj/machinery/computer/atmos_control/tank/nitrogen_tank
* '''N2 filter''': /obj/machinery/atmospherics/components/trinary/filter/atmos/n2
* '''Gas injector''': /obj/machinery/atmospherics/components/unary/outlet_injector/atmos/nitrogen_input
* '''Vent pump''': /obj/machinery/atmospherics/components/unary/vent_pump/siphon/atmos/nitrogen_output
* '''Gas sensor''': /obj/machinery/air_sensor/atmos/nitrogen_tank
* '''Turf''': /turf/open/floor/engine/n2

These objects have all the neccessary vars preset and start switched on - you'll only have to edit the dir if neccessary.

Additionally, you'll want this type of gas mixer for the airmix tank (N2 + O2):

* '''Air mixer''': /obj/machinery/atmospherics/components/trinary/mixer/airmix

== Power ==

=== APC ===
Each new room needs at least one, this will provide all the power for the room (magically). Each piece of machinery inside the APC's area will draw power from either the lighting, equipment or environmental channel.

Any room that is very equipment heavy (for example cargo bay) may need a beefed up APC (apc/highcap) to prevent early blackouts. These start with higher capacity power cells.

=== Wiring ===
Make sure the wires lead from the main power grid, and to the APC(s) of your area. If any equipment in your new area requires a wire under it, line it up, connected to the main power grid, and under the machinery.

Wires are also helpful when making electrical grilles (just dot wire under a grille), make sure the wires touch the main power grid (or they won't shock people).

== Equipment ==

=== Lights ===
Lights take up a lot of power, don't use too many! Make sure to put in just enough so the room is fully lit, but not so many that the equipment will go out in ten minutes of the round starting.

=== Light switch ===
For mood lighting, or to show the room is currently not in use by the primary occupant. These disable the lighting equipment (and power drain associated) in the area, but not desk lamps. Place these on walls, usually by a door.

=== Request Console ===
If a certain room has no need for materials, or produces no materials, do not give it a Request Console. If it does (for either case or both) make sure it has at least one, that is in a place where some one will see it.

=== Intercoms ===
At least every room should have one of these. They should be set to 145.9, and be speaker ON Microphone OFF. This is so radio signals can reach people even without head sets on. Larger room will require more than one at a time.

=== Security Cameras ===
Most areas should have these, enough to see the general area from a Human point of view, but, not bunched together for the AI's sake. Larger rooms may require more than one.

== Room Structure ==

=== Access ===
''' Refer to ..\code\__DEFINES\access.dm for door access values.'''

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'''.

[[File:DoorAccessImage1.png|thumb|left|300px]] This image shows a door on the Arrivals shuttle - since it's a public door, the access is set to "0", as everyone should be able to open it. If we look at the Brig front door, we would set the access to 63, because that's the value for Security front doors - accessible by Security positions, but no one else.

Multiple accesses to doors are handled by adding a semicolon (with no spaces) between access values (eg. "28;31" is for Kitchen and Cargo access). This might seem worthless, but it's useful for small maps, where jobs might need to share access due to cramped spaces.

There's an important difference between the two that you need to pay attention to - req_access_txt requires '''ALL LISTED ACCESSES''' to open the door, while req_one_access_txt lets anyone with '''ONE OF THE LISTED ACCESSES''' open the door. For example - say you want your Brig to be openable by the Detective and Security Officers, we would put "63;4" in '''req_one_access_txt''', because we want the Detective '''AND''' Security to have access. If we used req_access_txt, you would need '''BOTH''' accesses to open the door, meaning neither the Detective or Security could open it.

You can view all of the access values in the code/game/jobs/access.dm file. (Most should be self explanatory or have a label, but if you really aren't sure, you can take a look at Boxstation's map file and check the value on the door you're looking for).

=== Airless Floors ===

Ideal for rooms or chambers that mix gas, and for tiles exposed to space. Not ideal for areas that humans will cross in frequency.

Use these on external tiles (to prevent lag when the game starts) and chambers that will require gas mixing (toxins mix chamber/ furnace). Double check these to make sure you don't suffocate mobs in the new rooms.

=== Fire Alarms and Fire Doors ===
Make sure to put these INSIDE of the boundary of the area, so there is a lock down. Any spot that gets hot as a normal function should not have a fire Alarm right next to the heat source (toxin mix chamber). Make sure there is a fully sealed area (with the exception of maintenance doors for people to escape fires) that can't be open by normal civilians.

=== Weak Points ===
Judge how high security the room will be, if it is high security, reinforced walls and electrified grill windows may be in order. Areas that do not need a lot of security can use basic walls, and windows to your liking (though normal glass windows break very very easy). Each room should have one place that's weaker than the rest (like a back door, side entrance, or a window), just because the main entrance might be out of commission (and realistically, for traitors to break into).

=== Item and Machinery Distribution ===
Be smart about what will go in an area, keep a fine balance between the size of the room and amount of equipment. Large rooms may require multiple APCs to prevent power outages early in game. Second, make sure to place equipment that make sense for the area (security computer in a security area/ Medical vendor in a medical area).

=== Indestructible Turfs ===
Before you finalize a map, check for any indestructible turfs. These turfs ignore things like external damage and are typically meant for things like special ruins/rooms where you want to avoid people trying to circumvent a path. Due to these characteristics, they have no real place on regular station maps and would probably lead to confusion for players more than anything.

== Balance ==

=== Item contents ===
The harder the room is to enter, the more goodies or sensitive equipment there is inside. Make sure to keep this in mind (and don't make an empty room that's covered in blast doors, electrified grills, reinforced walls, and captain level doors).

=== Room security ===
A room is only as secure as its necessity. Public rooms should not have many security functions (other than a fire alarm), but private work space must be more secure (based on job). The bartenders do not need reinforced walls around their storage, but engineers do.

The highest security rooms should utilize the highest security measures. The lowest security rooms should utilize the cheapest security measures.

== Step_x, step_y and the broken movement syndrome ==

So you compiled the map and suddenly whenever you move you no longer get the animation of moving but just 'appear' on the next tile?

So a while back step_x and step_y were introduced to allow pixel based movement. SS13 does not utilize this. Step_x and step_y are variables that each atom has. The way they work is that as soon as you set any object on the map to use one of these variables, the game interprets that you overrode all default movement code and wrote your own - but you didn't (The code that makes the animation from tile to tile).

To fix this problem you need to close dream maker (save the project first, obviously). Open your map (.dmm) file in a text editor, such as notepad or notepad++. Search (ctrl+f) through the file for step_x and step_y and remove any reference to it. Once no more step_x or step_y -es are found in the file, save it and open it in dream maker once again. Compile the code and movement should work fine once more. Go to [[Community|the development IRC]] if you need more help.

==Shuttles==
Basically there's 3 types of shuttle dock stationary, transit and mobile
*stationary == places where the shuttle can dock
*transit == shuttle as it moves
*mobile == the place with the actual shuttle
so you'd have a transit dock in the transit area and 2 stationary docks, one in centcomm and the other one in the station and 1 mobile dock, in centcomm for most shuttles (apart from mining)

The shuttle docks are grouped by id eg id = "cargo_away" id = "cargo_transit"

You need to add the dock types to the map and edit the bounding boxes via varediting the dock, you need to varedit height, width, dheight and dwidth at minimum. These are offset by the dir so do keep that in mind, eg if dir == 2 then width goes from EAST to WEST, if dir == 4 then width goes from NORTH to SOUTH and dwidth/dheight are offsets from the lower-left corner of the plane switched to the dock's dir

You should also ensure the directions face the shuttle or face away from the thing the shuttle docks with.

If a shuttle's mobile docking port direction is different then the stationary docking port's direction, the shuttle and all items on it will be rotated accordingly. (Try it, it works properly for just about everything)

'''Warning the bounding box for the mobile dock must fit inside of the stationary dock (after any rotation)''' Or the shuttle will refuse to move.

If the shuttle's mobile docking port is in an area that is a subtype of /area/shuttle, Only turfs in the bounding box in that same area are moved. Otherwise it moves all turfs in the bounding box. This can be used for odd shaped shuttles. (the area will be transfer over as well)

Also note that the emergency shuttle and cargo shuttle need special subtypes of the dock type eg so /obj/docking_port/mobile/emergency

The other variables of note is traveldir, which defines if the shuttle rotates on transit, it's an angle in degrees (just imagine the shuttle is inside a circle . For example, if you want the shuttle going right to left set it to 270 degrees.

===Dwidth and Dheight in more depth===
dwidth/dheight is the offset of the docking_port obj from the (0,0) bounding box corner. In dir == 1 (north) 0,0 is the bottom left corner? This changes for each direction, For example when dir is 2 it's the upper right corner. so dwidth and dheight identify where the bounding box starts relative to the docking port obj whereaswidth and height determine the actual width and height of the bounding box

'''Note: We count step 0 as a tile, so a height and width of 9 is actually 10 tiles (tile 0 to tile 9)'''

Here is an example for the north facing shuttle dock direction - you can rotate this image to determine where the offset is for each other cardinal direction
[[File:ShuttleBox.png]]

==Other files==
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.

==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

== 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.

== На будущее ==
Other related guides: [[Understanding SS13 code]], [[SS13 for experienced programmers]], [[Guide to door access]] and [[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.

{{Contribution guides}}

Участник:TrashDoxx

2022-03-10T17:21:47Z

TrashDoxx: Дружелюбное приветствие это всегда хорошо.

Привет, меня зовут Войцех! А тебя?