#binary-format #serialize-deserialize #network-protocol #serialization #codec #element #text-format

wg-toolkit

Toolkit for various binary and text formats distributed by Wargaming.net (BigWorld, Core engine)

6 releases

0.4.1 Apr 1, 2024
0.4.0 Mar 30, 2024
0.2.0 Oct 25, 2022
0.1.2 Feb 15, 2022

#201 in Games

Download history 9/week @ 2024-09-19 5/week @ 2024-09-26 2/week @ 2024-10-03

258 downloads per month
Used in wg-toolkit-cli

MIT license

305KB
6K SLoC

WG Toolkit

Toolkit crate providing various implementations for codecs distributed by Wargaming.net. These codecs are part of the Core engine (previously known as BigWorld) notably used by World of Tanks. This crate also provides an implementation of the network protocol.

Library

  • Crate page
  • Crate documentation
  • Packed XML codec
    • Deserialization
    • Serialization
  • Tank model codec
    • Deserialization of visual tree
    • Deserialization of vertices/indices
  • Compiled space codec (WIP)
    • Deserialization of some sections
      • BWTB (header table)
      • BWST (string table)
      • BWT2 (terrain2)
      • BWSG (static geometry)
      • BWCS (compiled space settings)
      • BWAL (asset list)
  • Resource virtual filesystem (read-only)
    • Package indexing
    • Reading file either from native filesystem or packages
    • Reading directory entries from native filesystem and packages
  • Network protocol (WIP)
    • Packets encoding and decoding (partial flags support)
    • Appending elements to bundles
    • Assemble received packet in bundles
    • Iterate elements in a bundle

CLI

  • Crate page
  • Packed XML
    • Deserialization and display
    • Value editing (string, integer, boolean, float)
  • Resource virtual filesystem
    • Read file content and copy it to stdout
    • Read directory content with possible configured recursion

WoT CLI

Not yet published, not yet working, but present in the code base, might be integrated to CLI at some point.

Contributing guidelines

When contributing to the code base, some rules should be followed:

  1. Each major feature should have its own directory module;
  2. Each side-feature, used internally by core features should be located under util module in its own file module.
  3. When working on a custom reader and/or writer, but only implement one of the two, please anticipate how your module would be built with both implemented;
  4. Catch all errors and forward them toward the public interface;
  5. Custom error types should all be defined using thiserror::Error derivation;
  6. When working on a custom reader and/or writer that doesn't provide lazy read/write operations, please make simple public functions that directly output, like from_reader(reader: impl Read) or to_writer(writer: impl Write).

Credits

Thanks to SkepticalFox for wot-space.bin-utils python library, which directly inspired this crate.

Thanks to SkaceKamen for wot-model-converter python library, for its open-source work on processed model file format.

Dependencies

~10–21MB
~302K SLoC