Megu Posted June 29, 2023 Group: Members Topic Count: 32 Topics Per Day: 0.01 Content Count: 46 Reputation: 1 Joined: 02/13/12 Last Seen: Yesterday at 03:12 AM Share Posted June 29, 2023 Can someone help me find this error? Quote Link to comment Share on other sites More sharing options...
0 Tokei Posted June 29, 2023 Group: Members Topic Count: 16 Topics Per Day: 0.00 Content Count: 695 Reputation: 721 Joined: 11/12/12 Last Seen: 9 hours ago Share Posted June 29, 2023 Well, the error itself isn't too helpful. 0x8b3 is clif_showscript. So one of the possible cause is a script sending "showscript" (a script command) to a player too many times, probably in an infinity loop would be my guess. Though, the error message only shows the last packet that exceeded the length of the connection buffer, so a prior packet could be responsible too. It's hard to know for sure. If the error is somewhat new, then you should know if this rings a bell or not. If you still can't figure it out, then you could dump the last packet in your console (in socket.cpp): ShowDump(s->wdata + s->wdata_size, len); ShowError("WFIFOSET: Maximum write buffer size for client connection %d exceeded, most likely caused by packet 0x%04x (len=%" PRIuPTR ", ip=%lu.%lu.%lu.%lu).\n", fd, WFIFOW(fd,0), len, CONVIP(s->client_addr)); Then you can see what the string used by showscript was and track down the issue a bit more easily. If nothing else, then you'd have to dump the entire write butter, but hopefully you won't have to do that. Goodluck! 1 Quote Link to comment Share on other sites More sharing options...
0 Megu Posted June 30, 2023 Group: Members Topic Count: 32 Topics Per Day: 0.01 Content Count: 46 Reputation: 1 Joined: 02/13/12 Last Seen: Yesterday at 03:12 AM Author Share Posted June 30, 2023 21 hours ago, Tokei said: Well, the error itself isn't too helpful. 0x8b3 is clif_showscript. So one of the possible cause is a script sending "showscript" (a script command) to a player too many times, probably in an infinity loop would be my guess. Though, the error message only shows the last packet that exceeded the length of the connection buffer, so a prior packet could be responsible too. It's hard to know for sure. If the error is somewhat new, then you should know if this rings a bell or not. If you still can't figure it out, then you could dump the last packet in your console (in socket.cpp): ShowDump(s->wdata + s->wdata_size, len); ShowError("WFIFOSET: Maximum write buffer size for client connection %d exceeded, most likely caused by packet 0x%04x (len=%" PRIuPTR ", ip=%lu.%lu.%lu.%lu).\n", fd, WFIFOW(fd,0), len, CONVIP(s->client_addr)); Then you can see what the string used by showscript was and track down the issue a bit more easily. If nothing else, then you'd have to dump the entire write butter, but hopefully you won't have to do that. Goodluck! Thank you for this found out the error and who causing the error my problem solve Quote Link to comment Share on other sites More sharing options...
0 Ph34r Posted January 26, 2024 Group: Members Topic Count: 1 Topics Per Day: 0.00 Content Count: 12 Reputation: 0 Joined: 08/16/17 Last Seen: December 24, 2024 Share Posted January 26, 2024 @Megu Hi, i am also facing the same error. Can you please elaborate what was causing it for you and how you fixed it please? Quote Link to comment Share on other sites More sharing options...
Question
Megu
Can someone help me find this error?
Link to comment
Share on other sites
3 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.