You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in a room, to see if an apworld is supported or not, you have to look for them in the room's apworlds tables. Which isn't ideal to say the least. Let's find another way of differentiate them, merge all the support/unsupported tables together.
Questions:
How do we differentiate them? Color? Icon?
Changing the text color sounds like the easiest choice, it's quite unobtrusive but it's also very opaque for users. I also don't want to set the color for unsupported worlds to red as that would imply that they're bad.
An icon would be nice but we'd have to choose one. And I think that repeating the same icon 150 times on a page is kind of pointless.
In the case of a supported world using a non supported version?
Here the solution seems kinda obvious to me although it might be confusing for external people. We should decide if a world is supported or not based on the supported status of the chosen world per room. So if we play with a custom pokemon emerald version, it'll show as unsupported because it's not the apworld from the original release.
The text was updated successfully, but these errors were encountered:
Adding on to this, it may be worth having some way of presenting if a game needs a ROM to generate (MMBN3) and/or is procedural (Emerald). Will further help hosts drill down what to let through. This info may have to be crowd sourced.
Currently in a room, to see if an apworld is supported or not, you have to look for them in the room's apworlds tables. Which isn't ideal to say the least. Let's find another way of differentiate them, merge all the support/unsupported tables together.
Questions:
The text was updated successfully, but these errors were encountered: