Yesterday, a classic error or slip-up occurred with relation to Pokémon. Niantic had scheduled a special happening to occur in Pokémon Go, but as it occurred for a select part of the world, it became apparent that something was seriously wrong, causing the special happening to be cancelled for everyone else before the error propagated. Such an error is no stranger to Niantic by way of Pokémon Go... but then again, it seems the fandom of Pokémon is no stranger to errors in general that come from or generated by different sources, which I'd like to explore on this occasion of a post.
The error as above is on the part of the originator, which is fatal to an extent, more so with it being an in-game error. It's almost comparable to the Mewtwo error that happened for Pokémon Shuffle a long time ago. Sometimes, though, an error can also occur outside of the games, like for the Pokémon e-mail newsletters; on one occasion, faulty newsletters had been sent out, forcing the newsletter edition in question to be sent again. Thankfully, the latter two errors are rare and speaks for the quality control that is involved. As for Pokémon Go errors, those are a source of bemusement with some amusement on the side.
Meanwhile, errors can occur for those who report on Pokémon happenings, particularly with the need to communicate them to others. Sometimes, the Pokémon Go infographics by two very well-known providers of information contain some inaccurate tidbits in them, which perhaps may have resulted from misinterpretations of what had been given on the official Pokémon Go blog. This is expected, of course, by the nature of how information passes, given that they are the second party in sequence. It may always be a challenge to make out the information that has been only provided officially but simply.
I have to say, as a furnisher of Pokémon information myself, sometimes I mess up in the transmission or even the presentation of that on my blog posts, and sometimes I don't catch them in time. Even so, I always come back to try to fix those errors, whether instantly as I spot them or to take another post for that specific purpose. In that sense, I am not exempt from errors in the same way as the others above are not exempt either; this is also as I've declared the first time early on in this blog and time and time again have to repeat - something that becomes pertinent right now.
While it might take some time for Niantic to fix up that happening it intended to present without error and for the Trainers of Pokémon Go to enjoy it as it's meant to be, it may be considered that some errors are just meant to be until they need to be fixed. When it comes down to it, Pokémon is still a human creation from a figment of imagination, and to err is the nature of humans, even with fantasies. For the three parties as I've outlined above, this should apply equally well, even with different respects, and the best respect that can be given for them is to edit and make them right as things progress.
One year ago: Pokémon Music on Vinyl?
Two years ago: Usage Experience of Go Plus Peripherals
Three years ago: Tournament: Raid Group Sinister Cup
Four years ago: Two-Sided Stories
Five years ago: Pronouncing Pokémon
No comments:
Post a Comment
Hi folks! Feel free to comment, but know that I'll be selecting only the most appropriate and relevant comments to appear. Think before you post.