Check compatibility before the calendar
Generated links identify the course version so a score from one set of rules is not silently presented as equivalent after a version change. They also require a valid score and, for Daily, a real calendar date in the expected format. A partially copied URL or an edited parameter can break those checks. Use the complete generated link rather than reconstructing it from a screenshot.
Check local discoveries
A compatible invitation does not grant discoveries. Daily requires thirty-five total explored gaps, Moss requires ten and Ember requires fifty-five. If the requested course or companion is unavailable, the game selects an available alternative and drops the mismatched target. A locked forest is different: falling back to Wildwood changes presentation without changing the requested movement and obstacle pattern.
Know when a new invitation is clearer
Choosing another course or companion clears the incoming challenge context, so returning to the menu can intentionally leave the invitation behind. If the sender and recipient cannot reproduce the same setup, finish a fresh run with settings both can access and share that result. Do not promise that a years-old link will preserve its original rules indefinitely. A current compatible link and a visible course date provide a much clearer comparison. If an invitation opens as an ordinary game, that alone does not show that browser storage has been lost or that the sender’s score was false.