Guide to Telecommunications - Revision history

DesertSage at 06:04, 30 January 2022

2022-01-30T06:04:46Z

← Older revision		Revision as of 06:04, 30 January 2022
Line 1:		Line 1:
	{{Needs revision		{{Needs revision
	\|reason = The imagery ~~used~~ on this page is not ~~accurate~~ to ~~what exists~~ in ~~game, leading to~~ broken ~~placeholders, as well~~ as needs ~~compression for~~ a more concise ~~and accurate~~ read.		\|reason = The imagery on this page is not up-to-date, resulting in inaccurate depictions and the broken bottle being used as a placeholder in some cases. The Information also needs to be trimmed to be a more concise read.
	}}		}}

DesertSage at 05:35, 30 January 2022

2022-01-30T05:35:56Z

← Older revision		Revision as of 05:35, 30 January 2022
Line 1:		Line 1:
			{{Needs revision
			\|reason = The imagery used on this page is not accurate to what exists in game, leading to broken placeholders, as well as needs compression for a more concise and accurate read.
			}}

	The '''telecommunication''' system is a complete overhaul of the way radios work, introduced in [http://code.google.com/p/tgstation13/source/detail?r=2807 revision 2807]. It adds an entire realm of complexity to the very simple and previously straight-forward process of radio communication.		The '''telecommunication''' system is a complete overhaul of the way radios work, introduced in [http://code.google.com/p/tgstation13/source/detail?r=2807 revision 2807]. It adds an entire realm of complexity to the very simple and previously straight-forward process of radio communication.

imported>Angust: /* The Machines */ Added messaging servers. I only assume that's how they work (connect to hub).

2019-05-27T15:25:25Z

The Machines: Added messaging servers. I only assume that's how they work (connect to hub).

← Older revision		Revision as of 15:25, 27 May 2019
Line 163:		Line 163:
	=== [[File:Broad.gif]] Subspace Broadcasters ===		=== [[File:Broad.gif]] Subspace Broadcasters ===
	''Subspace Broadcasters'' are impressive pieces of hardware that are capable of opening large enough subspace windows to transfer de-compressed data bursts, in encoded radio waves, through. They are necessary for any network that is expected to output information back to receiving radio devices. They operate by directing high-powered lasers into a small subspace window and fluctuating the amplitude of radio waves through subspace, allowing the large data packets easier entering and exiting of subspace.		''Subspace Broadcasters'' are impressive pieces of hardware that are capable of opening large enough subspace windows to transfer de-compressed data bursts, in encoded radio waves, through. They are necessary for any network that is expected to output information back to receiving radio devices. They operate by directing high-powered lasers into a small subspace window and fluctuating the amplitude of radio waves through subspace, allowing the large data packets easier entering and exiting of subspace.


			=== [[File:Brokenbottle.png]] Messaging Servers ===
			''Messaging Servers'' process and route PDA and request console messages. Takes 15 minutes of calibration before it works if newly constructed. <br>Use a multitool to configure its settings and link it to the (tcommsat) network and hub. If there is no active messaging server, PDA and request console messages won't work.

	== Maintenance Guide ==		== Maintenance Guide ==

imported>Angust: /* Maintenance Guide */ minimum from "server" to "bus"

2019-03-02T09:24:32Z

Maintenance Guide: minimum from "server" to "bus"

← Older revision		Revision as of 09:24, 2 March 2019
Line 170:		Line 170:

	[[File:Multitool-tcomm.png\|thumb\|274px\|right\|The multitool-telecomm interface.]]		[[File:Multitool-tcomm.png\|thumb\|274px\|right\|The multitool-telecomm interface.]]
	If the machines have been overheated, you can fix them by simply reconstructing them. To do this, first unfasten the exterior bolts with a screwdriver. Next, dislodge the plating with a wrench. Next, remove the internal cables with some wirecutters. After that, you can use a crowbar to remove the internal components and circuit board. From there, you can either deconstruct the empty frame or simply rebuild it. If the machines have been completely destroyed, you're going to want to build more. You're going to have to bug R&D for some really high-tier circuit boards and stock parts, or salvage some parts from other toasted telecomm machines. Keep in mind, you don't have to reconstruct ALL the machines. At the very minimum you need 1 receiver, 1 processor, 1 ~~server~~, and 1 broadcaster. You might have to manually reconnect to relays if they are destroyed, this involves a long walk.		If the machines have been overheated, you can fix them by simply reconstructing them. To do this, first unfasten the exterior bolts with a screwdriver. Next, dislodge the plating with a wrench. Next, remove the internal cables with some wirecutters. After that, you can use a crowbar to remove the internal components and circuit board. From there, you can either deconstruct the empty frame or simply rebuild it. If the machines have been completely destroyed, you're going to want to build more. You're going to have to bug R&D for some really high-tier circuit boards and stock parts, or salvage some parts from other toasted telecomm machines. Keep in mind, you don't have to reconstruct ALL the machines. At the very minimum you need 1 receiver, 1 processor, 1 bus, and 1 broadcaster. You might have to manually reconnect to relays if they are destroyed, this involves a long walk.

	== Telecommunication Polymorphism ==		== Telecommunication Polymorphism ==

imported>Angust: /* Can We Fix It? */ Updated quick guide to mention tcommsat.

2018-12-31T16:09:35Z

Can We Fix It?: Updated quick guide to mention tcommsat.

← Older revision		Revision as of 16:09, 31 December 2018
Line 117:		Line 117:
	'''After building:'''		'''After building:'''
	# Clear ANY frequency filters on the machines.		# Clear ANY frequency filters on the machines.
	# ~~Grab~~ the Bus Mainframe ~~and put it on~~ your multitool buffer (down on the list, click "Multitool Buffer")		# Set network to ''tcommsat'' on every machine. This will unlink machines so do it before the next step.
			# Add the Bus Mainframe to your multitool buffer (down on the list, click "Multitool Buffer")
	# Link it to the Broadcaster, Processor, and Receiver (click "Add Machine").		# Link it to the Broadcaster, Processor, and Receiver (click "Add Machine").

imported>Denton: I've had it with this motherfucking NTSL on this motherfucking wiki

2018-11-13T20:06:16Z

I've had it with this motherfucking NTSL on this motherfucking wiki

← Older revision		Revision as of 20:06, 13 November 2018
Line 1:		Line 1:
	The '''telecommunication''' system is a complete overhaul of the way radios work, introduced in [http://code.google.com/p/tgstation13/source/detail?r=2807 revision 2807]. It adds an entire realm of complexity to the very simple and previously straight-forward process of radio communication.		The '''telecommunication''' system is a complete overhaul of the way radios work, introduced in [http://code.google.com/p/tgstation13/source/detail?r=2807 revision 2807]. It adds an entire realm of complexity to the very simple and previously straight-forward process of radio communication.

	...But, in turn, presents new strategies for antagonists ~~and offers the sandbox for some... [[NTSL_Scripts\|very interesting shenanigans]]~~.		...But, in turn, presents new strategies for antagonists.


Line 32:		Line 32:
	### Scan for servers.		### Scan for servers.
	### Click on a server.		### Click on a server.
	~~### <s>And see that Signal Execution is set to ''[NEVER]'', so that there's no malicious NTSL script blocking information</s> (NTSL-scripts were removed from /tg/-servers in 2015).~~
	### Go back to main menu and repeat steps for all servers.		### Go back to main menu and repeat steps for all servers.

Line 50:		Line 49:
	* Bus Mainframe: Regulates ;Radio signals		* Bus Mainframe: Regulates ;Radio signals
	* Processor: Decodes ;Radio signals		* Processor: Decodes ;Radio signals
	* Servers: Log ;Radio signals~~, <s>execute NTSL scripts</s>.~~		* Servers: Log ;Radio signals
	* Hub: Takes in ;Radio signals and sends them to appropriate machines.		* Hub: Takes in ;Radio signals and sends them to appropriate machines.
	* Relay: Connected to a Hub on another Z-level. Allows ;Radio signals on its Z level to be run through the telecomms infrastructure of its linked hub.		* Relay: Connected to a Hub on another Z-level. Allows ;Radio signals on its Z level to be run through the telecomms infrastructure of its linked hub.
Line 160:		Line 159:

	''Additionally'', Telecommunication Servers are capable of running user-written scripts (removed from /tg/-servers in 2015) through use of a Telecommunications Traffic Monitor. When a signal passes through a server (and the server is set to automatically execute code), the interpreter halts the signal until the code has finished executing, then releases the signal. During this time, the server's script interpreter can modify the signal's contents or flag it as a rejected signal, which will cause broadcasters to ignore it.		''Additionally'', Telecommunication Servers are capable of running user-written scripts (removed from /tg/-servers in 2015) through use of a Telecommunications Traffic Monitor. When a signal passes through a server (and the server is set to automatically execute code), the interpreter halts the signal until the code has finished executing, then releases the signal. During this time, the server's script interpreter can modify the signal's contents or flag it as a rejected signal, which will cause broadcasters to ignore it.

	~~''[[NT_Script\|Learn more about NT Scripting (NTSL)]]'' (removed from /tg/-servers in 2015).~~

	=== [[File:Broad.gif]] Subspace Broadcasters ===		=== [[File:Broad.gif]] Subspace Broadcasters ===

imported>Angust: /* The machines */ Made a note about NTSL strikethrough.

2018-10-03T12:49:34Z

The machines: Made a note about NTSL strikethrough.

← Older revision		Revision as of 12:49, 3 October 2018
Line 50:		Line 50:
	* Bus Mainframe: Regulates ;Radio signals		* Bus Mainframe: Regulates ;Radio signals
	* Processor: Decodes ;Radio signals		* Processor: Decodes ;Radio signals
	* Servers: Log ;Radio signals, execute NTSL scripts.		* Servers: Log ;Radio signals, <s>execute NTSL scripts</s>.
	* Hub: Takes in ;Radio signals and sends them to appropriate machines.		* Hub: Takes in ;Radio signals and sends them to appropriate machines.
	* Relay: Connected to a Hub on another Z-level. Allows ;Radio signals on its Z level to be run through the telecomms infrastructure of its linked hub.		* Relay: Connected to a Hub on another Z-level. Allows ;Radio signals on its Z level to be run through the telecomms infrastructure of its linked hub.

imported>Angust: /* Easy Guide to Fixing Telecomms */ Another note about NTSL scripts.

2018-10-03T12:48:51Z

Easy Guide to Fixing Telecomms: Another note about NTSL scripts.

← Older revision		Revision as of 12:48, 3 October 2018
Line 32:		Line 32:
	### Scan for servers.		### Scan for servers.
	### Click on a server.		### Click on a server.
	### And see that Signal Execution is set to ''[NEVER]'', so that there's no malicious NTSL script blocking information.		### <s>And see that Signal Execution is set to ''[NEVER]'', so that there's no malicious NTSL script blocking information</s> (NTSL-scripts were removed from /tg/-servers in 2015).
	### Go back to main menu and repeat steps for all servers.		### Go back to main menu and repeat steps for all servers.

imported>Angust: /* File:Server.gif Telecommunication Servers */ Added notes that ntsl-scripts are removed.

2018-10-03T12:47:15Z

File:Server.gif Telecommunication Servers: Added notes that ntsl-scripts are removed.

← Older revision		Revision as of 12:47, 3 October 2018
Line 159:		Line 159:


	''Additionally'', Telecommunication Servers are capable of running user-written scripts through use of a Telecommunications Traffic Monitor. When a signal passes through a server (and the server is set to automatically execute code), the interpreter halts the signal until the code has finished executing, then releases the signal. During this time, the server's script interpreter can modify the signal's contents or flag it as a rejected signal, which will cause broadcasters to ignore it.		''Additionally'', Telecommunication Servers are capable of running user-written scripts (removed from /tg/-servers in 2015) through use of a Telecommunications Traffic Monitor. When a signal passes through a server (and the server is set to automatically execute code), the interpreter halts the signal until the code has finished executing, then releases the signal. During this time, the server's script interpreter can modify the signal's contents or flag it as a rejected signal, which will cause broadcasters to ignore it.

	''[[NT_Script\|Learn more about NT Scripting (NTSL)]]''.		''[[NT_Script\|Learn more about NT Scripting (NTSL)]]'' (removed from /tg/-servers in 2015).

	=== [[File:Broad.gif]] Subspace Broadcasters ===		=== [[File:Broad.gif]] Subspace Broadcasters ===

imported>Bandit: /* Can We Fix It? */ NO MORE NTSL JESUS

2015-10-16T17:15:23Z

Can We Fix It?: NO MORE NTSL JESUS

← Older revision		Revision as of 17:15, 16 October 2015
Line 121:		Line 121:
	# Link it to the Broadcaster, Processor, and Receiver (click "Add Machine").		# Link it to the Broadcaster, Processor, and Receiver (click "Add Machine").

	That's it. You're done. It'll process all telecomms signals with no lag, no static, no loss of functionality ~~except for the inability to use telecomms scripts - though this is a great way to evade hostile scripts like a rogue AI's mute script~~.		That's it. You're done. It'll process all telecomms signals with no lag, no static, no loss of functionality.

	=A More Elaborate Guide to Telecommunications=		=A More Elaborate Guide to Telecommunications=