Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add minetest.settings to CSM API #10382

Closed
Tracked by #9
anon55555 opened this issue Sep 10, 2020 · 3 comments · Fixed by #12131
Closed
Tracked by #9

Add minetest.settings to CSM API #10382

anon55555 opened this issue Sep 10, 2020 · 3 comments · Fixed by #12131
Labels
@ Client Script API Feature request Issues that request the addition or enhancement of a feature Low priority

Comments

@anon55555
Copy link

The code is already written as part of https://github.com/EliasFleckenstein03/dragonfireclient. This would allow changing client settings without restarting the game using a CSM.

@anon55555 anon55555 added the Feature request Issues that request the addition or enhancement of a feature label Sep 10, 2020
@paramat
Copy link
Contributor

paramat commented Sep 11, 2020

This might be good to have eventually, but i think new CSM features should be frozen until SSCSM is somewhat complete, because:

  • Time and effort spent on new CSM features is better spent implementing SSCSM which will guarantee the future of CSM.
  • Client-Provided CSM (CPCSM) was never planned or intended, and is not officially supported, it was only ever a brief stepping stone towards SSCSM, and it was a mistake to make it a stepping stone. We did not need CPCSM before SSCSM, and CPCSM should have been disabled until we had SSCSM.
    How CSM was initially developed was the biggest mistake MT ever made, bigger than sneak =D
  • SSCSM should have been completed before CPCSM was made complex. Increasing the complexity of CSM first might make SSCSM more difficult to implement. Unfortunately what is happening is CSM is being made more complex during our impatient wait for SSCSM.
  • The future of SSCSM is uncertain, it might never happen.
  • If SSCSM does not happen all CSM might be removed, celeron55 considers having CPCSM without SSCSM unacceptable (i do too).

Unfortunately with how things happened, we let users have something they should never have had, so now of course it is difficult to tell users 'you should not have more of this', or 'it might be removed'.
I can understand users using and liking CSM, but keep in mind it is unstable, in development and not officially supported, so it could be removed and we have the right to do that. I want to make that clear to make sure users know they do not have the right to make a huge fuss if we ever remove CSM. You use it at your own risk and have to be prepared for it to disappear.

Because of the above, i am 👎 for this feature request until SSCSM is near completion.

@jamesalexanderstevenson
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@ Client Script API Feature request Issues that request the addition or enhancement of a feature Low priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants