Closed daniofordon closed 2 months ago
Can you test now with the latest updates?
error invalid thing type client id 0 in category 4
Can you test now with the latest updates?
error invalid thing type client id 0 in category 4
I can confirm, using TFS master, for protocol 13.10. (once the world ports are set to correct port and I get a character list), can't login.
Turns out there were only a few adjustments necessary to make this work for 13.10. Here are those adjustments
fixed?
yesterday I tried it , works in release 3.5 .( to make pr of feat: highscore) no packet error
but in the main repo there is a packets error when logging in.
ERROR: ProtocolGame parse message exception (4934 bytes, 4743 unread, last opcode is 0x03 (3), prev opcode is 0xa1 (161)): unhandled opcode 3
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1310)
according to the tfs console, the player logs in, but in the client it does not log in.
error invalid thing type client id 0 in category 4
try with httpPort = 80 in tfs config
no work
void ProtocolGame::parseItemClasses(const InputMessagePtr& msg)
GameForgeConvergence https://github.com/mehah/otclient/pull/789/files
I can login with those changes from your pr I don't know what forge is ( im player 8.6 jaja). check if there is a conflict in 13.32.
now there is a problem with items you can up in inventory if you have them in your inventory or if they are on the ground.
player named "koke" had one item in the inventory. player "sample" had nothing.
ERROR: ProtocolGame parse message exception (5156 bytes, 1326 unread, last opcode is 0x00 (0), prev opcode is 0x78 (120)): unhandled opcode 0
Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1310)
Priority
Low
Area
What happened?
TFS 13.10 Login Console Error
https://prnt.sc/l_pDV4QJCUgE
What OS are you seeing the problem on?
Windows
Code of Conduct