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
In reference to your comment in #19, you mentioned about custom values in the config.yml file. For those who add in custom values, instead of having to re-add them upon an update, a separate file could be used (if available) for custom values. In it, if someone wants to unprotect an item, simply use "- -(item name)" where the "-" attached to the item name means to remove it from the protection list.
The text was updated successfully, but these errors were encountered:
But that would require editing the config.yml file, which this request is trying to prevent.
So you're saying that
- -BIRCH_BUTTON
Wouldn't work? What about "!BIRCH_BUTTON" where "!" means to negate (not protect) it?
I'm sure there's a way to do it that you would be able to make work, so it's more of the concept of being able to remove something from the default list without editing the default file.
In reference to your comment in #19, you mentioned about custom values in the config.yml file. For those who add in custom values, instead of having to re-add them upon an update, a separate file could be used (if available) for custom values. In it, if someone wants to unprotect an item, simply use "- -(item name)" where the "-" attached to the item name means to remove it from the protection list.
The text was updated successfully, but these errors were encountered: