Hit list

[xackery]

• [x] fix help commands
• [ ] double read/write failures e.g. erudnext_chr
• [x] fix name padding ⁠🛠・client-side-modding⁠
• [x] although it loads fine but the string hash doesnt seem terminated properly. i needed to dig a bit to figure out the proper pattern for terminating the string hash, but i think i got it. pretty sure wlddoc already mentions the fact that it should be padded to a full dword so thats the first issue. and i think that the padding is supposed to be non-XOR'd null bytes. example of an original file that shows how the padding works (global_chr.wld): binary C5 (XOR to 00) = final string null terminator binary 00 (XOR to 2A) = non-xor'd null dword padding header field string-length reflects the dword padding (the decimal value is always divisble by 4)

[xackery]

bamzal — 08/08/2024 4:57 PM i think i pushed it too hard. erudnext_chr.s3d -> erudnext_chr.qail = everything working erudnext_chr.quail -> erudnext_chr_quail.s3d = everything working now i tried doing it to the same file that was just created in the previous step: erudnext_chr_quail.s3d -> erudnext_chr_quail.quail = lost meshops, and duplicated track instance erudnext_chr_quail.quail -> erudnext_chr_quail_quail.s3d = errors (likely due to issues above)

[xackery]

help image: