Reply To: 8K Instawin for devices other than NOX?

Forums Members Area Help 8K Instawin for devices other than NOX? Reply To: 8K Instawin for devices other than NOX?

#49164
GoofGoof
Participant

NOX only, the list changes position on pretty much every different phone / tablet so a universal list can’t be used.

What you can do though is work out where the list lies for your particular device and then save it. That saved list should then work for that particular phone every time you restart the game. Dinas made a nice tutorial showing how to search for your deck address and then move the GG list to the correct location: 

Couple of things:

  • The UI has changed a little bit since then, but the method is still mostly the same
  • Before you do any searching, tap the very bottom of the search screen where it says “Jh, Ca, Cb, A” etc and tick only ‘C++.bss’. This greatly reduces the number of bad values that appear in search by limiting the search to a select memory region.
  • The number he’s searching for is the number of cards left in the deck. Before the duel it’s 30, then he draws 4 cards; the deck now has 26 cards. Adjust this number to suit how many cards are in your deck and keep searching until you only have one address.
  • If the new ‘Var xxxxxxx’ address appears above the saved list instead of below it, enter a minus (-) sign in the ‘Change Address’ box before you paste in the copied offset value you found using the ‘Calculate Offset’ button.

Once you have the list in the right place you can edit it to achieve 8K instawin. Freeze XOR, Cards in Hand and both Deck values to 0. Freeze your LP to 1 and freeze the ‘Highest Effect DMG” to 10,000. Now save the list using the button to the right of the Load List button.

I’ve been meaning to make an updated guide for this but wasn’t sure if people really needed it or not. Post here if you want this and/or are having trouble with the guide. Not all android devices work with this, but most should.

PM me if you don’t get ‘LP on the brink’ in the duel assessment, this usually means XOR is wrong and can be a bit fiddly to find…