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

Etc.wz in GMS client file is not decoded correctly #215

Closed
wwj010 opened this issue Oct 6, 2022 · 5 comments
Closed

Etc.wz in GMS client file is not decoded correctly #215

wwj010 opened this issue Oct 6, 2022 · 5 comments

Comments

@wwj010
Copy link

wwj010 commented Oct 6, 2022

image
This shows up in GMS v236

@Kagamia
Copy link
Owner

Kagamia commented Oct 6, 2022

I don't have a GMS client, hope someone could provide a sample file to me :>

@Kagamia
Copy link
Owner

Kagamia commented Oct 7, 2022

Only occurs when WzVersionDetection is set to default.
image
As a workaround you can set it to fast.

The root cause is a little complicated, Wz_Image.TryDetectLuaEnc() method has some side effect, it will overwrite the crypto keys in Wz_Structure level, and finally cause the next Wz loading with a wrong crypto key.

@KENNYSOFT
Copy link
Contributor

image

KMS version is not affected. (I've loaded with WzVersionDetection = default)

You can refer:

@Kagamia
Copy link
Owner

Kagamia commented Oct 8, 2022

@KENNYSOFT cool! really helps.

@Kagamia
Copy link
Owner

Kagamia commented Oct 11, 2022

Reference from KENNYSOFT@e218685
Only store encType instead of entire Wz_Crypto for saving memory cost.

@Kagamia Kagamia closed this as completed Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants