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
Standard current tag use intermixes tags into uniques, when tags aren't really uniques, whereas tags alone do nothing, while a uniques functional use being present is in creating modifiers.
The text was updated successfully, but these errors were encountered:
From a code perspective, I don't think this makes too much sense. Especially with the recent ability to use conditionals for tags, all tags functionally do function as uniques, even if they have no code behind. There's also at least one official unique (fresh water) that code wise is checked as if it were a tag, making the distinction that much more murky to me
Also, one advantage of the unique system is we can reduce the number of fields we need to work from with more flexibility on how everything works. Adding a new field for just tags seems odd with that as a goal
Before creating
Problem Description
Tags can be arbitrarily set as an ambiguous unique. Would it be more apparent if a tags field were introduced? Same behavior, specific field.
Related Issue Links
No response
Desired Solution
Alternative Approaches
As noted.
Additional Context
Standard current tag use intermixes tags into uniques, when tags aren't really uniques, whereas tags alone do nothing, while a uniques functional use being present is in creating modifiers.
The text was updated successfully, but these errors were encountered: