I’ve always had more yellow than I need, but part of that is that there are fewer troops that actually use minor yellows, so we don’t tend to use as many.
If you’re talking Arcanes, it’s harder to know what the problem is, since we use so few and have the chance to buy them in glory packs occasionally. I’ve gotten a good variety of arcanes through PVP, so it’s not like I’ve only been getting Arcane Summers this whole time.
so i restarted test after update and it look like you are right i did 10 pvp fights and 10/10 opponent kingdom stones as rewards
good thing i got more then enough stones to not worry about it and for now, from my rival list only 2 were using whitehelm as home kingdom and i had a good variety but i imagine if a new player is only matched against whitehelm opponent there could be a problem for them to collect specific color in pvp
HOWEVER, What I find interesting is how, based on your experience it appears that the Gems server does not verify the client to see if your running the latest version, and let you play on the servers with an outdated version. Very odd. Wonder if that could cause the Guild corruption or other weirdness in the seen in the past…
I know on ps4 I can’t play gems if an update is available and I choose not to download it. I get a prompt saying I must update to latest version of this game.
Not sure if it was update or just a patch anyway i will pay more attention next time
Like i said, my console suppose to automatically download any patch or update but this time i had to do it manually
I’ve actually found something out, wow I feel slightly more important now! Do I win a prize? I’ll have a famine please! @Saltypatra I can confirm this is indeed a thing now because I had 5 ‘yellow’ pvp wins in a row today and was pointed to this thread. Indeed kingdoms now give matched stones as pvp rewards. We’re not happy! Why no Dev response?
Guys?
Regards
Daniel
Yep! I only posted this 5 days ago. They probably only had had time last week to test this verify its broken, go SH## and call it for the weekend.
I suspect this went live with the last client update so it went undetected for a while. We can guess it will be fixed either in the next client update (IF there is time and/or it hasn’t been submitted yet, or the update one after the next). Until then we will have to live with it like they did on PC for 2 years…
EDIT adding @Dan_ozzzy189 As this is really to him.