Pathfinder 2e Creatures/Adversaries from Demiplane Into Roll20

Hi Folks: I feel like I'm close, but missing something here.  I recently did the integration thing, syncing up my Roll20 Pathfinder 2e game with Demiplane.  It seems that creating characters in Demiplane and pulling them into Roll20 works pretty well.  My players are currently rebuilding their characters (birthed originally in Pathbuilder 2e) and bringing them into the game.  I think it will be very good for them. But, how about me?  Demiplane seems to have a pretty rich collection of Creatures that I can look at and review their bios, but I can't seem to bring them into my game.  With the tools synced, I can bring the Demiplane baddies up in the Compendium in Roll20, but still can't get 'em into the journal, put 'em on the map, make swings (etc.) from their character sheets.  Even in the Compendium, they're still just view-only info. I have read where you can open Adversaries in Demiplane and even make modifications and then do swings and such from the character sheets, but all this reference material seems to apply to Daggerheart.  Following the instructions while in the Pathfinder Nexus gets me nowhere.  I feel like I'm close on this one.  Can anyone push me over the hump? Thanks! Stu

Some of the PF2E content can be added, some cannot. If it can be imported into your game, then there will be an "Add" button beside the entry on the list in the Compendium tab. You press the button and wait (in my experience this takes some considerable time) for the entry to be copied over. There is no official Demiplane integration. Everything is in "beta". Macros will not work properly. API will not work properly. Help requests will be dragged out unnecessarily and then dropped.

Thanks Doc.  Sounds like it may be yet another app that's "not quite there".  As a retired developer, I look at this situation and think, "Why don't the Demipane guys just add a feature to their Add Character function?"  When the user selects Add Character, offer up the choice of using the builder, or let them go into the Creatures library and pick something.  Either way, when done, the user has the new character in their Characters library.  From there, the tools are already in place to allow the user to mod the character, use them in a Demiplane game, or add them to the Journal (and game) in Roll20.  Seems to me most of the work for this is already done.  Oh well, there I go doing that logic thing again.

Having the same problem and thoughts as well. The original Roll20 Pathfinder 1e character sheet worked perfectly like this, with drag and drop compedium sheets into journal characters that can be modified after. Totally agree with your 2nd point too. Why can't Creatures just be added as Characters in Demiplane? That would seemingly solve the issue.

Demiplane seems to be fundamentally antithetical to the practice of TTRPGs. It seems to be entirely for the purpose of showing off the products of publishers, not for using them. It doesn't allow for homebrewing or otherwise customizing specific characters or items for use by the GM. I hope that this isn't because of a misguided attempt to convince users to buy products rather than recreate them piecemeal from other sources, but the practices of the platform continue to point me in this direction.

Kinda feel like Demiplane maybe started as a character sheet builder (like Pathbuilder) and has since been trying to become a playing environment (and doing a so-so job).  Roll20 started as a playing environment with so-so character sheet features.  You'd think combining the two would bring a great win, but I'm not sure it's happened yet.  Maybe one day.

The way that acquisition should  have worked is this: Roll20 buys Demiplane, Roll20 tasks the Demiplane team with importing the Demiplane sheets and content into Roll20 content and sheets as appropriate. Roll20 gets the IP, code, and experience native to Demiplane and uses it to improve Roll20. I suspect (or rather, I hope) that the continuation of the two sites is due to the IP associated with Demiplane that is not  native to Demiplane. The RPGs that Demiplane has contracts with may include contract language that will not allow Demiplane to transfer the content to another provider. This would explain why Demiplane exists at all at the present and why Roll20 games don't import content from Demiplane, they open windows that show Demiplane content and (I suspect) access Demiplane through some separate API built for that purpose. I really don't get Demiplane. It has two aspects: 1) character creation and 2) content delivery. From my discussions with Demiplane representatives, they seem to be focused on 2. The character creation seems OK. It is flashy and restrictive. It trades flexibility for affordance, i.e., it allows basic users to create basic characters but it lacks the ability for users to do significant customization. I understand the urge to create a product like this. As to 2), I suppose that it is an effective way to deliver content online. It seems most effective as a means of rent seeking from customers: rather than buy individual products in PDF form and read them, you need to maintain a subscription for full functionality. Perhaps younger customers need things specially formatted for the web/mobile or they aren't interested in reading/buying. I can only hope that some market research lies behind the choices. What drove the acquisition? I suspect part was the threat of Demiplane as a competitor. I suspect part was to get the data assets of Demiplane in servicing content delivery. Nether of these, however, require the bizarre hybrid that Roll20/Demiplane has become.