PuloversMacroCreator VS ydotool

I came across a post where a player was asking Larian for a way to save character presets for Honour Mode since we may want to run the same character over and over. While we await that feature, I'll share what I've been doing to "save" my presets: I use a macro (you can choose any macro software you prefer, i use this one) to record my mouse and keyboard movements and clicks while creating my Tav.

At least it will be ever since you ran Auto White Balance on all 100-something recipes manually because you couldn't figure out how to bulk edit in GIMP and forgot you had at least three different macro programs installed.

Required Tools - Windows PC w/ Rocket League (EPIC / STEAM does not matter) - Pulover's Macro Creator (https://www.macrocreator.com/)

You would want something like this software - https://www.macrocreator.com/

I've used Pulover's Macro Creator to good effect, being able to take actions based on even a single changed pixel on a screen, or if a particular graphic or icon shows up.

- Macro Creator credit to Mr. Pulover and all the credited creators listed here: https://github.com/Pulover/PuloversMacroCreator (will enumerate all credits soon)

for both QBO and QBD use (not promoting) Pulover's Macro Creator https://www.macrocreator.com/

I haven't tried it, but it may be possible to assign shortcuts (https://www.tradingview.com/support/shortcuts/) to individual mouse buttons. Alternatively, you can try macro recorders like Pulover's Macro Creator https://www.macrocreator.com/

https://www.macrocreator.com free, open source

I've found using Pullover's macro program as a convenient way to automate some of this. https://www.macrocreator.com/

Wayland provides little by design, so this is quite typical. For example:

Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.

They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.

Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.

[0] https://superuser.com/questions/1221333/screensharing-under-...

[1] https://unix.stackexchange.com/questions/292868/how-to-custo...

[2] https://github.com/ReimuNotMoe/ydotool

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.

For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.