These are not preferences. Get them wrong and the macro appears broken: the character walks into walls, panning misses the water, or the script does not start at all. Two of the four problems below are environmental, and no code change can fix them.
Cause: Windows display scaling. Scaling shifts every screen coordinate, so detection that samples fixed positions reads the wrong pixels.
Fix:
Caveat worth knowing (code-level, not fixed here). The macro’s pixel probes are
hand-tuned for heights 768 / 953 / 1050 and widths 1366 / 1680 / 1856. There is
no 1920x1080 case — which is the very resolution the guidance above recommends. On
1920x1080 every probe therefore runs on its base ratio. That is a plausible cause of
“walks into walls” that scaling alone does not explain, and it is left documented
rather than guessed at. See MODIFICATIONS.md, “Known issues NOT fixed”.
Cause: high-frequency visual disturbance. Screen shake stops the macro from finding its targets, and it defeats any “wait until the view settles” test, so steps run to their time ceiling instead of stopping when they should.
Fix (in-game Roblox settings):
Correction to earlier advice: an earlier version of this project suggested turning Shift Lock ON for camera stability. For this game that is wrong. Shift Lock must be OFF with the camera on Classic.
Cause: you are running the Microsoft Store build of Roblox.
Fix: install the official desktop launcher from roblox.com/download. The macro only works with that build.
Cause: the script running under AutoHotkey v2, or too many overlay programs competing for input.
Fix:
Already handled in this build. On Windows the .ahk association is usually the
AutoHotkey UX launcher, which picks the interpreter from a script’s #Requires
header and defaults to v2 when there is none — so this macro could fail to open
even with v1.1 installed. This copy has #Requires AutoHotkey v1.1 on all 22 launched
scripts, and RUN ORNATE.bat calls the v1.1 engine by absolute path as a fallback.
If it still will not start, your AutoHotkey v1.1 install itself is the problem.
OrnateMacroV1.4.8 folder)Starts on F6, stops on F8.