New OHOL update broke hetuw

[AngryNakedWeasel]

New OHOL update broke hetuw.
20th of may 2023

[veykorax]

Yep, it is broken.

[Pleblu]

Any alternatives that work? I don't think anyone expected an update lol

[veykorax]

Any alternatives that work? I don't think anyone expected an update lol

Nope. You can try to somehow implement the code into the game files (somehow) so you dont have to run a separate EXE file

[selb]

Current hetuw works fine, but you have to do one of two things:

• Update the base game (whether by Steam or download), and use the hetuw exe with the updated game files
• If that doesn't work for some reason, change the content of the dataVersionNumber.txt file to 370 to hack around having old data files

[Secretfolo154]

I did the first, and when I opened up the dataVersionNumber.txt it was already set to 370. Does not work for me.

[veykorax]

I did the first, and when I opened up the dataVersionNumber.txt it was already set to 370. Does not work for me.

Same thing here!

[selb]

It looks like you need to bump it to 372, not 370, to use the existing hetuw exe. Sorry about that. (370 is the correct current data version, but bumping to 372 causes the client to self-identify as client version 372. It is the client version check that is failing, not the data version one as I had assumed.)

[selb]

(though by the time you read this it may be 373!)

[AngryNakedWeasel]

It got fixed with the Weekly Update #123. dataVersionNumber.txt value is at the correct value now. (thank you selb)

[Secretfolo154]

It looks like you need to bump it to 372, not 370, to use the existing hetuw exe. Sorry about that. (370 is the correct current data version, but bumping to 372 causes the client to self-identify as client version 372. It is the client version check that is failing, not the data version one as I had assumed.)

MVP right here ty. Fixed it for me.

[PXshadow]

https://github.com/hetuw/OneLife/releases/tag/OneLife_v372