Wiki - GameHacking.org - User contributions [en]

CMX

2009-05-03T20:03:01Z

Parasyte:

===Known Information===
----
'''Name''': Bryan Thomas Black 
'''Residence:''' Waterloo, Illinois 
'''Occupation''': Owner, and founder of <s>[[CMGSCCC]]</s> [[CodeTwink]]. 
'''Felony Conviction''': Plead guilty to copyright infringement charges on March 6, 2009. Scheduled to be sentenced on May 26, 2009. [[http://www.usdoj.gov/opa/pr/2009/March/09-crm-203.html USDOJ]]
== External Links ==
*<s>[http://cmgsccc.com CMGSCCC.com]</s> [http://codetwink.com CodeTwink.com]
*[http://fedcmx.ytmnd.com/ YTMND - CMX Gon' Give It To Ya!]

[[Category:People]]

EnHacklopedia

2009-01-27T04:23:26Z

Parasyte:

{{Template:EnHacklopedia Header}}

This is the [[GSHI]] port of '''EnHacklopedia'''; a hacking document that originated from [[Kodewerx]]. The original version had laid dormant for nearly a year which necessitates this.

Hopefully this port will bring life back in to what once was a very promising hacking document.

Enjoy and please feel free to contribute whatever you can,

''--GSHI Staff''

==External Links==
*[http://doc.kodewerx.org/ Original EnHacklopedia]
*[http://www.bsfree.org/hack/ EnHacklopedia - BSFree.org Mirror]

{{EnHacklopedia}}

{{Template:EnHacklopedia Legal}}

[[Category:GSHI pages]]

Kodewerx

2007-01-07T03:20:33Z

Parasyte: /* '''The Users''' */ Spelling.

[[Image:Kodewerx.png ]]

== '''Kodewerx''' ==

The origins of Kodewerx go back to March 5th, 2002, when the original "Codewerx" website launched in retaliation against GSCentral and their holier-than-thou attitudes. It should be no surprise that the new Kodewerx was launched for similar reasons. This time around, with a slightly different name (due to domain name issues) and a much larger supporting user base.

Kodewerx was founded on October 1st, 2006, and launched the Kodewerx Content Manager (KCM) project. KCM is designed on the idea that a website's users are its most important asset. KCM gives its users a certain level of control over the website content.

== '''The KCM''' ==

KCM is a Content Management System based around phpBB v2.0.21. It installs alongside phpBB and uses some of its configuration settings automatically, to easily integrate into your current phpBB environment.

KCM is designed as a community-driven website, where your users control the content in a weighted-voting manner. Users can add their own categories and sub-categories, which will initially be placed into "New Submissions". At this point, other users are able to vote 'yes' or 'no' for these categories to be added to the site permanently. Once added permanently, a category can be requested for deletion by any user, whereby other users can vote 'yes' or 'no' for permanent removal from the site.

In addition to submission and deletion of categories and sub-categories, the owner of the category as well as administrators and moderators may edit the categories as required. Moderators can be assigned to access KCM moderation features through customizable phpBB Usergroups.

Content creation under categories and sub-categories is supported by configurable content formats, defined by regular expressions. All content creation is handled in the same way as categories and sub-categories, with a weighted voting system and administrator and moderator control.

Finally, user-submitted content can be limited to phpBB Usergroups, if you prefer to have a more 'open' or 'secure' content submission medium.

A standard phpBB forum can be linked to the KCM news page. Each initial post for any topic posted to the KCM news forum will appear on your KCM home (news) page. The number of news posts displayed is configured by the "Posts Per Page" setting in your phpBB configuration.

== '''The Users''' ==

The users of Kodewerx range from Beginner hackers to the average user just looking for gaming codes. The leader of this said "Kommunity" is Parasyte in which he is notorious for his Nintendo WiFi hacking. The Kodewerx "Kommunist Kommunity" ,as it has been labeled by the owner and users, only has 3 active female members.

== '''Sage and BOsKO "The Kodewerx Gals"''' ==

Sage and BOsKO have been known to stir up trouble, but are very active in not only the Kodewerx IRC channel, but also their forums and their "Kommunity". They defend their fellow Kodewerx and GSHI users against the evil users and code stealers of GSCentral, which has become known as GaySexCentral. BOsKO coming from California, and Sage from Wisconsin; they use their heads in the game.
And there is one more, Mewy, she´s not active at the Kodewerx IRC channel, but she´s also against GSCentral, just like Sage and BOsKO.

== '''GaySexCentral (The Code Stealers)''' ==

It's a known fact that the Kodewerx Krew members were once a part of GSCentral. Since their divisions, a lot of "trollers" have come about on all three forums: Kodewerx, GSHI, and GSCentral. Most of them come from GSC, looking to talk about another member on their forum or IRC channel or, in most cases, to steal codes. Rune, the leader of this chaotic circus, has no code database. It has been rumored that Rune is too afraid to post. Others say that he's stealing more codes to form a database. The users of GSC say that he's just waiting for his brother "Rob". Whatever the deal is, no one will know.


== External links ==

*[http://kodewerx.net/ Kodewerx Website]
*[http://kodewerx.net/forum/index.php Kodewerx Forum]

Assembly Hacking

2007-01-07T03:18:39Z

Parasyte: /* NES */ Added some name history.

=Overview=

Assembly hacking is the art of editing a compiled program. Without the source code, and without notes from the source code, one has to deduce almost everything about the underlying code, and how it works with RAM.

There are several emulators that can aid one in creating a modification for a game. Games for console systems fall into the category of compiled programs, and generally, the source code is unavailable for these games.

The use of making an assembly hack for a game can be found with the Nintendo Entertainment System (NES) [[Game Genie]].

The codes that are entered into an NES Game Genie represent single-byte assembly hacks. Any assembly hack that could be done with a change of 3 bytes or less is possible to implement with a single Game Genie. The SNES Game Genie allows up to 5 codes, and 5 bytes of change. While this makes the possible usage of codes very limiting, it didn't prevent single-byte invincibility and infinite lives codes from appearing that could make it unneccesary to use additional codes.

For more modern assembly hacking of the same systems, emulators that support 50 or more codes for any given game aren't uncommon. The ROMs have been turned into files that can be patched with all the changes needed to give the game a script in a new language. Emulators that aid in the process of making assembly hacks have appeared for many different emulated systems. The effect is that more people are now capable of starting their own projects, and existing projects can be modified and/or repaired more easily.

=Emulators=

==NES==
FCEUXDSP 
http://www.the-interweb.com/serendipity/index.php?/categories/9-FCEUXD-SP

A project originated by Parasyte called FCEUd, picked up by bbitmaster and renamed to FCEUXD, and finally adopted as FCEUXD SP.

Setting breakpoints in ROM/RAM
Tools>Debug

In the breakpoint window, 'Add' the Executable address or Memory address you want. 
ROM is 8000-FFFF 
RAM is 0000-07FF, 6000-7FFF 
0800-3FFF is mirrored from some part of RAM. 
4000-4015 can be breakpointed if working on an NSF. If the 'Hex Editor' is opened in a normal game, then an NSF is loaded, you can use it to work on NSF RAM, in conjunction with the debugger.

'Hex Editor' is a memory viewer/modifier.

==SNES==
Geiger's SNES9X Debugger 
http://geigercount.net/crypt/ 
http://www.zophar.net/snes.html

Setting breakpoints in ROM/RAM 
Open ROM, Click 'Breakpoints' 
In the breakpoint window, enter the Executable address or Memory address you want. 
Standard RAM: 7E0000 - 7FFFFF 
SA1 RAM: 400000-407FFF, 303000-303FFF 
HiROM - C00000 - FFFFFF 
LoROM - 808000-BFFFFF (**0000 - **7FFF doesn't exist)

If you use the [[SA1]] logger with an SA1-using game, and wish to find an address that changed an address in RAM, you can see if the conversion chart on the [[SA1]] page shows you the address to search for in the log file.

==Genesis==
Gens Tracer 
http://www.romhacking.net/?Category=&Console=0&Game=0&Author=0&Recm=&Level=&utilsearch=++Go++&title=Gens+Tracer&dsearch=&page=utils&action=utillist

No breakpoints, but adequate tracing.

I've written a guide on the specific usage of the emulator.

The idea is that you can trace-log writes to and reads from memory, and you can also log all commands, and determine what's happening from the full log, by using what you find from the hook logging.

HazeMD 
http://haze.mameworld.info/

This emulator is harder to get setup to use a ROM, but comes with a MAME-style debugger. MAME's debugger is well known for being so powerful, considering the number of systems it can be used with when compiled into a build of MAME. The Gens tracer tends to have slightly better compatibility, while the HazeMD emulator has more potential for cheat codes, already having a Cheat system designed to handle multiple CPUs, which could be used for 32x game ROM hacks, and RAM hacks.

==Gameboy==
BGB 
http://bgb.bircd.org/

Load a ROM, and right-click the screen. 
Other>debug mode enabled: to enable debugging 
Other>debugger to enter the debugger 

Setting breakpoints in ROM/RAM 
In the debugger window: 
Debug>breakpoints for execution breakpoints 
Debug>access breakpoints for read/write breaks. 

==Gameboy Advance==
Visual Boy Advance Tracer 
http://www.romhacking.net/?Category=&Console=10&Game=0&Author=695&Recm=&Level=&utilsearch=++Go++&title=&dsearch=&page=utils&action=utillist

This emulator uses the Hook Log system. Those familiar with the hook_log Genesis or N64 emulators should have little trouble adapting to this system.

Visual Boy Advance 
http://vba.ngemu.com/downloads.shtml 
Windows - SDL

Unfortunately, no cheat device exists that can change the assembly, so hacking it is more a matter of patching the ROM, and less a matter of using it for simple cheats.

Not documented.

==Playstation==
PCSX 1.5 With Debugger 
http://www.romhacking.net/?Category=&Console=0&Game=0&Author=0&Recm=&Level=&utilsearch=++Go++&title=PCSX+1.5+With+Debugger&dsearch=&page=utils&action=utillist

Press F11 to enter the debugger. 
On-screen aids should be apparent.

==N64==
Nemu64 (Project64 debug version for testing, etc.) 
http://www.nemu.com/downloads.php 
http://www.thegshi.org/downloads/Project64%20Build%2052%20Debug%20Binary.zip

Setting execution breakpoints 
Plugins>Debugger: Commands... 
To set a break on execution, go to the line that you want to break on, and click in the vertical bar to the left(<) of the address you want to breakpoint.

Setting breakpoints in RAM 
Plugins>Debugger: Memory... 
Enable the read and/or write checkboxes, and right-click the memory space you want to set, unset, or change an access breakpoint on.

Some games don't run in Nemu, so you may have to switch to this hook_log based emulator if you want the codes 
http://www.romhacking.net/?Category=&Console=27&Game=0&Author=0&Recm=&Level=&utilsearch=++Go++&title=tracer&dsearch=&page=utils&action=utillist

The hook_log system is a little bit more demanding to use than a visual debugger, but with compatibility issues, it's better than lucky to have a second usable debugging emulator. The save-states can be decompressed, and loaded in their decompressed form if needed

An issue with this emulator is that not all instructions are logged, but it's still worth knowing about for the fact that many instructions are logged, and it can be used with write logging.

==Playstation 2==

[The current author is too lazy to write this, but will get around to it later if no one else does]