I made a plugin, that requires some triggers to be disabled on startup, so i disabled them. When MUSHClient opened though, they were enabled (My code didn't enable them, I checked). I looked at the plugin, and the enabled=y line is not there. I tried explicitly disabling them, i.e. enabled=n, and it worked fine. I'm going to venture a guess here, i think that you have coded MUSHClient to set variables to enabled by default if it doesn't find the "enabled" line... Am I right?
Triggers enabled by default
Posted by Poromenos on Thu 07 Nov 2002 11:31 AM — 2 posts, 7,390 views.
There was a slightly insidious bug there. When the plugin was loaded as part of the world loading, it assumed defaults for things, so triggers defaulted to enabled, however if you reinstalled the plugin, it assumed "no defaults", so your trigger would have been disabled the second time.
This is a bug, you are supposed to explicitly enable triggers (etc.) in plugins.
It will be fixed in 3.32.
That is, the default (if not supplied) for every entry will be zero or blank (if a string).
This is a bug, you are supposed to explicitly enable triggers (etc.) in plugins.
It will be fixed in 3.32.
That is, the default (if not supplied) for every entry will be zero or blank (if a string).