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
Would there be a chance of this causing problems for types that really shouldn't be listable. E.g. PlayerID can be expensive if enough players are specified, or in some commands (e.g. place players [place id]) it could be potentially problematic.
Would there be a chance of this causing problems for types that really shouldn't be listable. E.g. PlayerID can be expensive if enough players are specified, or in some commands (e.g. place players [place id]) it could be potentially problematic.
No, I don't think so. This would create a plural type out of any singular types, so commands can still choose to use the singular variation if they wish which isn't listable. This change would only mean that if a type like "integer" is registered, it will automatically register "integers". But if you only wanted one integer, you could still use type "integer" in your command. So the control is still up to the developer here.
No description provided.
The text was updated successfully, but these errors were encountered: