wows-depack VS minimap_renderer

Someone from the data mining community actually mentioned your project after I posted some success in getting files read. I took a look at your reversing story and was super impressed with how much you were able to determine through black box analysis.

The name `` is intentional here. Decompilers (or at least uncompyle) relies on the function name to figure out what composition syntax the function is for (or a lambda, or generator). The python compiler emits ``, ``, ``, ``, and `` depending on the type of function. The obfuscator renamed this function of course and causes the decompiler choke on a whole file if this appears at a module level.

The game developers also reached out to me and others after seeing this post appear on the /r/WorldofWarships subreddit. They want to understand why we would need to introspect these files for mod creation or data mining.

I already explained some of this in the post, but at a mod level the API docs are _really_ bad and actually no longer existent since the developers migrated away from a standard forum to Discord for all comms and killed the forum. For ModAPIv2 which is heavily restricted to pre-approved mod developers there are no docs at all!

Additionally, they rely on a community-created tool for rendering replays to an MP4 for their tournament match recaps: https://github.com/WoWs-Builder-Team/minimap_renderer. The replay format is entirely undocumented and relies on data mined from this tool and other resources for parsing some data structures.

There are a _ton_ of community-developed resources that have only been made possible through reverse engineering of some shape that are critical for understanding the game.

The first two points are the big motivator for development of this utility. Applications like minimap_renderer depend on game assets and reading these assets isn't easily automated with today's tools.