-
Notifications
You must be signed in to change notification settings - Fork 75
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
No name found for packet #178
Comments
quarry protocol but 💀 is it a ur code problem, or just when starting, if so role back to previous ver |
I tried to use https://github.com/LiveOverflow/minecraft-hacked just to try out quarry, so I didn't make the code myself. I also tried quarry examples but to no avail. I used the latest quarry at first, then downgraded it to the version where they added 1.18.2 but that fixed nothing. The error also randomly occurs repeatedly, so it's not only at the start |
have you tryed uninstalling it and reinstalling, and can I see your code |
The code is literally the same exact code from the repository I linked, and in order to downgrade quarry, I had to uninstall it and install a older version which is literally uninstalling and reinstalling |
heres the code tho if u dont wanna go to the repo
|
I am having the same issue, I have used the same code but it also happens with the example code for proxy-hide-chat |
I keep getting this error:
Traceback (most recent call last): File "C:\Users\****\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\quarry\net\protocol.py", line 241, in data_received name = self.get_packet_name(buff.unpack_varint()) File "C:\Users\****\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\quarry\net\protocol.py", line 207, in get_packet_name raise ProtocolError("No name known for packet: %s" % (key,)) quarry.net.protocol.ProtocolError: No name known for packet: (760, 'init', 'upstream', 79)
I get this every single time I try to use quarry as a proxy, and for some reason quarry never picks up on any of the other packets and doesn't call my callbacks
(this is on 1.18.2 if it's important)
The text was updated successfully, but these errors were encountered: