Implement the mapper tool (extraction of geometry data from the client)

[alexrp]

https://github.com/tera-arise/arise/tree/master/src/tools/mapper

Lots of research to be done here still.

[alexrp]

Projects to look at for this effort:

• https://github.com/gildor2/UEViewer
• https://github.com/balannarcis96/skylake-tools
• https://github.com/VenoMKO/RealEditor

[foglio1024]

• https://github.com/Foglio1024/tera-map-importer

Depends on:

• Umodel
• GPK_Repack CLI (included)

EDIT: pushed updated wip code to: https://github.com/Foglio1024/tera-map-tools

[alexrp]

We would probably use this: https://github.com/ikpil/DotRecast

[alexrp]

Informally assigning @foglio1024 since he's doing some investigation into topology stuff in the leaked official server files.

[alexrp]

Following the reverse engineering of the geometry format used by the leaked official servers, I've converted that data to a custom format that's much more compact (4 GB -> 970 MB). It will be stored in the arise-geometry repository, which will be used as a shallow submodule in this repository.

This geometry data is for patch 100.02 so it is obviously out of sync with the client we're targeting (115.02), but it will get us started. The goal is still to extract the geometry from the client ourselves.

[alexrp]

The mapper tool can now take retail geometry/path data and convert it to our custom (and much more compact) formats.

The next step will be to integrate path data generation into the mapper tool so the only inputs are geometry files.

Then eventually we'll generate geometry from map files directly.