(Do not post here if you need help getting XCXGecko to run; read this thread instead)
I've added the ability in XCXGecko to change the offset, applied to all code addresses. This is meant to support people using different firmware / payload configurations, as the base memory addresses are different (urgh).
I'd like to get a few people to test this beta release of XCXGecko and make sure it works. I myself have confirmed that it still works with WiiU 5.3.2 + Loadiine (MiiMaker + pyGecko) + pyGecko (Loadiine 5.3.2) payload configuration. I'd welcome feedback from people with the following setups:
I've added the ability in XCXGecko to change the offset, applied to all code addresses. This is meant to support people using different firmware / payload configurations, as the base memory addresses are different (urgh).
I'd like to get a few people to test this beta release of XCXGecko and make sure it works. I myself have confirmed that it still works with WiiU 5.3.2 + Loadiine (MiiMaker + pyGecko) + pyGecko (Loadiine 5.3.2) payload configuration. I'd welcome feedback from people with the following setups:
- 5.5.x, disc/e-shop (to confirm default offset)
- 5.3.2/5.4.0, OnionKnight's Loadiine v4 + pyGecko combined payload (I couldn't find this payload on new exploit index sites, so maybe it has been deprecated)
- 5.5.x, Loadiine, US copy of XCX
- 5.5.x, Loadiine, EU copy of XCX
- 5.5.x, Loadiine, JP copy of XCX
Pedantic Tips:
- after opening GUI, toggle Offset dropdown in toolbar to match your setup, then connect to WiiU
- start by reading your funds or miranium, and confirm correct values
- don't trust the labels for the Offset dropdown entries. If you know the offset for your setup, enter it (in decimal), test to confirm a few working READ/POKEs, then reply here to let me know
- if you change Offset, you should ideally re-cache item/gear slots (d'uh)
Last edited by MiMiCAX,