1.7 protocol error 60 on join

[ArranTuna]

Describe the bug

I tested newest 1.7 64 bit server (mtasa_x64-1.7-untested-26530-20260415) and I got protocol error 60 when joining the server (tried with the newest nightly (mtasa-1.7-untested-26546-20260419) and a matching nightly (mtasa-1.7-untested-26530-20260415) both fail.

I then tried with no resources, and it works fine, started starting resources to see which causes it and it seems that if in-game when starting, you don't get the error, I reconnected and got the error.

I then tried constantly reconnecting to see when I'd start get protocol error during resource starts. When I got the error, I stopped the starting of more resources, started stopping recently started resources, still couldn't join despite stopping all the resources that had been started since my last successful join, so I've no idea.

Steps to reproduce

Unknown, if any devs would benefit from joining the server to get the protocol error I can tell you the IP/port/password.

Version

Client: v1.7-untested-26530
Server: v1.7-untested-26530 64 bit windows (also tested 32 bit and same error)

Additional context

Relevant log output

Security Policy

• I have read and understood the Security Policy and this issue is not security related.

[FileEX]

I was unable to reproduce this issue. I pulled the latest resources and built debug, nightly, and release versions, and did not encounter any protocol errors with the default resources on a local server.

[Lpsd]

I am pretty sure it's something related to bitstream and usage of specific functions/parameters but we just haven't tracked it down yet.

@ArranTuna if it is possible to narrow it down to a single resource that would be great -- otherwise we'll keep searching

[ArranTuna]

It's a certain resource or resources that cause it, which I couldn't narrow down. I can send you the server details so you can join and get the error yourselves?

[ArranTuna]

The oldest available server build works, so I'm going to trial and improvement to get the exact build it starts in,

[ArranTuna]

I've narrowed it down to mtasa_x64-1.7-untested-26183-20260205.exe

Also I noticed that, that's the build where you see these corrupted strings:

• Connected! [W = J1' ~ L 1S ]

Some notes from my trials:

exe mtasa_x64-1.7-untested-26183-20260205.exe 6.75MB 2 months old. BAD on double check: managed one login, reconnected and bad again.
exe mtasa_x64-1.7-untested-26141-20260123.exe 6.74MB 2 months old. GOOD but first connection resulted in connection lost
exe mtasa_x64-1.7-untested-26129-20260122.exe 6.74MB 2 months old. GOOD
exe mtasa_x64-1.7-untested-26127-20260121.exe 6.74MB 2 months old. GOOD but first connection resulted in connection lost

[ArranTuna]

NanoBob suggested I look for setPedAnimation calls and it turns out setPedAnimation on a ped is causing this, he says he's working on a fix for it.

[FileEX]

Maybe #4821 fixes it