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
Is your feature request related to a problem? Please describe.
As a server owner, I want a way to edit my configs in a GUI like I would be able to on a client.
Describe the solution you'd like
Allow mods to register their configs as server-modifiable. When the mod in question is present on server and client, a command (added by FL) can be used such as /flconfig <modid>. Server side checks permission, serializes necessary config data and sends to the client, which then spins up a config GUI to edit from. Upon save, client sends the updated config back to the server which loads it in.
Server owners must explicitly opt in to this in a config before anyone has access to this, and even then, they should be able to limit who has access via permission manager, allowlist, or maybe permission level.
Additional context
Challenges:
Knowing which ConfigBasedSerializables to sync - may have to be provided when registering for this command
How to get the Config GUI Builder to take in the server's configs instead of the client's - maybe back up client configs then load server configs on the client, then switch back to client configs once they save/cancel?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a server owner, I want a way to edit my configs in a GUI like I would be able to on a client.
Describe the solution you'd like
Allow mods to register their configs as server-modifiable. When the mod in question is present on server and client, a command (added by FL) can be used such as
/flconfig <modid>
. Server side checks permission, serializes necessary config data and sends to the client, which then spins up a config GUI to edit from. Upon save, client sends the updated config back to the server which loads it in.Server owners must explicitly opt in to this in a config before anyone has access to this, and even then, they should be able to limit who has access via permission manager, allowlist, or maybe permission level.
Additional context
Challenges:
The text was updated successfully, but these errors were encountered: