>>37361293No, dude.
>>37361280Meltan, yes. My bad.
When it leaked, Joe immediately started shittalking Niantic.
>I knew this would happen. I knew that they wouldn't reveal it themselves as Niantic would stupidly add it to network traffic before reveal>Like seriously? How does an error like that happen? Of all the incompetent things we have seen, this takes the cakeAfter that, Joe spent his time arguing with people and continuing shittalking Niantic.
>I just can't wrap my head around how something so stupid and incompetent could happen. It's not like 352 and 808 are close enough numbers, even on the number pad, to get typo'd.>So many people really not understanding what placeholders are. If kecleon needed a placeholder it would have got one in December. They wouldn’t have designed an entirely new model and concept for it. Come on>The Community never ceases to amaze me. So willing to accept baseless fakes but when something potentially real leaks it is dismissed, claimed it’s an amalgam of other Pokémon etc.Then the whole thing about JynxClub. You know, the "back off" and "Yeah I'm definitely holding you to this" tweets.
Lastly, after the whole shitstorm started to fade, Joe changed his mind and casually started defending his shitty behaviour (while still shitting on Niantic sometimes).
>Not my fault it seemed more likely for Niantic to screw up than to tease something. I blame their history :P>Yeah. It's quite unfortunate that the first thought about the new Pokémon was that Niantic messed up. It's sad but that's just based on their history of screwing a lot up>See, this is how you get people excited about Let's Go :) While it seemed a mistake at first, this was really clever marketingThe whole thing was fucking childish and unprofessional.
