as Pribambase stays connected it seems to be creating a lot of duplicate information. I'm not sure what I can provide to get you useful troubleshooting information though. I first noticed the issue as I was having frame drops, and duplicating an object I was making texture modifications appended it as "Object.8392" in the scene inspector.

I've updated blender and pribambase to the latest release versions of writing.

I haven't been able to figure out exactly what's causing this, but I have reproduced it, and I do believe it's related to pribambase somehow.

Maybe operating on a non-uniform scale object is somehow doing it?

Hello. Could you explain how it’s reproduced step by step? In particular, how you set up textures (animation/uv/layers). Also please check if there’s anything in system console (window -> toggle system console).

Yes, I apologize but I've been struggling with itch.io and its refusal to let me paste images into my posts.

To my knowledge I'm using the defaults for Pribambase.

step1 is of course launch blender/Aseprite and load my scene.

step2 is to connect Pribambase on both Aseprite and Blender.

Step3 is to spend a few hours fighting with my UV unwrapping. While writing and documenting this I realize that the act of doing a UV unwrap is creating roughly 70 additional "Jaws" somehow between each unwrap.

When Pribambase is not connected, it only increments the object identifier by 1 in the scene inspector.
Unfortunately the log window is not displaying any activity.

I am a little curious about if having my mapping nodes attached via node wrangler might be doing something with the material. Regardless, I'm interested in seeing what we can do to get this patched up. In the meantime the quick performance fix is running the clean up function and culling unused data, so it's not entirely unworkable. Just gets real framerate-chunky.

I tried to follow that, including double materials, and do not see any loose data appearing:

though it doesn’t look like the latest version of the panel? in case you had it installed before, could you try removing addon first, then installing again?

After that if the issue remains, could you try to replace ‘image.py’ in ’%Appdata%\blender foundation\blender\3.6\scripts\addons\pribambase` with this version and check system console again, after that replication happens.

Removing Pribambase 2.4.1 did in fact result in it getting replaced by pribambase 2.6.0

I thought that I had done that correctly previously but I must have installed an old version somehow. I'm elated to report that this seems to have fixed the issue! You were absolutely spot-on in recognizing the layout of the old version. Sorry to have troubled you.