NetStack VS FixedMath.Net

Yeah I've used https://github.com/nxrighthere/NetStack for networking serialization, it's slick and what I'd use if it were multiplayer, I almost started implementing it here but after just compressing it was good enough for this project.

There are some nice libraries out there for compression of values: https://github.com/nxrighthere/NetStack for example does the quaternion compression for you.

I was using Unity and the libraries from Photon TrueSync (discontinued network solution). It was using this fixed point math libary - FixedMath.NET. This one has a lot of safety checks though in simple operations that makes calculations really really slow, so I changed the implementation of the fixed point number type a bit to be faster, along with some drawbacks. I probably don't recommend to use that one for a game, but what TrueSync provided was a good starting point for me. Code performance seemed rough to handle in general - even with the number type performance improvements (considering you have to be able to run several update cycles per frame). the fixed point number here uses a 64 bit integer under the hood. Some other people I talked to said that they would inline the code for calculations so instead of your custom number type, you directly work on the 64 bit integers to avoid the minor allocation cost of your custom number type. I only have some custom circle to circle collision checks for hitbox-hurtbox overlap detection and 2d physics raycasts for a relatively light simulation. Games like street fighter only have axis aligned bounding box collision checks - which should be by far the simplest way to check for hitbox-hurtbox overlap. And they have no physics since all environments are just a flat plane. This would be really easy calculation wise.