Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Its because of the Logic: while #charposx <> 2149 && #charposy <> 1415 ; <- LogicWhich is why pathfind is part of the loop, so it WILL keep trying until BOTH conditions are met.
So once either your #Charposx = 2149 or your #Charposy = 1415 it will break from the while because you are telling it to only move while BOTH of them aren't what you want. ....
That will force it to continue to perform the code until it satisifies both Conditions.Exactly! I mean isn't that what the AND (&&) is saying.... Isn't that the condition - that BOTH have to be true ? What else would AND be for?
event pathfind 2149 1415 -23
while #charposx <> 2149 && #charposy <> 1415
{
wait 5
event pathfind 2149 1415 -23
}Please note that your script will keep on executing while the character is moving.but in my example the script jumps out of the while loop before it reaches the coords.
top:
event pathfind 2149 1415 -23 3s
wait 1s
if #charposx <> 2149 && #charposy <> 1415
{
wait 10
goto top
}
else
halt
menu Button EUOButton1 236 84 71 25 Pause menu Button EUOButton1 236 60 67 25 Continue
menu Button EUOButton1 236 60 67 25 Pause
...... she does tend to hold the button down though.. = )She's just making sure...
set #menuButton N/A
set %EndScript #false
Repeat
If #MenuButton <> N/A
{
gosub #menuButton
set #menuButton N/A
}
until #menubutton = closed
halt ; End script
That's a neat idea. Yeh, voice processing lag is kinda annoying. Even Siri has to say something to hide the fact that processing is going on.One would think with today's higher-end systems, that the recognition process for short spoken words would be in the nanoseconds, not milliseconds. Somebody needs to get off their ass on that front if you ask me... Talk about a problem begging for a solution... You know the future is all voice as well as I do... so where the hell is the innovation in that area?
