#Amber Sea Accumulation Mission Bug (Clear 1 Dimension Domain)

1 messages · Page 1 of 1 (latest)

smoky panther
#
  1. 10:55AM April 30, 2025 & 3:50AM May 2, 2025 (in-game time)
  2. PC
  3. Amber Sea (Challenge Missions)
  4. I had all of Stellar Witching Hour's Dimension Domains cleared before Amber Sea was added to events in-game. One mission requires us to clear 1 Dimension Domain for 100 Tidal Shells.

After clearing, at least 1 Dimension Domain for the first 2 days of Amber Sea, I am unable to to clear the challenge.

daring pasture
#

same, still having the same issue, someone suggested repairing our PGR. I'll try and update again

heavy karma
#

same

smoky panther
#

Day 3 just now, still not working

smoky panther
#

Amber Sea Accumulation Mission Bug (Clear 1 Dimension Domain)

smoky panther
# heavy karma same

be sure to open your own bug report thread to make it easier for the staff to see

inner dagger
#

"We recommend checking related rules in detail in game or with players in our official Discord channels. Thank you for your support and understanding."

#

So here I am 😄

smoky panther
#

I'm coping hard hoping for the clear 1 dimension domain mission to be cleared everytime I clear it once

smoky panther
inner dagger
#

Yes :>

#

I tried everything, recleared stage, did the 100% special stage, did auto-clear, did a normal stage, a boss stage - nothing.

#

I replied to the CS email told them that I did visit the official Discord and there is in fact a bug report for this already :>

smoky panther
#

yea 2 other people reported it too tho I still recommend doing a report so they get the message there's an issue

#

it'll take a bit for them to check here/fix the issue, next time there's a hotfix update, it might fix it

last ore
#

hey guys, can ! make it to 25k on second slot machine if i miss a day?

#

seems kinda impossible unless i got 10 gold cards in 10 pulls

heavy karma
#

yay they mailed us the missing coins

smoky panther
eager whale
#

I don’t rember getting the mail for coins but i reported the bug again, oops