#Use other's sets as origins
1 messages · Page 1 of 1 (latest)
I wanna bump this after discovering that removing the disabled attribute from the "Add origin" button exposes an API(?) Limit of 5 origins.
I started working with emote sets as origins to my own set, then friends wanted to use these sets so I found out that you have to make the person editor for your channel if they want to use yours.
It'd be great to make the origins more flexible in use:
• give a more reasonable origin limit to sets (like 10-20 or combined max. of the origins smaller than max slots)
• add a flag to sets to mark it public
• allow to share with URL
• add a url input in origin form to add public sets (maybe even search or a dedicated emote set main section)
• remove origin restriction of editor relation for public sets
• make origins recursive (do not allow cycles by either checking set ids for duplicates before adding the origin or not allowing public sets to have origins)
origins are not recursive
