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
Currently (as of v0.2.1) in a dedicated server environment, there is no way to change ThatOrThis' settings without manually editing choices.json. This is not considered a lack of feature (since ThatOrThis is not designed for server-side anyway), but it would be nice to have a similar GUI as on client-side.
Features would be like:
An additional button will be added to the server GUI (that window with console and memory usage bar charts), which brings you to the settings window.
The settings window will be remade using a Java GUI toolkit (Swing?) mimicking the layout and behavior of a client-side settings screen.
The window will not be textured, and because of the inability to render formatting codes, all formatting codes will be omitted from the display.
If server is started in headless mode (-nogui), no button or window will be shown.
This feature will, however, need to rewrite a lot of vanilla GUI components. Also, since even server.properties needs to be edited by hand, there is no strong demand to implement this feature. So I'm posting this question issue here for suggestion and feedback.
The text was updated successfully, but these errors were encountered:
Currently (as of v0.2.1) in a dedicated server environment, there is no way to change ThatOrThis' settings without manually editing
choices.json
. This is not considered a lack of feature (since ThatOrThis is not designed for server-side anyway), but it would be nice to have a similar GUI as on client-side.Features would be like:
-nogui
), no button or window will be shown.This feature will, however, need to rewrite a lot of vanilla GUI components. Also, since even
server.properties
needs to be edited by hand, there is no strong demand to implement this feature. So I'm posting thisquestion
issue here for suggestion and feedback.The text was updated successfully, but these errors were encountered: