Need help editing Macro for "Hail to the King" Jump Rope Achievement

[Jawmuncher]

Disregard Thread

Edited February 15, 2019 by Jawmuncher
Not fit for forum

[irJessica]

I see you’ve already edited to say disregard thread, does this mean the original script works?

[Gman2]

Any scripts that work or do I have to connect my PC directly to the router?

[The Pants Party]

The original macro was created by someone on PST. The site is down at the moment, but the macro script is here as well:

 

https://github.com/septomor/FF9-Jump-Rope-Script/blob/master/Jump.ahk

 

You can find the instructions on how to run the macro here:

 

https://psnprofiles.com/guide/7421-final-fantasy-ix-trophy-guide#26-hail-to-the-king

 

Just ignore the part about PS4 Share since we are running it natively on Windows 10.

[J0shUK]

The original macro was created by someone on PST. The site is down at the moment, but the macro script is here as well:

 

https://github.com/septomor/FF9-Jump-Rope-Script/blob/master/Jump.ahk

 

You can find the instructions on how to run the macro here:

 

https://psnprofiles.com/guide/7421-final-fantasy-ix-trophy-guide#26-hail-to-the-king

 

Just ignore the part about PS4 Share since we are running it natively on Windows 10.

Doesn't seem to work for me. Appears as though the delay is off somewhere. Tried loads of different variables, highest I've got is around 150.

[Floyd.]

Doesn't seem to work for me. Appears as though the delay is off somewhere. Tried loads of different variables, highest I've got is around 150.

 

I got to 176 manually after a few tries, and having played the original version many times, this port is definitely different. If you can only get to 150 with a script, something else is influencing the timing because 150 isn't even a "speed milestone" like 20, 50, etc.

[J0shUK]

I got to 176 manually after a few tries, and having played the original version many times, this port is definitely different. If you can only get to 150 with a script, something else is influencing the timing because 150 isn't even a "speed milestone" like 20, 50, etc.

 

I got 213 manually last night, doubt I'll ever reach 1000

 

Was just saying that it doesn't seem the script above is compatable with PC because it assumes you are using PS4 share play, which obviously runs through the network and has delay, which playing directly on the PC does not.

 

With regards to it not being a speed milestone, delay can still effect it. If it is off by 1ms somewhere, this can have an effect many jumps later. Doesn't just have an instant effect.

[The Pants Party]

Hmm... maybe this will work since it's a native PC game?

 

https://steamcommunity.com/app/377840/discussions/0/361787186422679797/?ctp=5

[J0shUK]

Hmm... maybe this will work since it's a native PC game?

 

https://steamcommunity.com/app/377840/discussions/0/361787186422679797/?ctp=5

 

That won't work either as you can't use your mouse in game (unlike the Steam port).

[The Pants Party]

Dang. Well, I'm sure we'll get a savior eventually. Above anything else, this community is inventive in getting the easiest possible way to earn achievements.

[Shred Asics 13]

Pretty sure I ignored this back in the day as I barely even remember this mini game.

 

 

Is this worse than the Slippery achievement from Pier Solar (for those who played?). I remember secretly wishing there was a macro or keyboard availability..but eventually got it.

 

 

 

This is going to make my brain hurt.

[The Pants Party]

I've never played IX so I can't compare them but I'm right there with you about the Slippery game in Pier Solar. I absolutely thought it was impossible but just kept at it and eventually got the rhythm and it was so satisfying when I nailed it.

[Never Final]

So here is my progress on getting the script that Pants posted to work.

 

 

Before you get excited I have not got this to work completely. 969 jumps is my best and thats after messing with this script for 3 or 4 hours last night. Due to the differences in peoples PCs this will never work the same for everyone. So nearly everyone will have to fiddle with the settings to get it to work if it ever does. My advice is to get it setup and run it over and over. If you notice a consistent problem mess with that part of the script or change your latency. (Ive found 851 latency is good for me and I have a fairly high end pc). Do something like watch a movie on another screen while running this over and over. You only have to get lucky once. Anyway on with my progress report.

 

 

A few changes had to be made to deal with the frame rate drop and make things a bit easier for testing.

 

 

 

First off download the script and AutoHotKey and load it up.

 

 

Edit the script by adding a line at the very top before the "t::" that says "r::Reload" with no quotations. This will allow you to reload the script while in the game instead of having to alt tab to do it.

 

 

 

Now once you have the script edited Save it and load it and have it ready to run.

 

 

Now right click your desktop, go to Display Settings and change your resolution to its lowest setting. Mine is 800x600 (I normally run at 2560x1440 which means the game runs at that same resolution). This will solve 99% of the frame rate problems.

 

 

Now run FFIX and get Vivi ready. You should be at the point where he has a ! over his head and it says 0 jumps in the left top corner.

 

 

Press "t" to start the script, it will immediately pause. Press "ESC" to unpause it and it will run. If Vivi messes up then let him get up and move out. let the script run through the girls text until she says "Sure, Vivi can play" then press "r" to reload the script. This should put you right back at the beginning so you can try again.

 

 

Now I have yet to get this to work. I have gotten to 969 jumps with it though. There are a few hangups. At 50 jumps and at 320 jumps. The script tends to mess up there alot. I believe this to be an error in the script rather than the game dropping frames though and im unsure how to fix it.

 

 

See the jump transitions do not start at 20, 50, 200, 300. but at 21, 51, 201, and 301. The script is coded for the previous and not the later I believe. I dont understand the authors code enough to fix it myself but maybe someone else can.

 

 

Also to note depending on the age of your pc you may have to adjust the "Latency" setting in the script. This is just the wait period between pressing enter for the very first ! to start and Vivi's actual first jump. This will help align all the rest of Vivi's jumps.

 

It really sucks that this is an achievement as while I did it back in 2000 in the initial release I now have to much pain in my hands to be able to consistently press a button for that time length. The highest ive gotten manually is just under 300. And that caused so much pain I couldnt play the rest of the day. So getting this script to work is the only way Ill be able to accomplish this achievement.

 

 

Anyway I hope this helps progress everyone towards this achievement at least a little bit

Edited February 20, 2019 by Never Final

[Floyd.]

Dang. Well, I'm sure we'll get a savior eventually. Above anything else, this community is inventive in getting the easiest possible way to earn achievements.

So here is my progress on getting the script that Pants posted to work.

Didn't take long lol. I'll try and give this a shot once I beat the game, because ain't nobody got time for 1k manual jumps.

[NShepherd N7]

I got to 433 jumps... I was flying high but it just takes so god damn long to get to 1000. It's like 7 minutes of methodically pressing the button...

[Shred Asics 13]

 

 

Anyway I hope this helps progress everyone towards this achievement at least a little bit

 

 

 

 

First, thank you for your efforts on this! It really is discouraging to have this as an achievement. I completely echo your comments on hand related pain. Many of us who are fans of this era of FF are older now and this is physically annoying. For me, I had broken my thumb from sports back in the day and even though it heals, it's not the same. The Pier Solar mini game I mentioned above is an insane amount of D-Pad thumb work and it was a tall order for me. Thankfully, there is a midway checkpoint and I literally took an hour break in between...NERVOUS as all hell that the power would go out:p

 

 

I'm almost positive my thumb would lock up after 4-5 minutes of this.

 

 

 

I mean hell, I couldn't even do the Blue Dragon button mash achievement and had to buy a friggin' Turbo controller to cheese it.

 

 

 

Sometimes I really wish I could just let these achievements go....

[Link2430]

So, also to give an update (which isn’t necessarily super helpful): I was able to get QueueTip’s script from PlayStation Trophies to work for the Play Anywhere Windows 10 version of FFIX. It took a lot of time and frustration but it eventually worked. I was able to consistently get over 1000 jumps. I shut the game down, decided to clean it up to share here later, and when I went back to run the script again it didn’t work. Ugh.

 

The script does take some set up for each user. I attempted to make it work regardless of screen size and location but that seems impossible since you can independently adjust the width and height of the FFIX window. AHK has a tool called Window Spy which will tell you the mouse position relative to the active window as well as the color of the pixel under the pointer. The hard part is that FFIX hides the mouse in its window so you have to turn on “Show location of pointer when I press the CTRL key” in Windows settings. So, each person needs to figure out Vivi’s shadow color and coordinates in two spots. Once under him when the counter displays 0 and once again after he has failed and is standing outside of the jump rope. This part was difficult for me since the mouse didn’t show even when I pressed the CTRL key it only showed the circle and that was only sometimes. You also want to make sure the color value isn’t changing when you get the mouse into the correct position. One really good thing about this script is that it automatically restarts the jump sequence if you have the pixel detection set up correctly.

 

I know this isn’t helpful yet, but I’m going to try and clean up the script a little more and post it here after some testing. I hope I can consistently get it to work for me, but I’m just not there yet.

[Floyd.]

Amazing work, guys, thank you for your efforts!

[The Pants Party]

I'll echo Floyd, I would likely be lost trying to toy with the scripts so if anyone gets something that has worked I can try to size my window correctly and all that jazz to work with it!!

 

I'll be finishing New Vegas tomorrow and will start FF9 next. I'll give this a few legit tries.

[lordrex217]

Finally got mine to work yesterday after some really annoying framerate issues initially. So here is what worked for me.

 

1. I did not play on my 4k monitor. It would run super slow (almost half speed). I used my other 1080 monitor and got it to run normally.

 

2. I set the screen resolution to 1440x900. I only did this because people in the pstrophies thread said to.

 

3. I also played in a window mode instead of full screen.

 

4. I did this at the beginning of the game. The script did not seem to work at the other jump rope location at the end of the game.

 

5. I used the first script from the pstrophies link and only changed the latency to 839 after two failed attempts at 840.

 

Again, this is what worked for me, so take some of it with a grain of salt. I did get all the other achievements too so if anyone has questions feel free to ask.

[Link2430]

Alright, I think I got it, but I definitely need people to test this out. I only have one computer I can try this on. Credit goes to QueueTip over at PlayStation Trophies for figuring this script out, I just adjusted it so hopefully we can use it on our side.

 

First thing, follow these steps to get AHK setup on your machine (adapted from https://www.playstationtrophies.org/forum/6083888-post158.html):

 

1. Download AutoHotKey https://autohotkey.com/, and SciTE4AutoHotkey https://fincs.ahk4.net/scite4ahk/.

 

2. Copy and paste every part of the script (below) into a new file on SciTE4AutoHotkey, then save the file (preferably on the desktop for easy access).

 

3. Open up FFIX, take the game out of full screen and into windowed mode, and go to the jump rope game. Press Enter on your keyboard until the game shows "0 times" and Vivi has a white ! above his head.

 

4. Find the file and double click to start the script.

 

At this point, we need to find where Vivi's shadow is at the beginning of the jump rope game. This is the hard part so try to be patient. Find where the script is running in the bottom right of your screen (usually under hidden icons near the clock in Windows 10). You should see a green H symbol. Right click that symbol and select Window Spy. A new window will pop up similar to this: https://imgur.com/9q8IL0d

 

Select the check box Follow Mouse if it isn't already checked. Also, make sure under your mouse settings you turn on “Show location of pointer when I press the CTRL key”. That way when you press the control key a circle shows you where your mouse pointer is. One catch is that when your mouse is within the FFIX window, it disappears. Press the control key until you get an idea of where your mouse is and get it under Vivi's shadow where the color value (in the mouse position section of Window Spy next to color) doesn't change. This part isn't super easy so take your time. You'll want to either snap a picture of the Window Spy window with your phone or jot down the coordinates and color. The relevant information for us is in the mouse position section. Referencing the above picture, we need to know the coordinates next to "Client:" (yours will definitely be different, this is only an example). So, according to the picture, we would note 1825, 841, and the color value CCA053.

 

Alright, first step complete. Take this information and plug your values into line number 43 (always leave 0x before putting your color value):

PixelSearch, x, y, 1825, 841, 1825,841, 0xCCA053, 50, Fast RGB

 

Next, we need to get Vivi's shadow after he has failed the jump rope game so we can automatically restart the script. Go ahead and manually fail the game until you get to where the girl says, "Come play with us again!". At this point, redo the step above getting Vivi's shadow location using Window Spy. Then place these numbers and the color value just as above but this time on line number 61. Here is an example (same idea as shown above, the numbers will not be the same):

; Detect if failed and back at the start to retry
PixelSearch, x, y, 1272, 1179, 1272, 1179, 0x2E2208, 50, Fast RGB

 

Now, you are well on your way. Don't resize the FFIX window or you will have to find Vivi's coordinates again!

 

Save the script and press "R" on your keyboard to reload the script. Get Vivi back into the position where he has a ! above his head and he is outside of the jump rope. Press the "A" key to run the script. There will be tooltips noting each jump and a number you can disregard. Make sure the in game jumps and the tooltip jump numbers are in sync. If not, you have other issues we may can work out. If you are failing on the first jump and are seeing a tooltip stating "Not detected, check coordinates and/or color" you will need to redo the above steps to find Vivi's shadow. Again, that part can be frustrating so try to be patient. If Vivi fails a jump, the script should automatically restart for you so leave it running. If it doesn't, recheck your pixel coordinates after Vivi has failed.

 

Here are a few disclaimers/notes:

I definitely have had some issues getting this to work. One day it worked great, then I had to make some significant logic changes to make it work the next day. I hope this will work for at least some people. If you get the pixel detection working right and it doesn't constantly fail on 20 or the same exact number each time, it should eventually work, so let it do its thing. I've had success running this script at different window sizes on my computer using the above steps.

 

Since I had so many issues between days, I wasn't going to adapt this to share, but then I read about how some physically can't do this achievement and I wanted to hopefully help at least someone.

 

Let me know if it works for anyone and if you have any questions, I will try to help. Good luck!

 

Full script:

Esc::ExitApp
r::Reload
CoordMode, Pixel, Relative

a::
Process, priority, , High

loop 
{
i = 1

; jump intervals
a = 667
b = 532
c = 467
d = 433
e = 383
f = 400

delay = 100
balancer = 0
currentInterval := a
extraTime = 0

ToolTip, start, 400, 400

; Initiate steps to begin
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.
Sleep, 2000
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.
Sleep, 3000
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.

; Detect position
	Loop 
 	{
	PixelSearch, x, y, 793, 977, 793, 977, 0x452400, 50, Fast RGB
 			If (ErrorLevel = 0) 
 			{
 				;sleep, 100
 				tooltip % "Detected shadow"
 				break
 			}
		else
		{
			tooltip % "Not detected, check coordinates and/or color"
		}
 	}

start := A_TickCount + 50

loop
{
	; Detect if failed and back at the start to retry
	PixelSearch, x, y, 1272, 1179, 1272, 1179, 0x2E2208, 50, Fast RGB
		If (ErrorLevel = 0) 
		{ 
			; reset
			tooltip % "Restarting"
			sleep, 3000
			Send {Enter down}  ; Press down the Enter key.
			DllCall("Sleep", "Uint", 100)
			Send {Enter up}  ; Release Enter key.
			sleep, 2000
			break
		}
	
	; Manual override
	GetKeystate, state, Enter
	if (state = "D" and stop = 0)
	{
		break
	}

	timer := A_TickCount - start

	if (i = 1) 
	{
		currentInterval := a
	} 
	else if (i = 20) 
	{
		currentInterval := b
		balancer = 0
	} 
	else if (i = 50) 
	{
		currentInterval := c
		balancer = 0
	} 
	else if (i = 100) 
	{
		currentInterval := d
		balancer = 0
	} 
	else if (i = 200) 
	{
		extraTime = 50
		delay = 70
		currentInterval := e
		balancer = 0
	} 
	else if (i = 260) 
	{
		extraTime = 20
		balancer = 0
	} 
	else if (i = 301) 
	{
		currentInterval := f
		balancer = 0
	}

	; If jumps are too late remove the = below
	if(i >= 1) 
	{
		DllCall("Sleep", "Uint", (currentInterval - timer + balancer + extraTime))
	}
	Gosub, jump
}
}
return 

jump:
fullTime := A_TickCount - start - extraTime
start := A_TickCount
if(i > 1) 
{
balancer += currentInterval - fullTime
} 
ToolTip, Jump %i% - %fullTime%, 400, 400
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", delay)
Send {Enter up}  ; Release Enter key.
ToolTip
i += 1
extraTime = 0
return

[sthxdnn]

Of course, there is a full script and guide to follow 24 hours after I complete the game; just my luck. Well, either way, I'm extremely proud to have TrueAchievements recognize me as the first 5 completionists for it for my first 300k. Excellent work, man. If anyone needs any advice anywhere else for this game, I'd be glad to help.

 

-Titanous Arrow

[xsoenx]

Tried the scripts out to getting a max of 12 out.

For some reason on PC the game keeps dropping my inputs, when i try to talk to town folk, sometimes have to press Enter 2-6 time before i start talking to them, but i can see on the ! that it flashes like i pressed the button. It's the same with a controller.

 

 

Tried changing the Resolution, refresh rate (have a 144 hertz monitor) tried in window mode and resize that, and still nothing :/

[iberianham82]

Alright, I think I got it, but I definitely need people to test this out. I only have one computer I can try this on. Credit goes to QueueTip over at PlayStation Trophies for figuring this script out, I just adjusted it so hopefully we can use it on our side.

 

First thing, follow these steps to get AHK setup on your machine (adapted from https://www.playstationtrophies.org/forum/6083888-post158.html):

 

1. Download AutoHotKey https://autohotkey.com/, and SciTE4AutoHotkey https://fincs.ahk4.net/scite4ahk/.

 

2. Copy and paste every part of the script (below) into a new file on SciTE4AutoHotkey, then save the file (preferably on the desktop for easy access).

 

3. Open up FFIX, take the game out of full screen and into windowed mode, and go to the jump rope game. Press Enter on your keyboard until the game shows "0 times" and Vivi has a white ! above his head.

 

4. Find the file and double click to start the script.

 

At this point, we need to find where Vivi's shadow is at the beginning of the jump rope game. This is the hard part so try to be patient. Find where the script is running in the bottom right of your screen (usually under hidden icons near the clock in Windows 10). You should see a green H symbol. Right click that symbol and select Window Spy. A new window will pop up similar to this: https://imgur.com/9q8IL0d

 

Select the check box Follow Mouse if it isn't already checked. Also, make sure under your mouse settings you turn on “Show location of pointer when I press the CTRL key”. That way when you press the control key a circle shows you where your mouse pointer is. One catch is that when your mouse is within the FFIX window, it disappears. Press the control key until you get an idea of where your mouse is and get it under Vivi's shadow where the color value (in the mouse position section of Window Spy next to color) doesn't change. This part isn't super easy so take your time. You'll want to either snap a picture of the Window Spy window with your phone or jot down the coordinates and color. The relevant information for us is in the mouse position section. Referencing the above picture, we need to know the coordinates next to "Client:" (yours will definitely be different, this is only an example). So, according to the picture, we would note 1825, 841, and the color value CCA053.

 

Alright, first step complete. Take this information and plug your values into line number 43 (always leave 0x before putting your color value):

PixelSearch, x, y, 1825, 841, 1825,841, 0xCCA053, 50, Fast RGB

 

Next, we need to get Vivi's shadow after he has failed the jump rope game so we can automatically restart the script. Go ahead and manually fail the game until you get to where the girl says, "Come play with us again!". At this point, redo the step above getting Vivi's shadow location using Window Spy. Then place these numbers and the color value just as above but this time on line number 61. Here is an example (same idea as shown above, the numbers will not be the same):

; Detect if failed and back at the start to retry
PixelSearch, x, y, 1272, 1179, 1272, 1179, 0x2E2208, 50, Fast RGB

 

Now, you are well on your way. Don't resize the FFIX window or you will have to find Vivi's coordinates again!

 

Save the script and press "R" on your keyboard to reload the script. Get Vivi back into the position where he has a ! above his head and he is outside of the jump rope. Press the "A" key to run the script. There will be tooltips noting each jump and a number you can disregard. Make sure the in game jumps and the tooltip jump numbers are in sync. If not, you have other issues we may can work out. If you are failing on the first jump and are seeing a tooltip stating "Not detected, check coordinates and/or color" you will need to redo the above steps to find Vivi's shadow. Again, that part can be frustrating so try to be patient. If Vivi fails a jump, the script should automatically restart for you so leave it running. If it doesn't, recheck your pixel coordinates after Vivi has failed.

 

Here are a few disclaimers/notes:

I definitely have had some issues getting this to work. One day it worked great, then I had to make some significant logic changes to make it work the next day. I hope this will work for at least some people. If you get the pixel detection working right and it doesn't constantly fail on 20 or the same exact number each time, it should eventually work, so let it do its thing. I've had success running this script at different window sizes on my computer using the above steps.

 

Since I had so many issues between days, I wasn't going to adapt this to share, but then I read about how some physically can't do this achievement and I wanted to hopefully help at least someone.

 

Let me know if it works for anyone and if you have any questions, I will try to help. Good luck!

 

Full script:

Esc::ExitApp
r::Reload
CoordMode, Pixel, Relative

a::
Process, priority, , High

loop 
{
i = 1

; jump intervals
a = 667
b = 532
c = 467
d = 433
e = 383
f = 400

delay = 100
balancer = 0
currentInterval := a
extraTime = 0

ToolTip, start, 400, 400

; Initiate steps to begin
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.
Sleep, 2000
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.
Sleep, 3000
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", 100)
Send {Enter up}  ; Release Enter key.

; Detect position
	Loop 
 	{
	PixelSearch, x, y, 793, 977, 793, 977, 0x452400, 50, Fast RGB
 			If (ErrorLevel = 0) 
 			{
 				;sleep, 100
 				tooltip % "Detected shadow"
 				break
 			}
		else
		{
			tooltip % "Not detected, check coordinates and/or color"
		}
 	}

start := A_TickCount + 50

loop
{
	; Detect if failed and back at the start to retry
	PixelSearch, x, y, 1272, 1179, 1272, 1179, 0x2E2208, 50, Fast RGB
		If (ErrorLevel = 0) 
		{ 
			; reset
			tooltip % "Restarting"
			sleep, 3000
			Send {Enter down}  ; Press down the Enter key.
			DllCall("Sleep", "Uint", 100)
			Send {Enter up}  ; Release Enter key.
			sleep, 2000
			break
		}
	
	; Manual override
	GetKeystate, state, Enter
	if (state = "D" and stop = 0)
	{
		break
	}

	timer := A_TickCount - start

	if (i = 1) 
	{
		currentInterval := a
	} 
	else if (i = 20) 
	{
		currentInterval := b
		balancer = 0
	} 
	else if (i = 50) 
	{
		currentInterval := c
		balancer = 0
	} 
	else if (i = 100) 
	{
		currentInterval := d
		balancer = 0
	} 
	else if (i = 200) 
	{
		extraTime = 50
		delay = 70
		currentInterval := e
		balancer = 0
	} 
	else if (i = 260) 
	{
		extraTime = 20
		balancer = 0
	} 
	else if (i = 301) 
	{
		currentInterval := f
		balancer = 0
	}

	; If jumps are too late remove the = below
	if(i >= 1) 
	{
		DllCall("Sleep", "Uint", (currentInterval - timer + balancer + extraTime))
	}
	Gosub, jump
}
}
return 

jump:
fullTime := A_TickCount - start - extraTime
start := A_TickCount
if(i > 1) 
{
balancer += currentInterval - fullTime
} 
ToolTip, Jump %i% - %fullTime%, 400, 400
Send {Enter down}  ; Press down the Enter key.
DllCall("Sleep", "Uint", delay)
Send {Enter up}  ; Release Enter key.
ToolTip
i += 1
extraTime = 0
return

 

First of all, thank you for you effort and share this with us...

It's not working for me, i follow your instructions step by step but nothing, just one jump and fails, i do not know what I,m doing wrong, the only doubt i have is where the "vivi's shadow is"....

you mean to set the mouse pointer aproximately at vivi's feet?

I am not english native so I get confused sometimes

I added some pictures where i set the pointer to get the values

https://imgur.com/a/ojeX6ey

Thanks a Lot!

[Link2430]

First of all, thank you for you effort and share this with us...

It's not working for me, i follow your instructions step by step but nothing, just one jump and fails, i do not know what I,m doing wrong, the only doubt i have is where the "vivi's shadow is"....

you mean to set the mouse pointer aproximately at vivi's feet?

I am not english native so I get confused sometimes

I added some pictures where i set the pointer to get the values

https://imgur.com/a/ojeX6ey

Thanks a Lot!

 

Sorry about all of the edits, I was on my phone.

 

In your first picture, we don't need to detect the shadow at that point. We need to get Vivi into position where the game says 0 jumps and then check his shadow. This position looks like where Vivi is in your second picture.

 

So, in that case on line 43 in your script it should look like this:

PixelSearch, x, y, 416, 468, 416, 468, 0x462A00, 50, Fast RGB

 

For the second pixel detection, you need to have failed the jump rope game and check Vivi's shadow again when the girl says "Come play with us again!".

 

You should see a small message show up if the first detection doesn't work. If the script can't see it, then a small box will appear where you actual mouse pointer is stating "Not detected, check coordinates and/or color". If you see a small message stating "Detected shadow" then it worked, but that message doesn't stay on the screen for long.

 

Hope that helps.

Edited February 23, 2019 by Link2430