Zol'tun Kulle infinite turn in XP (Post-nerf)

[nav4321]

Mmnogodbaracc, do arears crate level 1 or do the core the azmodan quest, and you must make sure ur leecher char has 21%+ exp rewarded per kill gem and high exp per kill gear, you just keep going on and doing runs and aoe'ing like crazy, if you do it right, its easy 5-6 mil xp per hour

[CPCS0101]

Well, I see someone beat me to the punch on some AutoIt code, but here's what I got working for my setup. I use two separate computers so it's a little different. If nothing else, it's something for others to work off!

I modified his Booster / Leechers for 1920x1080, the booster is simply changing the pixel checks, so that's easy to post:

Global $Paused
HotKeySet("-", "TogglePause")
HotKeySet("{PGDN}", "Terminate")


WinActivate("Diablo III")
Sleep(20)
	While (True)
	$_waiting = True
	While ($_waiting) ;Wait for Party Request box
		;$_inviteCoords = PixelSearch(1695, 1015, 1725, 1045, 3798272)
		$_inviteCoords = PixelSearch(1726, 929, 1726, 929 ,0x36E400)
		If Not @error Then
			$_waiting = False
		EndIf
	WEnd
	;MouseClick("left", 1706, 1033, 1, 0) ;Click Accept on Party Request
	MouseClick("left",1727,930,1,0)
	Sleep(5000) ;Wait 5 seconds
	Send("{ESC}") ;Open Game Menu
	Sleep(500)
	;MouseClick("Left", 965, 645, 1, 0) ;Click Leave Game
	MouseClick("Left",965,580,1,0)
	Sleep(100)
	;MouseClick("Left", 840, 700, 1, 0) ;Click Accept dialog for leaving party/game
	MouseClick("Left",840,630,1,0)
	Sleep(5000)
	;MouseClick("Left", 260, 460, 1, 5) ;Resume Game
    MouseClick("Left",260, 414, 1, 5)
WEnd


Func TogglePause()
	$Paused = Not $Paused
	While $Paused
		Sleep(100)
	WEnd
EndFunc   ;==>TogglePause

Func Terminate()
	Exit 0
EndFunc   ;==>Terminate

The leecher, I almost completely rewrote so that the event handling is handled non sequential. This avoids hiccups, but the matchmaking issue is beyond annoying, will need to see if there's a way to give certain parts the ability to interrupt (though I doubt it). I also do unique searches to find the user (as it's not always the first in my list.. ) and as such, it will be completely unusable to anyone else. However if requested I can post the code so it can be modified to run on whoever's machine if they're savvy enough.

[CPCS0101]

I modified his Booster / Leechers for 1920x1080, the booster is simply changing the pixel checks, so that's easy to post:

Global $Paused
HotKeySet("-", "TogglePause")
HotKeySet("{PGDN}", "Terminate")


WinActivate("Diablo III")
Sleep(20)
	While (True)
	$_waiting = True
	While ($_waiting) ;Wait for Party Request box
		;$_inviteCoords = PixelSearch(1695, 1015, 1725, 1045, 3798272)
		$_inviteCoords = PixelSearch(1726, 929, 1726, 929 ,0x36E400)
		If Not @error Then
			$_waiting = False
		EndIf
	WEnd
	;MouseClick("left", 1706, 1033, 1, 0) ;Click Accept on Party Request
	MouseClick("left",1727,930,1,0)
	Sleep(5000) ;Wait 5 seconds
	Send("{ESC}") ;Open Game Menu
	Sleep(500)
	;MouseClick("Left", 965, 645, 1, 0) ;Click Leave Game
	MouseClick("Left",965,580,1,0)
	Sleep(100)
	;MouseClick("Left", 840, 700, 1, 0) ;Click Accept dialog for leaving party/game
	MouseClick("Left",840,630,1,0)
	Sleep(5000)
	;MouseClick("Left", 260, 460, 1, 5) ;Resume Game
    MouseClick("Left",260, 414, 1, 5)
WEnd


Func TogglePause()
	$Paused = Not $Paused
	While $Paused
		Sleep(100)
	WEnd
EndFunc   ;==>TogglePause

Func Terminate()
	Exit 0
EndFunc   ;==>Terminate

The leecher, I almost completely rewrote so that the event handling is handled non sequential. This avoids hiccups, but the matchmaking issue is beyond annoying, will need to see if there's a way to give certain parts the ability to interrupt (though I doubt it). I also do unique searches to find the user (as it's not always the first in my list.. ) and as such, it will be completely unusable to anyone else. However if requested I can post the code so it can be modified to run on whoever's machine if they're savvy enough.

Shortly after this I promptly changed it to be non sequential too lol, however handling the matchmaking error is becoming increasingly frustrating. It's as if you'll need to make a function and just call it over and over

EDIT: the reason for the above is that you don't "have" to wait for the matchmaking error to occur to continue the cycle. As such, this is about 2 to 7 seconds slower than the old infinite zk. However as mentioned this means that the matchmaking error is introduced randomly and as such, will most likely need to be checked randomly too

[alastor2262]

I modified his Booster / Leechers for 1920x1080, the booster is simply changing the pixel checks, so that's easy to post:
[
The leecher, I almost completely rewrote so that the event handling is handled non sequential. This avoids hiccups, but the matchmaking issue is beyond annoying, will need to see if there's a way to give certain parts the ability to interrupt (though I doubt it). I also do unique searches to find the user (as it's not always the first in my list.. ) and as such, it will be completely unusable to anyone else. However if requested I can post the code so it can be modified to run on whoever's machine if they're savvy enough.

i believe that you posted twice the booster code but not the leeecher one

[chumii]

Hey guys

I tried this by hand with a friend, but i get confused by all this "leave party" / "Leave game" stuff.. we managed to get the xp on the leecher about 5 times, but after that the leecher couldnt resume anymore..
what confuses me is

5. A take Soulstone, B leaves game.
6. B leaves game and turns in

What game should B leave at 6. if he already left the game on 5,?
and when exactly has the booster to leave his game after leecher accepted the invite?

oh, and this on ****ed my mind =)

Woink, The best way to do this without failing is to leave the party immediately after accepting the invite, You need to press escape several times, Once you have left party and you both are in the same party (As shown in my video) wait atleast 5-10 seconds before leaving the game with the HOST.

If I leave the party, how can we be in the same party? and how can anyone be in a game after leaving a party?? in my understanding, "leave party" in this case means to leave the game with the booster, but then i cant leave the game again after 5-10 seconds cause i already left it...

could anyone write that in a "for dummies" style please?? =)

[tsoul]

could anyone write that in a "for dummies" style please?? =)

So what you have to do:
A - booster
B - Leecher

1. A creates a game on Act II Quest 8, part 3 (enter Zoltan Kulle Chamber)
2. B joins.
3. A kills ZK. B stays in the city.
4. After ZK is dead B leaves game clicks "Resume Game", run for Black Soulstone, TP back to city, Turn quest in, Join A's game.
5. A take Soulstone, B leaves game.
6. B RESUMES game and turns in
7. (A must have the quest to turn in AND BE IN TOWN) the trick is that u must have auto join off , A sends B "INVITE TO Party" and B clicks accept. There will be a significant delay in joining the A's game. B WILL NEED TO LEAVE 5-8 SECONDS AFTER ACCEPTING INVITE TO PARTY.
8. B will see that both of you are in same party in the menu.
9.A will have to leave party AND GAME after 5-8 seconds (For this to work) and B resumes and turns in.
10.A Resumes and repeats step 7 to 9.

[Mimesis]

make sure he accepts invites (in the options)
also make sure that u do it on normal mode (unless u have killed diablo on normal/nm already)

it doesn't work for anyone on my friends list, not just the booster, can't request invite from anyone who isn't in the menu.

[cdkeys4trade]

this don't work anymore?

[Iaccidentallytwink]

I'm having tons of trouble with this new version of the exploit.

No matter what I do, I can't get it right every time so that the resume button is available after the booster leaves. I get an error every so often. Is there any indication of when to leave on each character?

[alastor2262]

I'm having tons of trouble with this new version of the exploit.

No matter what I do, I can't get it right every time so that the resume button is available after the booster leaves. I get an error every so often. Is there any indication of when to leave on each character?

got the same problem with the resume button, still dont know for sure if it is a timing issue or a lag issue, tryied a lot of different timing for both leecher and booster but still can get it right for more than 30 runs......

[nav4321]

I'm having tons of trouble with this new version of the exploit.

No matter what I do, I can't get it right every time so that the resume button is available after the booster leaves. I get an error every so often. Is there any indication of when to leave on each character?

Yeah, there is an indication, you can look a the AH button on the leecher, once it blinks that means u need to leave party, pm me or something so i can help you out or give me your skype mate if this doesnt help.

[CPCS0101]

Hey guys

I tried this by hand with a friend, but i get confused by all this "leave party" / "Leave game" stuff.. we managed to get the xp on the leecher about 5 times, but after that the leecher couldnt resume anymore..
what confuses me is



What game should B leave at 6. if he already left the game on 5,?
and when exactly has the booster to leave his game after leecher accepted the invite?

To be honest, the first few steps are extra fluff. lol, old school way of getting the credits. You can easily perform this from step from Step 7. Here's basically how it works.

Player A (Booster) in a game that is on the turn in portion, Player B in a totally separate game, doing I don't care so long as he is actaully in a game.
Player B Requests an invite from Player A
Player A accepts the request, which automatically sends an invite to Player B
Player B accepts the invite, which causes a really long pause between B joining A's game
As soon as possible, Player B leaves his GAME (not party), which takes him back to the dashboard
Player B will now see that he's in a party (this is due to the lag time between joining another game) because he's on the dashboard and there's still 2 people on the screen
Player A then leaves his game, this "disbands" the party.
Player B will at this point be waiting for the "Resume" option to become valid. This SHOULD happen as soon as Player "A" leaves the party.
Because the game is still technically registered player B as joining Player A's game, when he resumes he is on the same step as Player A, in his own game.
Player B turns in
Player A resumes a fresh hot biscuit

Cue random "matchmaking" error that occurs, on player B's side.

oh, and this on ****ed my mind =)



If I leave the party, how can we be in the same party? and how can anyone be in a game after leaving a party?? in my understanding, "leave party" in this case means to leave the game with the booster, but then i cant leave the game again after 5-10 seconds cause i already left it...

could anyone write that in a "for dummies" style please?? =)

Your assumption is correct, leave is leave game, never party.You should never truly ever be in a game with the booster, ever. you'll be in a party, yes, but following the above, you'll only ever see the booster when on the dashboard.

[CPCS0101]

Yeah, there is an indication, you can look a the AH button on the leecher, once it blinks that means u need to leave party, pm me or something so i can help you out or give me your skype mate if this doesnt help.

Ingenious, though with 2 computers there's no easy way to link them, it does allow for those to figure out their own time intervals between one PC and the other.

so let's try this agan, remodified the script to the following for the booster: (1920x1080)

Global $Paused
HotKeySet("-", "TogglePause")
HotKeySet("{PGDN}", "Terminate")

While(True)
WinActivate("Diablo III")
Sleep(20)
	  PixelSearch(1726, 929, 1726, 929 ,0x36E400) ;Looking for Invite Check Box
	  If Not @error Then
		 MouseClick("Left",1727,930,1,0) ;accept invite check
	  EndIf

	PixelSearch(18,694,18, 694,0x69160E,1,1) ;wait for message about player joining party, this may be unique and will need to be modified
	If Not @error Then
	   Sleep(5200)
	   Send("{ESC}")
	   Sleep(200)
	   MouseClick("Left",965,580)
	   Sleep(100)
	   MouseClick("Left",840,630)
	   Sleep(2000)
	EndIf
   
	PixelSearch(940, 631, 940,631, 0x330800, 1,1) ;If an error has occured, catch it (canont create game?)
	If Not @error Then
	   MouseClick("Left", 940, 631)
	EndIf
	
	PixelSearch(152,419,152,419,0x3F0900,1,1) ;Click Resume
	If Not @error Then
	   MouseClick("Left", 152, 419)
	EndIf
WEnd


Func TogglePause()
	$Paused = Not $Paused
	While $Paused
		Sleep(100)
	WEnd
EndFunc   ;==>TogglePause

Func Terminate()
	Exit 0
EndFunc   ;==>Terminate

And as for the leacher... (remember that there is most def. Unique code in this) (also 1920x1080):

Global $Paused
Global $stallercounter
HotKeySet("-", "TogglePause")
HotKeySet("{PGDN}", "Terminate")

WinActivate("Diablo III") ;Bring Diablo to foreground
Sleep(20) ;Slight delay to allow Diablo to maximize

While (True)

PixelSearch (892,582,892,582,2229248,1,1)
If Not @error Then
   ;Sleep(1000)
   Call ("MatchError")
   MouseClick("Left", 892,582)
   Sleep(500)
   PixelSearch(826,628, 826,628,2491648,1,1)
   If Not @error Then
	  Call("MatchError")
	  MouseClick("Left", 825,633,1,0)
   EndIf
EndIf

PixelSearch (891,579, 891,579,590852,1,1)
If Not @error Then
   Send ("{ESC}")
   Sleep(500)
   Send ("{ESC}")
EndIf

PixelSearch(1856,1008,1856,1008,0x200100,1,1) ;look for open friends list
If Not @error Then
   $stallerCounter = 0
   For $i = 339 to 879 step 54
	  $coord0 = PixelSearch(1468, $i , 1468, $i , 0x547B9C,1,1) ; THIS IS UNIQUE CODE TO SEARCH FOR A SPECIFIC PERSON
		 If Not @error Then										; IT WILL NEED TO BE MODIFIED TO MATCH YOUR BOOSTER, GLUCK
			PixelSearch($coord0[0] + 74, $coord0[1] + 14, $coord0[0] + 74, $coord0[1] + 14, 0x44647E,1,1)  ;ALSO UNIQUE CODE
			If Not @error Then
			   MouseClick("Right", $coord0[0], $coord0[1],1,0)
			   Sleep(500)
			   MouseClick("Left", $coord0[0] + 26, $coord0[1] + 144,1,0)
			   Sleep(10)
			   Send("O")
			   ExitLoop
			EndIf
		 EndIf	
	  Sleep(10)
   Next
EndIf

$coord11 = PixelSearch(300,400,800,700, 10416639,1,1) ;Checking for Waypoint1
If Not @error Then
   Call ("WaypointCheck",$coord11)
EndIf

$coord12 = PixelSearch(300,400,800, 700, 7693172, 1,1) ;Checking for Waypoint2
   If Not @error Then
   Call ("WaypointCheck",$coord12)
EndIf

PixelSearch(1272,791,1272,791, 4854272,1,1) ;Forgot what this is for lol
If Not @error Then
   $stallerCounter = 0
   Call ("MatchError")
   Send("{ESC}")
   Call ("MatchError")
   Send("{ESC}")
   Call ("MatchError")
   Send("O")
EndIf


PixelSearch(900,290,960,300, 0xFF0000,1,1) ;If for any reason it fails, we still talk to adria and still want to continue
If Not @error Then
   $stallerCounter = 0
   Send("{Esc}")
   Call ("MatchError")
   Send("O")
EndIf

PixelSearch(150 ,417 ,150 ,417 , 1772552, 1,1) ;If stuck in infinite resume game grey (!?)
If Not @error Then
   $stallerCounter = $stallerCounter + 1
   If $stallerCounter > 50 Then ;Clearly we're not supposed to be here
	  Send("O")
	  $stallerCounter = 0
   EndIf
EndIf

PixelSearch(151,417,151,417,3934976,1,1) ;Not Sure, resume i believe
If Not @error Then
   $stallerCounter = 0
   MouseClick("Left", 151, 417,1,0)
   Sleep(100)
EndIf

PixelSearch(1726,931,1726,931,3799808,1,1) ;Search for accept request
If Not @error Then
   $stallerCounter = 0
   $exitif = False
   PixelSearch(831,632,831,632,3738624,1,1)
   If Not @error Then
	  MouseClick("Left", 831,632,1,0)
	  $exitif = True
	  Call ("MatchError")
	  Send("{Esc}")
   EndIf
   If Not $exitif Then
	  MouseClick("Left", 1726,931,1,0)
   EndIf
   Sleep(100)
EndIf

PixelSearch(935,635,935,635,4000000,1,1) ;Unable to Join Game Check
If Not @error Then
   $stallerCounter = 0
   MouseClick("Left",935,635,1,0)
   Sleep(100)
EndIf

Wend
Func TogglePause()
	$Paused = Not $Paused
	While $Paused
		Sleep(100)
	WEnd
EndFunc   ;==>TogglePause

Func Terminate()
	Exit 0
 EndFunc   ;==>Terminate
 
 Func WaypointCheck($coord)
   MouseClick("Left", $coord[0] , $coord[1])
   Sleep(1000)
   MouseClick("Left", 686, 75)
EndFunc

Func MatchError()
PixelSearch(936,632,936,632,3804160) ;look for the matchmaking error
   If Not @error Then
	  MouseClick("Left",936,632,1,0)
	  Sleep(200)
	  ;MouseClick("Left",1856,1008)
   Else
	  Sleep(200)
   EndIf
EndFunc

G'luck and have fun

EDIT: It's important to note, that if the script is failing it may be required to adjust the wait time before leaving games. It was working fine for 30m, so i posted it, but shortly after the booster was leaving a half-second too soon, so increased 5200 to 6000 and it's back to fine.

[nhcoohrh]

Well I don't understand why you guys try to find "sleep" times in a blind way to get this working.

I analyzed the "bug" with 2 machines.

1st) the host was just accepting the invite a small pause (to not break the invite process, because we need to confirm on leecher) leave game w8 a while in menu and comeback to game.

Now by hand I analyzed what happen on the on the leecher side.

From Menu, I make request invite, get confirmation and accept again. Then what we see it's that when the Host goes to menu, the Resume button becomes available, we could join and deliver the quest and leave game. So my theory its this.


- Host creates GAME#1
- Leecher request to join GAME#1
- Host accepts.
- Leecher Confirms. (now the request to pull Leecher to GAME#1 went to the server and this takes much time to proccess normaly, but is already inside the party because Host got that information). I will call the this "RequestJoinGAME#1"
- Host leaves GAME#1 and go to menu.
- Leecher , before be pulled by server to GAME#1 and when Host breaks the party, have possibility to join GAME#1 if his at menu. (thats why you can invite at menu no need to be ingame). Note the Resume button it's only available when the HOST break the party (we got information that host leaves party on leacher).

Next:
If we stay ingame with leacher after quest delivered, we will get a error message from the server regarding the "RequestJoinGAME#1" that is no more possible since host break the party.

If we deliver and exit game, we avoid this error message, however the "RequestJoinGAME#1" it's still there, so if we just click on Request Invite party and host accepts, we will not need to confirm, because the leecher will be pulled to GAME#1 even if host is already on GAME#2.

the question here it's how to handle better with this error messages of Server and loop this.

We basically have a small window after party is break and before the joingame process finish. Seams that when we do the request ingame, and know when host break the party if we leave join old game deliver and w8 for the error message we could work on this method.

You leecher just need to know when host is at menu and break the party.

[CPCS0101]

Well I don't understand why you guys try to find "sleep" times in a blind way to get this working.

I analyzed the "bug" with 2 machines.

1st) the host was just accepting the invite a small pause (to not break the invite process, because we need to confirm on leecher) leave game w8 a while in menu and comeback to game.

Now by hand I analyzed what happen on the on the leecher side.

From Menu, I make request invite, get confirmation and accept again. Then what we see it's that when the Host goes to menu, the Resume button becomes available, we could join and deliver the quest and leave game. So my theory its this.


- Host creates GAME#1
- Leecher request to join GAME#1
- Host accepts.
- Leecher Confirms. (now the request to pull Leecher to GAME#1 went to the server and this takes much time to proccess normaly, but is already inside the party because Host got that information). I will call the this "RequestJoinGAME#1"
- Host leaves GAME#1 and go to menu.
- Leecher , before be pulled by server to GAME#1 and when Host breaks the party, have possibility to join GAME#1 if his at menu. (thats why you can invite at menu no need to be ingame). Note the Resume button it's only available when the HOST break the party (we got information that host leaves party on leacher).

Next:
If we stay ingame with leacher after quest delivered, we will get a error message from the server regarding the "RequestJoinGAME#1" that is no more possible since host break the party.

If we deliver and exit game, we avoid this error message, however the "RequestJoinGAME#1" it's still there, so if we just click on Request Invite party and host accepts, we will not need to confirm, because the leecher will be pulled to GAME#1 even if host is already on GAME#2.

the question here it's how to handle better with this error messages of Server and loop this.

We basically have a small window after party is break and before the joingame process finish. Seams that when we do the request ingame, and know when host break the party if we leave join old game deliver and w8 for the error message we could work on this method.

You leecher just need to know when host is at menu and break the party.

Because there seems to be some kind of interval time that the leecher is still in their own game and leaves before the host leaves. If you do it via your method, after a quick 6 attempts, the resume button never becomes available, this might just be horrible luck and proves that it's just the server's determination to figure out where you are, but.

my original script doesn't use waits, it relied on prompts. I'm still getting only a 50% success rate though, so let's try using this method and see what happens.

EDIT: My results are less with the back to home screen method , more like 30%. It's really based on the server's interpretation of whose game you're in.

EDIT2: Still testing, but it seems that, regardless of how or where you request the invite, the closer you are between the Booster leaving the game and the server autojoining the leecher, the more successful you are. So if you delay the booster, you're more likely to get it to resume the proper game.