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

Fix runtimes and multitool bricking if a sentry_computer is deleted #5345

Merged

Conversation

Drulikar
Copy link
Contributor

@Drulikar Drulikar commented Dec 30, 2023

About the pull request

This PR resolves some runtimes and the bricking of a multitool if it is loaded with a deleted sentry. The weakref resolve in the multitool wasn't checked if the resolve passed. Additionally, the sentries would remain encrypted to a non-existent computer. If bricking an encrypted sentry is intended, it needs to be handled more gracefully.

Explain why it's good for the game

Fixes a runtime when using a multitool linked to a deleted sentry_computer:
image

Fixes a runtime when using said multitool to unpair the sentry from a deleted sentry_computer.
image

Testing Photographs and Procedure

Screenshots & Videos
  1. Link tuner w/ a laptop
  2. Delete laptop
  3. Spawn a new laptop
  4. Use tuner on new laptop
  5. Runtime when trying to clear because the weakref resolve wasn't checked.
Untitled.mp4

Changelog

🆑 Drathek
fix: Fix handling of sentry_computer deletion
/:cl:

@github-actions github-actions bot added the Fix Fix one bug, make ten more label Dec 30, 2023
@realforest2001 realforest2001 added this pull request to the merge queue Jan 1, 2024
Merged via the queue into cmss13-devs:master with commit 0863c06 Jan 1, 2024
28 checks passed
cm13-github added a commit that referenced this pull request Jan 1, 2024
@Drulikar Drulikar deleted the Fix_Sentry_Computer_Deletion branch January 1, 2024 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fix Fix one bug, make ten more
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants