![]() |
Intentional Cloning?
So, I was just thinking about the pokemon games, and I realized that all of them have a cloning glitch when depositing a pokemon. So my question for you guys is: Do you guys think Nintendo knows to some degree knows that there is a cloning glitch when they are in the development process, or even intentionally place a glitch in the game to reward faithful players?
If you don't think so, why don't you? If you do think so, why do you? Just thought this would be a fun little thread to get some more people's opinions about this. For the record, I belive that they know about the glitches, and leave them in there for fun, but I'm not sure about intentionally putting glitches in the games. |
You know.. It may be possible. But I think the one in Diamond and Pearl was actually a glitch. But for the other ones I'm not sure.
|
I highly doubt that they would add such a glitch in the game; it could be considered an unfair advantage. Plus I don't think too many people want bugs in their system. It might give them a bad rep (unless you like using that glitch ^^). I think it's just something that can't be taken away from the games; a permanent glitch. Unintentional and possibly no way of removing it. But to get the real answer, we'd have to ask the makers themselves.
|
Nintendo goes through many safety precautions to prevent glitchs, but they can't completely eliminate the cloning glitch because of the way Pokemon are saved on the cartridge. They need to be copied to another location when moved, then deleted from the old location. In order to prevent cloning glitches all together, they would need to rework the entire system.
|
I heard from somewhere that there was this item cloning glitch in the japanese version of pokemon diamond and pearl. Something about double battles. But I think they fixed it in the english version.
|
Sheek, what I mean is, when they are going through said precautions, they may know that the glitch is in there, but choose to leave it in there.
|
Quote:
|
Yeah. Well, do you think any of it is intentional besides the big reworking it would require?
|
I don't think so, they didn't intentionally put it there, but they intentionally left it there because of the work it would require to fix.
So I guess it depends on which angle you look at it. |
Laziness shouldn't be a factor when making a game.. They should go as far as they need to in order to perfect the game....
|
They weren't being lazy, they were doing what was best in the long run. Like I said, they'd have to reword the ENTIRE game, specifically the way in which game/Pokémon data is saved on the cartridge. Meaning pushing back release dates amongst other things.
It's not as if the cloning glitch is an imperfection anyway. |
Well they had and knew about the glitch since the games started. If they're making new games, why not fix that problem during construction? 4th Generation and still nothing.
But maybe the problem is there is no alternative to fix it. Then they'd have a legitimate reason for not doing it. I believe this more than them being lazy, it seems more logical in my opinion. |
Quote:
In Gen I and II, it's a risky procedure involving disconnecting at a precise moment in a link trade. This can still be done during a Wi-Fi trade and can result in cloning one or both Pokemon being traded, or it can result in losing 1 or both. The GTS Cloning glitch doesn't intentionally happen, but it happens as a result of a safeguard. D/P/Plat makes TWO save files each time the game is saved. A primary and a backup. In case the first file is corrupted for any reason (power runs out or is turned off at an inopportune time, among other reasons and ways), the second file is loaded. This is a GOOD thing. The reason the GTS Clone glitch works is because it "corrupts" the first save, loads from the backup save, and also loads the Pokemon to the GTS. The Emerald clone glitch is, from what I hear, the easiest to use, but I don't own Emerald and am not familiar with it. These really aren't glitches that you can stop, like Missingno or any number of glitches in Pokemon Green. These glitches are unintended side affects that weren't meant to be discovered anyway, and in the case of Gen 4 games, meant to protect your saves. So for better or for worse, cloning is here to stay. |
It's not intentional. The glitch has been there since the very begining. It's something that can't be removed.
|
Its not intentional. Think about it. Most cloning glitches require saving and turning off power between the save. This makes it so it pretty much splits the data. Its not intentional. Its just that we are smart enough to find ways to confuse the games :)
|
Hey, I think its intentional... at least there should be one of the programmers of the Pokemon games looking at all forum discussions, and it can't be possible that they don't know about that glitch, besides, it's an ever existing glitch, and if it were the opposite way, that if they wouldn't know that, then the programmers are just being ignorant and wouldn't really know what they're doing; making this unintentionallity being impossible!!!
|
Its not that they are being ignorant or stuip about it. think about it, if it cost you 10 million dollars to fix a built in glitch, not to mention you would have to recall alll the old games.... would you do that or forget about it? (as the glitch does not harm your play its not needing to be fixed for such a big expense as it would take.)
they are being buisness smart, not stupid. It's all about profits not perfection. |
Look at the Wifi Cloning Glitch, it's the by-product of a precaution to avoid the players losing pokemon in the result of console/connection failure. If they had instead removed this precaution, then it would be worse in the long run. Imagine the complaints they would cop if players were losing their pokemon...
|
Quote:
|
Quote:
|
Quote:
EDIT: Maybe not intentional but it's a sure way of people not losing their Pokemon (as Archer stated). But it's cool. |
Quote:
In Gens I and II, cloning could be the result of a well-timed system shut-off during a box deposit. In these games, there wasn't enough storage to afford a backup save file, so the one you had was it. It would have been extremely easy for them to put a check (either a checksum or a "write in process" flag) to detect a partial game save, but their only option in this case is to delete the savefile entirely. Instead, they were thoughtful, and let the player recover a corrupt savefile in this case. Cloning was one of the possible results. In GenIII and on, the savefile is backed up, and attempting this causes the old savefile to be restored. All the various trading cloning "glitches" (not true glitches for the following reason) are completely unavoidable for one very basic reason: It's impossible to perfectly synchronize two machines. One is always going to perform a particular key save operation just a little bit before the other, and if the other is shut off during this window of opportunity, one game gets saved but the other does not. Cloning is the result. Again, for the GTS, they could've made it that YOUR game saves before the remote server does, which would've resulted in possible deletion of your Pokémon, but, instead, they opted for the cloning possibility because they deemed it preferable. Emerald cloning is weird and probably could've been prevented. |
Not just laziness but they would have release dates and stuff to look at, so if the glitch was found like two days before release, then they would leave it, no?
|
| All times are GMT -8. The time now is 7:29 AM. |
![]()
© 2002 - 2018 The PokéCommunity™, pokecommunity.com.
Pokémon characters and images belong to The Pokémon Company International and Nintendo. This website is in no way affiliated with or endorsed by Nintendo, Creatures, GAMEFREAK, The Pokémon Company or The Pokémon Company International. We just love Pokémon.
All forum styles, their images (unless noted otherwise) and site designs are © 2002 - 2016 The PokéCommunity / PokéCommunity.com.
PokéCommunity™ is a trademark of The PokéCommunity. All rights reserved. Sponsor advertisements do not imply our endorsement of that product or service. User generated content remains the property of its creator.
Acknowledgements
Use of PokéCommunity Assets
vB Optimise by DragonByte Technologies Ltd © 2023.