Jaka Kranjc

Nice work! I only noticed a blog/blob typo, but have no comments on the architecture. Is there any reason we wouldn't use the same implementation for the existing users, as...

Thanks!

This will likely be a "wontfix", since I imagine the code is littered with assumptions that items with attachments can't be stacked.

Or it was a design decision, it's impossible to say. I don't think we should do anything about it, this is clearly mod territory.

Sounds like memory corruption then, not really related to the sound, perhaps not even the detector. But that's hard for you to debug, since it requires something like valgrind or...

Something like this might have been useful 15 years ago, but now that almost everything is already written, I don't see anyone gaining anything by rewriting all the parsers, writing...

Depends on what everything you'd stick in it. Eg. if you want to make the file formats machine readable, that's great and wouldn't need to affect deployment, since jekyll has...

I don't know what you mean, since the opcodes are already easily machine readable. Everything is parametrized and the description is plain html most of the time (a few liquid...

The notes are sometimes interspersed in the description, not always at the end. And there can be several of different severities, so the proposed format is not good enough. I...

Links: opcodes link to each other via anchors, so you'd end up with broken links unless you replicated the naming and therefore layout (all in one file). Actions and triggers...