Closed R3ZV closed 7 months ago
Issue fixed in 76b87f1
Changed from uint8_t to uint16_t
The bug was due to the fact that C++ treats unsigned char and uint8_t as the same type (i.g. value 68 is treated as char D). It doesn't behave like u8 in Rust which has u8 and char of different types.
Reading the JSON file doesn't result in any errors yet some of the fields are empty when printing the player's information to stdout not even defaulted to 0.