When we create a new emote, unlike the previous site, we stay inside the emote creation page and are not transferred to the created emote page. This makes us sometimes think that the emote is not made or that it is spam and is made several times. In addition to the fact that we do not go directly to the new emote page and we have to open profile for check the emote.
#Creating new emote
balmy pivot
If this is one of the new changes, please add a message to let us know when the emote is created, and the button to create an emote has a timeout of at least a few seconds (Ex. 5 seconds) to prevent the emote from being spammed by accident.
Because it doesn't show any message after the new emote is created.
- I use the web version on mobile
drowsy creek
This is wrong, you are being redirected to the created emote
balmy pivot
No, The first days when the new site was launched and the menu button and add emotes were working correctly for me, I created some emotes and every time it stayed in the emote creating page and was not transferred to the created emote page. I still have this problem
drowsy creek
Can you show a screenshot or video of it?
balmy pivot
Yep
balmy pivot
As you can see in the video, when I enter the site, the menu and add emote buttons do not work, when they work, for example, when I enter the add emote page, the exit button does not work. Or, when the menu is opened, the add emote button does not work, nor does it close the menu by clicking the menu button again.
To test whether the problem is with the internet or my browser or not, I finally entered the previous site and tested the buttons and their loading there.
Also, for adding emotes, I tried to add emotes in this video. But neither the emote was added, nor did it show me a confirmation message or a problem in confirming the creation of the emote. When I turned on the desktop mode to enlarge the screen in the add emotes section, it returned to the main screen and even my Twitch account was disconnected. (This has never happened before on the new site, I don't know what the reason could be. Maybe I refreshed the page too much or changed from mobile to desktop mode)