Many properties within SteamPending are readonly, despite Provider.pending being public static. #4174
Closed
Jdance-Media
started this conversation in
Ideas
Replies: 2 comments
-
It never should have been public in the first place. Unfortunately, when I was younger I defaulted to making everything public without a good reason. The code I've written in the last few years has better distinction between what should be public for plugins vs default private or internal. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ah okay. Makes sense. Will avoid using Provider.pending and SteamPending then considering that it might be subject to change. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are several plugins out there that modify a character's appearance when they first join the server. There are currently two ways of going about this:
If the player can make a new SteamPending to modify properties like color, face, beard, and etc. then it seems pointless for those properties to be readonly, as it only creates a hassle for plugin developers and doesn't really totally prevent modifying them.
Beta Was this translation helpful? Give feedback.
All reactions