KABAM DIDN΄T REMOVE THE ADDITIONAL 6* NAMOR DUPES?????
ReallyYeah
Member Posts: 251 ★★
Kabam hasnt removed from everyone the additionals dupes of Namor????
https://www.youtube.com/watch?v=PxdHAkVhVO0&feature=youtu.be
4:46, Seatin says that he got back namor during the champion balance refund
As you can see from the video below he literally says in 0:11 that HE HASNT PULLED NAMOR 7 TIMES
https://www.youtube.com/watch?v=Vch9kHhG1W4
So my question to Kabam is, will the additional dupes be removed?
Namor is one of the highest prestige champs in the entire game, and by removing the additional dupes from some people is a d**k move
I also had a 6* Namor awakened namor due to the error, but you guys removed the dupe (which was fair)
https://www.youtube.com/watch?v=PxdHAkVhVO0&feature=youtu.be
4:46, Seatin says that he got back namor during the champion balance refund
As you can see from the video below he literally says in 0:11 that HE HASNT PULLED NAMOR 7 TIMES
https://www.youtube.com/watch?v=Vch9kHhG1W4
So my question to Kabam is, will the additional dupes be removed?
Namor is one of the highest prestige champs in the entire game, and by removing the additional dupes from some people is a d**k move
I also had a 6* Namor awakened namor due to the error, but you guys removed the dupe (which was fair)
1
This discussion has been closed.
Comments
And from that INITIAL REFUND, there were far less Sig Stones and more of the Dup Status directly on the champ himself. But all in all, adding them up (not even counting that some of the Generic 6* SigStones might have actually been from his Cull instead of Namor), his Namor + Stones probably is at the appropriate combined level.
He just liked to go for the ClickBait and say “7 DUP'S !!!!”
You don’t know what was actually taken back, or not taken back. But as said, his 6* Namor afterwards was far less than the MaxSig he said he was at prior to it all. (and I’m assuming then that the extra SigStones he still has as Stones instead of having reapplied them all to Namor yet.
Anyways, why would Seatin's account have any bearing on your own account. If they treated your account correctly, that’s all you should be concerned about.
And it’s not like it is the difference between having him Dup or not when all is said and done. Even if there were still some problem with his, it is maybe the difference between Namor Dup'd at Sig 120 versus Sig 140 (when you factor all the SigStones that were returned.
This post is as ill informed as Grounded’s post. Seatin refunded his Namor specifically to reallocate the sig stones into his Sunspot which is sig 160 along with his Silver surfer. The math doesn’t add up for 2x sig 160 6*s and a sig 120 Namor with the sig stones you can naturally acquire from the game.
In Seatin's case, again you don’t know how many or what might have been corrected afterwards, it is only a matter of how high a Sig Level he is. There is no questions that his should be Dup'd or not.
It basically cancels out though, which apparently you don’t understand.
You seem to think this has no impact on anyone when that is far from true. Anyone who is now or in the future competing against his alliance’s Prestige is impacted by the error as that Namor is in his prestige raising it by 75 points; that isn't the end of it though because more importantly anyone is now behind him by 100 6* sig stones which impacts the future. This isn’t a ripple it’s a wave and one Kabam themselves spoke about when addressing the error in forum posts and in game mail.
And summonerNR you’re wrong again, watch the video his Namor should have been returned a single dupe, the sig stone difference was an extra 6 given his math and additionally the whole reason of refunding Namor was to reallocate resources, you think he was just like “oh well I guess I’m not getting my sig stones back to reallocate”, which was the entire reason for selling Namor?
https://youtu.be/a6UFSstUKuo
https://forums.playcontestofchampions.com/en/discussion/187637/namor-rank-up
https://forums.playcontestofchampions.com/en/discussion/187449/namor-and-cull-corrections-finished