Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outfits Changes Error [getBytel Not enough data to read a byte. Current position: 18, Length: 10. Called line 1692:43 in void ProtocolGame: :parseSet0utfit(NetworkMessage&) error #3155

Closed
2 of 5 tasks
otmexa opened this issue Nov 27, 2024 · 4 comments · Fixed by #3162
Labels
Priority: Low Minor impact Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@otmexa
Copy link

otmexa commented Nov 27, 2024

Priority

High

Area

  • Datapack
  • Source
  • Map
  • Other

What happened?

[getBytel Not enough data to read a byte. Current position: 18, Length: 10. Called line 1692:43 in void ProtocolGame: :parseSet0utfit(NetworkMessage&)
error

That error happens when you change your outfit in OTC. I marked it as high priority, because it even gave me a little lag, when there are byte problems, it makes the chars become somewhat slow.

I'm using clean install from last commit on ubuntu 22.04

In client 13, it does not send that error in the cons

What OS are you seeing the problem on?

Linux

Code of Conduct

  • I agree to follow this project's Code of Conduct
@otmexa otmexa added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Nov 27, 2024
@github-actions github-actions bot added Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing labels Nov 27, 2024
@kokekanon
Copy link
Contributor

V8?

@otmexa
Copy link
Author

otmexa commented Nov 27, 2024

V8?

It's true I forgot to mention.

@kokekanon
Copy link
Contributor

kokekanon commented Nov 27, 2024

try this:

789354a

is from pr 3061

@otmexa
Copy link
Author

otmexa commented Nov 27, 2024

try this:

789354a

is from pr 3061

Thank you very much, I will try it in a while and let you know if it worked, although I don't doubt that it will work since the error came from that line xD

I just tested it, and it works perfectly for otcv8 and client 13.40

@dudantas dudantas linked a pull request Dec 3, 2024 that will close this issue
8 tasks
@murilo09 murilo09 added Priority: Low Minor impact and removed Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing labels Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Minor impact Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants