Increase circuitry camera working range

[NerdyVampire]

Circuitry is by far the most relevant when combined with expeditions, but camera consoles cannot connect to "body cams" once they are off-station, which is tragic since they allow on-ship personnel to follow along and feel included.

I would love for the limitation to be laxed or even entirely removed. It's fun and it gives science in particular some powerful and fun things to do, that can also interact with the rest of the crew. I'd definitely be game for setting up a camera console in public so crew can watch Calix work (and potentially die), and outfit expeditions with body cams so the bridge crew/command can actually keep an eye on them.

Seems like an easy opportunity that adds a fair bit of gameplay and fun.

Options: (I prefer A or B. C is cool, but might be mechanically weird)
A: It works within comms range (2 tiles)
B: It works unlimited
😄 It works unlimited, but distance scrambles/delays it.

Edited Thursday at 23:25 by NerdyVampire
title was bad

[Roostercat]

As an XO player I would actually quite like the ability to spy on expeditioners at all times with my beady little eyes

[Fyni]

I'd just like functioning body cams for expeditions only (that is - working off ship), purely for AIs and the one command member forced to stay behind, and for them to NOT be circuit exclusive.

[Nagito Komaeda]

As another XO player, yes please oh my Lord. Being able to actually see what's going on while sitting on the Horizon seems exactly like something we already should have had.

[NerdyVampire]

21 hours ago, Fyni said:

I'd just like functioning body cams for expeditions only (that is - working off ship), purely for AIs and the one command member forced to stay behind, and for them to NOT be circuit exclusive.

That's fine too, but please also make circuitry cams work so science can do stuff that makes us feel useful and not just chaotic ^_^ simple bodycams with no other function are cool, then science can add extra cool things to their own versions.

[NerdyVampire]

Far as I can see, the code in question is this, which only allows for Horizon camera consoles to connect to on-ship cameras.
 

if (!(C.z in GetConnectedZlevels(starting_z_level)))
        to_chat(user, SPAN_NOTICE("This camera is too far away to connect to!"))
        return FALSE

(https://github.com/Aurorastation/Aurora.3/blob/master/code/game/machinery/computer/camera.dm line 120)

Which uses

/proc/GetConnectedZlevels(z)
	. = list(z)
	for(var/level = z, SSmapping.multiz_levels[level][Z_LEVEL_DOWN], level--)
		. |= level-1
	for(var/level = z, SSmapping.multiz_levels[level][Z_LEVEL_UP], level++)
		. |= level+1

(https://github.com/Aurorastation/Aurora.3/blob/master/code/modules/multiz/basic.dm line 15)

It should really just use the same logic as telescience imo; any Z-levels that the Horizon are linked with, except when deepscan is active (which would be too far).

(https://github.com/Aurorastation/Aurora.3/blob/master/code/modules/telesci/telesci_computer.dm line 464)

Edited yesterday at 09:14 by NerdyVampire

[zha everything broken]

This is on my to-do list (medium-term) as part of a larger rollout of remote monitoring systems available to bridge and command.

I will probably PR a stopgap for this though in the meantime, once I'm done with Assunzione.

[NerdyVampire]

16 minutes ago, zha everything broken said:

This is on my to-do list (medium-term) as part of a larger rollout of remote monitoring systems available to bridge and command.

I will probably PR a stopgap for this though in the meantime, once I'm done with Assunzione.

Oh sounds awesome Batra ^_^