Denizen/0.7/Troubleshooting: Difference between revisions
From Citizens Wiki
Aufdemrand (talk | contribs) No edit summary |
Aufdemrand (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
<div style="margin-right:2.0em; margin-top:35px; padding:10px; font-family:camingodos-web; font-size:110%;"> | <div style="margin-right:2.0em; margin-top:35px; padding:10px; font-family:camingodos-web; font-size:110%;"> | ||
<span style="font-family:natalya-alternate-one; font-size:650%; margin-right:-7px; margin-left:-10px;">D</span>enizen can seem a bit complicated at first. | <span style="font-family:natalya-alternate-one; font-size:650%; margin-right:-7px; margin-left:-10px;">D</span>enizen can seem a bit complicated at first, especially when you don't know what to look for when something isn't working exactly like you want. Luckily, if you are having problems, there are several tools available to help you. | ||
</div> | </div> | ||
| Line 14: | Line 14: | ||
==== Trigger not working? ==== | ==== Trigger not working? ==== | ||
<div style="margin-right:2.0em; padding:10px; font-family:camingodos-web; font-size:110%;">Denizen NPCs, by default, have only their Click Trigger and Chat Triggers enabled. Use <tt>/denizen trigger list</tt> to see the status of the triggers for your NPC. Red means disabled. See: [[Denizen/In_Game_Commands#Trigger_Toggles|Trigger Command]] | <div style="margin-right:2.0em; padding:10px; font-family:camingodos-web; font-size:110%;">Denizen NPCs, by default, have only their Click Trigger and Chat Triggers enabled. Use <tt>/denizen trigger list</tt> to see the status of the triggers for your NPC. Red means disabled. See: [[Denizen/In_Game_Commands#Trigger_Toggles|Trigger Command]] | ||
<br> | |||
You may also have a plugin conflict. If you suspect this, try disabling all plugins except Permissions, Citizens2, and Denizen to see if the problem persists. | |||
</div> | |||
==== Script not working as intended? ==== | |||
<div style="margin-right:2.0em; padding:10px; font-family:camingodos-web; font-size:110%;">Turn on <tt>/denizen debug</tt> and check out the information being output when your script runs. There's likely some information in there that can be used to track down the problem, whether it be failed requirements, incorrect flow logic, syntax, or simply a spelling mistake. | |||
</div> | |||
==== Still having problems, what now? ==== | |||
<div style="margin-right:2.0em; padding:10px; font-family:camingodos-web; font-size:110%;">If you are still having problems check your console messages for errors, especially at start up. Any kind of error, from any plugin, may lead to problems. If all else fails join us on [http://webchat.esper.net/?channels=denizen-dev EsperNet in #denizen-dev]. | |||
: | |||
If you are still having problems check your console messages for errors, especially at start up. | |||
If all else fails join us on | |||
</div> | </div> | ||
Revision as of 05:39, 29 August 2012
Denizen can seem a bit complicated at first, especially when you don't know what to look for when something isn't working exactly like you want. Luckily, if you are having problems, there are several tools available to help you.
Assignments not working?
To check assignments on a Denizen use /denizen info with the NPC selected to make sure assignments have taken. This also shows other great information, such as bookmarks and activities. If you are the NPC's owner you can also sneak and right click to view this info. See: Info-Click
If assignments are not showing up, ensure that your assignments.yml is properly formatted, you've saved your assignments.yml, and you've used /denizen reload. See: Reload Command
Trigger not working?
Denizen NPCs, by default, have only their Click Trigger and Chat Triggers enabled. Use /denizen trigger list to see the status of the triggers for your NPC. Red means disabled. See: Trigger Command
You may also have a plugin conflict. If you suspect this, try disabling all plugins except Permissions, Citizens2, and Denizen to see if the problem persists.
Script not working as intended?
Turn on /denizen debug and check out the information being output when your script runs. There's likely some information in there that can be used to track down the problem, whether it be failed requirements, incorrect flow logic, syntax, or simply a spelling mistake.
Still having problems, what now?
If you are still having problems check your console messages for errors, especially at start up. Any kind of error, from any plugin, may lead to problems. If all else fails join us on EsperNet in #denizen-dev.