Hey Gary,
We’ve made some changes to how event plugins work since Deadline 7.2. A couple ones that will affect your plugins immediately are that we’ve removed dlinit files, plugin information is now stored in the database. Also, we’ve changed from a binary disabled/enabled state to a tri-state that is made up of the following three states: Global Enabled, Opt-In, and Disabled. More information on how Event Plugins look in Deadline 9 can be found here: docs.thinkboxsoftware.com/produc … ugins.html
Also, if you are using the Shotgun API in your custom plugin we made some changes to that as well. The dependencies for Shotgun have been moved from being in the same folder as the Event plugin to being a part of our PythonSync folder. Therefore, it’s possible that you are using an older/newer version of the API then we are, which may be preventing your script from running.
As for updating the cache, Event plugins are run in a separate sandboxed process now. Deadline applications will periodically check if their copies of an event plugin are stale and will reload them. You can force this to reload by restarting the Slaves. For the Monitor, “Tools -> Synchronize Scripts and Plugins” will update any stale Event Plugins.