warframe-items VS Warframe-OCR

It's okay if you don't have a exported file, at least now i have a chance to get a full file, game has so much stuff to level, it's nuts. I think that this tool (wf-foundry) is safe of inconsistencies because every new item and resource is automatically pulled from this repository which is supported by Warframe Community Devs (it's on the readme.md), so theres that

The API used by the mobile app is public (https://github.com/WFCD/warframe-items/issues/91), and the sorties file contains all the individual prestige ranks, all 60 of them.

If you're looking to match the set that they can be found in, you can find them in our data archive on on the corresponding api

That was already a known thing back in February, if you knew where to look. The api used by the mobile app is public (https://github.com/WFCD/warframe-items/issues/91), and contains all the nightwave ranks, including the 60 prestige ranks.

For this intermission, last time I checked the max rank was 90 (prestige 60). There's a public API that the mobile app uses, and that contains all the ranks. Meanwhile, the worldstate API has an end date of July 19th (this is not the official end date, this is a placeholder). You can reach rank 104 by July 19th, so the cap being at 90 makes sense.

Source is the mobile export their app uses, as usual. You can find the same stuff on the WFCD warframe-items repo or my warframe-data.

Yes, you can link them statically. Here's a Python script I wrote to install and build a Python module in Rust. It will install the required development libraries on Linux and build a static build of tesseract on Windows (it also downloads the LLVM based clang compiler, I forgot why). Then it set up two environment variables VCPKG_ROOT to discover the tesseract library and RUSTFLAGS -Ctarget-feature=+crt-static (this forces the vpkg crate to link tesseract:x64-windows-static and not the dynamic version).

Tesseract is slow but not too slow. I wrote a multi-threaded wrapper around the Rust bindings und a Python wrapper around that. Granted it is not very polished and I apparently forgot to make the Rust repository public but it works. The previous version of the project for which I made this wrote the image to disk and called the tesseract binary which took half a minute for a few of images. Definitely not usable for real-time processing. Now it takes around 200-300 ms with 12 worker threads. I'm not sure if there is further potential to make it faster though.

I don't like maturin workflow either because it installs directly to the python environment. This is not very useful during development. I wrote a module import file which loads the python module from the shared library. You could easily invoke cargo before importing the module (remember to delete the previous shared library file) to have a fully automated development processes.