Bot Policy

[LeekiLoku]

Okay so I got perma'd but whatever, im here to know what is the policy about bots (janitor, Floor, Mule and Medibot) when they get emmaged do they not do anything, or is it different. I just dont know the bot policy.

[Bepis]

https://tgstation13.org/wiki/Guide_to_robotics#Bots

each entry tells you what happens if they're emagged

edit: guessing you'd be subject to silicon policy when in control

https://github.com/tgstation/tgstation/pull/76691

[Timberpoes]

Blame the codebase for merging a PR requiring policy without getting the policy situation ironed out first.

There is no current policy, so server rule 1 applies. Don't be a dick.

Being a dick is a fast track to a perma. Exploiting bugs while being a dick is a super fast track to a perma.

[Vekter]

This thread isn't relevant whatsoever to Loku's ban, nor do we have any kind of actual policy set up for bots yet aside from the common sense of "don't be a dick". I'm not sure we need one, to be honest - the only bot that can actually do anything antagonistic when not emagged is the MULE and it can't run people over unless it's been hacked or emagged as of a change this morning

[BlueMemesauce]

Timberpoes, MULEbots running people over is not a bug, it has been in the game for years, it just didn't happen often before since nobody cared to use the MULEbots.
And it is completely relevant Vekter. The whole point of having rules is to make the core rule of "don't be a dick" more clear. Everyone has different interpretations of what that means. And we still need a policy to determine what happens when bots are hacked/emagged. Are they allowed to kill people with their dangerous abilities or is the bot just useless now and forced to do nothing?

[conrad]

Are they allowed to kill people with their dangerous abilities or is the bot just useless now and forced to do nothing?

Why are those the only two options?

[Vekter]

Timberpoes, MULEbots running people over is not a bug, it has been in the game for years, it just didn't happen often before since nobody cared to use the MULEbots.
And it is completely relevant Vekter. The whole point of having rules is to make the core rule of "don't be a dick" more clear. Everyone has different interpretations of what that means. And we still need a policy to determine what happens when bots are hacked/emagged. Are they allowed to kill people with their dangerous abilities or is the bot just useless now and forced to do nothing?

I told you this in another post but I'll mirror it here - MULEbots that are possessed aren't supposed to be able to run over STANDING, living humans with a mind datum.

[LeekiLoku]

I told you this in another post but I'll mirror it here - MULEbots that are possessed aren't supposed to be able to run over STANDING, living humans with a mind datum.

Changing z-levels crush humans and also tram, so yea its a bug. Will it ever be fixed? Probably not, because it seems like it would be hard.

[BlueMemesauce]

Are they allowed to kill people with their dangerous abilities or is the bot just useless now and forced to do nothing?

Why are those the only two options?

Because when a bot gets emagged it replaces their abilities with dangerous abilities. For example, if a firebot gets emagged, its firefighting capability gets replaced with the ability to create fires. And if you aren't allowed to set people on fire and that's literally the only thing you can do then that means you're forced to do nothing.

[Constellado]

If a non sentient bot gets emagged, it goes ham and hurts people. That is fun.
Do we want ghost role bots to do the same?
I sort of do.
Image a world where you are an antag and you go and emag every bot you see, and these bots end up doing nothing.
Boowamp. Boring.

Issue is these sentient bots are way smarter than the non sentient ones and will cause a lot more damage.

[Archie700]

I believe bots should have a simple law set that precludes any harm done by the borg, then states to serve the station.

Of course that completely changes if it's hacked or emagged, with its own zeroth law.

[Ezel]

i believe this should be disabled by default a player needs to download a PAI before it becomes a PAI
why can ghosts pop into any bot without a problem what if a cargo tech wanted to use a mulebot but both mulebots ficked off cuz ghost role is enabled by default i think this should be a player thing to activate instead of on its own

[Ezel]

Timberpoes, MULEbots running people over is not a bug, it has been in the game for years, it just didn't happen often before since nobody cared to use the MULEbots.
And it is completely relevant Vekter. The whole point of having rules is to make the core rule of "don't be a dick" more clear. Everyone has different interpretations of what that means. And we still need a policy to determine what happens when bots are hacked/emagged. Are they allowed to kill people with their dangerous abilities or is the bot just useless now and forced to do nothing?

Mulebots could always been able to run over people it the hacking in the past only let the mulebots be able to knock over people and be faster and be able to load anything on it the knocking over got removed cuz it was OP but they always been able to run over people unhacked

[BlueMemesauce]

i believe this should be disabled by default a player needs to download a PAI before it becomes a PAI
why can ghosts pop into any bot without a problem what if a cargo tech wanted to use a mulebot but both mulebots ficked off cuz ghost role is enabled by default i think this should be a player thing to activate instead of on its own

MULEbots was just made disabled at roundstart in https://github.com/tgstation/tgstation/pull/76837 but other bots like cleanbots and medibots are still enabled.

[Ezel]

i believe this should be disabled by default a player needs to download a PAI before it becomes a PAI
why can ghosts pop into any bot without a problem what if a cargo tech wanted to use a mulebot but both mulebots ficked off cuz ghost role is enabled by default i think this should be a player thing to activate instead of on its own

MULEbots was just made disabled at roundstart in https://github.com/tgstation/tgstation/pull/76837 but other bots like cleanbots and medibots are still enabled.

I still think this should be the case for all bots with special interaction (to turn them evil if they're emagged)
I don't think a ghost should just be able to join a random medibot and cuck a antag out of his heals (that normally a medibot would give)

[kieth4]

When you spawn in you get a flavour text, just follow it. Not everything needs to be about going sicko-mode murder.