Monster Hunter

[Game2Death]

Intro: I have a game for the Ps2, called Monster Hunter. It's fairly old made in 2004. I am in the United States, and have a US Ps2 and game. I have a 9.2 Code Breaker and am currently upset with what I did.

Story: Ok, so I bought this game and loved it to death, I played for hours and hours and hours. I played online with people, made tons of friends, and this was my first ever online game. I had spent hours trying to get this one item, (Rathalos Plate) and you have a 1% of getting it! I needed like 12! I had only 1. So I put in my Code Breaker and clicked "99x item" and accidentally hit "Low game time" I was proud of my game time. It went from 684 hours on one character to 0:00! I was so sad, and then my 2nd character went from 300 some hours to 0:00! I almost cried! Now I know you are probably thinking "who cares" well that was 6 months ago and it still bigs me every day. I quit that game because of that that, and I got new games. I really want a code to ease my mind of that time.

Request: Ok, so if anyone would make a code that I could alter the time? Then I realized that maybe that's hard, so maybe something easier would be to make every minute or second count as a hour.

Slight begging: If this board won't help like the other 15-25 that I tried, I am going to leave my Ps2 on fr 29 days to get my time back. Please help me.

Thanks,
G2D

[LiquidManZero]

Well, I have an idea here. I decided I would take a look at the contents of the "low time" code. Very rude of them to hide it from the users by encrypting it... But anyway:

Always Low Game Time
203E9F9C 00000000

This here is a perfectly normal 32bit write code... Let's see... 684 hours would be about 2462400 second, and in hex (at least what Google claims) it'd be 0x2592C0. So taking that and replacing the pointless value of nothing in the "low time" code, and then reencrypting the little bastard... There's this, which might or might not work:

684 Hours Game Time (or at least a lot of time, if not that many)
5243C90C 1DEEFD21

I'd recommend taking a bit of care with this code, backing up save files and such before trying to do anything even like saving with it on.

If this isn't quite the value you're looking for, let me know what the game says with it on, and I'll try to adjust it to compensate.

[Game2Death]

Well, I have an idea here. I decided I would take a look at the contents of the "low time" code. Very rude of them to hide it from the users by encrypting it... But anyway:



This here is a perfectly normal 32bit write code... Let's see... 684 hours would be about 2462400 second, and in hex (at least what Google claims) it'd be 0x2592C0. So taking that and replacing the pointless value of nothing in the "low time" code, and then reencrypting the little bastard... There's this, which might or might not work:



I'd recommend taking a bit of care with this code, backing up save files and such before trying to do anything even like saving with it on.

If this isn't quite the value you're looking for, let me know what the game says with it on, and I'll try to adjust it to compensate.

Trying it now....

[Game2Death]

Holy crap I love you....:cool

[LiquidManZero]

Heh, awesome. I never really could get the idea of "low time" codes anyway.

[tempernet]

This a cool game

[masterwriter42]

Wow, I had that problem, too. I think I already got rid of my save file, though. I got the game in 06 (or was it 05?) and stopped playing it the same year. I tried playing it one day in 07, but remembered about the time thing, and I'd had some other kind of buggy problem going on, too. I think it was that I had beaten the game, but the after game was messed up.