Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better differentiate supported and unsupported apworlds #28

Open
Eijebong opened this issue Nov 21, 2024 · 1 comment
Open

Better differentiate supported and unsupported apworlds #28

Eijebong opened this issue Nov 21, 2024 · 1 comment

Comments

@Eijebong
Copy link
Owner

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.
@RePod
Copy link
Contributor

RePod commented Dec 6, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants