Code Ambiguity

[rimsky82]

Now that the codes from all of the games in the old databases have been joined together, I'm seeing a lot of the following:



You'll see the same code, entered differently 4 times. Since the site is smart enough to decrypt, convert, and encrypt, having the same code posted in different formats just creates ambiguity. I'm betting the db size could be cut in half with all of the dupes we have.

So why don't I just make a script that deletes the dupes? That should be easy, right? Well, sure. Except... the picture above just begs the question: Who hacked the code? And this question will exist for any set of dupes with different hackers listed as contributors.

The possibility exists that any number of separate hackers hacked the same code on their own, and posted it in a different format. And then there are the hacker wanna-bes that convert using arcrypt or omniconvert, and then claim they hacked the code. We sort out the hackers from the wanna-bes and then comma-delimit the hackers for credit. OK, go.

Unfortunately this can't really be done easily or overnight. I suppose for now we take care of these on a case-by-case basis.

Leave your opinions... and maybe even your solution for the example above.

[Helder]

I have seen many times duplicated codes from the same user but one is without a hacker name. So I would suggest you tackle these first then we should see the size drop a bit.

[terpsfan101]

Request:

Can you display Sega Genesis PAR codes in the format they were in before you made these changes. Most of the PAR codes in the xxxxxx:yy format (not xxxxxx:yyyy format) were already byteswapped (is this the correct term?).

[terpsfan101]

Here are some examples of Sega Genesis PAR codes that no longer work since you made these changes. These are for Sonic 2:

Originally Displayed as:

FFB02B:01 Always Have Shield
FFFE19:01 Play as Super Sonic (No Powers)

Worked in Kega Fusion:

FFB02B:0001 Always Have Shield
FFFE19:0001 Play as Super Sonic (No Powers)

Now Displayed as and no longer working in Kega Fusion:

FFB02A:0001 Always Have Shield (Sonic can't move)
FFFE18:0001 Play as Super Sonic (This is the RAM address for continues, so you get infinite continues instead of Super Sonic)

Basically the point I'm trying to make is leave it up to the user to decide whether or not to add 00 in front of the value or subtract/add 1 from the address. In other words, go back to the way things were before this update. It's a real pain to have to use other sites now for PAR codes (especially with GS Central down), since they are no longer handled correctly here. I've tested hundreds of PAR codes in the XXXXXX:YY format in KEGA Fusion (see mine and Mighty Mo's cheat code pack), and probably 95% of them worked by adding 00 in front of the YY, not by subtracting 1 from XXXXXX.

[lee4]

Because Gens and Fusion handling address differences in little endian and big endian matter.

[terpsfan101]

Well, it seems rather arbitrary to display the codes in GENS format, rather than Kega Fusion/genplus-gx format. So we had codes before the update that worked in Kega Fusion and didn't work in GENS, now after the update we have codes that work in GENS, but no longer work in Kega Fusion.

[terpsfan101]

Solution:

Dispaly the PAR codes in the format they were submitted in:

XXXXXX:YY codes display as XXXXXX:YY, instead of XXXXXW:00YY or XXXXXY:00YY

If you export XXXXXX:YY, you get XXXXXX:00YY if you select Kega Fusion and you get XXXXXW:00YY or XXXXXY:00YY if you select GENS.

[terpsfan101]

To sum things up, alot of the 8 digit PAR codes no longer work in Kega Fusion with the new code format. And since all PAR codes are now displayed as 10 digits, the only way I can find out which PAR codes were originally 8 digits is to compare them to other sites, like the Old GameHacking site.

[Hybrid]

heh i always thought that we should display them as they would work on actual hardware you know an actual Pro Action Replay (PAR). but i guess i'm weird like that. (i've always hated the way emulators handle RAM codes)