I see. In that case, I believe that I was getting confused by an inconsistency in the naming of item modifier functions? Because the `set_custom_data` function (which I had been attempting to use before trying a different route with `set_components`) merges into the custom_data component. Seeing this explanation, I can see this difference in behavior; The following item modifier will produce both the "some_custom_data" and "!some_custom_data" tags:
Perhaps something like having separate `set_...` and `merge_...` variants of both functions would be less confusing, but that seems more fitting for the Minecraft Suggestions page than a bug report.
I see. In that case, I believe that I was getting confused by an inconsistency in the naming of item modifier functions? Because the `set_custom_data` function (which I had been attempting to use before trying a different route with `set_components`) merges into the custom_data component. Seeing this explanation, I can see this difference in behavior; The following item modifier will produce both the "some_custom_data" and "!some_custom_data" tags:
Perhaps something like having separate `set_...` and `merge_...` variants of both functions would be less confusing, but that seems more fitting for the Minecraft Suggestions page than a bug report.
Thank you for the response!