What You'll Learn
- Common error fixes
- Performance solutions
- Compatibility
Common error fixes
Macro not doing anything
If the macro isn't doing anything, you most likely have the wrong screen scale. The scale
affects
the coords on your screen, so even if you are using a 1920x1080 resolution but you have a 125%
scale, then you lose out on a bit of screen space. This can also affect how the macro is
working.
The easiest solution to fix this problem is to change your scale to 100% with the following
method:
- Right click your wallpaper
- Select "Display Settings"
- Find the box that says "scale" and check if the number in it is 100%
It has to be at 100% for the macros in the GUY2 Launcher to work correctly.
Wrong resolution error
If you get an error saying that your resolution isn't supported (we currently support 2560x1440,
1920x1080, and 1366x768), then you have the wrong screen resolution selected. To change it you
must:
- Right click your wallpaper
- Select "Display Settings"
- Find a box that says "Display Resolution" and click on it
- In the drop-down box, select the 2560x1440, 1920x1080, or 1366x768 resolution depending
on which one you're able to choose from
This will allow you to run the macros in the GUY2 Launcher with no issues regarding your
resolution.
Failed to download images
If you get a "Failed to download images" error, then there are 2 possible issues: either your
internet stopped working while the macro tried to download the images for image recognition, or
you have an outdated launcher.
To update the launcher, all you must do is press the "update" button visible on the left side of
the launcher, then wait until it finishes updating and proceed to delete the macro that had
issues and download it again. This should fix the issue.
Invalid Code
If you get the "Invalid Code" error when trying to verify, make sure you put
YOUR correct Discord user ID and not someone else's. Then make sure that when
you copied the code, there wasn't any space at the end of the code when pasting it into the
launcher.
Performance solutions
You may face issues with the macros in the GUY2 Launcher, like clicking too fast or too slow.
This may be caused by your internet or by your computer specs. Unfortunately, I have no way of
knowing which user will have what ping when using the macro or if their PC is good or not, but
there is a way to fix this. If your PC isn't too good, then try lowering your resolution.
Lowering your resolution from 1920x1080 to 1366x768 (both resolutions are supported) will reduce
the number of pixels your GPU has to generate for each frame, making the total number of pixels
on your screen decrease from 2.073 million pixels to 1.049 million, which is almost a 50%
reduction. This
will allow you to get slightly more FPS, which might solve your issue if it's
NOT ping-based.
If your issue is ping-based, then you might need to press the "edit" button under the macro you
want to run and find all "time.sleep(time)" lines and then add some time to every single one of
them. For example, if a line says:
time.sleep(0.3)
Then change the time in the brackets based on the ping you have. So if your ping is 160, that
means
you should change the time from 0.3 to 0.46, like this:
time.sleep(0.46)
And then just save the file by using the keybind "Ctrl + S" or any other way you know of to save
a file.
Compatibility
GUY2 Launcher and the macros inside it are mainly built for Windows. I tested everything on Windows
10 and 11, and they work perfectly fine there, but I am pretty sure older versions like Windows 8
should work too. I have not personally tested Windows 7 or older, so I cannot guarantee it, but
since the launcher is very lightweight it might still run. Still, I recommend sticking with Windows
10 or 11 since that is what I develop and test on.
The launcher also works if you have multiple monitors, but keep in mind that it will only function
on your main monitor. So if you run Roblox on a second screen and expect the macros to click and
move there, it will not work. Always make sure the game is on your primary display or else you will
run into problems.
Another important detail is that Roblox must always be run in fullscreen unless a macro specifically
tells you otherwise. Windowed or borderless windowed modes can cause the macros to click in the
wrong spots or completely fail image detection. So to avoid problems, just use fullscreen at all
times unless there is a good reason not to.
Screen scale is also a huge factor. You must set your display scale to 100% or the macros will not
function correctly. Even something small like 125% scaling completely throws off the coordinates,
and suddenly nothing lines up the way it should. So always double-check your scale before running
anything.
There are no minimum hardware requirements for the launcher. It runs fine on both low-end and
high-end PCs. The only thing that can slightly affect performance is your screen resolution. For
example, running at 2560x1440 requires more resources than 1366x768, so lowering your resolution
might give you better performance if your computer is struggling.
Language settings also matter. Your Windows system can be in any language, but Roblox itself must
always be set to English. Custom fonts, textures, or any modifications to the default look of Roblox
will break the macros because they rely on the default visuals. And most importantly, you must use
the browser version of Roblox, not the Microsoft Store version. The store version won't work 9
out of 10 times with the GUY2 Launcher.
At the moment, GUY2 Launcher does not support Linux, macOS, or mobile devices. I am not planning to
add support for them any time soon, though maybe in a year or so I might look into it. Right now the
focus is only on Windows, since that is where the majority of Roblox players are.
To put it simply: the launcher works on Windows (10 and 11 tested, 8 should be fine too), it only
works on your main monitor, you must use fullscreen with 100% scaling, and Roblox must be in English
on the browser version with no modifications. Follow these simple rules and you will not run into
compatibility issues.