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.
Summary
New version of the Wilderness Player Alarm with improvements for plugin inter-operability
Detail
There are two main issues with the plugin that I'm trying to fix here:
I was only able to reproduce this using a user-provided profile which pulled in a truly obscene amount of external plugins. I don't know how people play the game like this, and I don't have insight into which plugin could have caused this. But it turned out to be a simple one-line change to fix it.
This one also weirdly only repro'd with a large profile. It involves GUI elements from other plugins on the same layer getting pushed around by the alarm. My solution to mitigate this is to expose the layer that the alarm is on to the user and allow control of that. Sort of like the ping grapher plugin allows for, but preferring an enum over a bool.