Kay

There is an intermittent UI bug that hits the queue screen that does not result in a perpetual queue, but can cause confusion on where you are in the queue - was everyone here able to enter their intended world eventually?

Worlds that are getting merged are already in maintenance and players have been kicked. So if you’re not in maintenance, you’re good.

Messaging is more difficult to parse across worlds when we are doing global warnings - I’ve let the team running the downtime know, and we will work on that for future messaging.

Correct, worlds that are the destination world (those that are getting other worlds merged into them) do not experience downtime - wars, invasions, planned PvP fun, whatever you got goin’ on, will not be interrupted as we do not put those worlds into maintenance.

The territory ownership for worlds that are merging is not transferred with the merge - only the destination world retains territory ownership (and those worlds do not experience downtime at the time of the merge, so any wars on destination worlds can go forward with no interruption). Territory owners should be reimbursed for the land ownership lost in a merge.

War declarations should not be possible on the worlds set to merge once they are confirmed for merge either, so if you were able to declare after the messaging went up, let us know. If this war was declared and not already canceled when we posted messaging on the world, let us know too.

You’re making a laughing stock of these cows! Leave them be.

We hear you and are working with our Customer Support folks to ensure we are buttoned up on penalties. Appreciate the details, they help us drill into where process needs to be reevaluated.

Should be up again now.

Going to keep it up for an extra hour into the wee hours of July 5 (1:00AM PT), to make up a bit for the lost time.

It is suppose to run through end of day July 4. It’s being addressed now and should be back up shortly.

Hey there, we just checked in game and the math is adding up as having the 1.25x active. What is your in game name, world and region so we can look at your experience specifically?

Not sure why it didn’t reply to the OG poster - @Coerced this was for you.

Going to send this to QA and see if we can repro. What world were you on, RTT at the time of the hang, and any other details you can provide?

The Ruby gyspum requirement reduction (from two to one) to craft the orb is an intentional change, the note missed our sweep unfortunately. CMs are updating the notes.

this is on our radar, but not ready to share much more than that yet. Should have details to share within the next few months on whether it is possible in the near term.

I said it’s not something to expect in the very near term Re: Transmog. Idk where that post is either.

Also, at some point we will share an updated roadmap (not changes to this year, that hasn’t changed from what Scot already shared in a dev update).

This should be addressed. Let me know if you notice the bug again. Via DM thanks again for reporting.

Thanks for reporting, I’m a bit shocked that Support asked you to keep this topic up.

We ask that any exploitable bugs and behaviors be reported via DM to any of the CMs or Devs.

We have the info now, but in the future please DM.

Though I shouldn’t need to say it, I’m going to anyway: don’t exploit this bug, otherwise our exploit detection may escalate your account for penalty to CS.

Hmmm, no. What is your PTR character name?

omg.

We are looking into this.

the transfer error is related - relog and you should be able to transfer. Let me know if the issue persists after relog.

Fix is in, you will need to relog to pick up the change (no download). Let me know if for some reason the relog didn’t work for you.