#Google Sheet to Foundry PF1

1 messages · Page 1 of 1 (latest)

hallow lotus
#

This might very well end up a somewhat difficult and/or hacky endeavour. The system is decidedly not written with a scenario in mind in which it is not the one in control of its data, and you will have to circumvent a lot of what the system does if you want to do this.
As an example: The system expects an actor to have data.data.abilities.str.value to be a number (e.g. a Strength score of 12), but most calculations will of course not use that value it all. They're interested in the modifier, which the system will derive at runtime in data.data.abilities.str.mod as 1.

lucid saddle
#

The sheet provides for both the attribute value as well as the modifier.

#

The most important thing I need to access would be skills though.

digital cape
#

If you know the ranks, you can update those instead of the totals.

lucid saddle
#

This is the sheet

#

It's a full character sheet, everything is calculated automatically

digital cape
#

Or insert Changes that set the skills to specific values.

#

I honestly feel that using PF1 in Foundry is making this more complicated for you and you'd have more luck using simple world building or something instead in combination of the external sheets.

hallow lotus
#

Trying to shoehorn an external sheet into the PF1 system will be painful, since it simply is not built for that. I was about to offer a simplistic (if tedious) approach of substituting an actor's and their item's data fields with your data on data preparation, but even with that you would most likely end up having to fight the system more often than not.

#

Using another system that does not make as many assumptions about documents and their data would probably be easier. The PF1 system is meant to provide a character sheet, and do all the calculating and data deriving, automatically factoring in feats increasing your damage or ability scores, buffs increasing your AC and so on. If you want and need none of that, there's a good chance the system will just get in your way, since you basically ignore 99% of it.

lucid saddle
#

I use it for npcs though :/

#

I guess having a custom variable to access the data next to foundry variables would je sufficient.

#

Something like @autosheet.str or @autosheet.perception so I can check my players stats and make calculations and stuff.

hallow lotus
#

Do those NPCs have their own actors in Foundry? If you just want some data that can be referred to, you can hook into pf1.prepareBaseActorData (or Derived) and throw your data into the actor's data in there.

#

You can then use your values in rolls, but having @autosheet.perception in there would not affect perception rolls triggered from the sheet or using the system's API in Foundry via Actor#rollSkill etc.

lucid saddle
#

The players using the autosheet have their own Actors. The NPCs use the pf1e system and would not depend on Amy Extertal data.

hallow lotus
#

Ah, I misunderstood. The players use the Google sheet, and NPCs the system, okay.

lucid saddle
#

I understand that this is by no means how the system is intended to be used

#

So if I understood everything correctly (there is a good chance I didnt) I could add skill ranks and bonuses to the foundry sheet of my players, right?

#

What prevents me from setting the attribute values in the character sheet?

#

(Whereas attributes aren't even top priority right now, skills and maybe defenses would be awesome)