Network Admin: Difference between revisions
m (Signal techs are available to play) |
No edit summary |
||
| (17 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{JobPageHeader | {{JobPageHeader | ||
|headerbgcolor = | |headerbgcolor = #ba9b67 | ||
|headerfontcolor = | |headerfontcolor = white | ||
|stafftype = ENGINEERING | |stafftype = ENGINEERING | ||
|imagebgcolor = # | |imagebgcolor = #d2be9c | ||
|img_generic = Generic_signal.png | |img_generic = Generic_signal.png | ||
|img = SignalTech.png | |img = SignalTech.png | ||
|jobtitle = | |jobtitle = Network Admin | ||
|access = [[Telecoms]], Telecoms Admin | |titles= AI Tech Support, SysOp | ||
|access = [[Telecoms]], Telecoms Admin, R&D Console | |||
|additional = [[Engineering]], Power Equipment, [[Tech Storage]], [[Construction Area|Construction]] | |additional = [[Engineering]], Power Equipment, [[Tech Storage]], [[Construction Area|Construction]] | ||
|difficulty = Easy | |difficulty = Easy | ||
|superior = [[Chief Engineer]] | |superior = [[Chief Engineer]] | ||
|duties = Ensure telecommunications never goes down, write a helpful tcomms script, have the AI turn it off when it crashes and stops working, get lynched by the CE when a processor overloads and you don't know how to fix it. | |duties = Ensure telecommunications never goes down, write a helpful tcomms script, have the AI turn it off when it crashes and stops working, get lynched by the CE when a processor overloads and you don't know how to fix it. | ||
|guides = [[NTSL]], [https://forums.yogstation.net/index.php?threads/garys-guide-to-ntscript.14759/], [https://forums.yogstation.net/index.php?threads/guide-to-signal-tech-aka-how-to-be-elite-hackerman.14367/] | |guides = [[NTSL]], [[Guide to Telecommunications]], [[NTSL_Scripts| Premade Scripts]] [https://forums.yogstation.net/index.php?threads/garys-guide-to-ntscript.14759/], [https://forums.yogstation.net/index.php?threads/guide-to-signal-tech-aka-how-to-be-elite-hackerman.14367/] | ||
|quote = | |quote = PDA me for custom job titles. No I will not turn off my auto translate script. | ||
}} | |age=22}} | ||
Your job tends to be simple, make communication over the radio more efficient and make sure the machines don't go down. That and you can shut Poly up without ever having to touch him. | |||
Your job tends to be simple, make communication over the radio more efficient and make sure the machines don't go down. That and you can shut | |||
'''Bare minimum requirements:''' Make sure a rogue [[AI]] doesn't upload harmful scripts. | |||
==Telecomms== | ==Telecomms== | ||
Keeping the machines up is the most important part of your job, so if it all breaks in [[Traitor|some]] [[Blood_Cult|freak]] [[Nuclear_Operative|accident]] it is your job to repair it. | |||
== Scripting and stuff == | |||
You can find most of what you need to learn through the guide [[NT_Script]]. The language can be hard and it's recommended for you to read the guide before your first round as a signal technician. | |||
==What you Can do to Pass the Time== | ==What you Can do to Pass the Time== | ||
Most of the actually important work for a | Most of the actually important work for a telecom's admin can be done within the first minute of a round, and apart from the simple quality of life things there can be a lot for a telecom's admin to do that would actually help the station. While you can't hear what's going through most of the channels you can check the logs and make sure everything is fine. If you notice anything odd, feel free to turn on your security transceiver and tell [[Security]] about it, though they might get annoyed if you mention every little thing to them. | ||
If the station is in dire enough | If the station is in dire enough straits, you can ask the [[Chief Engineer]] for the decryption key from his desk. This will allow you to access messaging logs. You can use these to pick out anyone messaging anything privately who might want to harm another. | ||
Feel free to make | Feel free to make announcements if you deem them important enough for the crew to know. This generally includes letting everyone know that you know the t-comms shutdown, and you are working on it. Please leave it for emergency only though. | ||
==War Ops== | |||
When the nukies declare war, IMMEDIATELY get to work on building a backup telecoms' system. Nine times out of ten, the telecoms satellite will be the first target of them, so building a backup network is extremely important. | |||
==In Space, No-One Can Hear You Scream== | |||
As a [[Traitor]], the biggest asset you have is your scripting. Do some crazy shit like changing all comms messages to redirect [[Security]] towards a nonexistent threat for a while. Or, you can just mute your target, but that's boring. You also have an intercom in your control room that lets you tune into and listen to any channel including Command or Security. | |||
== Tips == | |||
* Upload a script that states people's jobs after their names, so that way, security knows who's making claims. | |||
* Upload a script that makes Poly silent. The engineers might not notice, but if they do, they will thank you. Ask first, though, since some engineers like Poly. | |||
* Fun scripts tend to let the rest of the station know you aren't purposefully ruining telecoms. | |||
* The random event Processor Overload will blow telecommunication processors, so be ready for that. | |||
{{Jobs}} | {{Jobs}} | ||
[[Category:Jobs]] | [[Category:Jobs]] | ||
Latest revision as of 13:28, 9 December 2023
| ENGINEERING STAFF | |
  Network Admin |
Alternative Titles: AI Tech Support, SysOp Access: Telecoms, Telecoms Admin, R&D Console Additional Access: Engineering, Power Equipment, Tech Storage, Construction Difficulty: Easy Supervisors: Chief Engineer Duties: Ensure telecommunications never goes down, write a helpful tcomms script, have the AI turn it off when it crashes and stops working, get lynched by the CE when a processor overloads and you don't know how to fix it. Guides: NTSL, Guide to Telecommunications, Premade Scripts [1], [2] Minimum Age: 22 Quote: PDA me for custom job titles. No I will not turn off my auto translate script. |
Your job tends to be simple, make communication over the radio more efficient and make sure the machines don't go down. That and you can shut Poly up without ever having to touch him.
Bare minimum requirements: Make sure a rogue AI doesn't upload harmful scripts.
Telecomms
Keeping the machines up is the most important part of your job, so if it all breaks in some freak accident it is your job to repair it.
Scripting and stuff
You can find most of what you need to learn through the guide NT_Script. The language can be hard and it's recommended for you to read the guide before your first round as a signal technician.
What you Can do to Pass the Time
Most of the actually important work for a telecom's admin can be done within the first minute of a round, and apart from the simple quality of life things there can be a lot for a telecom's admin to do that would actually help the station. While you can't hear what's going through most of the channels you can check the logs and make sure everything is fine. If you notice anything odd, feel free to turn on your security transceiver and tell Security about it, though they might get annoyed if you mention every little thing to them.
If the station is in dire enough straits, you can ask the Chief Engineer for the decryption key from his desk. This will allow you to access messaging logs. You can use these to pick out anyone messaging anything privately who might want to harm another.
Feel free to make announcements if you deem them important enough for the crew to know. This generally includes letting everyone know that you know the t-comms shutdown, and you are working on it. Please leave it for emergency only though.
War Ops
When the nukies declare war, IMMEDIATELY get to work on building a backup telecoms' system. Nine times out of ten, the telecoms satellite will be the first target of them, so building a backup network is extremely important.
In Space, No-One Can Hear You Scream
As a Traitor, the biggest asset you have is your scripting. Do some crazy shit like changing all comms messages to redirect Security towards a nonexistent threat for a while. Or, you can just mute your target, but that's boring. You also have an intercom in your control room that lets you tune into and listen to any channel including Command or Security.
Tips
- Upload a script that states people's jobs after their names, so that way, security knows who's making claims.
- Upload a script that makes Poly silent. The engineers might not notice, but if they do, they will thank you. Ask first, though, since some engineers like Poly.
- Fun scripts tend to let the rest of the station know you aren't purposefully ruining telecoms.
- The random event Processor Overload will blow telecommunication processors, so be ready for that.
