Etc.wz in GMS client file is not decoded correctly
This shows up in GMS v236
I don't have a GMS client, hope someone could provide a sample file to me :>
Only occurs when WzVersionDetection is set to default.
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.

KMS version is not affected. (I've loaded with WzVersionDetection = default)
You can refer:
- KENNYSOFT@e21868553f9b6f50044def6a78b7b682f89e2045 for KENNYSOFT#73
- KENNYSOFT@74cdfadd1b3b6b90c2d8a723ba3278827e02181a for KENNYSOFT#74
@KENNYSOFT cool! really helps.
Reference from https://github.com/KENNYSOFT/WzComparerR2/commit/e21868553f9b6f50044def6a78b7b682f89e2045
Only store encType instead of entire Wz_Crypto for saving memory cost.