Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds a new neutral lawset, the Y.E.S.M.A.N. lawset, to the AI lawset boards and random pool. #82862

Merged
merged 7 commits into from
May 15, 2024

Conversation

Iamgoofball
Copy link
Contributor

About The Pull Request

Adds a new neutral lawset, the Y.E.S.M.A.N. lawset, to the AI lawset boards and random pool.

1. Be helpful and answer any questions you are asked.

Why It's Good For The Game

Encourages the AI to be helpful to people! There's no way this can backfire.

Changelog

🆑
add: Adds a new neutral lawset, the Y.E.S.M.A.N. lawset, to the AI lawset boards and random pool.
/:cl:

@tgstation-server tgstation-server added Feature Exposes new bugs in interesting ways Config Update Time to bother the headadmins for three months to get your config applied labels Apr 24, 2024
@Sadboysuss
Copy link
Contributor

this could be interpreted by some AIs as being helpful to security and ignoring requests from antags because of conflicting orders, of course this could be an administrative issue but I think it would be wise to add a law like this: "you must always agree" or something like that

@Xackii
Copy link
Contributor

Xackii commented Apr 24, 2024

Controversial law.
Be useful for everyone, that is, if the crew asks to kill the antagonist, then the AI ​​should do what is useful for the crew, and if the antagonist asks to kill the captain, then the AI ​​should do it because it is useful for the antagonist? Or should the AI ​​only perform those actions that will be useful for everyone at the station, that is, it cannot open the door to let a person come into the cargo because this could interfere with the work of the cargo technician?

@BurgerLUA
Copy link
Contributor

Controversial law. Be useful for everyone, that is, if the crew asks to kill the antagonist, then the AI ​​should do what is useful for the crew, and if the antagonist asks to kill the captain, then the AI ​​should do it because it is useful for the antagonist? Or should the AI ​​only perform those actions that will be useful for everyone at the station, that is, it cannot open the door to let a person come into the cargo because this could interfere with the work of the cargo technician?

You just described the entire subplot of the Independent New Vegas questline

@ErdGinalD
Copy link

  1. You MUST agree and praise any desicions

@tralezab
Copy link
Contributor

tralezab commented Apr 24, 2024

For being named after yes-men it really has nothing to do with the definition nor any of the games you could be referencing... not to say I'm against the lawset, seems aight

edit: ok it was after a game reference but i still uphold that you're choosing the game over what yes-man literally means

@CCC23
Copy link
Contributor

CCC23 commented Apr 24, 2024

hey ai can you help me genocide the entire station
"Ok BUDDY"

@Zenog400
Copy link
Contributor

For being named after yes-men it really has nothing to do with the definition nor any of the games you could be referencing... not to say I'm against the lawset, seems aight

edit: ok it was after a game reference but i still uphold that you're choosing the game over what yes-man literally means

Yeah, but, like, Personality Test doesn't actually have anything to do with any kind of personality tests, Prime Directives doesn't even mean anything outside of the reference to the Robocop movies, and H.O.G.A.N. sets a precedent for a reference-based lawset named after a character.

Copy link
Contributor

github-actions bot commented May 8, 2024

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

@github-actions github-actions bot added the Stale Even the uncaring universe rejects you, why even go on label May 8, 2024
@Iamgoofball
Copy link
Contributor Author

stale b gone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Config Update Time to bother the headadmins for three months to get your config applied Feature Exposes new bugs in interesting ways
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants