-
Notifications
You must be signed in to change notification settings - Fork 42
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
Release code just for fun cuz its patched anyways #9
Comments
Don't be a script kiddie write your own code. |
Write my own code ? I do not want to. I would simply like to see how They did it, and how They chose to go about it. It has nothing to do with being a "script kiddie" or stealing their code. |
They will probably release more stuff related to nocom in the future which may include some parts of the code. I don't think they will release the whole thing. |
The exploit seems to be only patched in 2b2t. It does perfectly work on any other 1.12.2 paper server (and maybe in newer versions). |
I just want to know how you are able to "click" blocks outside of render distance. As in click do you mean somehow send packets outside of your render distance ? or literal clicking... |
You just tell the server that you do lol. CPacketPlayerDigging. Just lie about the position that you're clicking. |
holy crap so its just that easy ? |
Yes literally. I will leak nocom source code now:
it can be any action it doesnt matter |
so ur telling me u could literally just put blockPosToCheck to 10m blocks out and check if its loaded or not depending whether or not the server sends back a response?? lol |
yeah lol, and on top of that, the response that the server gives you is the block at the coordinate you asked about so you either get a "yea that's cobblestone" or you get silence, no reply (meaning chunk is unloaded). |
please make a repo with the code, am interested and I am sure others are as well.
The text was updated successfully, but these errors were encountered: