WebHost: Massive overhaul of options pages

[LegendaryLinux]

What is this fixing or adding?

This is a big one.

I have re-written player-options and weighted-options in Jinja, rather than generating it all in JavaScript. The pages are completely usable without JS now, though JS will provide some nice features.

What has been done:

• player-options and weighted-options are now created entirely in Jinja
• weighted-options is now a per-game page because 87MB of HTML is ridiculous and my 16-core system couldn't render the page in under fifteen seconds
• Interactive elements are hidden by a tag if JS is disabled. This does not prevent the user from accessing any options
  • The randomize buttons will not disable their respective inputs, but the toggle will still work without JS
  • The presets select is hidden
• All option types have been implemented
• Option groups have been implemented, and their divs are collapsible (no js required)
• Implement server-side generation of the YAML export
• Implement "generate single-player game"
• Load the user's previous settings from localStorage, and save settings when the form is submitted
• Implement option presets functionality on player-options
• Allow option groups to have a specified display order (implemented by @alwaysintreble)
• Changed the "Generate Game" button to read "Generate Single-Player Game" to reduce confusion experienced by new users

Out of scope, but I did it anyway

• Added support for option visibility in simple and complex pages, allowing devs to choose if options should appear nowhere, in player-options only, or on all options pages
• Updated supported-games page to include links to the "Advanced Options" pages
• Updated supported-games page to use details/summary tags for collapsible content
• weighted-options pages now share a theme with their other game pages

Important changes for world devs:

• The tooltip text rendering has been changed. It is no longer passed through JSON, and so takes its formatting more from the doc comment string now. You should look at your world pages and update the whitespace in your docs to make sure they look how you want.

How was this tested?

I tested this locally, and generated many, many YAML files.

If this makes graphical changes, please attach screenshots.

[LegendaryLinux]

in Rogue Legacy options for example, when loading the "Limited Potential" preset, the NamedRange of Progression Balancing is not setting to 0 correctly as defined in the preset.

Also the text shows as "disabled" near the range slider, but still exports a 50.

Also appears the preset name no longer outputs in the description YAML.

This has been fixed.

[LegendaryLinux]

So my preference is for either the automatic sort to be done only if valid_keys is unordered

@Zunawe, I know just enough Python to be dangerous. How would I accomplish this? My understanding is Lists are always unordered, or rather, they have the order they were defined with.

Edit:
Actually, I think I've got it:
{% for key in (option.valid_keys if option.valid_keys is ordered else option.valid_keys|sort) %}

[Zunawe]

Sorting looks good to me now. Thanks.

[hatkirby]

There seems to be something off with the way the option pages handle the width of the browser. I'm seeing a horizontal scrollbar on every game's options page, and there's nothing to the right (presumably it is just extra space that would be used to center the page).

[LegendaryLinux]

@ScipioWright I bumped the width of the option name column up a bit.
@hatkirby, Is that Firefox? I don't see that width issue in Chrome or Firefox.

[hatkirby]

Firefox 126.0 on Windows, at 1210px width.

[LegendaryLinux]

I found and fixed the issue by adding overflow-x: hidden to the html style for that page. It aligns properly and has no content over there. I have no clue what was causing it. The issue was not present on the weighted-options or landing pages.

[Ishigh1]

I tested this branch on my Stardew Valley Tilesanity branch that adds 30000 unique items and locations. With it, the option page just crashes after trying to load the options for every item and locations and taking all of my RAM.
It is an extreme example and I don't intend to merge my branch into core (for a while?) anyway, but I think it's good to keep in mind that this limits the amount of locations and items a world can have before its option page breaks
Well, maybe things could be solved by only loading the item/location option part on demand, if there is few enough items and locations, or maybe we'll never accept a world with that many items and locations into core, I don't know, but I thought this should be considered at least