With Blender 3.0, the asset manager and asset-system will be released. I plan on switching all MatLib functionality to it, as well as extend it with a pool of shared assets in the form of 3d models. Assets could be used by anyone, but only selected contributors would have the ability to push updates to the repository.
[x] Create separate seut-assets repository
[x] Convert all MatLibs into Blender assets
[x] Rework "Overwrite MatLib"-functionality (remove? It should be handled by the asset-system...)
[x] Remove all MatLib linking / syncing code
[x] Rework export
[x] Rework import (remap materials)
[x] Rework addon preferences to include a path to the asset folder
[x] Potentially implement some simple sync options to be able to load the latest assets from the repository automatically (include warnings about overwrites)
[x] DLC / vanilla marker for assets instead of materials
[x] Rework export to write XML entries for materials also based on whether they're marked as vanilla
[x] how to handle textures in repo vs. local textures? support multiple texture source folders?
With Blender 3.0, the asset manager and asset-system will be released. I plan on switching all MatLib functionality to it, as well as extend it with a pool of shared assets in the form of 3d models. Assets could be used by anyone, but only selected contributors would have the ability to push updates to the repository.