Register - Login
Views: 99386782
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
04-24-22 05:35:54 AM
Jul - The Cutting Room Floor - Converting Cheat Engine to Gameshark [and vice versa] New poll - New thread - New reply
Next newer thread | Next older thread
sup3rsloth
Random nobody
Level: 3


Posts: 1/1
EXP: 47
For next: 81

Since: 01-23-16


Since last post: 6.2 years
Last activity: 6.2 years

Posted on 01-23-16 12:48:32 PM Link | Quote
So I'm playing around with Cheat Engine at the moment and seeing what I can change in Kirby 64.
I'm trying to figure out if there is an easy way to work out the Gameshark address based on the Cheat Engine address and vice versa.

So for example I know that a Gameshark code to change kirby's ability to double fire is:


Gameshark: 8012E853 0008 


where "12E853" is the memory address and "0008" is the ability number.

I have found that this changes this cheat engine address appropriately:

Cheat Engine: 3756E850 0008


So in theory if I find the difference between the Cheat Engine address and the Gameshark address, I should be able to apply that to convert other addresses.

So in this case,

Cheat Engine Address - Gameshark Address 

= 3756E850 - 12E853
= 3743FFFD (let's call this the Hex Difference)


Using this logic, I've wanted to find the address where current health is stored by going backwards from the infinite health Gameshark code I have. To find the Cheat Engine address, I have gone

 Gameshark Address + Hex Difference

= 0D6E50 + 3743FFFD
= 37516E4D


My question is: if I ultimately want to find and create new Gameshark codes, is this the right way of going about it? Doing things this way is giving me mixed results at the moment..

Cheers guys

ps. if there is a proper name for the hex difference, let me know
Next newer thread | Next older thread
Jul - The Cutting Room Floor - Converting Cheat Engine to Gameshark [and vice versa] New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

27 database queries.
Query execution time:  0.094279 seconds
Script execution time:  0.004155 seconds
Total render time:  0.098434 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 224 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 207 column 17 - Warning: missing <tr>
line 207 column 17 - Warning: discarding unexpected <table>
line 210 column 35 - Warning: missing <tr>
line 210 column 50 - Warning: missing </font> before </td>
line 210 column 91 - Warning: missing </font> before </table>
line 212 column 35 - Warning: missing <tr>
line 212 column 50 - Warning: missing </font> before </td>
line 213 column 37 - Warning: unescaped & or unknown entity "&id"
line 212 column 224 - Warning: missing </font> before </table>
line 214 column 17 - Warning: discarding unexpected </textarea>
line 214 column 28 - Warning: discarding unexpected </form>
line 214 column 35 - Warning: discarding unexpected </embed>
line 214 column 43 - Warning: discarding unexpected </noembed>
line 214 column 53 - Warning: discarding unexpected </noscript>
line 214 column 64 - Warning: discarding unexpected </noembed>
line 214 column 74 - Warning: discarding unexpected </embed>
line 214 column 82 - Warning: discarding unexpected </table>
line 214 column 90 - Warning: discarding unexpected </table>
line 216 column 9 - Warning: missing </font> before <table>
line 228 column 25 - Warning: discarding unexpected </font>
line 237 column 37 - Warning: discarding unexpected </font>
line 215 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 21 - Warning: <img> lacks "alt" attribute
line 161 column 62 - Warning: <img> lacks "alt" attribute
line 161 column 110 - Warning: <img> lacks "alt" attribute
line 161 column 160 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 204 column 1760 - Warning: <img> proprietary attribute value "absmiddle"
line 204 column 1760 - Warning: <img> lacks "alt" attribute
line 213 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 213 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 213 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 222 column 25 - Warning: <img> lacks "alt" attribute
line 227 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 207 column 17 - Warning: trimming empty <tr>
line 210 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 66 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md