Scripts fail based entirely on the name of the script

[smaltby]

The below script does not work. ----- An Enemy in our Midst ----- 'An Enemy in our Midst': Type: Interact Requirements: Mode: All List:

• -FLAGGED 'AnEnemyInOurMidsts1'
• -FAILED 'AnEnemyInOurMidsts1'
• -FINISHED 'AnEnemyInOurMidsts1' Steps: 1: Click Trigger: Script:
  • CHAT "You've been a great help to my city lately. However, I must task you with something new, something far more serious then your previous trivialties."
  • CHAT "A dreadlord seems to have infiltrated what was presumably though to be a safe area."
  • CHAT "The spottings have been in the hills behind the city, formerlly though protected by this city, the fortress on the other side of the hills, and the mountains on either side."
  • CHAT "But that protection seems to have been infiltrated. I need you to find and kill that dreadlord before it can cause serious damage."
  • CHAT "So, will you assist me, ?" Chat Trigger: 1: Trigger: /Yes/ Script:
    • CHAT "Good, I knew I could count on you. Talk to the Mayor in Riverstead to the east. Riverstead was where the last sighting was."
    • FLAG 'AnEnemyInOurMidsts1' 2: Trigger: /No/ Script:
      • CHAT "I understand, it's a grand task. If you change your mind though, please come talk to me."
      • FAIL 'AnEnemyInOurMidsts1'

---- Assignment ---- Denizens:
King Aeres: Interact Scripts:

• 10 An Enemy in our Midst Texts: #These texts will be shown to the player if no matching scripts are found, since Jill has no interact scripts, these will always be shown. No Click Trigger: I have nothing for you at the moment, . No Damage Trigger: How dare you! Guards, guards! No Chat Trigger: I'm sorry, I don't quite understand what you mean. Denizen Unavailable: Please wait a moment, I am busy.

However, if I change the name to "An Enemy in our Mysts", the script works fine. After realizing this, I tested several names, and on random occasions, the script will fail solely based on that name change... I have no reason why this is happening...but it's very frustrating having scripts fail randomly like that.

[smaltby]

Never mind this. The owner was using an older version of denizen. The newest build fixes this.

[aufdemrand]

Make sure you do a /denizen reload each time you change something. A look at the debug output would help diagnose, if you run into this again.

[smaltby]

There was no output, the script just didn't run, even with Mode: NONE, and /denizen reload was run every time.

[aufdemrand]

Please reopen if issues still persist.