Skip to content
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

New OHOL update broke hetuw #33

Open
AngryNakedWeasel opened this issue May 21, 2023 · 11 comments
Open

New OHOL update broke hetuw #33

AngryNakedWeasel opened this issue May 21, 2023 · 11 comments

Comments

@AngryNakedWeasel
Copy link

AngryNakedWeasel commented May 21, 2023

New OHOL update broke hetuw.
20th of may 2023

@veykorax
Copy link

Yep, it is broken.

@Pleblu
Copy link

Pleblu commented May 23, 2023

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

@veykorax
Copy link

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
Copy link
Contributor

selb commented May 29, 2023

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
Copy link

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

@veykorax
Copy link

veykorax commented Jun 2, 2023

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
Copy link
Contributor

selb commented Jun 2, 2023

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
Copy link
Contributor

selb commented Jun 2, 2023

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

@AngryNakedWeasel
Copy link
Author

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

@Secretfolo154
Copy link

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
Copy link
Contributor

PXshadow commented Jun 5, 2023

risvh pushed a commit to risvh/OneLife-1 that referenced this issue May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants