Quote:
Originally Posted by Farling
This would then reduce the requirement down to HeroLab supporting having characters from multiple files displayed in a "single portfolio" view, and monitor for changes to files so that it can prompt the user to ask if they want to reload the updated character's portfolio.
I don't see the need to store player's character HL portfolios inside RW.
|
- At the start of the session, import the characters from the shared drive copy to the GM's "the party" copy (replace existing if necessary). All PCs are now in one portfolio.
- Launching encounters from Realm Works automatically merges them into the running copy for combat.
- After the session (or as otherwise desired), export the GM's "master" copy of each PC to the shared drive, one by one, over-writing any existing file. Alternatively, export as a separate "draft" file so the player can call out discrepancies. When resolved, only one file per PC should remain on the shared drive.
- If desired, delete the local copy from the GM's "the party" set (keeping any NPCs needed).
Aside from that, remember that per-character reveal is "coming". To do that, it means that Realm Works needs to be aware not just of the Players, but the Player Characters, internally. That also at least implies that PCs will be somehow distinguishable from "Individual" Topics. Like many other initiatives, this has been pushed to the back-burner while the Content Market dominates the available working time. Once the Content Market is out, Rob has indicated that there will be another survey .. so something to keep in mind when assessing your priorities for that.