LZ detector showing as not installed in the pilots console on the alamo

[Drewzeedo5]

Testmerges

BYOND Version: 515.1635 Server revision compiled on: 2024-04-12T10:54:55+00:00 Master commit: 177164b The following pull requests are currently test merged: #5914: 'Ports stripping menu from TG' by ihatethisengine at commit 25cba9c #6015: 'Colony Synthetic variants with a refresh' by QuickLode at commit c6f1f9a #6040: 'Better throw logic' by Git-Nivrak at commit 7314763 #5401: 'M540-B Armored Recon Carrier' by Zonespace27 at commit 6cbd84f #6103: 'Med Vendor Rebalance' by Drulikar at commit bc95c5d #5957: 'OT CAS rocket' by iloveloopers at commit d9da5fe #6107: 'Adds medlinks to the marinemeds in medbay' by Drulikar at commit 9b99343 #6039: 'Project ARES TM Holder (v5)' by realforest2001 at commit e46cc87 #6114: 'dehardcodes client version warnings' by harryob at commit 653037e Local commit: 27378272b3edc2f5604f1c5a88de6f367490988b TGS version: 6.3.1 DMAPI version: 5.9.0

Round ID

Map: Trijent Dam Round ID: 21729 Server Time: 2024-04-13 02:22:35 Round Time: 00:37 Operation Time: 08:34 Security Level: GREEN Primary LZ: LZ1 'Admin' Operation Name: Peacekeeping Mission Foxtrot-X-ray View Tactical Map

Description of the bug

installed LZ detector as PO, not showing as installed, cameras not working in the weapons console

What's the difference with what should have happened?

see LZ detector cams on weapons console when selecting cameras

How do we reproduce this bug?

installed LZ detector as PO, not showing as installed, cameras not working in the weapons console

Issue Bingo

• Issue could be reproduced at least once
• Issue happened in a recent (less than 7 days ago) round
• Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)

[Drewzeedo5]

[ihatethisengine]

Not a bug, you are meant to use camera console to access LZ detector cameras. "Component not found" message is due to the fact there is no menu for the component, as there is nothing to interact with.

[ihatethisengine]

[Huffie56]

@Drewzeedo5 if you could change your issue name and description to match what ihate say above that would be nice.
your issue isn't a bug but a misleading screen error...