Hey folks,
I’m migrating some pipeline tools into AYON and could use a hand with addon distribution.
I’ve successfully written the create, load, and extract scripts for managing V-Ray proxies in 3ds Max. The local integration works perfectly. However, I’m stuck on the next phase.
What is the correct procedure for taking these local scripts, packaging them, and distributing them as a global addon for other artists on the team? Do I need to set up a specific create_package.py structure, or is there a streamlined way to bundle these custom 3ds Max integrations to our server?
Any pointers or examples from similar addons would be hugely appreciated!
Hello,
Let me break your topic into smaller chunks:
-
Where to add custom plugins that can be global or target a specific DCC?
You can clone the repo of the target DCC addon and extending/modifying it directly.
Also, you can have your studio addon and with plugins that targets specific DCCs as we have in deadline addon.
-
How to pack and addon?
The dev process is straight forward, you clone this repo GitHub - ynput/ayon-addon-template: This is a boilerplate git repository for creating new ayon addons · GitHub and continue working following the addon structure we have.
then run python create_package.py and upload it to your server.
Hey @mustafa_jafar,
Thanks for the response. I’d already cloned the template and run create_package.py — the .zip builds fine. My problem is the upload itself: the server throws ERROR: Custom addons uploads are not allowed.
I’m admin on the instance, so I’m guessing this isn’t a user-permission. We’re on ynput.cloud (taos.ayon.app).
One more thing — I noticed ayon-3dsmax ships the Redshift proxy family but no V-Ray equivalent. What I built mirrors that exact pattern: create/load/publish for vrayproxy and vrayscene. If that’d be useful to others, I’d be happy to contribute it upstream into the official Max addon — what’s the right way to go about that, a PR to ynput/ayon-3dsmax?
Thanks 
