Pathfinder stopped searching the wrong frames. When a death came long after the mistake behind it — walking off a ledge and dying at the bottom — Pathfinder used to search the handful of frames right before the death, where nothing it pressed could possibly help, and burn attempt after attempt there. It now checks, frame by frame, whether pressing would change anything at all, skips the stretches where it wouldn’t, and looks back as far as the frame that actually decided the run. And when a fix only buys a few frames, it tries different versions of the press before it first, instead of settling for the cramped one. There’s a new Agency Map toggle in the Pathfinder tab too, which draws which frames an input could change while you play.

Editor playtests run at the right speed. With an FPS cap above 240, a playtest in the level editor ran fast — 1.5x at 360 FPS — because the game took a step on every drawn frame instead of only when one was due. Playtests also start clean now: the frame count, the macro’s position and any held jump are reset, and the editor’s song preview stops, instead of carrying over from whatever happened before. Thanks to the YouTube commenter who reported the editor timing.

Frame-window markers can’t go missing silently. A manual frame window on a macro without a recorded path got counted by the legend but never drew in the level. It now uses the position Calculate measured for that click, and the Frame Windows tab tells you if any click has no position to draw at. Thanks to the GitHub issue #4 reporter for sticking with this one.

Fixes a crash 1.7 introduced. Someone reported GucciBot simply giving up when entering a level, with no crash log to show for it. The overlay that draws frame-window markers hangs onto references to things inside the level, and it only let go of them on one specific kind of exit — so leaving a level any other way (finishing it and going straight to the menu, for instance) left it pointing at things that no longer existed. That was survivable before 1.7. The new legend reads one of those references every single frame, so 1.7 turned it into something you would actually hit.

Deleting a macro now deletes everything belonging to it. It used to remove a fixed set of companion files and leave the rest — backups in particular — sitting in the folder forever.

The checkpoint bug is fixed, and it was the big one. Pathfinder and the frame-window analyzer both depend on saving a checkpoint and replaying from it. Every checkpoint was storing the player’s position from one frame earlier than the frame it was filed under, so each time the bot restored one it quietly lost a frame of forward movement — and the error stacked with every restore. It only ever showed up in the X position, because that’s the one value that moves every single frame no matter what the player is doing, which is why it hid for so long. Found by comparing GucciBot’s checkpoint code against Silicate’s, after anticroom mentioned his Silicate port of the analyzer worked correctly. Both features now do what they always claimed to: Pathfinder solves a level end to end and its result holds up on a clean replay, and frame windows measure against checkpoints that actually match their own timestamps.

Pathfinder saves its own macros now, named after the level, instead of finishing silently and leaving you to press Playback and then Save to find out whether it worked.

The frame-window sound was late by a third of a second — not a timing bug, just 374ms of dead silence sitting at the front of the audio file before the “Brrr” actually starts. Trimmed. (The file also had seven seconds of silence on the end, so it went from 158KB to 11KB.)

A new “Default Look” toggle for the overlay, for people who’d rather not configure tiers: one plain ring per click, a fixed colour ramp from red for the tightest windows through to blue for the most forgiving, and the number to the left of the ring. Optional bell sounds instead of the Brrr. The legend was rebuilt to match, using Geometry Dash’s own font instead of a lookalike.

Two additions to a macro’s “...” menu: convert a macro saved under another theme’s extension over to .brrr, and run Calculate straight from there without loading the macro first.

Also: 1.6.5 shipped an update checker that crashed the game on launch. It’s gone, and the reason it broke turned out to point at the real cause of the file-picker crashes people reported in 1.6.4 and 1.6.5 too — two of Geode’s async systems being mixed in a way that doesn’t work. And the frame-window “strange sound” a few people reported was never broken: the default is Gucci Mane saying “Brrr”, the settings text just wrongly called it a chime.

Switched the main Claude model from Claude Sonnet 5 to Claude Opus 5 — the more powerful model.

A follow-up to 1.6.4’s file-picker crash fix, plus a new convenience. The fix: that first pass stopped clicking the same Import button twice in a row from crashing the game, but “Import Sounds/Images” and “Import Folder” sit right next to each other on the Frame Window settings page, and clicking one, then the other, wasn’t covered — a real sequence if the first click’s dialog opened behind the game window with no visible cue. Every file-picker button on that page (and trainer music import) now checks that none of the others are already waiting on a dialog before starting a new one. The new part: GucciBot checks for a newer release on launch now — nothing shows up if you’re current, but a popup with a direct link appears if you're not.

Two real crashes, both from community bug reports rather than Nigel’s own testing. Saving a macro under a custom theme wrote a filename with no extension at all, so it saved fine but silently vanished from every macro list on the next refresh — the theme-extension getter was dropping its leading dot. And clicking Import (sounds/images on the Frame Window, folder import, trainer music, or a custom theme’s audio) a second time before the first file-picker dialog closed could crash the game outright, since nothing stopped the second click from destroying the first pick while it was still waiting on the OS dialog. A real crash log (GitHub issue #1) made the second one possible to actually pin down instead of guess at.

A rename, not a feature. Nigel changed his GitHub username from guccimanefan to Nigelx1 and asked for the old handle dropped everywhere, not just on GitHub — the mod’s own id (nigelx1.guccibot, was guccimanefan.guccibot), the developer field, the in-game Credits tab, the README, and every mention on this site itself. Existing installs of the old id keep working as-is; grabbing this version means installing fresh under the new id rather than an in-place update, since Geode treats a changed id as a different mod.

Credits reconciled across about.md, the README, the in-game Credits tab, and this site — same people, same order everywhere now. GWDdoS was missing from two of those surfaces, Juice was accidentally credited twice here, kepe’s credit was dropped (no code taken, no personal involvement), ToastexGD’s credit now reflects that ToastyReplay is the actual foundation GucciBot started as, and Tech N9ne (Red Kingdom’s real inspiration) was added after being missed entirely. Also fixed two spots on this site that wrongly credited Nigel with writing the fake Gucci Mane quotes — both are Claude’s.

GucciBot’s first outside pull request, from anticroom: a 7-fix pass on Calculate’s frame-window accuracy. Input matching now checks action type, not just frame/player/holding. Shifting a press now carries its paired release along, so cube/ball/UFO taps keep their original hold duration during a probe shift instead of silently stretching it. Room and shift-bound calculations now check they’re comparing the same player and action stream. A valid-shift counter no longer keeps counting past a known survival gap, and the level-complete screen is suppressed while Calculate is running its own internal simulation. Also bumps the Geode SDK requirement to 5.10.1.

Frame-window analysis gained a third algorithm — Alignment-Independent, which re-tests the previous click’s own timing alongside this one instead of just the click itself — selectable right next to Time-Based and Recovery Range without touching either. A new “Circle Skin” marker style, and Megahack’s Practice Fix is now called out directly as heavily recommended before running Calculate. Three new themes — WakaBot, YoungstaBot, and KnockerzBot — plus Big Brrr tracks finally added for ToosiiBot, SexyyBot, and SaweetieBot, which never got one despite predating the feature. Autoclicker was reworked to match Silicate’s own model: Hold Ticks, Release Ticks, and Clicks Per Hold are now fully independent per player instead of one shared setting forced onto both, and the hitbox trail no longer redraws duplicate samples landing on the same pixel. Also: GucciBot now requires ToastyReplay Lite to be installed (it doesn’t need to be enabled) to run at all.

LemonadeBot’s Big Brrr track got swapped for the correct one — a download-tool mixup had bundled the wrong song entirely. Fixed.

A credits fix. 1.5 shipped Click Indicators — real scoring, matched Perfect / OK / Miss against the macro’s own click bar — without ever crediting where the idea actually started: Bogdaner09’s mod, which Nigel found and GucciBot built its own version around. Fixed.

Click Indicators got real scoring — every press and release you make against the macro’s own click bar gets matched and rated Perfect / OK / Miss, with the last timing delta shown live. The Jupiter My Favourite Trainer also picked up Video Mode: a full-screen review overlay that plays your own footage back riding the exact same click-bar clock as the macro, plus an alignment tool that scrubs the video directly to the first click instead of nudging an offset slider by hand. Improved frame window performance when using an external Practice Fix — native Practice Fix coming soon, hopefully. Five new themes joined the lineup — RomoBot, GrizzleyBot, Red Kingdom, LemonadeBot, and BrrrBot, the last with its own live snow overlay — and you can now build your own: full color palette, your own extension, your own quotes, even your own Big Brrr track.

Compact mode finally does what it’s named for — save, name, run Calculate, and pick a macro without leaving the corner panel. A death-mid-click recording bug that’s been reported (and mis-fixed) more than once finally got tracked down properly, using Juice’s own fix for it instead of guessing again. Rendering got real upgrades too: the FFmpeg setup that used to be an easy-to-miss manual step for every fresh install now just ships with the mod, frame-window cues actually make it into the output video, and there’s an optional 4-track split — combined, music, SFX, and frame-window cues on their own tracks. Also: SaweetieBot and MaybachBot joined the lineup, MaybachBot with its own Big Brrr track.