They also appear regardless of whether they were hidden when exiting or not

image-2.png (47,006 bytes)

image-3.png (42,417 bytes)

Also only completed quests are affected

For some reason, I can't reproduce it

For me (Android), it does look like in this bug report, but only visible very short when going frame by frame, the quests instantly separate each other with an animation and look fine.
A strange thing is that the wave quest always showed as uncompleted (state from before starting this game), every time i reopened. The other quests stayed always completed.
When unpausing the reopened game, the reverted wave quests would all re-complete themselves (slower when the gametime is slowmotion) and properly vanish except for the current one as they should.
Attached is a short clip of the animation as it happens for me, looks fine to me.
However this wave-quest thing is not entirely only visual, i tried what happens when you end game without unpausing: The wave quests are correctly gone afterwards even though they were not shown as completed during the game, but you actually get scammed of their rewards (except for one wave quest, which completes between pressing the "end game" button and the game actually ending - seems like a bit of time passes there). So you could in theory lock yourself out of unique wave quest rewards.

Quests are fed into the game while it is running, they are not stored in the replay - wave quests behave as expected.

I don't really know if I should report this as a separate issue, but I get a similar issue to this one where upon continuing a level, and pressing unpause, causes all the previous quests that I've completed to briefly pop up, with some award icons appearing alongside them.

image_2024-05-17_194130743.png (198,763 bytes)

@Oofster - that's intended and works fine. Quests are not stored in the replay and have to be re-simulated on continue.

Should be fixed in build 204, needs testing

looks better now, no more overlap when resuming a level. but i never had them permanently stuck so maybe someone else needs to confirm?
opened separate issue #0002471 for what i mentioned in the comment above

That bug is not related.
Keeping this thread open for a couple of days.