Closed odisk777 closed 1 month ago
you solved it?
you solved it?
I have not been able to solve the problem. But I just found a developer has client 10 with spirit 13. I will investigate this week to compare and look for a solution. I was about to solve the issue but the magebot doesn't work for example in client 10 and in the servers with tfs base it works normally with the same client 10.
any solution?
any solution?
I have just discovered that the bug exists in both client 10 and OTC. The inventory is bugged for example go to where the monsters are and have mana potion and consume them and do not mark the consumption in the client after the second or simle mind stays at 100 and does not show empty of mana potion. until you give it many times and appears bugged. in the server log it showed a LUA with a problem when this happened, and I managed to fix it but the bug remains the same for both clients.
I have canary version 3.1.1 (november 2023) and I don't think this problem happens anyway I will try it. I will try to upload some gifs now
Hello everyone I discovered that the main problem of all this is in the inventory when using some position or something like that is bugged. this in the OTC, I guess in tibia client is completely closed because it does not allow this process. I was testing version 3.1.1 of canary and this error is not present!
https://github.com/opentibiabr/canary/assets/65802862/786f1023-a598-4fe7-b844-44d77734e563
There is a possible solution for the inventory with the OTCV8 client in Tibia client 10, which still presents problems causing the client to close. The temporary solution in the old client, as both mana potion and life potion, you must go to the line suggested below and delete it; it's a temporary fix that is "playable".
Potions.lua
LINE 95 - > container:addItem(potion.flask, 1)
Therefore, we still have protocol errors in the OTCV8 client that I'm not exactly sure what they are.
Error Log
ERROR: ProtocolGame parse message exception (327 bytes, 211 unread, last opcode is 0xb4 (180), prev opcode is 0xa0 (160)): InputMessage eof reached Packet has been saved to packet.log, you can use it to find what was wrong. (Protocol: 1100)
https://github.com/opentibiabr/canary/compare/main...odisk777:canary:patch-5?diff=split&w=
ERROR: ProtocolGame parse message exception (327 bytes, 211 unread, last opcode is 0xb4 (180), prev opcode is 0xa0 (160)): InputMessage eof reached
@odisk777 solved?
Priority
Medium
Area
What happened?
Hello everybody there is a bug in the OldProtocol when you use magic while attacking a monster the Client 10 closes. test image.
What OS are you seeing the problem on?
Linux, Windows
Code of Conduct