Note: This issue was the result of a misunderstanding of how the Origin feature worked, mainly because the use of the word "Origin" implies (to me) that the set being chosen in the Origin dropdown is the parent, and the set it's being added to is the child*. I discussed this at length with ansonx10 and we spitballed a number of alternative names for the feature. The most promising one we came up with was “Include other set”, which I think better describes the functionality and directionality.
*e.g., “I have a normal set called Default and a set of overrides called Halloween; I open the settings for Halloween and set Default as an origin, because Halloween is the child”. In reality, the opposite is true.
Below is the original text of the post.
Take an example channel which has a default emote set with 900 emotes. If a user creates a holiday emote set with 200 emotes that replace 200 emotes in the base set, the "Origin" feature behaves in an unexpected way. It appears that emotes from the origin always appear in the holiday emote set, even if the holiday emote set replaces them. As a result, using Origin here to create a full holiday set is impossible, because it would result in an emote set with a size of 1100. This is despite the fact that the actual number of usable emotes in the set is still only 900-- 700 emotes from the original default set and 200 from the holiday set.


style emotes…



