Rather than "normalize" seed codes to BCEX format (which causes issues
with delimiter usage in some scenarios), leave the seed code alone and
break its data out into fields that can/should be parsed instead.
Previously a character's command data could be a list or a dict
depending on if command randomization was on. This resulted in having to
inspect the object and determine its type in tools using the output.
This change guarantees character command data will be a dict of
name->description. The description is pulled from the COMMANDS section
of the spoiler log. If it doesn't exist (or the command is not present,
which should never happen), the description will simply be the command
name again.
- Tidy parse_MONSTERS and use a loop for all the sub-sections that use
the same logic rather than repeat the logic over and over.
- Docstring and type hint everything
- Use Pathlib for opening the log file
- Use `.values()` instead of `.items()` where I only want values
- Bump to 0.3
Apparently if you create a dict with pre-populated data, pyright infers
the dict's types for type checking purposes, and this can be wrong here
where my data dicts are massive sprawling affairs of dynamic info.
The right thing to do is probably turn this into a class, but for now
I'll just split the dicts pyright complains about up differently.
For now this just brings us to parity so a BCCE spoiler log will produce
the same JSON output as a BCEX log. More testing needed on how else BCCE
differs.
Due to inconsistent structure of spoiler logs, r- spells with "Equal
chance of any of the following" could end a line with a ':;". This just
find-and-replaces ':;' with ':' because that should never happen in
reality.
Rather than COMMANDS and its join to CHRACTERS['commands'] be a messy
cluster of \n, do some string parsing to make it look much cleaner and
more readable.
