Exception: Demiurge::Errors::BadScriptError
- Defined in:
- lib/demiurge/exception.rb
Overview
A BadScriptError will normally not benefit from retrying. Instead, one or more scripts (World Files and/or action code) associated with this error is presumed to be bad or outdated. The primary thing to do with BadScriptErrors is to accumulate and count them and possibly to deactivate one or more pieces of bad code or in-world areas containing them. Error counting can allow an administrator to locate (or guess) the bad script in question and disable one or more objects to remove the problem. While it's technically possible to disable bad scripts automatically, that will sometimes function incorrectly. At best it can sometimes help, and at worst it can cause severe damage.
Direct Known Subclasses
LocationNameNotFoundError, NoCurrentIntentionError, NoSuchActionError, NoSuchAgentError, NoSuchStateKeyError, TooManyIntentionLoopsError, TooManyNotificationLoopsError
Instance Attribute Summary
Attributes inherited from Exception
Method Summary
Methods inherited from Exception
#backtrace_chain, #formatted, #initialize, #jsonable
Constructor Details
This class inherits a constructor from Demiurge::Errors::Exception