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
This is partially in reference to #4, but is relevant to OCMFixer as a whole.
As OCMFixer has grown in size, it is now resetting a number of attributes and values which may or may not be relevant to a specific case. The issue here is that, for example, a server may want to reset max health on players while preserving their armor attributes. It is quite possible that artificially high armor values via attributes on players are an intentional feature of the server, and it would, therefore, be detrimental to reset those when only max health needs to be reset.
The best way to do this, I believe, would be to implement a jobs/task system, where each attribute to be reset/patch to be applied is a separate job, and then the jobs to be applied can be determined by the user at the time of running the command.
Three possibilities for this system would be a GUI where they can toggle checkboxes for the ones they want to run, with defaults pre-selected for them, a JSONMessage-based UI which does the same thing, or simple command parameters. For the command parameters option, it may also be beneficial to allow for attribute "groups", so that there could be a "default" group with the default jobs selected.
The text was updated successfully, but these errors were encountered:
This is partially in reference to #4, but is relevant to OCMFixer as a whole.
As OCMFixer has grown in size, it is now resetting a number of attributes and values which may or may not be relevant to a specific case. The issue here is that, for example, a server may want to reset max health on players while preserving their armor attributes. It is quite possible that artificially high armor values via attributes on players are an intentional feature of the server, and it would, therefore, be detrimental to reset those when only max health needs to be reset.
The best way to do this, I believe, would be to implement a jobs/task system, where each attribute to be reset/patch to be applied is a separate job, and then the jobs to be applied can be determined by the user at the time of running the command.
Three possibilities for this system would be a GUI where they can toggle checkboxes for the ones they want to run, with defaults pre-selected for them, a JSONMessage-based UI which does the same thing, or simple command parameters. For the command parameters option, it may also be beneficial to allow for attribute "groups", so that there could be a "default" group with the default jobs selected.
The text was updated successfully, but these errors were encountered: