Gecko dotNET Bugs and Requests

[Bully@Wiiplaza]

I have to report some geckodotnet issues again (the first two are happening to WiiRD,too!) :p

Game: The Conduit
- If I applyed a C2 code, it works fine. But if I press apply a SECOND time, while the code is already written into the disassembly, it CRASHES! The code itself is right and working! It always crashes when doing this. Note that this only happens to "The Conduit" On some other games, it already got fixed.
- Second issue is that if you do a memory search, the game takes extremely long time to "run" again.
Example: I made a Mem90 Dump and searched for 00000006. When it reached it´s 100%, it displays the results, BUT the game was only running again after 10 more seconds of waiting!! Why does it take longer? (Only happenes to The Conduit) ???
- Third is a general issue on adding codes. If you rightclick something and press gct codes, it will ask you: "Enter the new codename!"
There, you can press OK and CANCEL. But if you select CANCEL, it will STILL add the code to the list. Normally, cancel should NOT add the code, if you press it. (If you select OK, it just adds the code aswell, but it should only do it, WHEN pressing YES xD :P)

Bully...

[dcx2]

1) Do you have "Pause While Sending" checked?  It sounds like this would solve the problem you're having.  If it doesn't, I still have another suggestion for you...but PWS always fixed that problem for me.

2) Weird...try pausing before searching and then unpausing after it's over and let me know how that worked out for you.

3) lol, you're right, the cancel button wasn't wired up properly.

4) Re: FST, I think I'm going to say Original and...Replacement?  New?  Destination?

5) I'll look into the Notepad DelCurSheet_Click.  I've never touched the Notepad stuff before, really.

6) I think the zombie process is caused by the watch list, perhaps...so I'm going to try to rework how that runs.

[Bully@Wiiplaza]

1) Do you have "Pause While Sending" checked?  It sounds like this would solve the problem you're having.  If it doesn't, I still have another suggestion for you...but PWS always fixed that problem for me.

2) Weird...try pausing before searching and then unpausing after it's over and let me know how that worked out for you.

1.) hmm... I didn´t use "Pause While Sending"
Anyway, it froze even with it enabled in the past (I think)
But I will try again, maybe it got fixed somehow :D

2.) If this works? Seems too easy and I could bet that I tried this too.
I´ll also do it again.

3.) Would be good, if you can fix the cancel issue, it is a bit annoying if you don´t want to add the code, but it does though... ::)

[Bully@Wiiplaza]

k James.
now I´m coming back to The Conduit!

- I ticked Pause while sending and sended a C2 code
- Now, if I send again ANY code, if ASM or not, the game crashes (but only if I had applyed an ASM code before)
WHY?? This is weird and annoying... I wish I could make every code without ASM to prevent crashes.
How could I/someone fix this? :confused:

[dcx2]

Hold on there...you can't just remove a C2 code on-the-fly!  It will create a "dangling branch" that will cause your game to crash.  You should be able to replace the C2 code with another C2 code.  Or if you want to "unhack" the code, you must replace the branch with the original instruction.

Imagine using an 04 write to nop out a stw.  Now imagine you want to turn this hack off.  If you disable your code on-the-fly...your code will still be on.  That's because nothing wrote the original stw back.  That's your responsibility, and thus why I added History to the disassembler, so you could unhack ASM patches at will.  If you C2'd the stw instead of nop'ing, the same rules apply; nothing writes the original stw over the b to the C2's ASM...but if you disable the C2 code, the b doesn't go to that ASM anymore...fail.

I actually have a copy of the Conduit somewhere...got it from newegg for like $8 or something...I will take a look at this.  I'm assuming yours is PAL though, huh?  If you want to be extra-safe, uncheck Pause While Sending, and then manually pause the game before applying codes, and then check every address that you've ever C2 hooked in the disassembler tab.  If you don't see the original instruction, write it in.  After you've checked all addresses, you can hit Run Game again.  Sorry if that's hard...no one ever said hacking was easy.

Some tips that might help...you can edit your code in the disassembler tab.  You can't add lines, but you can nop stuff and modify lines.  Set a breakpoint on your C2 hook address, and then Step Into.  Then switch to the Disassembler tab and you'll see your code.

[Bully@Wiiplaza]

you were right, writing back the original instruction and then apply back some codes doesn´t cause a crash.
Btw. I posted something to the game hacking help related to The Conduit xD
If you can take a look at it for your own, it may be easier.

[James0x57]

Since there's the search history now; a sweet feature would be to "highlight results with a pattern" or "eliminate results that aren't in a pattern".


example usage:
I have 3 items and want to find which one I have out. So I'll switch, unknown search, switch, unknown search, repeat repeat.
If I keep searching when I switch the items in the same order and don't skip any, then I press the pattern results button and it will show me which addresses have values that follow a repeating pattern in the search history!

A number field that gives the length of the pattern (so I'd do 3 for the example above) would make the checking algorithm much faster.




Also could be useful for finding coordinates (the Y coord would be easiest if you moved between different-height flat areas).
Anything that could be repeated but is unknown would benefit from a post-search filter like this! =)

[Bully@Wiiplaza]

request:
multi select adresses in the memory viewer (strg + click) and able to create the whole code with gct wizard like it´s possible on the search tab

[Romaap]

request:
multi select adresses in the memory viewer (strg + click) and able to create the whole code with gct wizard like it´s possible on the search tab

strg = Ctrl on non-German keyboards. ;)

[Bully@Wiiplaza]

request:
multi select adresses in the memory viewer (strg + click) and able to create the whole code with gct wizard like it´s possible on the search tab

strg = Ctrl on non-German keyboards. ;)

damn, forgot that, LOL :eek:

[dcx2]

I think the Memory Viewer was originally designed so that only one cell could ever be selected.  There are a lot of assumptions based on being able to select only one cell at a time.  So I doubt that I will do that...sorry.

Regarding the search result pattern, the problem really becomes "how do you specify a pattern?"  I find it easier to just scroll through the Search History Old up/down, and delete the results that don't match the pattern I'm interested in.

[Bully@Wiiplaza]

I think the Memory Viewer was originally designed so that only one cell could ever be selected.  There are a lot of assumptions based on being able to select only one cell at a time.  So I doubt that I will do that...sorry.

and how would you test about 6 adresses on a memory viewer site very fast, if they are doing something?
poking them is a bit slow and it isn´t as good as freezing the value :confused:

[Bully@Wiiplaza]

i got another idea:

can it be done?
...that geckodotnet searches about 5 seconds in the RAM, then it unpauses and let it run the game run for about 1 sec, then search again for 5 sec and so on till the search is complete? :P
This is not useless for sure, I could need it sometimes :D

[James0x57]

I suspect that you only want that so you can hack online.. Searching like that would very much limit your range of hacks too...

[Bully@Wiiplaza]

Searching like that would very much limit your range of hacks too...

why would it limit anything? :confused: