Zugg Software :: View topic

Wanderer Joined: 09 Dec 2007 Posts: 58

the point of the quest.
if you press a good key it gives "As you play the key, the organ emits a pure joyous note encouraging you on."
but, if you click a wrong key you have to start over with pressing the good key, then guessing the next one.
you have 6 keys in total and every press takes balance (+2 seconds)
I have no idea how to make it so that it finds the SECOND key, after pressing the first one.
then it has to find the THIRD key, after press the first one and then the second one.
then it has to find the FOURTH key, after press 1, 2 and 3
that continues up to SIXTH.

Posted: Sun Jan 20, 2008 12:43 pm

It'd help if you'd explain fully what the different messages mean. Your script is interpreting "The organ grumbles to your touch. Slightly out of tune perhaps?" "The pipes give out a harsh hiss as if scolding your efforts." and "The key clunks down but no sound comes from the pipes." as meaning "wrong note, try again" - which seems reasonable - but it's interpreting "A note awry spoils your melody - perhaps a missed key, or the slightest of mistakes?" as meaning "right note, but make it sharp" and "You grope around for the impossible note but soon give up the search." as meaning "right note, but make it flat".

It seems like the latter means "You've tried to press a key that doesn't exist" - for example, there's no b sharp or c flat (see wikipedia for a picture of a normal keyboard - although technically c flat is b, I can see why they wouldn't want to program it that way), and that the "slightest of mistakes" message means that it's the right note but could be either sharp or flat from that note. That means that your script will take a very long way round or perhaps even end up looping - where the script tries to press the sharp of a note, but the actual answer was the flat, it'll fail and begin again.

Is the difference between "slightest of mistakes" and "out of tune" one of degree? So a mistake of a semitone (ie, sharp-flat) will give you the "slightly" message, whereas a mistake of a tone or more will give you the "out of tune" message? That'll affect the way you detect an error when you press the sharp of a note, because it'll give the "out of tune" error should you press the sharp when the answer was the flat. And also, does the system properly understand that b and c and e and f are a semitone apart, so if you press c and the solution is b, it'll give the "slightest of mistakes" error rather than the "out of tune" one? I ask because if the system doesn't understand that pressing c flat is the same as pressing b, you'll need to script around that circumstance.

In addition, it'd be much better to use the "you can press another key" message rather than a two second alarm, to account for lag. What message does the server give for that?

My first thought is that the simplest way to solve this problem, assuming that the "out of tune" message means an error of a tone or more and that it properly understands that c flat = b, is with a simple brute-force method where you have a string list of all the possible keys:

#var Keys {c|c sharp|d|d sharp|e|f|f sharp|g|g sharp|a|a sharp|b}

Then you have a variable, @TryingKey, which is a number, beginning at 1. You decide which key to press like so:

press %item(@Keys,@TryingKey)

and then if you get the "slightest of errors" message, you know that the answer is TryingKey+1, which you then try, and if it's the answer, put in another string list:

#var CurrentTune %additem(@CurrentTune,@TryingKey+1)

If you get the "out of tune" message, you can add 2 to @TryingKey and try again.

When you want to replay the tune up to the current point, you have something like this:

#var NoteNumber 1
#alias ReplayTune {#var NoteNumber 1;#t+ Replay;press %item(@Keys,%item(@CurrentTune,1))}

#trig "Replay" {You can press another note} {#if (@NoteNumber=<%numitems(@CurrentTune)) {press %item(@Keys,%item(@CurrentTune,@NoteNumber));#add NoteNumber 1} {#t- Replay;RepeatAboveLogic}}

Where RepeatAboveLogic is an alias that repeats the guessing logic I have above, starting from TryingKey=1

Wanderer Joined: 09 Dec 2007 Posts: 58

thanks for the help, but c flat is not the same as b, the system does not get that.
and it's Right hand ready. instead of you can press another note.

i'll try to work it in.

Wanderer Joined: 09 Dec 2007 Posts: 58

Wanderer Joined: 09 Dec 2007 Posts: 58

i have an example how it is done manually.

Wanderer Joined: 09 Dec 2007 Posts: 58

this is what i have now

Posted: Sun Jan 20, 2008 6:10 pm

Really, you needn't make any changes to the note-guessing logic if you don't want to; it just made sense in my mind to couple the note-guessing logic with the tune-replaying logic. But you don't need to.

Since the puzzle doesn't work as I assumed, the brute-force method I described isn't the best way to do it. Your original method was probably better.

To store your current tune, though, the simplest way is to use a string list rather than individual variables (your variables 1-6). That allows you to use a single trigger for the "As you play the key, the organ emits a pure joyous note encouraging you on." line.

#trig "CorrectAnswer" {As you play the key, the organ emits a pure joyous note encouraging you on.} {#additem CurrentTune @organpress;#temp {Right hand ready.} {op a}}.

Then, to replay the current tune:

#var CurrentNote 1
#alias ReplayCurrentTune {#var CurrentNote 1;press %item(@CurrentTune,1);#t+ Replay}
#trig "Replay" {Right hand ready.} {#add CurrentNote 1;#if (%item(@CurrentTune,@CurrentNote) {press %item(@CurrentTune,@CurrentNote)} {#t- Replay;op a}} "" {disable}

You should never ever use #wait in a trigger.

Wanderer Joined: 09 Dec 2007 Posts: 58

ok, it seems to work pretty good!
except some minor mistakes, I think they are on my side, i'll try to fix them

Wanderer Joined: 09 Dec 2007 Posts: 58

it goes like that

Wanderer Joined: 09 Dec 2007 Posts: 58

hmm, i'm really stuck now, my triggers clash with yours, and I know yours are right,

when I do a misskey, it directly sends a message to the mud to press it, then @organpress changes, and if the next key is a successkey, it makes the currentnote a misskey, or a successkey.

when I do a misskey, it ignores the currentnotes and does not try to replay them, but gives the right value.
EDIt: since the currentnote replace waits for balance, it makes it slower than the #alarm or #wait values.