nerdsinspace / nocom-explanation Goto Github PK

Many people would like to see the source code of the exploit

.

Would it be possible to share the full Latex/PDF file of the probability calculations?

I don't quite understand how you efficiently look for differences between other particles to converge on the player. I thought of something, but I don't think it'd work. First, you get a hit. Second, you check 4 chunks cardinally adjacent to the original chunk, this should allow you to get a general idea of where the hit occurred in the render distance. Then, you generate your particles and wait. You then, informed by the render distance measurement, click all the chunks in the player's render distance before they moved. You then compare this to where the hits are in the square and then do this for each particle. I think I don't understand how anything actually works and this just feels wrong though so I've been wondering how a program can do this in an orderly fashion.

Thanks.

what exactly happened to it when it was locked? does it mean you can't access it from the launcher, or it can't join servers?

im pretty sure you can unlock it by linking it to a phone number or email or some shit idfk

"it's X = -245760 to X = +245759 on horizontal, and Z = -138240 to Z = -138239 on vertical"

For some reason I'm having a hard time believing that the heatmap is describing a 1-block wide 491,519-long area :)

hi guys how are you doing :)

What would happen if instead of break block packet you were to send place block packet?

please make a repo with the code, am interested and I am sure others are as well.

I dont even play on 2b, but it would be very cool for the community to be able to tour large bases you guys found while this exploit was being used.
I think noone cares about small stashes or houses, but as Fit showed, there where many big ones you found.
If this could compromise bases not yet blown up on the real server i can understand when you hold off doing this.

would love to see more render videos of some nice bases. obviously would have to be ones that have already been griefed, but it would be fun to see the before and after of some of the larger builds. would be a good way to monetize the data you have via youtube. just an idea.

could you abuse the ABORT_DESTROY_BLOCK packet like in antiantixray exploits?
example: https://github.com/cornos/Atomic/blob/e5393cb131db40024b51d5e5f2e73ddf2a91d080/src/main/java/me/zeroX150/atomic/feature/module/impl/exploit/AntiAntiXray.java#L76

How were you able to manage query performance and storage optimizations with the amount of data you were processing? I would assume it's a pretty big feat considering you have two terabytes worth of data in a single database. Did you host a managed database with DO, or did you provision a droplet with block storage and just manage your own installation?
Also, why didn't you use something like Kubernetes and make it truly scalable? Anyways, cool project.

apparently, if player is in queue, queue loads the chunk that the player logged off, so why dont we just track that shit also

I have a question. If nocom gets a response that a specific chunk is loaded, shouldn't it also mean that chanks surrounding it could also be loaded due to players render distance my guess is that you do scan around that area for all loaded chunks and then get the loaded chunk in the middle which should be the chunk where player is in right now, also spawn chunks should be always loaded so I don't know how nocom is able to track players inside the spawn area. My question is how is nocom able to find exact cords of the player inside the loaded chunks? Because from what I understand, it only checks if chunk is loaded or not, that information doesn't say where player is located inside the chunk.

can you use it with things like Cubic Chunks or other mods and have real time rendering system that would be better than Chunky or something. It would be interesting to see it not track player but use for rendering stuff. If this is not possible that is fine, but I think it would be cool. Also I don't want the code btw I just want to see if possible.

Issues being made of non issues is a pain, especially with GitHub discussions being a fully accessible thing now.