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
Show a notification when we block an action due to cheatsAllowed or some other (existing or yet to be added) restriction.
This might be easier to implement if we refactor our config usage to go through get or is methods?
This will likely require some kinda notification queue, so that we can clear, enqueue, and show (dequeue) notifications in a non-blocking way, without them clobbering each other.
I think users may wish to configure when they see these notifications and how often.
E.g. one user might like to know the server they just logged into has x, y & z config options disabled, while another user might prefer to see an "action blocked" notification when their camera starts colliding with blocks.
Why is this useful?
It is confusing to have the mod setup to work a certain way, yet have it actually behave differently.
Notifying users that some action was blocked or some config is currently disabled due to reason xyz would make this less confusing.
Existing features
The configurable server whitelist/blacklist already shows a "freecam not allowed on this server" notification when attempting to toggle
The text was updated successfully, but these errors were encountered:
Description of the feature
Show a notification when we block an action due to
cheatsAllowed
or some other (existing or yet to be added) restriction.This might be easier to implement if we refactor our config usage to go through get or is methods?
This will likely require some kinda notification queue, so that we can clear, enqueue, and show (dequeue) notifications in a non-blocking way, without them clobbering each other.
I think users may wish to configure when they see these notifications and how often.
E.g. one user might like to know the server they just logged into has x, y & z config options disabled, while another user might prefer to see an "action blocked" notification when their camera starts colliding with blocks.
Why is this useful?
It is confusing to have the mod setup to work a certain way, yet have it actually behave differently.
Notifying users that some action was blocked or some config is currently disabled due to reason xyz would make this less confusing.
Existing features
The text was updated successfully, but these errors were encountered: