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

[Suggestions] Network Configurator Improvements #112

Closed
54M44R opened this issue Oct 27, 2022 · 0 comments · Fixed by #116
Closed

[Suggestions] Network Configurator Improvements #112

54M44R opened this issue Oct 27, 2022 · 0 comments · Fixed by #116

Comments

@54M44R
Copy link

54M44R commented Oct 27, 2022

Suggestions

  1. Locking Configurator to a pusher / grabber
  2. A method to remove / reduce the spam of messages when applying configurations

Locking Configurator

The ability to lock a configurator's configurations to a pusher / grabber would be useful to reduce misclicking heavily when using the configurator tool.

In theory, the configurator would become "locked" when you store a configuration. If you store a configuration from a pusher, then from that point on, you can only apply that configuration to a pusher. If you tried to apply said configuration to a grabber, it would not. You could clear this by changing the configuration.

Reducing / Removing messages

When applying a large amount of configurations, your chat is quickly overwhelmed by messages. This can be extremely annoying when you're on a decently sized server, and the act of configuring your network causes the server chat to fly by.

There are two ideas I have with reducing the message spam.

  1. Reduce the message to a simple confirmation message. You could implement a command toggle or allow the user to Shift + R Click in the air to toggle this.
  2. Append a number to the message to state how many times configurations were applied. I'm not sure whether this is possible, but if it is, you could use the same two possible implementation suggestions in 1.

Ideally it would be nice to simply disable the message entirely, but theoretically, you could include all these applied configuration messages by allowing the user to shift through them by using Shift + R Click in the air. This would allow users to choose how they wish to see the messages, if at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant