MeanMug

This isn't a console exclusive issue, it's the same on all platforms.

I cannot reproduce this with the given information. We are still keeping attention on any reports of instability to try and identify a cause though, so this report may become part of a solution eventually.

This isn't a bug with the game, it's an issue with the server environment the game is on, and affects basically anything involving a player purchasing a product that gets added to their account. You'll need to change worlds after making a purchase or performing an action that adds a product to your account (such as crafting a new class) in order to receive it. The platform team is aware of the issue, but it's a difficult problem to resolve. If you do accidentally do this action more than once, please reach out to Customer Service to get their help.

Not sure if there was something going on at the time this report was put in, but I cannot reproduce this issue in the current game. Spamming the interact key on the portal to a world doesn't seem to have any negative effect on getting into the world that portal is for. If there's any more info to help reproduce this please update this issue.

This has been known for a long while, just linked this with the internally logged issue.

This isn't a bug with Trove, and not something the Trove team can address. I've passed your feedback on to the internal team about the Glyph launcher requesting administrator privileges.

There isn't enough information here for me to reproduce this. I know there are some weird behaviors sometimes with coin challenges, especially right now, but I don't have any way to repro this on the info provided.

Is this issue still occurring? There were some problems over the weekend that may have been causing this.

This is one of those old bugs where the author wrote it without clearly stating the issue. Can you please explain precisely what the problem is you're pointing out here?

This has been a known bug for some time, but I've linked this report to the original bug internal report and raised the old issue for consideration.

I misunderstood the report, got it logged now. Thanks!

I don't have the ability to go back in time and play the delve that was active at this specific depth, but I cannot reproduce this issue in current delves with the Chloromancer and the Gladiator deltalith active. If this still occurs and you've got more info, please update this.

There isn't anything here specific enough to direct me to a reproducible crash. Please make sure you're sending in crash reports when they occur, those do get checked and analyzed.

I can't reproduce this based on the information I've got here. If this is still occurring and there's anything else you can provide, please update this.

There isn't nearly enough information here to reproduce this issue.