ebbit1q

while admirable in effort, please don't bother linting and formatting the spoiler code, the spoiler code is full of quickly written hacks and should rather be given a do over...

I don't want to sound harsh, if you'd really like to improve the spoiler system we can talk on discord how to change the code over from the current hacks...

I think you're selling yourself short there tom, learning a scripting language like python that has ample documentation and tutorials available would be no harder than learning to use github's...

you can take it step by step, I'd be happy to help you

it does, we just have to do this at the start of every spoiler season

it clearly ignores changes not made by humans which makes sense

thank you for your suggestion, the guidelines you've copied are only relevant to the application itself however, which is written in C++, the spoiler automation is written in python.

none of the stuff that is left is relevant to python, python code is to be written according to the official python style guide https://peps.python.org/pep-0008/

this is a great idea and something I've been thinking about before, I always imagined it being something to add to oracle/the xml format instead of in the client itself...

it's kind of silly that this code will break in 2050 though, it probably by now has used 30% of the total expected life since it was written in 2011...