GameRig 2.1 sets 'blender': (4, 5, 4) in __init__.py, preventing use with Blender 4.2 LTS.
After testing, the addon works fine on Blender 4.2.9. The bone_collections API that v2.1 relies on (replacing the deprecated rigify_layers from v0.3.5) is fully available in Blender 4.2's Rigify — the built-in Rigify metarigs use the exact same patterns (arm.collections, collections.active, etc.).
Proposed fix
Lower the version requirement in __init__.py:
# Before
'blender': (4, 5, 4),
# After
'blender': (4, 2, 0),
Why this matters
Users on Blender 4.2 LTS are currently forced to use v0.3.5, which is broken on 4.2 due to the removed rigify_layers API. GameRig 2.1 already has the correct implementation — it's just being blocked by an overly conservative version gate.
GameRig 2.1 sets
'blender': (4, 5, 4)in__init__.py, preventing use with Blender 4.2 LTS.After testing, the addon works fine on Blender 4.2.9. The
bone_collectionsAPI that v2.1 relies on (replacing the deprecatedrigify_layersfrom v0.3.5) is fully available in Blender 4.2's Rigify — the built-in Rigify metarigs use the exact same patterns (arm.collections,collections.active, etc.).Proposed fix
Lower the version requirement in
__init__.py:Why this matters
Users on Blender 4.2 LTS are currently forced to use v0.3.5, which is broken on 4.2 due to the removed
rigify_layersAPI. GameRig 2.1 already has the correct implementation — it's just being blocked by an overly conservative version gate.