Yeah good point, I’ve updated the post to show where you would make the changes on
tk-config-basic as well.
So with my example, I’m expecting that the user will launch the software through Shotgun Desktop or the Shotgun browser integration, every time they want to use the distributed plugins. Even if the plugin doesn’t need to be downloaded, it may still need to be set up again, ie setting the environment to point to it, so that approach will do it when they launch.
I’m not quite sure what you mean by “just launching Toolkit”? Do you mean like running Shotgun Desktop but not launching anything?
You could change it so that the logic was run at a different point, such as via the
engine_init.py core hook, obviously, you would need to make a few changes such as pulling down plugins for all software since you won’t be passed on specifically. Also how you “set up” the plugin to be used is up to you, but the
before_app_launch.py is a convenient place to do it usually.
I’m not sure if that answers your question?