search

SGA-A / c2c

Source code for the custom app exclusive to cc, where most interactions begin and end.
MIT License
1 stars 0 forks source link

Moving user settings to one command #80

Closed SGA-A closed 5 months ago

SGA-A commented 6 months ago

Is your feature request related to a problem? Please describe. You can change your profile bio, title, avatar and visibility in multiple different commands along with many other customization options. This is nice, but the problem is this is dispersed amongst many other commands. So the vast majority of the time, the end-user will often never encounter these customizabilty options. This issue is extremely similar to #14.

Describe the solution you'd like Abstract all the customizability commands into a single command. You can add more commands if its not related to one another. For example, if you want to change the server multiplier, it could be in the /serversettings command, but not the /settings (aka /usersettings) command. A dropdown can be displayed to show all the available settings to customize. When the user opens the command, you can display a small guide on what this is or begin displaying the first setting already when the user calls the command.

The title of the select option should instantly convey what this setting is, with a suitable description of what this setting is about, what should the user know about this setting that may encourage them to click it? It needs to be a meaningful description.

Once the user selects the option, do whatever is necessary there. As for how you will seperate each setting, it might be a good idea to seperate each setting into a function to avoid making the select class callback massive.

Describe alternatives you've considered No other alternatives have been considered at this time.

Additional context None

SGA-A commented 5 months ago

This is almost complete. We just need to add a server settings menu, for those with manage server permissions. The custom profile management setting is also in the works.

Edit: Figured it is unnecessary to create an entirely new command for managing server settings as there aren't that many settings to toggle in the first place. So the plan to make a server settings menu has essentially been scraped completely, though we'll consider it in the future if we need it, but not right now.