Repository navigation
Fixed
The bulking phase is read correctly at any display scaling.
If your Windows scaling was anything other than 100%, the macro looked in the
wrong place for the phase badge and usually found nothing.
Eating to a phase target no longer runs past its stop.
Same cause. "Eat until Bulking Phase 25" could never stop if the phase could not
be read.
Starting a second session no longer continues the first one.
If you stopped a run and started another on the same exercise, the macro treated
it as the same session still going. Your elapsed time, reps and sets carried
over instead of resetting.
Switching lift mode mid-run no longer breaks your stats.
Strength and Hypertrophy get different weights from the game. The macro kept the
old mode's weight as the baseline, so switching to the lighter one counted as
losing weight: gain went negative, kg/hr went negative.
Hypertrophy no longer wastes the last rep.
A set could stop with a full rep's worth of stamina still on the bar. The macro
now knows what a rep actually costs instead of relying only on a running average
that drifted as you got stronger.
A stalled set leaves instead of ending the run.
If the last rep turns out to be unaffordable, that is a finished set. It now leaves
after a couple of seconds. A set that never manages a rep at all still stops and warns.
The weight is read correctly when its digits touch.
At weights like 410 kg the 4 and the 1 run into each other with no gap
between them and the reader could not tell them apart.
Lifting straight after a shaker works.
The shaker was never put away, so its menu stayed open and the game gave that
menu priority over the machine prompt. Meaning that the navigation went into the
shaker interface instead and failed the whole set.
Your lifetime stats and personal bests can no longer vanish.
If saving failed the macro said nothing. It now tells you in the panel's top bar and
writes the reason to the log and it will never write a damaged stats file that
later looks like it was tampered with.
Stamina shows up as soon as the game does.
The readout used to sit blank until you first pressed F8. The macro measures the
HUD as soon as it finds Roblox, so the bar is live straight away. If it cannot
measure yet it keeps quietly trying and fills in when it can.
A blocked phase or weight reader now says so.
The menu and lifting readers already fell back to timings and told you when they
gave up. The phase and weight readers did not: if something covered them they
failed forever in silence and the numbers just stopped moving.
A reader that gives up now switches itself back on.
Previously when a reader failed, it stayed off for the rest of the session.
If a video window covered the stamina bar for a minute, you ran on fixed timings
even if you moved the video. The macro now retries between sets, so a reader comes
straight back once whatever was covering it moves.
It will never switch on a reader you turned off yourself.
Only readers that were on and failed on their own are eligible.
Ctrl+Shift+F brings the panel back when it is minimized.
The panel redraws less.
The UI was redrawing itself up to seven times a second whether or not anything had
changed. Nothing looks different; it just stops doing work for no reason.
Changed
The eating report no longer claims how many chickens you ate.
Nothing on screen confirms a chicken was consumed yet. The post now carries
what was actually bought, the phase you started at and the phase you
finished at. If eating carried you past your target phase, it will tell you.
That is normal since the macro finishes the chicken it already bought which
can sometimes cross over the wanted Phase by one.
The macro just reports it but doesn't flag it as a problem.
Added
Reader health in the Discord reports.
Every progress and session-end post now says which readers are running, which
you switched off, and which gave up on their own and why. A reader falling back
posts once when it happens and that is easy to miss in a busy channel; this way
the state is in front of you every time the numbers are.
A "Mode switched" post.
When you switch lift mode mid-run, the mode you are leaving gets its numbers
posted before they are cleared, so nothing is lost.
Known issues
The weight is read at a set position for100% display scaling.
This means that the weight reader at other display scaling might not work as intended.
I measured all the menus for 100%, 125%, 150% and 175% manually on
1920x1080, 1440x900 and 800x600. That's 12 measurements down to the pixel
for 7 different things the macro keeps track on. I'm sorry if there are mistakes.
If your Windows scale is above 100%, you may see
"WEIGHT PANEL fell back to timings".
This changes nothing about the macro itself, it will just fail to record
personal bests and the kg/hr figure, so a session continues normally without it.
If the messages bother you, switch the weight reader off under
Settings -> Readers and it stops.
Notes
- If you run at non-100% scaling, this is the release where phase reading starts
working. Worth confirming your phase shows correctly in the panel. - If you had turned the phase reader off because it never worked, turn it back
on.
Internal
Not player-facing, listed for completeness:
- Twelve unused constants removed from the tunables section. Three were dead
duplicates of values that actually live elsewhere. - The
Ctrl+Shift+Dself-test reported the weight region from its own unscaled
copy of the coordinates while the engine read a scaled one. It now reports
exactly what the engine reads. - The weight reader was checked against the largest weight the game currently
allows, 10000 kg. #Warnenabled, routed to the debugger rather than a message box since a warning
could steal focus from Roblox and kill a run.- The digit split threshold now scales with the HUD, like every other pixel
measurement. - Documentation corrected in several places where it described behavior the
code did not have, including a static checker that was never written.