-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vicky 3 dates parsed wrong #15
Comments
Ah, the heuristic if a date is present fails on Thanks for the report, I'll push out a fix in a couple hours. |
I cut v0.4.6, which should have this fix in there (needs a few more mins to show up in github releases). Let me know how it goes 😄 I don't think it's perfect yet, as there are some game state models that have a slightly different fixed / floating point encoding than others (like the EU4 spoiled me with consistent 32bit and 64bit fixed / floating point encoding |
Awesome thank you, will let you know when I do the next edit round for our mp game. To go by what is fixed/floating point, you can use as a rule of thumb that if it is something that needs to be synced over the network it will be fixed point (i.e anything that affects gameplay), if it is cached values for the interface etc it will be a floating point |
When trying to parse a vicky 3 save it will fail to parse the dates. It turns the date string into an int causing the save to be loaded wrong. For an example melt a vicky 3 file and check admirals/generals
cooldown_repair_date
value.The text was updated successfully, but these errors were encountered: