[Debate] Lucky & Trade in Pokemon Go
25件のメッセージ normal
25件中21〜25件を表示
28/03/2019 23:58
20/04/2019 16:39
Basile and Pest have the exact same Pokémon as a proof in this chart :
https://www.video-games-records.com/pokemon-go-poids-maximal-dinoclier-record-r521013.html
I think that when it's obvious like that, it should not be allowed.
https://www.video-games-records.com/pokemon-go-poids-maximal-dinoclier-record-r521013.html
I think that when it's obvious like that, it should not be allowed.
20/04/2019 19:26
Asep :
Basile and Pest have the exact same Pokémon as a proof in this chart :
https://www.video-games-records.com/pokemon-go-poids-maximal-dinoclier-record-r521013.html
I think that when it's obvious like that, it should not be allowed.
This may not necessarily be the result of a trade. If two players who are above level 30 are in the same location at the same time and catch a Pokemon that spawns there, that Pokemon will have exactly the same CP, Level, IVs, Height, and Weight.
I'm unsure if this is the case for that Shieldon specifically, but given that its CP is the same for each player (and thus would have had to roll almost identical IVs in the trade), it is very likely that they simply both caught the same Pokemon.
Basile :
If I'm right, the only monsters affected by the CP changes are:
Snorlax, Vaporeon, Chancey & blissey, rhydon, galeking and slaking ?
These are all of the Pokemon that had their maximum CP reduced in the October 15 2018 rebalance:
Aggron -4
Donphan -9
Noctowl -16
Steelix -25
Ho-Oh -26
Rhyhorn -28
Relicanth -29
Vaporeon -43
Slaking -117
Rhydon -121
Snorlax -130
Chansey -214
Blissey -462
The only Pokemon that have VGR records exceeding their new maximum CP are Rhydon, Snorlax, Chansey, and Blissey. That said, there are many submissions across most of the Pokemon in that list that - while still possible - are now much more difficult to reach than they used to be.
20/04/2019 23:23
@Asep: Yes, it happens that we have the exact same pokemon, such as this one that we both evolve for instance:
1
2
3 (I have powered up this one once)
Because, when you catch a pokemon, if somebody catch the exact same, you have both the same weight/height and CP, if you are both more than lvl30.
But you have to catch the exact same one, counting that it will stay only 15 to 30min.
I also have some that are the same than Yoshi55, considering that I am playing a lot with him, but I probably found better ones after or before in the game.
For the CP rebalance, I'm OK if we choose to not allow the old scores.
What do you guys think about it?
It can stay the way it is, also, it does not matter for me, as you can always found better mons while playing (Only chansey, blissey, snorlax and rhydon are exceptions)
1
2
3 (I have powered up this one once)
Because, when you catch a pokemon, if somebody catch the exact same, you have both the same weight/height and CP, if you are both more than lvl30.
But you have to catch the exact same one, counting that it will stay only 15 to 30min.
I also have some that are the same than Yoshi55, considering that I am playing a lot with him, but I probably found better ones after or before in the game.
For the CP rebalance, I'm OK if we choose to not allow the old scores.
What do you guys think about it?
It can stay the way it is, also, it does not matter for me, as you can always found better mons while playing (Only chansey, blissey, snorlax and rhydon are exceptions)
21/04/2019 14:32
Basile :
@Asep: Yes, it happens that we have the exact same pokemon, such as this one that we both evolve for instance:
1
2
3 (I have powered up this one once)
Because, when you catch a pokemon, if somebody catch the exact same, you have both the same weight/height and CP, if you are both more than lvl30.
But you have to catch the exact same one, counting that it will stay only 15 to 30min.
I also have some that are the same than Yoshi55, considering that I am playing a lot with him, but I probably found better ones after or before in the game.
OK, didn't know you were playing together ;)
25件中21〜25件を表示
You must be logged in to reply to this topic.