Most built-in plugins don’t do that (they just try to use the executable as instructed, and fail with an error when the command can’t be found), but you can also consider throwing a UserError, which halts the entire execution of beets. There is no way to throw an error to just selectively prevent the plugin from loading.
Ya, I guess it is a UserError. Like when I have something written wrong in the config.yaml file and beets stops. That will work perfectly
The write variable method does work. I was using the wrong method to do an import. Thank you for all your help. My plugin is now complete.
1 Like