Can't do anything with the addon since Blender 3.4.0

[Cappyadams]

so, I recently re-installed the addon and when I tried to do anything with the cats addon, I would get an error. (pic below). It won't even let me update the addon in the preferences. what do I do to fix this?

[Spectre-Slayer]

unfortunately, coding for the cats plugin has not been updated since June 27 of 2021 and your only option until they make the update is to download the 2.93 version of blender and install the add-on from there

[Cappyadams]

unfortunately, coding for the cats plugin has not been updated since June 27 of 2021 and your only option until they make the update is to download the 2.93 version of blender and install the add-on from there

I see.

[aech12]

3.4 broke plenty of addons, 3.3 was lts so in 3.4 they felt the freedom to change more stuff

[3dcinetv]

If the support of Cats update stopped for further compatibility with Blender 3.3+, why are the "supporting patreons" still appearing beyond 2.93?
It's annoying to have to go back to 2.93 "just to get blendshapes" named, generated, eye bone rolls, etc.. 😓 and then still get to see the supporting panel instantly opened (taking more space) in blender 3.3+ knowing the addon "is not supported" in that version.
Could you guys do a call-to-action to crowdfund the addon's compatible api for Blender 3.6+ beyond? at least 3.6, please. I'm positive the VRChat and Blender community would crowdfund it gladly.

[furry72]

or reach the .zip folder of the CATS plugin, browse it and find the file "init.py"

copy the file on your desktop and edit it with a text editor, notepad is enough

look for the word 'TESTING' in the code, you should find a line that looks like this bpy.context.window_manager.addon_support = {'OFFICIAL', 'COMMUNITY', 'TESTING'} (I found it at line 319)

remove the TESTING part from that line, comma and single quotes included, the result has to look like bpy.context.window_manager.addon_support = {'OFFICIAL', 'COMMUNITY'}

save the file, copy it from your desktop and paste it back into the .zip file

uninstall and install the plugin again, it shouldn't give you the error anymore