| 4 people marked this as a favorite. |
We answered this on the discord but I'll post something here to at least put our (The PF2e on Foundry VTT team) position on the remaster where people can see it.
We will be treating the remaster as a large errata. Nothing we've seen thus far looks to be too big a change that the game won't be entirely recognizable. We are not going to fork the system or maintain legacy options unless Pathfinder Society also supports those legacy options. Things like the removal of alignment will likely come with guidance as to what to do with creatures that deal alignment damage on their strikes or abilities and we'll know more about how we'll handle that when we finally see the remastered rules. But things like negative damage becoming void damage is an easy switch for us to do. Removing ability scores, likewise, is something that should be easy to handle.
For changes like creatures not being reprinted, we have no plans to remove creatures from our compendiums. We would need a real reason to actually delete an NPC. Some spells will be rendered useless, like Divine Lance, that will get removed and some new spell will be put in its place in theory but we'll know more when we get the remaster. Things that are getting renamed will just be renamed, and if needed we will migrate the name change. This is most likely in the case of Flat-Footed -> Off Guard, because our automation relies on the item "slug" (A version of the item name that is stable even for people using translated versions of the system) and that slug would change if we change the name in the main system repo. But that's an easy migration to do and for 99% of users they won't notice anything except the normal migration message on loading the system for the first time post remaster.
For premium modules let's lay out what the premium modules even do so people know what the system controls and what the module adds. When you enable a premium module like Gatewalkers it asks you to import the adventure. That adventure is a set of pre-made scenes, journals, macros, etc. The module does not store the full actors it uses, instead it stores a reference to the system's version of those actors. So if the module needs a Mitflit it doesn't use its own version it grabs a new copy from the system and applies any stored changes they have for that actor (such as elite / weak or changing the name of the actor to be a specific NPC). This way the module doesn't have to update or maintain its own actors, they piggyback on ours. If we find a mistake in an actor that actor will be fixed in the next system update, and we have fast turnaround on system releases so we can get fixes out faster than the modules can. So, for the premium modules when you do an import it will grab the remastered versions of monsters when you import, and if you've already imported we will handle migrating any breaking changes on your world's existing actors.
I personally am really looking forward to seeing more of the remaster. Additionally, if anyone wants to help out with our system data entry now is a great time to jump in and learn how to before the remaster comes out so when people get those PDFs we can make sure we keep up our streak of getting content into the system for major books on the release date. We have a Discord server where all us system devs hang out. Feel free to ping me if you want to try a starter data entry (or code) project, as I have a few things good for people new to the process and we can help you get set up.