Commits on Sep 13, 2026
-
Backtrack, bow aimbot with lead, sprint reset, hitbox expander
…
Backtrack: a second injected netty handler (lodestone/Backtrack) spliced before packet_handler that holds the current target's movement packets for a bounded delay and re-fires them on the same event loop. The server rewinds the target to where your latency says you last saw it when validating a hit, so hitting the delayed position still lands as long as the delay stays inside that rewind window. Only the target's movement is held; everything else passes instantly. Entity id per packet is resolved reflectively once per class and cached. Bow aimbot: solves the launch angle by simulating the arrow — power*3 initial speed, 0.05 gravity, 0.99 drag per tick — and leads the target by its own velocity, converging flight time and lead together. Aims only; the release is still yours. Sprint reset: stops and restarts sprint around an aura swing so the hit lands on a sprint (re)start and takes the knockback bonus. Off when criticals is on, since a crit needs no sprint. Hitbox: expands the target box outward by a configurable margin for selection and aim, within the reach tolerance the server already allows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lodestone committed 1 day ago -
Force-send position so witness-dependent moves reach the server
…
Criticals, and any move the server has to see to credit, only worked on the tick's own position send — and not at all while Blink held those sends back. World.flush_position builds a ServerboundMovePlayerPacket.PosRot and sends it through the client's own ClientPacketListener.send, then updates xLast/yLast/ zLast so the client agrees a packet went out. Criticals now flushes the leaving-ground position on the hop, so the server registers off-ground-and- descending at the moment it matters regardless of Blink. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lodestone committed 1 day ago
Commits on Sep 11, 2026
-
Lodestone client: injected in-game menu driven through JNI
…
The project gains a second half. The external explorer stays (and is how every name below was verified against the running game), but the cheat menu now runs inside Minecraft: - inject a DLL, hook glfwSwapBuffers, draw egui in the game's own GL context - drive the game through JNI rather than raw memory, so writes go through the GC's barriers and methods can be called directly - five draggable windows: Combat, Movement, ESP, Visuals, Misc - client-side only: nothing depends on owning the server Modules wired to the game: fly (vanilla/smooth/glide/teleport), speed (abilities/velocity), no-fall, jetpack, auto-sprint, noclip, step, high jump, jesus, spider, freecam; kill aura, aimbot (camera/silent, smoothed), trigger bot, reach, auto clicker with jitter, anti-knockback, criticals; entity ESP with boxes, tracers, nametags and health bars; fullbright, custom FOV, no hurt camera, no weather, no view bob; hide-from-capture. Per-module keybinds, a panic key, and settings saved to disk. GL state the game leaves behind has to be neutralised before drawing and put back after: a sampler object on unit 0 renders everything black, and a stale GL_UNPACK_ROW_LENGTH scrambles the font atlas. Unload unhooks and goes inert rather than unmapping the module, which crashed the game while the window still pointed at our window procedure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
lodestone committed 3 days ago
NewerOlder