Quote:
Quote:
NPC says : are you a [young Paladin of Brell] ?
you say : i am a young Paladin of Brell.
NPC says : then go and get me this or that
becoming :
Quote:
NPC says : are you a [young Paladin of Brell] ?
you say : yes.
NPC says : then go and get me this or that
|
Cant this already be done that way? for instace.
Code:
sub EVENT_SAY {
if($text=~/Hail/i) {
quest::say("Greetings! You must be a stranger or [new to the Hall]. If you are a stranger. be warned that these halls are intended for the Ebon Mask only. If you are found to be a member of another house. you just may feel the sting of a blade in your back.");;
}
if($text=~/i am new to the hall/i) {
quest::say("Then I am glad to make your acquaintance. Have you ever been to Freeport? If not. how would you like to go? It is a test of your cunning we wish. Are you prepared to risk your young life? Are you [ready to venture to Freeport]?");;
}
If you change the line that reads:
Code:
if($text=~/i am new to the hall/i) {
To:
Code:
if($text=~/yes/i) {
Will that not do what you are saying in that particular example you gave?
Mayhap I am concentrating on the wrong thing here, but I would think that with that particular instance, you would not want anything other than what you have... If you made it a boolean, where false = 0, and true is anything else, then you could type ANYTHING in there to activate the next part of the quest. Therefore it would HAVE to be a static string...
Of course you could always add $text strings so that the user can type it a few different ways (read have a few different responses the NPC would accept). Obviously we know that the =~ tells us that we can type "yes", or "Yes", or any variation thereof, as long as the 3 letters "y", "e", and "s" are represented. Your thoughts? Opinions? Likes? dislikes? Favorite color?
P.S. Just threw in that last one to see if you were ACTUALLY paying attention what with that long winded book of mine..
[edit]
Quote:
|
a global must be set to "<none>", "__absent__" or whatever you want set it rather than delete the record.
|
And:
Quote:
|
The database can be updated, but, well, the variable remains set in the package (read : npc quest variable scope) unless it is reset by a new value.
|
Silly question, but since we CAN update simple things like loot drops on mobs, then would it not stand to reason that we could simply write a script to reset the value to say 0 ( or whatever the default value is)? I may be missing your point here, so If I am wrong explain a little better what you mean..
Threaded Mode
