Official Paizo on d20Pro!!!

There is a paizo external app authorization tool;
This lets d20pro access paizo to see what books/things a client already owns. Then, at checkout, the client is only charged for content they do not already own. So, if you had a module which cost 10 dollars from paizo, and you purchased our 15 dollar conversion (with 10dollar pdf) then the client gets charged 5 dollars. The marketplace reflects this so the client knows they already own the pdf/paizo product to access the paizo API currently, you open D20PRO, log in with your account then click on manage account (Manage Account to enter your Paizo token).

This is currently, in a soft release in the .20 Beta and is not in the wild as of yet, though I believe they (devs and paizo reps) are finally getting forward movement on this and the kinks worked out of it.

 

Ursus! (I see an active trend) yeah, another sore spot we're working on. In order to get the final push for Paizo done we're having to revamp the marketplace substantially. This is taking a LOT more time than I'd hoped. And Paizo keeps sending us the wrong info for testing.

We literally spent months with them populating the wrong vendors products on their end.... very, very frustrating.

 

re: Ursa vs. Ursus - fixed.

 

Yes, we will be building out Automation where ever possible.

 

We rarely if ever give hard dates. Experience has proven it just isn't prudent to do so, it doesn't help anyone on either side of the fence (topic).. It's hard on us as devs, say like something comes up totally unexpected and that is out of our control (has happened more than once) then we have to adjust both internally and externally and go around and change all those dates. This leads to confusion and misinformation both internally and externally. On the outside, it creates unhappiness just in general, if the date is not met or pushed back or changes in any way, resentment builds up in the community.

We do a great deal of communicating with our community and are always willing to give a 'heads up' on the state of things as best we are able to, there are some things, we are not legally allowed to discuss openly; which is also a factor in all of this.

I hope this makes sense, we want everyone to be informed. if you are concerned about this stance, please let me know and I'll see if I can get @owlbear to explain it a bit better than I can.

 

The Pathfinder Core is fairly complete, it'll need testing after completion.
I haven't heard anything as to its timeline recently.

 

Work is steadily walking forward, to my understanding, PF Core is about to go into internal testing/review... It'll then move to release.

 

2nd Edition is still quite some time off. The Playtest is out, I could be wrong, but I doubt we will build out for the Playtest data. If I understand the scene correctly, we will be building out for the full release using the playtest data as a template (planning mechanism).

 

Yes, there certainly is. There's been a lot of bumps in the road, but progress on the original PF1 project is still underway. If folks are interested in helping out, I know that the team member who took on this task would likely be very grateful for an assist.

As you all know, there is a massive amount of PF rules content to sift thru!

For the record, the initial release of the PF Core Rules will be Traits and Content/Text. This will include a new Rules API update to work with Bloodlines which are annoying since they provide bonus spells differently then every other class in the history of 3.5 and its derivatives - ack!

The Bestary I will also release with updated 3.7.x creatures for the full range and official art.

Both of these products are in the pipeline and being actively worked on again as of this month.

Regardings PF2, we're looking at it but not worrying too much about the conversion as it shouldn't be a major undertaking for D20PRO to support both. Additionally, I'm looking at some basic conversion mechanics which would allow rules switching via the Options->Rules panel to actually perform some conversion behind the scenes. This is hypothetical and behind the 3.7.4 update as well as a map update. Although the plan and dev style I've used thus far includes some sliding sideways between tasks -- honestly, I'd go crazy otherwise!