[Halloween Spotlight] Overlapping proximity prompts consume a Key when trying to claim a rune-reward item

Summary

In the Halloween Spotlight event, at the reward spot for a rune-unlocked item, two proximity prompts overlap:

  1. a free Claim prompt for the rune-reward item, and
  2. a Use Key prompt for a different, key-gated item behind it.
    Because Use Key tends to be frontmost (AlwaysShow) and takes focus, interacting consumes a Key even when the player intends to claim the free rune-reward.

Location

Near the rune-reward item (see attached screenshots).

  • Image 1 (before) / Image 2 (after)
  • When moving close to the rune-reward item, two prompts appear at once, Use Key remains focused, and a Key is consumed.

Steps to reproduce

  1. Obtain the required Rune and unlock the target area.
  2. Go to the spot where the rune-reward item can be claimed for free.
  3. Stand right in front of the rune-reward item.
  4. Press the interact key/button once (E / controller confirm).
  5. A Key is consumed, and the key-gated item is taken instead of the free rune-reward.

Note: This is especially hard to avoid on gamepads, where selecting the correct prompt is difficult.

Actual result

  • Use Key takes focus, and a Key is unintentionally consumed.
  • Keys are scarce and hard to obtain, so this causes unplanned loss and frustration.

Frequency

Reproduces every time with the current behavior.

Impact

Players carefully plan where to spend Keys. This disproportionately frustrates children who struggle to obtain high-difficulty Keys.

Attachments

  • Screenshots: Image 1 (before) / Image 2 (after)

Requested mitigation

Please refund 3 Keys to all players who used a Key at this spot during the affected period.

Alternative / Proposed fix

Show the Use Key prompt only in front of the key-gate/door so it never overlaps with the rune-reward claim prompt.

Expected behavior

When the rune-reward item is available, interacting should claim it for free and must not consume a Key.
The Use Key prompt should not take focus in this scenario.

A private message is associated with this bug report

1 Like

Thank you for the detailed notes! The team is working on a fix for this to be pushed out tomorrow.

2 Likes

Following up the team was able to push a fix. Please feel free to message back if you see the issue occur again. Thanks so much!

2 Likes