xxxgugaxx Posted July 20, 2024 Posted July 20, 2024 We are loaking for a developer to help us to fix critical error. Some times we have a massive crash critical error. At bosses with pvp , some times 1x1 or just stop at city too.. Base l2jmobius ( @Mobius ). Protocol 447 . We can pay with binance 1 Quote
0 Tryskell Posted August 17, 2024 Posted August 17, 2024 I definitively don't know this protocol, and I doubt that error can happen on IL chronicle, but I would check what the error says ; whatever StatusUpdate packet, involving name/title changing. It looks like it can't properly format a string, so probably using invalid characters to do so. I would verify alphanumerical checks or at least enforce it to that only, on all associated packets. It's enough someone craft a packet with invalid characters, and the associated packet can't compute it to crash your client. Back on IL, some similar behaviors server-side sending 0 as runspeed. If your NPC had 0 runspeed, packet was crashing all clients involving the NpcInfo packet call. You had to manually delete the NPC spawn from SQL to avoid the faulty NpcInfo to be sent. In your case, it looks more like a StatusUpdate, at least that's what it says. Quote
0 Mobius Posted October 6, 2024 Posted October 6, 2024 Protocol 447? Pretty much non private or leaked files. Of course you will come to maxcheaters asking for support. Quote
Question
xxxgugaxx
We are loaking for a developer to help us to fix critical error.
Some times we have a massive crash critical error. At bosses with pvp , some times 1x1 or just stop at city too..
Base l2jmobius ( @Mobius ). Protocol 447 . We can pay with binance
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.