JavaScript is required to use Bungie.net

Forums

originally posted in: Pokemon Switch
5/23/2018 8:11:47 PM
3
Also take this with a grain of salt. I saw this news from a channel on YouTube who mentioned these leaks coming from 4chan, but they failed to mention these leaks came out on April 1st of this year. They had also mentioned with these leaks, that these said remakes of Pokemon Yellow would also include the return of your pokemon following you around as well as them being integrated somehow with Pokemon GO and that you could also link you GO accounts with these games. They say you may catch the pokemon in game similar to how we catch Pokemon in Pokemon GO. But, who knows the validity of this. All in all, Whatever they announce, I am sure I will need to buy a switch soon lol
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • The original leak came out on April 1st, but there were several followups more recently.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by SuperStormDroid: 5/24/2018 1:41:42 PM
    I would not trust 4chan when it comes to leaks. They supposedly "leaked" the roster for BlazBlue Cross Tag Battle, but the leak was [url=https://mobile.twitter.com/ArcSystemWorksU/status/948378440926990337]completely false[/url] according to Arc System Works America.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Oh i know, rumours should never lead to someone holding their breath. However i do see some things, happening around these rumours that to me, make see this as a "Probably" not a "Possibly" kinda thing

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon