Make drones area unrestricted

[grungussuss]

This pr:
https://github.com/tgstation/tgstation/pull/87983
Added a config flag that allows drones to interact in the supermatter and atmospherics area.
I propose setting the flag to 0 in config on some (or all) servers so drones can have some fun.

[Vekter]

What kind of fun are you intending? Because the design space around drones has been to make them incapable of doing anything that sabotages the station, for very, very good reason.

I'm not necessarily against this, but I do have concerns given how hard drones have historically been to administrate, as well as this being a PR that you created and had merged, so part of me worries that the intent is to enable doing fuckshit as a drone.

[DrAmazing343]

I think I said as much on the PR adding granularity to the config for drones, but I believe we can now handle the administrative issues this could cause. Ghostrole bans can be doled out to those who fail to comply with their laws, and seeing a slow rise of genuine law-abiding drones on Manuel, I'm very much happy to enable them to actually do their jobs. I specifically asked them to make this a policy thread so I could remember to bring it up with my fellow headmins, and so I will do that now.

[Vekter]

Okay, in that case, that removes a lot of the ambiguity here.

I'm not really sold on this. We've tried it a couple of times and the main issue tends to be that we really don't have a reliable way to log a lot of the things that drones are capable of that go against their laws. I distinctly recall being unable to really effectively moderate a lot of situations where a drone had taken and moved something elsewhere because we just didn't have a way to log that kind of thing.

I feel like the stuff they can get up to with atmos and the supermatter does have better logging, but I'm concerned this will enable a lot of low-effort sabotage issues when someone figures out where the lapse in our logging is that might allow them to do it and get away with it.

If the other admins agree that it's worth trying, I'm willing to give it a shot, but I can already see those same problems from before happening again.

[NoxVS]

I don't really want drones doing stuff in that area is my problem, it's the realm of atmos techs and engineers. They shouldn't be undoing sabotage or anything in these areas. I really prefer just being more lenient on drone laws but using code to cripple what they can do to make sure they aren't out of line.

Honestly though, I don't think there's a need for drones. You can easily do everything a drone does by just asking for access changes and doing it as a human. We even have revived crewmember ghost roles for this.

[grungussuss]

You should bring up the things that need logging so that the codebase can add it

[Vekter]

You should bring up the things that need logging so that the codebase can add it

The problem is that it's shit that can't reasonably be logged, unless we want to log literally every instance of someone touching, grabbing, and/or moving something. One of the big issues we've had in the past was people taking drone roles and moving corpses around, either dragging a friend to medbay or dragging whoever killed them to space. My big concern here would be a drone using their access to the supermatter to dust corpses.

[DaydreamIQ]

I like drones. But they shouldn't be touching atmos at all. HOWEVER there is a nasty bug that basically soft locks you if you find yourself stuck in either area without gravity as you can't lay down rods to move but the answer to that is just...stay away from those areas

[Longestarmlonglaw]

I don't really want drones doing stuff in that area is my problem, it's the realm of atmos techs and engineers. They shouldn't be undoing sabotage or anything in these areas. I really prefer just being more lenient on drone laws but using code to cripple what they can do to make sure they aren't out of line.

Honestly though, I don't think there's a need for drones. You can easily do everything a drone does by just asking for access changes and doing it as a human. We even have revived crewmember ghost roles for this.

I agree, drones are outdated, outperformed by engineering borgs, and their laws to avoid interaction go directly against part of ss13 as a whole: the "Talking to others" which you can't do because of the drone laws.
Remove drones, or rewrite their laws.

[EmpressMaia]

No. Drones shouldn't be able to maintain the stations powe source. They are there to help in fixing breaches and looking funny when wearing hats

[xzero314]

Please keep drones out of atmos and engineering.

[datorangebottle]

It's always annoyed me that drones can't repair the engine room after it explodes or atmos after it burns down.
Solving active problems is a 'no', but if the room is just a massive hole they should be able to fix that.

[grungussuss]

You should bring up the things that need logging so that the codebase can add it

The problem is that it's shit that can't reasonably be logged, unless we want to log literally every instance of someone touching, grabbing, and/or moving something. One of the big issues we've had in the past was people taking drone roles and moving corpses around, either dragging a friend to medbay or dragging whoever killed them to space. My big concern here would be a drone using their access to the supermatter to dust corpses.

Drones can't touch bodies nowadays afaik, if they can we can fix that