Settings and activity
173 results found
-
679 votes
PonPonTheDreambunny
supported this idea
·
-
17 votes
An error occurred while saving the comment PonPonTheDreambunny
supported this idea
·
-
21 votes
Hey!
This is a good suggestion thank you! This has been discussed a couple of times in the past. We can’t promise any ETA on such a feature but it would be interesting to investigate.
Our main concerns so far would be what can be included is random: should it have filters, should it be games on all platforms or only selected ones, all age ratings etc..
If you have more ideas or specifics that always helps, we’ll leave this ticket open meanwhile!
Thank you!PonPonTheDreambunny
supported this idea
·
-
28 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
Currently IGDB seems to rely on ISO 3166-1 for regions, which is an easy source to add all current regions, and then rely on ISO 3166-3 for historical region such as "East Germany [DDDE]".
But currently there's an issue where IGDB uses "NA" (Namibia) for North America, "AS" (American Samoa) for Asia and "WW" (unassigned, but not private use) for Worldwide. These three codes have to change, and I suggest using UN M49. You would then use code "003" for Northern America (excludes Central America and the Carribean), "142" for Asia and "001" for Worldwide. But I understand if this would be hard to change, and arguably Namibia and American Samoa aren't going to be relevant, and there's likely not going to be a country with the code WW anytime soon. However, still a good practice not misusing ISO 3166-1.
However, this should not cause any issues adding popular regions like Russia [RU], Sweden [SE], United Kingdom [GB], France [FR] and so on without any collissions. As of now, I'd like to add Swedish, German, Polish and Russian localisation with covers and titles.
An error occurred while saving the comment PonPonTheDreambunny
commented
Other regions that should be added is every single country, honestly. Because releases are different even within Europe, and this is also very useful when adding localised content such as titles and covers.
PonPonTheDreambunny
supported this idea
·
-
101 votesPonPonTheDreambunny
supported this idea
·
-
31 votes
Hey! We’re in the progress of making some updates to our search technology.
Stay tuned!
PonPonTheDreambunny
supported this idea
·
-
2 votesPonPonTheDreambunny
shared this idea
·
-
42 votesPonPonTheDreambunny
supported this idea
·
-
161 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
This issue only appears (or rather does not appear) on Android, while it works on iOS and the web.
In my situation, 50 % are on the web, 30 % are on Android, 20 % are on iOS. This means that 30 % are not receiving important messages.
PonPonTheDreambunny
supported this idea
·
-
6 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
@DraleZero you have a good point about having shorter cooldowns for when paying with bits. I already think there should be two options for cooldowns: global and per user (so you could have 1 min global but 5 min per user for better control).
But it would also be useful to have separate cooldown for bits as well, as you say. Easiest is to have a switch that says "Bits ignore limits" and bypasses the cooldown and limited number of usages. Otherwise having a switch that lets you override the values for bits, giving you a second set of values to fill out.
I assume that if you set 3 min points-cooldown and 1 min bits-cooldown, it doesn't matter if a viewer redeemed it with points or bits, since it should be 3 min since the last time that redeem was used in any way to be able to use points again.
Then on the screen where it counts down, have the counter placed above the button it's counting down for (and add the timer to mobile as well, and allow us to set seconds on custom redeems).
PonPonTheDreambunny
shared this idea
·
-
5 votesPonPonTheDreambunny
supported this idea
·
-
9 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
After looking into this, Twitch specifies cooldowns internally in seconds and allows you to specify any value of seconds (up to presumably 604 800 s) using API. Using for example Streamer.bot allows you to set the cooldown to 30 seconds (shows up as 0 minutes on Twitch Dashboard).
I have seen redeems that behaves unexpectedly if you redeem them around the same time. But the redeem only lasts for less than 5 seconds. So having the cooldown be 5 seconds would resolve this issue.
Summary: Twitch already supports seconds, and only need to add it to the UI.
PonPonTheDreambunny
supported this idea
·
-
9 votesPonPonTheDreambunny
supported this idea
·
-
82 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
With double the price of tier 2 compared to tier 1, logically we should have the same number of slots as for tier 1. This would encourage viewers to upgrade to tier 2 since they could get access to so many more emotes.
Encouraging more people to subscribe to tier 2 is also benificial to Twitch, since people start paying twice as much per month.
I have seen some few streamers going so far as to starting a second channel and running both side-by-side as a way to access more emotes. By instead by having more emotes on tier 2, it's easier for the streamer to just run one channel and for viewers to subscribe a single tier 2 instead of two tier 1s.
Tier 3 does cost 5 times more than tier 1, but having an additioal number equal to 3 times the slots of tier 1 might be a lot. But at least having the same number of slots is reasonable.
PonPonTheDreambunny
supported this idea
·
-
36 votesPonPonTheDreambunny
supported this idea
·
-
165 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
Since the web-version shows a countdown for cooldowns, Twitch might be unsure how to best implement this. One simple method is to display the longest timer out of the two (since there's a global and personal countdown).
This does mean that the timer could jump up in time if another user redeems it (5 min personal cooldown, 1 min global cooldown: when the personal timer is down to 30 s, and someone else redeems it, it will jump up to 1 min). But this already happens currently when someone redeems it and the timer shows up (going from 0 s to 1 min in cooldown).
Twitch could also have two different messages depending on if it's the personal countdown or global countdown.
An error occurred while saving the comment PonPonTheDreambunny
commented
Definitely needed.
Some redeems have long cooldowns just so a single user can't spam it. But the user can still redeem it whenever it comes available again, making it so other users don't get much of a chance to use it.
Having a longer cooldown per user and shorter global cooldown; there will be a moment where this user can't redeem it but other users can.
In my personal situation. I have it so users can pick my outfits and queue up outfits. One or few users like to queue up a long of outfits on their own. I don't have a cooldown on these redeems, but having a cooldown wouldn't even prevent this from happening. Only a cooldown per user would at least slow these users down.
I don't mind them doing it, but a cooldown per user would at least give other users a chance to insert their own requests inbetween.
PonPonTheDreambunny
supported this idea
·
-
12 votesPonPonTheDreambunny
supported this idea
·
-
4 votesPonPonTheDreambunny
supported this idea
·
-
7 votesPonPonTheDreambunny
supported this idea
·
-
20 votes
An error occurred while saving the comment PonPonTheDreambunny
commented
Some additional minor comment:
- Have it remember your last option in the dropdown for quicker redeems.
- Having the option to add icons for the dropdown (completely optional for the streamer) could make the dropdown easier to quickly select from.
- Dropdown with dividers by having a line with just a single -
- Dropdown with groups/headers by having a line start with a single -
- When using the grid of icons, having the option for how many icons it should display per row, will be very useful in certain situations.
- Also with the grid of icons, having blank rows resulting in empty slots, can help with organising the grid.
- In addition to icons there could be large images, useful for picking outfits for the streamer's model, with it being similar to in videogames when you pick outfits.PonPonTheDreambunny
shared this idea
·
I'd like to add that IGDB does support information regarding languages for audio, subtitles and interface.
However, these options can be a bit odd since it has "English" and "English (UK)". Having "English" be a general English works fine for audio when you have mixed accents, but considering "(UK)" it seems IGDB uses it to mean US English.
There's also "Spanish (Spain)" and "Spanish (Mexico)" specifically and not a more general "Spanish (Latin America)". It also has "Chinese (Simplified)" and "Chinese (Traditional)", and the same options appear for all three fields, so you can specify this for audio, which doesn't make much sense.
Languages available in Mini Metro not available on IGDB are: Bulgarian, Catalan, Welsh, Greek, English (US) [technically], Esperanto, Irish Gaelic, Croatian, Indonesian, Maori, Malay, Norwegian Nynorsk, Slovak, Serbian (Cyrillic), Serbian (Latin), Swedish (Finland), Tajik, Chinese (Traditional, Hong Kong)