EVO Player can't be sent to sbc storage.
Product: EA SPORTS FC 25 Platform:PlayStation 5 Please specify your platform model. Sony PlayStation 5 What is your Gamertag/PSN ID/Switch ID? Which mode has this happened in? Ultimate Team™ Whi...
Forum Discussion
I am currently working around this by discarding and doing a quick recovery in the next 7 days. That is not a long term solution. I'd at least like an answer.
- @SelamiCap As far as I know, you can not have 2 evolved versions of the same player item in the club. When you try to evolve a new version of the same player, the game will give you an error message like - "Already evo exist for the same player". This is a thing since Evolutions launched last year in FC24.
As per my understanding, I don't think SBC storage will allow you to store a duplicate evolved version of the same player.Despite that, I do have two different versions of the same player completed and I have not received a message of the sorts. If there is indeed a restriction and not a bug, it is a silly restriction that results in a disconnection from ultimate team.(P.S to EA from a dev perspective: This is not how you handle request failures, especially when you know the reason for the failure, but then again there's a lot of weird decisions in EAs dev solutions, spaghetti code most likely) .
If they're the same, then the duplicate storage should allow me to store the duplicate as it is indeed a duplicate.
Two EVO players should be different if the EVO applied is different, just as a special version of a card is different from its normal version and can be stored with no issue.
I would like to keep my future EVO paths open on both sides and this issue is impacting that. I am currently recovering the card and discarding it again to recover it again later but that is only glue to either a hidden behaviour of EA where they don't allow two EVOs of the same player to exist or just a bug.
From the rarity systems POV, it makes sense that they're duplicate as they are the same player with the same rarity. However there is no reason for the SBC Storage to not accept the card and I firmly believe this is a bug.
