Make NoEnterPlayer easier - revamp command structure #46
Description
Is your feature request related to a problem? Please describe.
- The number of bannable players in a NoEnterPlayer flag is limited by the number of characters you can send in a message
- To add another player to the flag, you have to type all the players in the list again.
Describe the solution you'd like
The entire command format has to change maybe?
Important to recognize the three types of flags.
- Boolean flags are either enabled or disabled and store no other information. For example, NoVehicle.
- Single-input flags take in 1 input. For example, EnterMessage
- Multi-input flags can take in 1 or more inputs. For example, NoEnterPlayer.
Biggest issue I’m trying to solve is that flags that are multi-input flags can’t be easily modified.
Also smaller issue: I don’t really like the word unset and I know a lot of people find it unintuitive. Could be replaced with something else. At the moment I’m thinking create and delete. Do provide feedback on the words to use but I want to focus the convo more on how param lists work.
To fix the smaller issue, im thinking to restructure the command so set and unset get pushed to come up later in the command structure.
Examples below. I think Boolean and single-input flags work well but I don’t yet love the way multi-inputs work
For Boolean flags:
/claimflag NoVehicle create
/claimflag NoVehicle delete
For single-input flags:
/claimflag EnterMessage create hello world
/claimflag EnterMessage delete
For multiinput flags:
/claimflag NoEnterPlayer create player1 — controversial removing the earlier ability to set multiple lines at the same time
/claimflag NoEnterPlayer add player2
/claimflag NoEnterPlayer remove 1 — removes line 1
/claimflag NoEnterPlayer info — shows which item is on which line
/claimflag NoEnterPlayer delete
would love some feedback from all GPF users