✨ ARCHIVE MODE ✨
The forum has now been set to read-only mode, no new posts, resources, replies etc will not be possible.
We recommend you join our Discord server to get real-time response: Discord Invite Link
I think that would be good. I like the idea of having it be completely random. It sounds pretty good as is but here's my own personal twist on it:My idea: after you save the game, in the next pokemon encounter you have a 0,1% chance to battle MissingNo.
If you battle MissingNo your game crashes (you have saved 2 minutes before) and you will receive an achievement.
Maybe it can be disabled in the option screen.![]()
this would be cute but snoe has a point imo, alsoMy idea: after you save the game, in the next pokemon encounter you have a 0,1% chance to battle MissingNo.
If you battle MissingNo your game crashes (you have saved 2 minutes before) and you will receive an achievement.
Maybe it can be disabled in the option screen.![]()
this is way too much for a simple ref to gen 1 lolI think that would be good. I like the idea of having it be completely random. It sounds pretty good as is but here's my own personal twist on it:My idea: after you save the game, in the next pokemon encounter you have a 0,1% chance to battle MissingNo.
If you battle MissingNo your game crashes (you have saved 2 minutes before) and you will receive an achievement.
Maybe it can be disabled in the option screen.![]()
After you beat the Elite 4 and red at the end of the game, there's a 0.1% chance (maybe raise that to 100% if you follow the known steps from Pokemon Red to encounter the glitch) of encountering MissingNo (which could be turned off). If you encounter MissingNo, a whole boss battle sequence begins, and you enter a battle with MissingNo (Lv 90, perhaps? Maybe Higher? Maybe Lower?) As you begin to lower MissingNo's HP, the game starts glitching out (i.e. Missing or corrupted textures, flickering items in the background), more and more as MissingNo's HP lowers. Once you beat MissingNo, you get loads of EXP and the game auto-saves before appearing to seriously crash. You open it up again, and everything is back to normal, and you get an achievement for defeating MissingNo.
MissingNo would be uncatchable, and anytime you try to catch him, perhaps the pokeball just bounces off of him and comes back to you with a little error message at the bottom of the screen to fit with the glitch part of it. This would probably be a big load to program for the staff, and I wouldn't be surprised if it never makes its way into any part of the game, but it would make for a seriously epic endgame battle, not much unlike Mewtwo in FireRed or Rayquaza in Emerald, just with a little more presentation, I guess.
Maybe if you try to encounter MissingNo (before defeating Red at the end of the game) by doing the whole Cinnabar Island thing, you get an error message and the game exits out of the battle sequence, taking you back to the coast just off of cinnabar island.
Lol yea I know, I don't even think MissingNo should be included anymore because it wouldn't really fit w/ the game. I guess I just turned simple into super crazy hard to battle boss that will likely be pointless in the gamethis would be cute but snoe has a point imo, alsoMy idea: after you save the game, in the next pokemon encounter you have a 0,1% chance to battle MissingNo.
If you battle MissingNo your game crashes (you have saved 2 minutes before) and you will receive an achievement.
Maybe it can be disabled in the option screen.![]()
this is way too much for a simple ref to gen 1 lolI think that would be good. I like the idea of having it be completely random. It sounds pretty good as is but here's my own personal twist on it:
After you beat the Elite 4 and red at the end of the game, there's a 0.1% chance (maybe raise that to 100% if you follow the known steps from Pokemon Red to encounter the glitch) of encountering MissingNo (which could be turned off). If you encounter MissingNo, a whole boss battle sequence begins, and you enter a battle with MissingNo (Lv 90, perhaps? Maybe Higher? Maybe Lower?) As you begin to lower MissingNo's HP, the game starts glitching out (i.e. Missing or corrupted textures, flickering items in the background), more and more as MissingNo's HP lowers. Once you beat MissingNo, you get loads of EXP and the game auto-saves before appearing to seriously crash. You open it up again, and everything is back to normal, and you get an achievement for defeating MissingNo.
MissingNo would be uncatchable, and anytime you try to catch him, perhaps the pokeball just bounces off of him and comes back to you with a little error message at the bottom of the screen to fit with the glitch part of it. This would probably be a big load to program for the staff, and I wouldn't be surprised if it never makes its way into any part of the game, but it would make for a seriously epic endgame battle, not much unlike Mewtwo in FireRed or Rayquaza in Emerald, just with a little more presentation, I guess.
Maybe if you try to encounter MissingNo (before defeating Red at the end of the game) by doing the whole Cinnabar Island thing, you get an error message and the game exits out of the battle sequence, taking you back to the coast just off of cinnabar island.
Haha! Great point!It still isn't purposely obtainable, therefor if it makes an appearance at all, it should just be an Easter Egg.Actually MissingNo has been in almost every Pokemon game I can think of. In Red/Blue/Yellow, it was called MissingNo, and was very easy to find due to it's popularity. But it did appear in other games, just not as the name "MissingNo" but commonly a series of question marks.
I had a MissingNo in Pokemon Crystal that generated itself in my PC from a Gyrados after a really weird freezing incident. It wiped my whole party if I tried to use it. It was really glitchy, but it did exist.
Of my knowledge, MissingNo was only "encounterable" in Red/Blue (not Yellow), but it exists in every game. You could get MissingNo from multiple glitches in the later games, but not wild Pokemon encounters.
Why do people want a Pokemon that looks like a glitchy, pixely penis?
I think that would be good. I like the idea of having it be completely random. It sounds pretty good as is but here's my own personal twist on it:My idea: after you save the game, in the next pokemon encounter you have a 0,1% chance to battle MissingNo.
If you battle MissingNo your game crashes (you have saved 2 minutes before) and you will receive an achievement.
Maybe it can be disabled in the option screen.![]()
After you beat the Elite 4 and red at the end of the game, there's a 0.1% chance (maybe raise that to 100% if you follow the known steps from Pokemon Red to encounter the glitch) of encountering MissingNo (which could be turned off). If you encounter MissingNo, a whole boss battle sequence begins, and you enter a battle with MissingNo (Lv 90, perhaps? Maybe Higher? Maybe Lower?) As you begin to lower MissingNo's HP, the game starts glitching out (i.e. Missing or corrupted textures, flickering items in the background), more and more as MissingNo's HP lowers. Once you beat MissingNo, you get loads of EXP and the game auto-saves before appearing to seriously crash. You open it up again, and everything is back to normal, and you get an achievement for defeating MissingNo.
MissingNo would be uncatchable, and anytime you try to catch him, perhaps the pokeball just bounces off of him and comes back to you with a little error message at the bottom of the screen to fit with the glitch part of it. This would probably be a big load to program for the staff, and I wouldn't be surprised if it never makes its way into any part of the game, but it would make for a seriously epic endgame battle, not much unlike Mewtwo in FireRed or Rayquaza in Emerald, just with a little more presentation, I guess.
Maybe if you try to encounter MissingNo (before defeating Red at the end of the game) by doing the whole Cinnabar Island thing, you get an error message and the game exits out of the battle sequence, taking you back to the coast just off of cinnabar island.
I think this is more something to implement with a mod, not in the main game!Random idea: a custom story based around MissingNo.
I'm thinking that it could be a version of pokemon in which Red had conquered MissingNo, an evil pokemon that threatened to destroy the world. 20 years later, you come along (in johto) and hear that MissingNo appeared in some city. You have to travel to said city to find the MissingNo. MissingNo then leads you on a chase through Johto and eventually the Kanto region. As the story continues, you learn more about the backstory of MissingNo (which could be written later) and uncover some pretty important evidence (also written later).
I dunno, it seems like a kind of stupid idea to me, and has nothing to do with the current topic, but hey, this thread is titled "MissingNo?", so I thought I would share it. What do you guys think?
I was thinking of a separate model to add that to. Not part of the actual game (that would be a little silly to completely throw out the original plotI think this is more something to implement with a mod, not in the main game!Random idea: a custom story based around MissingNo.
I'm thinking that it could be a version of pokemon in which Red had conquered MissingNo, an evil pokemon that threatened to destroy the world. 20 years later, you come along (in johto) and hear that MissingNo appeared in some city. You have to travel to said city to find the MissingNo. MissingNo then leads you on a chase through Johto and eventually the Kanto region. As the story continues, you learn more about the backstory of MissingNo (which could be written later) and uncover some pretty important evidence (also written later).
I dunno, it seems like a kind of stupid idea to me, and has nothing to do with the current topic, but hey, this thread is titled "MissingNo?", so I thought I would share it. What do you guys think?But I really like your other idea!
![]()
I agree with you there, MissingNo is a legend that should be preserved. However, I think it would be fun to at least take an attempt to interpret the legend of MissingNo and write a story about it. Honor it in a way other than words. I think it would be fair that any interpretations of MissingNo's backstory would be dedicated to its existence and the legend it created that even 15+ years later is still remembered by millions.i like how you guys have kept up the posting about MissingNo. brings a tear to my eye that you care so much about something that defined the pioneers of pokemon.
i still think however the best thing to do for such a legend is to leave it lay where it rests in time. to be remembered, not implemented.
however, if your undying determination to breathe life into MissingNo. is successful, more power to you.