Tutorial: Custom plugin paths

Commands:

The two tcl commands you can add to an init.tcl that will add a plugin directory path are.

1: plugin_addpath

2: plugin_appendpath

plugin_addpath:

This will add the path to the beginning of Nukes plugin paths.

plugin_appendpath:

This will add the path to the end of Nukes plugin paths.

What is the difference?

The difference is if you use plugin_addpath then your preferences.nk and window_layouts.nk file will be saved into this directory since it will be the first directory listed under plugin_path.

Example 1:

This example will demonstrate having a directory used to store plugins, this plugin directory contains sub-directories one for each version of Nuke. Depending on which version of Nuke is running it will only add the corresponding plugin directory for its version.

You could even get more creative and have the path being added search for environmental variables, my personal init.tcl file replaces the above code with.

It grabs the environmental variable $HOME and then uses that as part of the path.

Example 2:

This last example is my init.tcl file, it will append my NFXPlugins directories to the plugin_path as well as add 2 other directories one which contains gizmos and the other tcl scripts.