cRO Timeout on Account Server

[skyzhishui]

------------------ Openkore Issues Template ------------------

• Openkore version git: 1edc50f
• Server: cRO
• Bug Report / Feature Request:After the recent change in authentication methods, openkore has been unable to log into cRO. Currently, the account uses a mobile verification code login mode similar to SSO authentication.
• Summary: Connecting to Account Server... Connecting (acc.ro.zhaouc.com:6900)... connected Timeout on Account Server, reconnecting. Wait 34 seconds...

  Before the change in authentication method,cRO's charBlockSize has been changed from 155 to 175.

[skyzhishui]

After the first successful verification,I can use the cookies to maintain login status. Here is the cookie format I obtained: userData60={"appId":60,"accountId":"17xxxxxxxxxxxxxxxx0","token":"8**0","userName":"{your_phonenum}","avatar":"default.jpg","firstLogin":0,"realNameState":1} appId :may be a fixed value. accountId :the ID of the parent account. token:a 32-character string.

the API can be used to further obtain the information of the bound sub-accounts: childAccountId :the ID of the child account. childAccountToken :the ID of the primary account.

other parameters that may be fixed include: unionAppId=102020086 unionChannelId=102024001 gameServerId=9999

the result of capturing packets for login:

[cola111222]

Hello, can you help me with the verification and Poseidon issues? I have configured Poseidon, and the address I obtained is exactly the same as the one you provided. However, I am not sure how to start the RO client with Poseidon to implement the fake server functionality. Can you teach me how to do this? QQ: 414275974. Payment is possible, big brother.