How are you liking the new job?
Crazy how fast almost three months goes by! Having such a blast Unity have been so amazing to me.
How are you liking the new job?
Crazy how fast almost three months goes by! Having such a blast Unity have been so amazing to me.
Official Wessite requires localisation to 4 languages, they can't get that up in the speed they can here
While that's true there should be an emphasis on official news coming from the official site not everyone reads reddit!
Hey, do we have any more updates on if this has been figured out?
Posted a thread now (it's fixed).
Thank you for your hard work and late night working on this.
So, just to confirm, the people with screenshots of max stacks of items did actually fake it?
Nothing in our analytics would indicate it - however I would encourage anyone who has genuinely experienced it to let us know and submit a Lost Items ticket.
Whew, so no big deal. I guess the people with screenshots of max stack runes and such were faked?
We don't have any evidence our side to indicate an influx of runes to that level - from our analytics those items looked like they would on any other day.
If anyone is concerned though, I would say to submit a support ticket and we can investigate.
Great work!
This should be fixed now - details here.
(Please don't ask me to elaborate any more on the intricacies of this - there's a reason I work in CM and not QA!)
Thank you everyone who has shared their stories with us over the past few hours. It's been a bit of a whirlwind!
After a lengthy investigation, we've successfully identified and fixed the issue at around 3.20pm GMT - it was a two-level bug that involved an item being dropped to the ground when being deposited and that items would be dropped to the ground when depositing them whilst also moving another item into that slot - making it appear that the player's item has switched from one to the other. In the example here, the perception was that the spirit weed seeds turned into Cosmic Runes. What actually happened was that the ...
Read more External link →This has been hotfixed. Thanks for the report :)
Added in another update - TL;DR - it's fixed!