#[EXPERIMENTAL] Origins feature works opposite than intended

1 messages · Page 1 of 1 (latest)

balmy kite
#

apologies if this is a little confusing, I'm not the best at explaining things (autism is a bitch) but i'll try my best, feel free to ask for elaboration.

Issue Description: Adding an origin to a set replaces all the emotes in that set as opposed to adding the emotes that are missing (i.e. "PogU" in Christmas set with Main set as an origin, both containing variants of the "PogU" emote, will display the "PogU" from the Main set as opposed to the christmas set.)

Where issue occurs

The Issue occurs on the website, when editing users emotes (explained further in recreation)

Recreation

  1. Create 2 sets, both of which contain an emote of the same name. (Which i will be referring to as Set1/Emote1 and Set2/Emote2 from here on) Also add another emote to Set1 (Emote3)

  2. Add Set1 as an origin to Set2

  3. Emote3 will be added to Set2 as intended, but also replaces Emote2 with Emote1.

  4. If Set2 is added as an origin to Set1 instead, it will replace Emote1 with Emote2 while still leaving Emote3. This is the work-around I have been using for the past week or so.

Note: As far as I am aware, the goal of the origins feature would be the following: adding Set1 as an orgin to Set2 would keep the emotes from Set2 and add emotes from Set1 where there are no name conflictions. The feature does the latter, but still replaces emotes where there are conflictions.

Expected Behavior

Set2 with Set1 as origin: https://i.imgur.com/N3t7acC.png

Set1 set with Set2 as origin: https://i.imgur.com/HroYxw3.png

Imgur
Imgur
grizzled jackal
#

The origin system is the way they decided to implement the ability to enable multiple emote sets at once. Currently, the origin sets take priority over the original set

#

That's what you're saying right? If so, that's intended

#

It's people can swap out identically-named emotes with seasonal/event variations, like for Christmas.

#

Then when the origin is disabled, the regular versions would be restored

#

This is one of the reasons I feared it would be confusing to people to implement it this way.

balmy kite
#

it might be a good idea to change the name & description of the feature because the way its currently layed out is a little confusing and i only figured out how to make it work by chance

grizzled jackal
#

I wanted it to be a re-orderable list, and it could just say somewhere that "higher sets take priority"

#

like Minecraft resource packs

balmy kite
#

thats not a bad idea

grizzled jackal
#

but how it currently is, the lower origins take priority

#

I tested it a little, so maybe it's actually based on something else

balmy kite
#

even while messing around with it while making this i encountered a couple things that confused me

#

i unfortunately dont remember what those couple things were but

#

yeah

grizzled jackal
#

Your problem can be solved by just enabling origins in the opposite order though, right?

#

i.e. your regular set + the seasonal origins

balmy kite
#

yeah

#

not that big of a deal

#

i just thought I'd report it to make it less confusing for other people lol

balmy kite
#

i'd also suggest origins be managed here rather than the profile itself

image.png
#

call it something like "override" idk