Oculus Runes

From LSWiki

Revision as of 09:47, 18 October 2016 (edit) Suldrek (Talk | contribs) ← Previous diff		Revision as of 19:19, 18 October 2016 (edit) Suldrek (Talk | contribs) Next diff →
Line 1:		Line 1:
-	ZMud brute force triggers for the Oculus rune puzzle (Kian):
-
	The first line directly under the pattern # is the actual trigger pattern. The rest is the execution code.		The first line directly under the pattern # is the actual trigger pattern. The rest is the execution code.
	These triggers (put them in a class folder so you can easily disable them later) produce two variables: @oculus, which counts how many times the oculus has been rotated, and @count, which tells the script how many times runes have been flipped. You only get 15 moves, so when the 15th move occurs, it restarts the script. When the oculus has been rotated 5 times, the script attempts to make you enter the portal (assuming success.) If that fails, it moves on to flipping the current first rune until count restarts it.		These triggers (put them in a class folder so you can easily disable them later) produce two variables: @oculus, which counts how many times the oculus has been rotated, and @count, which tells the script how many times runes have been flipped. You only get 15 moves, so when the 15th move occurs, it restarts the script. When the oculus has been rotated 5 times, the script attempts to make you enter the portal (assuming success.) If that fails, it moves on to flipping the current first rune until count restarts it.

---

Revision as of 19:19, 18 October 2016

The first line directly under the pattern # is the actual trigger pattern. The rest is the execution code. These triggers (put them in a class folder so you can easily disable them later) produce two variables: @oculus, which counts how many times the oculus has been rotated, and @count, which tells the script how many times runes have been flipped. You only get 15 moves, so when the 15th move occurs, it restarts the script. When the oculus has been rotated 5 times, the script attempts to make you enter the portal (assuming success.) If that fails, it moves on to flipping the current first rune until count restarts it.

It took me about an hour to work out all the kinks and try different iterations of this script, but this is the simplest and most effective version. I had a success after about five minutes of running it.

Special Note: The rest of the Illuminatorium puzzles took me less than 5 minutes a piece to complete. I spent about three HOURS trying to solve the Oculus runes by traditional method (pen and paper) and eventually decided I'd had enough of it.

To start the script execution, turn off triggers and "flip first rune" until you get a message saying colors flicker across your oculus. Then turn triggers on, and "look at runes on oculus" one time. The rest is automated until success or you get disconnected from the MUD.

Pattern 1

The first rune is %1 and points %2.  The second rune is %3 and points %4.  The third rune is %5 and points %6.

#IF %2=downward {
 flip first rune
 #wait 1000
 look at runes on oculus
 } {
 #IF %4=downward {
   flip second rune
   #wait 1000
   look at runes on oculus
   } {
   #IF %6=downward {
     flip third rune
     #wait 1000
     look at runes on oculus
     } {
     rotate oculus left
     #MATH oculus (@oculus+1)
     #IF @oculus=5 {
       #MATH oculus (@oculus*0)
       enter portal
       } {look at runes on oculus}
     }
   }
 }

Pattern 2

The Illuminatorium Oculus reacts to your proximity

#MATH count (@count+1)

Pattern 3

You see colors flicker across the Illuminatorium Oculus as its runes reorient themselves.

#MATH count (@count*0)
look at runes on oculus

Pattern 4

You don't know how to 'enter'.

flip first rune
#wait 1000
#IF @count<14 {enter portal}
#IF @count=14 {flip first rune}