Fix: Set DenyReason when access check fails #41012
Open
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #40987
Related to PR #40883
Set DenyReason in CheckUserHasLockAccessEvent when access is denied to display "Access denied." popup to users. Uses ??= to avoid overriding reasons from other lock systems.
About the PR
Added an
else
clause toAccessReaderSystem.OnCheckLockAccess
that sets theDenyReason
field when a user is denied access to a locked entity.Why / Balance
After PR #40883 refactored the lock system to use an event-based architecture, users stopped receiving the correct text popup when attempting to interact with locked entities (lockers, doors, etc.) without proper access. This restores the "Access denied." popup text.
Technical details
AccessReaderSystem.OnCheckLockAccess
to setargs.DenyReason
using the existing"lock-comp-has-user-access-fail"
localization key whenIsAllowed
returns false??=
(null-coalescing assignment) to ensure we don't override deny reasons that may have been set by other lock type systems (e.g., fingerprint readers)Media
Requirements
Breaking changes
None
🆑 Changelog