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

Update wilderness player alarm #6276

Merged
merged 1 commit into from
Jul 12, 2024
Merged

Update wilderness player alarm #6276

merged 1 commit into from
Jul 12, 2024

Conversation

adhansen
Copy link
Contributor

@adhansen adhansen commented Jul 12, 2024

Overview

Apologies for the back-to-back PRs on the same plug-in. There was a slight regression in #6239 that I slipped in:
With the homemade timeout functionality that I removed, there was logic to check the players in range each tick such that the alarm would go off whenever someone new entered the alarm radius. With the migration to notification overrides, I deleted a lot of that. As a consequence, once a user has been notified of a player nearby, they won't get notified again until they are completely alone or exit & re-enter the dangerous area.

This small change will cause the alarm to trip anew when more players enter the alarm radius, which is useful for places like chaos altar or revs where there may be individuals co-existing and then a new player shows up.

@runelite-github-app
Copy link

@Unmoon Unmoon merged commit 2fa3a6a into runelite:master Jul 12, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants