Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

Map Pack update deleted my unrelated map

I have the  Pathfinder Playtest Flip-Mat Multi-Pack  in my campaign. Today it asked to perform an update. When I logged in directly after performing this update, the top map in my campaign folder had been deleted and replaced with a blank white 25x25 called 'Start'. The player tab, which had been on the deleted map, was also moved to one of the maps from the pack.  Is there any way to get my map undeleted or reverted? I had a lot of carefully placed items on that map, it was the overview map for my entire campaign.
1617565361
Gold
Forum Champion
Uh oh. That's bad.  Good luck.  Symapthies. Try to use the "Roll Back" feature of Roll20. Try reporting your issue in the "Help Center" at the top of Roll20. Notice/Follow there are several other threads about recent Patches that deleted or over-wrote content. Appears to be an ongoing and widening problem.  At first it was Frostmaiden Patch 1.4 and 1.5, but now there are parallel reports for the Salmarsh 1.5 patch, and Out Of The Abyss, and Princes of the Apoc, and now this thread for Pathfinder Flip-Mat Multi-Pack doing this.
Thank you Gold, I greatly appreciate the suggestions. I was unaware of the Rollback feature, it sounds like it should be perfect for this situation!   Unfortunately, the feature is having no effect whatsoever. The Rollback function claims to be successful, but nothing is changed in the campaign. Maps, chat, everything is the same as if I hadn't used the feature, which is surprising. I would think that if the saved states had errors or simply weren't there, the Rollback wouldn't claim to be successful. I've now tried all the saved states which were supposedly made before this problem arose, but no dice.  I will definitely be reporting the issue to the Help Center and keeping an eye out here. Thanks again.