Plugins and version dependencies

Why hyprbars, hyprdrag and native modules have to match the system version.

What the plugins add

hyprbars adds title bars. The project version contains its own hover areas and the color of inactive bars. hyprdrag reports move and resize interactions to the interface for the snap preview.

Why an update can require a rebuild

Hyprland plugins use internal interfaces of the compositor. A build therefore has to match the actual target packages. The packaging ties the plugins to the Hyprland and libstdc++ versions in use, and the terminal module to Qt and qtermwidget.

A message such as Version mismatch should be solved with a matching rebuild or a matching package set. Bypassing the version check does not produce a compatible build.

Check what is loaded

In a running Hyprland session, this read-only command lists the loaded plugins:

hyprctl plugin list

Make sure you do not also load a second, unpatched hyprbars version through another plugin manager. The project features require the matching build.