Add in Override/Hide on New Item and Edit Representation Menu
complete
N
Nicolas - Product Lead @ Decentraland Foundation
complete
Doki The team already implemented the fix! Now the Overrides configuration is saved when you edit a representation.
N
Nicolas - Product Lead @ Decentraland Foundation
in progress
The team will work on a fix to SAVE the Overrides configuration when you edit a representation.
Nicolas Earnshaw
Hey Doki
I'd like to ask you a couple of things, to have a little bit more context and implement this better
When uploading an emote, we include an extra step that takes you to through emote preview screen always. What would you think if we did that for wearables too? The up side is that creators can try out their overrides on an avatar there, and have a better idea of the effects of their settings. The down side is that this screen might be slower to load.
Would that be a good solution to the problem you encounter?
Do you add overrides on all categories of wearables? Or are there categories where they're never relevant?
Would encountering these settings only make sense if you select certain categories that are more common to use with overrides? (mainly head-related ones)
Thanks
Nico
Doki
Nicolas Earnshaw
Ok I like the sound of it!
I don't add overrides on ALL categories of wearables it depends from each wearable to each wearable. For instance, a lot of upper bodies hide lower bodies to make dresses etc. It all just depends on the creator.
Nicolas Earnshaw
under review
Thanks Doki, this looks like a good initiative to consider for the next cycle :D
Doki
Nicolas Earnshaw Thank you : ) Hope it can be considered!
N
Nicolas - Product Lead @ Decentraland Foundation
Doki
Hi Doki, the team will work on a fix to SAVE the Overrides configuration when you edit a representation.
So, the first time you want to change the Overrides, you still have to go to the Wearable Preview. But, if you edit the representation, the previous Override configuration will be saved, so you don't need to go to the Wearable Preview again :)
Will that be good enough? I'm hesitant about adding the option to the main flow when you first create a Wearable, as it is not a mandatory step to Publish the Collection, and it is not used for all wearables.
Thank you for your feedback!
Doki
Nicolas - Product Lead @ Decentraland Foundation
That sounds a lot less complicated!
Doki
The amount of times I change out my wearables is a LOT. When testing, we're constantly re-uploading the files and seeing if there's changes.
When we have files that contain hide/overrides, we often have to re-apply them in the properties menu whereas it would be helpful if it could retain the information like all the other slots do (name/rarity etc).
This also helps for when we are testing in world as we need to be on a Testing Network but if we're making a change in the builder to the properties menu then we need to switch to Ethereum and then change back to the Testing Network and refresh the testing world tab. With the override/hide already being on the edit representation menu, we wouldn't have to switch back and forth between networks to re-apply the hides/overrides and would only need to refresh the testing world tab.