Disable multitool linking and update guidebook (#1284)

mirrorcult · web-flow · commit e6a64bc655c1 · 2026-02-27T02:27:42.000Z
* Disable multitool linking and update guidebook

* fixes
diff --git a/Resources/Prototypes/Entities/Objects/Tools/tools.yml b/Resources/Prototypes/Entities/Objects/Tools/tools.yml
@@ -134,7 +134,9 @@
   name: multitool
   parent: BaseItem
   id: Multitool
-  description: An advanced tool to copy, store, and send electrical pulses and signals through wires and machines.
+  # ES START
+  description: An advanced tool used to analyze power and send electrical pulses through wires.
+  # ES END
   components:
   - type: EmitSoundOnLand
     sound:
@@ -155,18 +157,19 @@
   - type: Tool
     qualities:
       - Pulsing
-  - type: NetworkConfigurator
-  - type: ActivatableUI
-    key: enum.NetworkConfiguratorUiKey.List
-    inHandsOnly: true
-  - type: UserInterface
-    interfaces:
-      enum.NetworkConfiguratorUiKey.List:
-        type: NetworkConfiguratorBoundUserInterface
-      enum.NetworkConfiguratorUiKey.Configure:
-        type: NetworkConfiguratorBoundUserInterface
-      enum.NetworkConfiguratorUiKey.Link:
-        type: NetworkConfiguratorBoundUserInterface
+  # ES START
+  #- type: NetworkConfigurator
+  #- type: ActivatableUI
+  #  key: enum.NetworkConfiguratorUiKey.List
+  #  inHandsOnly: true
+  #- type: UserInterface
+  #  interfaces:
+  #    enum.NetworkConfiguratorUiKey.List:
+  #      type: NetworkConfiguratorBoundUserInterface
+  #    enum.NetworkConfiguratorUiKey.Configure:
+  #      type: NetworkConfiguratorBoundUserInterface
+  #    enum.NetworkConfiguratorUiKey.Link:
+  #      type: NetworkConfiguratorBoundUserInterface
   - type: Tag
     tags:
       - Multitool
@@ -179,7 +182,9 @@
     price: 56
   - type: GuideHelp
     guides:
-    - Networking
+    # ES START
+    #- Networking
+    # ES END
     - WirePanels
     - Airlocks
     - InspectingPower
diff --git a/Resources/Prototypes/_ES/Guidebook/engineering.yml b/Resources/Prototypes/_ES/Guidebook/engineering.yml
@@ -134,7 +134,6 @@
   text: "/ServerInfo/_ES/Guidebook/Engineering/Valves.xml"
   children:
   - ESManualValve
-  - ESSignalValve
   - ESPneumaticValve
   - ESPassiveGate
   - ESPressureRegulator
@@ -145,12 +144,6 @@
   name: guide-entry-manualvalve
   text: "/ServerInfo/_ES/Guidebook/Engineering/ManualValve.xml"
 
-- type: guideEntry
-  id: ESSignalValve
-  hidden: false
-  name: guide-entry-signalvalve
-  text: "/ServerInfo/_ES/Guidebook/Engineering/SignalValve.xml"
-
 - type: guideEntry
   id: ESPneumaticValve
   hidden: false
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/AccessConfigurator.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/AccessConfigurator.xml
@@ -7,7 +7,7 @@
   </Box>
 
   Configurable devices can include airlocks, secure crates and lockers, as well as access restricted machines.
-  Note: Airlocks can have their accesses configured by the [color=#a4885c]Network Configurator[/color] (or multitool), for convenience.
+  Note: Airlocks can have their accesses configured by the multitool, for convenience.
 
   ## Where to find Access Configurators
   Each station is equipped with up to two access configurators. The first is in the possession of the Chief Engineer, while the second can be found with the Head of Personnel.
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/AirAlarms.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/AirAlarms.xml
@@ -10,8 +10,6 @@
 
   A room will often have an Air Alarm mounted on the wall, for quick control over multiple devices in that room.
 
-  You can see how to link devices in the [textlink="Link" link="ESNetworking"] guide.
-
   ## User Interface
   Interacting with an Air Alarm will bring up a menu with 3 sections:
   - Top: The current status of the air alarm. This includes the current pressure and temperature of the area the air alarm is monitoring.
@@ -27,8 +25,6 @@
   Air alarms will automatically drop (close) linked [textlink="firelocks" link="ESFireAndGasControl"] when the [color=Red]Danger[/color] status is reached.
   These [textlink="firelocks" link="ESFireAndGasControl"] will automatically raise (open) when the status returns to [color=green]Normal[/color].
 
-  Air alarms have [textlink="signal" link="ESNetworking"] outputs for each of the three statuses, which can be used to trigger other [textlink="signal" link="ESNetworking"] devices when the status changes.
-
   ## Sensors
   All [textlink="Air Vents" link="ESAirVent"] and [textlink="Air Scrubbers" link="ESAirScrubber"] have a built-in sensor, which reports back to the air alarm.
   These sensors can be adjusted in the [bold]Sensors[/bold] tab of the air alarm menu.
@@ -39,8 +35,6 @@
   These thresholds can be adjusted and disabled as needed.
   For example, if you are monitoring a room that naturally has a low temperature (such as a freezer) or a high temperature (such as a burn chamber), you can adjust the temperature thresholds to match the expected values.
 
-  An air sensor can also be constructed and [textlink="linked" link="ESNetworking"] to an air alarm.
-
   <Box>
     <GuideEntityEmbed Entity="AirSensor"/>
   </Box>
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/AirScrubber.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/AirScrubber.xml
@@ -7,12 +7,12 @@
   </Box>
   The air scrubber requires [textlink="power" link="ESPower"] through a nearby [textlink="LV cable" link="ESVoltageNetworks"] to function.
 
-  The default behavior of an air scrubber is to scrub all gasses except Nitrogen and Oxygen from the atmosphere it's exposed to. It will continue this behavior unless directed by a [textlink="linked" link="ESNetworking"] [textlink="air alarm" link="ESAirAlarms"].
+  The default behavior of an air scrubber is to scrub all gasses except Nitrogen and Oxygen from the atmosphere it's exposed to. It will continue this behavior unless directed by a linked [textlink="air alarm" link="ESAirAlarms"].
 
   The scrubber can be welded with any welding tool to stop it from functioning.
 
   ## Configuration Options
-  When [textlink="linked" link="ESNetworking"] to an [textlink="air alarm" link="ESAirAlarms"], air scrubbers gain more functionality.
+  When linked to an [textlink="air alarm" link="ESAirAlarms"], air scrubbers gain more functionality.
 
   The target gasses for scrubbing can be defined in the "Gas filters" dropdown. Keep in mind this resets if you change [textlink="air alarm" link="ESAirAlarms"] modes.
 
@@ -39,7 +39,7 @@
 
   This effectively multiplies its total speed, as air scrubbers will now preform their scrubbing work on 5 tiles at once.
 
-  Scrubbers [textlink="linked" link="ESNetworking"] to an [textlink="air alarm" link="ESAirAlarms"] in auto mode will automatically enable WideNet mode under the [textlink="air alarm's" link="ESAirAlarms"] "Filtering (Wide)" mode when a high concentration of unwanted gasses is detected in the atmosphere.
+  Scrubbers linked to an [textlink="air alarm" link="ESAirAlarms"] in auto mode will automatically enable WideNet mode under the [textlink="air alarm's" link="ESAirAlarms"] "Filtering (Wide)" mode when a high concentration of unwanted gasses is detected in the atmosphere.
 
   WideNet is extremely useful in quickly scrubbing large amounts of tritium from plasma burn chambers.
 
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/AirVent.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/AirVent.xml
@@ -33,7 +33,7 @@
   The amount of gas they leak out is relative to the current pressure of the pipenet they're connected to.
 
   ## Configuration Options
-  When [textlink="linked" link="ESNetworking"] to an [textlink="air alarm" link="ESAirAlarms"], air vents gain more functionality.
+  When linked to an [textlink="air alarm" link="ESAirAlarms"], air vents gain more functionality.
 
   Air vents have two "vent direction" options: Releasing and Siphoning.
   - Releasing simply releases gasses into the atmosphere from the connected pipenet.
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/Airlocks.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/Airlocks.xml
@@ -56,10 +56,6 @@
 
   They can open, close, bolt, and set to emergency access using these remotes.
 
-  ## Linking
-  Airlocks can be linked using the [textlink="Link" link="ESNetworking"] system to other devices.
-  This allows for proper station airlocks to space, or to link multiple airlocks together.
-
   ## Styling
   Airlocks can come in different styles to match station departments. The department style commonly reflects the required access level.
 
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/AtmosphereInOut.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/AtmosphereInOut.xml
@@ -12,14 +12,5 @@
   With these devices, Atmos can insert, extract, or scrub unwanted gasses from any atmosphere they would like.
   This allows the maintaining of a safe, breathable atmosphere.
 
-  Some of these devices require [textlink="power" link="ESPower"] to function, and can be linked to an [textlink="air alarm." link="ESAirAlarms"]
-
-  [textlink="Linking" link="ESNetworking"] compatible devices to an air alarm unlocks more configuration options and functionality. Otherwise, these devices follow their default behavior as defined in the subguides.
-
-  <Box>
-    <GuideEntityEmbed Entity="AirAlarm"/>
-    <GuideEntityEmbed Entity="Multitool"/>
-    <GuideEntityEmbed Entity="NetworkConfigurator"/>
-  </Box>
-
+  Some of these devices require [textlink="power" link="ESPower"] to function, and are linked to an [textlink="air alarm." link="ESAirAlarms"]
 </Document>
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/Engineering.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/Engineering.xml
@@ -20,7 +20,6 @@
   <Box>
     <GuideEntityEmbed Entity="Welder"/>
     <GuideEntityEmbed Entity="Multitool"/>
-    <GuideEntityEmbed Entity="NetworkConfigurator"/>
   </Box>
   Your core toolset is a small variety of tools.
   If you're an engineer, then you should have a belt on your waist containing one of each; if not, you can likely find them in maintenance shafts and in tool storage within assorted toolboxes and vending machines.
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/FireAndGasControl.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/FireAndGasControl.xml
@@ -35,13 +35,10 @@
   A common example of this is a firelock that has released due to both sides being exposed to space.
 
   ## Connecting to Air and Fire Alarms
-  Firelocks can be connected to [textlink="air alarms" link="ESAirAlarms"] and fire alarms to receive instructions on when to drop.
-  Firelocks use the [textlink="List system" link="ESNetworking"], and you can connect these devices using a multitool or network configurator.
+  Firelocks may be connected to [textlink="air alarms" link="ESAirAlarms"] and fire alarms to receive instructions on when to drop.
 
   <Box>
     <GuideEntityEmbed Entity="Firelock" Caption=""/>
-    <GuideEntityEmbed Entity="Multitool" Caption=""/>
-    <GuideEntityEmbed Entity="NetworkConfigurator" Caption=""/>
     <GuideEntityEmbed Entity="FireAlarm" Caption=""/>
     <GuideEntityEmbed Entity="AirAlarm" Caption=""/>
   </Box>
@@ -65,7 +62,7 @@
     <GuideEntityEmbed Entity="FireAlarm"/>
   </Box>
 
-  Devices with sensors can be [textlink="linked" link="ESNetworking"] to fire alarms, which will trigger the fire alarm if the sensor enters the [color=red]Danger[/color] temperature threshold as defined by its sensors.
+  Devices with sensors may be linked to fire alarms, which will trigger the fire alarm if the sensor enters the [color=red]Danger[/color] temperature threshold as defined by its sensors.
 
   When the fire alarm is triggered, all connected firelocks will be overridden with a [color=red]Danger[/color] alert state and will drop.
 
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/Networking.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/Networking.xml
@@ -3,62 +3,5 @@
   On the station, devices need to communicate to each other to preform their functions.
   [textlink="Air alarms" link="ESAirAlarms"] need to talk to their respective devices, [textlink="doors" link="ESAirlocks"] need to be linked to form proper airlocks, and much more.
 
-  This is done through two systems, the Link system and the List system.
-
-  You can use either the Multitool or Network Configurator to interact with these systems.
-  You can switch between the different systems using [color=yellow][bold][keybind="AltActivateItemInHand"][/bold][/color] or by hovering your cursor over the device and using [color=yellow][bold][keybind="AltActivateItemInWorld"][/bold][/color].
-
-  <Box HorizontalAlignment="Stretch">
-    <Box>
-      <GuideEntityEmbed Entity="Multitool"/>
-    </Box>
-    <Box>
-      <GuideEntityEmbed Entity="NetworkConfigurator"/>
-    </Box>
-  </Box>
-
-  Some devices will require access to link devices to them.
-  For example, you need Atmospherics access to link devices to an [textlink="air alarm" link="ESAirAlarms"].
-  For doors, you'll need the access level of the door you're linking to.
-
-  ## Link System
-  The link system is used for explicitly linking two devices, such as linking a door to another door.
-
-  <Box>
-    <GuideEntityEmbed Entity="AirlockExternal"/>
-    <GuideEntityEmbed Entity="AirlockEngineering"/>
-    <GuideEntityEmbed Entity="BlastDoor"/>
-    <GuideEntityEmbed Entity="SignalButton"/>
-  </Box>
-
-  Under the link system, devices have [bold]ports[/bold] that are capable of either sending or receiving signals.
-
-  Hovering over a port using your cursor will show a tooltip that tells you what the port does.
-  For example, output ports will state the conditions under which they will invoke a signal, and input ports will state what the device will do if it receives a signal.
-
-  ## List System
-  The list system is used for linking multiple devices to a single primary device, such as linking multiple atmospherics devices to an air alarm.
-
-  <Box>
-    <GuideEntityEmbed Entity="AirAlarm" Caption=""/>
-    <GuideEntityEmbed Entity="GasVentPump" Caption=""/>
-    <GuideEntityEmbed Entity="GasVentScrubber" Caption=""/>
-    <GuideEntityEmbed Entity="AirSensor" Caption=""/>
-    <GuideEntityEmbed Entity="Firelock" Caption=""/>
-  </Box>
-
-  Each device has its own unique address, which is used to identify it in the list system. When you link a device to a primary device, you are adding the device's address to a list of devices that the primary device will communicate with.
-
-  You can save a device's address to your tool by interacting with the device using [color=yellow][bold][keybind="Use"][/bold][/color].
-
-  Once you have a list of devices saved to your tool, you can link them to a primary device by interacting with the primary device using [color=yellow][bold][keybind="Use"][/bold][/color], which will bring up a UI.
-
-  The UI has multiple options:
-  - Set: Overwrites the current list of linked devices with the devices saved on the tool.
-  - Add: Adds the devices saved on the tool to the current list of linked devices.
-  - Clear: Removes all linked devices from the air alarm.
-  - Copy: Copies the list of currently linked devices to the tool.
-  - Show: Draws a line between the primary device and all linked devices. This is useful for visualizing the area the air alarm covers.
-
-  If you need to clear your tool, you can press [color=yellow][bold][keybind="Use"][/bold][/color] on the tool or use [color=yellow][bold][keybind="ActivateItemInHand"][/bold][/color] to bring up a list of saved devices, and then press the "Clear" button.
+  [color=red][bold]On ES, machine linking is not currently exposed for players to interact with and is slated to be reworked, although machines like the above still use it internally.[/bold][/color]
 </Document>
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/SignalValve.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/SignalValve.xml
diff --git a/Resources/ServerInfo/_ES/Guidebook/Engineering/Valves.xml b/Resources/ServerInfo/_ES/Guidebook/Engineering/Valves.xml
@@ -3,14 +3,12 @@
   Valves are a quick way to halt or permit gas flow through a [textlink="pipenet" link="ESPipeNetworks"].
   <Box>
     <GuideEntityEmbed Entity="GasValve"/>
-    <GuideEntityEmbed Entity="SignalControlledValve"/>
     <GuideEntityEmbed Entity="PressureControlledValve"/>
     <GuideEntityEmbed Entity="GasPassiveGate"/>
     <GuideEntityEmbed Entity="GasPressureRegulator"/>
   </Box>
   All valves do not require [textlink="power" link="ESPower"] to operate.
 
   Valves may look simple, but they can enable a wide variety of complex pipe systems, including:
-  - Signal valves responding to air alarm or logic gate outputs
   - Pneumatic valves controlling variable venting of waste gasses from a burn chamber
 </Document>
diff --git a/Resources/migration.yml b/Resources/migration.yml
@@ -320,6 +320,9 @@ AnomalyLocator: ESAnomalyProbe
 # 2026-2-23
 ESVendingMachineRestockGlobal: null
 ESCrateRestock: null
+
+# 2026-2-25
+NetworkConfigurator: Multitool
 # ES END
 
 # 2023-07-03
