bigplrbear
C# programmer for the IAPL
- 36
- Posts
- 14
- Years
- Ridgecrest, Ca
- Seen Aug 13, 2011
What I'd do is create a pointer to access a certain memory location that you want to check, then perform a catch of some sort, to see if any data was changed in memory by the end user. If it detects such data change, the game would work as normal- but saving would be disabled.
Personally though, I would actually welcome cheaters/people who like to find bugs in games. Part of the fun in playing pokemon games, especially in older ones, is finding glitches (such as Missingno.).
In fact, our programming team has actually considered loading battle data in such a way that could possibly allow the formation of a missingno. if certain conditions are met (no pokemon data in a certain area, for example) by essentially loading junk data (random sprites/random pokemon data) from memory instead of what it should load. Of course, bugs like that really effect stability, so it's pretty iffy, but still ;)
edit- wow, I'm really derpy tonight. I've edited that code like five times because I got 'correct' and 'incorrect' mixed up. I need some coffee >.>
Code:
//maybe something to the tune of...
byte catch_code(int **pointer_to_check, byte saving_disabled)
{
if (**pointer_to_check == &correct memory location or correct variable)
{
return saving_disabled = 0; //don't return an error
}
elseif (**pointer_to_check == &incorrect memory location or incorrect variable)
{
return saving_disabled = 1; //return an error
}
}
Personally though, I would actually welcome cheaters/people who like to find bugs in games. Part of the fun in playing pokemon games, especially in older ones, is finding glitches (such as Missingno.).
In fact, our programming team has actually considered loading battle data in such a way that could possibly allow the formation of a missingno. if certain conditions are met (no pokemon data in a certain area, for example) by essentially loading junk data (random sprites/random pokemon data) from memory instead of what it should load. Of course, bugs like that really effect stability, so it's pretty iffy, but still ;)
edit- wow, I'm really derpy tonight. I've edited that code like five times because I got 'correct' and 'incorrect' mixed up. I need some coffee >.>
Last edited: