EOSERV Bug Tracker > Bug #193: Quest "if" scenarios need correction

Bug #193: Quest "if" scenarios need correction

Quest "if" scenarios need correction
ID #193
Submitter Apollo
Product EOSERV
Severity Normal
Status CLOSED, INVALID
Submitted 27th Nov 2012
Updated 22nd Mar 2013
Apollo Submitter 11 years, 19 weeks ago

If I understand from the example given, this should work:

if InputNpc(2) ShowHint("Hint Message")

For some reason, this does not work. I have tried various versions of the example such as adding the semicolon and action and no method creates the desired effect of simply showing a hint without moving a state.

Comments

Apollo Submitter 11 years, 19 weeks ago

Seem to be all of the dialog rules effected like this. :/

Sausage Developer 11 years, 2 weeks ago

This is not how "if" works. You need a rule trigger:

rule InputNpc(2) ShowHint("Hint Message")

Updated Status to CLOSED, INVALID

Add Comment

Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".

Please log in to add comments. EOSERV Bug Tracker > Bug #193: Quest "if" scenarios need correction