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

[Bug]: medical-scan-target works inconsistently #20089

Open
1 task done
zagoon opened this issue Oct 21, 2024 · 2 comments · May be fixed by #20083
Open
1 task done

[Bug]: medical-scan-target works inconsistently #20089

zagoon opened this issue Oct 21, 2024 · 2 comments · May be fixed by #20083
Labels
✔️ Issue Replicable The issue has been confirmed to be replicable.

Comments

@zagoon
Copy link

zagoon commented Oct 21, 2024

Checks

  • I have searched the bug with a few keywords, and I confirm this bug was not yet reported.

Location

Horizon

Describe the issue

Medical-scan-target often doesn't work when you jump to a mob ("This isn't a scannable target"). Moving away (but remaining on the same screen) and jumping back onto them will fix it for a while, but it may break again later in the round.

This is generally agnostic of how you attempt to follow them (follow verb, crew manifest, double-clicking, chat, etc.)

Examples:

scannable1

scannable2

scannable3

I scan Auil'suos, move away and observe somewhere else for a while, then come back and attempt to scan them again (unclear how long this takes to reproduce, but it did eventually break for all the previously scanned mobs above):

scannable4

scannable5

How to reproduce

If you jump to a mob immediately after ghosting, this bug may not trigger. Future jumps will likely trigger it. Recommend trying multiple mobs to proc it.

Round ID

No response

Staff ckey

No response

@AlaunusLux
Copy link
Contributor

Caused by changes in #20083 (for visibility)

@FluffyGhoster
Copy link
Contributor

Will be fixed whenever we refresh the testmerge

@FluffyGhoster FluffyGhoster added the ✔️ Issue Replicable The issue has been confirmed to be replicable. label Oct 23, 2024
@FluffyGhoster FluffyGhoster linked a pull request Oct 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✔️ Issue Replicable The issue has been confirmed to be replicable.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants