You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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):
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
The text was updated successfully, but these errors were encountered:
Checks
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:
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):
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
The text was updated successfully, but these errors were encountered: