(When the main villain in your next story is a Zorak Zorani deathlord, and skeletons, zombies, and vampires may play a big role, you start running into these issues :-)).
NOTE: Although I believe there are some systemic issues with such actors in RQG, this is probably actually a Foundry interoperability bug. However, I thought it might at least be a good idea to create an issue here so we could track the solution, even if it means bumping the bug up to the Foundry devs if a more system local solution cannot be found.
RQ "Blank Stats" Can Cause Foundry Fits
When creating prototypes of creatures without some primary attributes (for example, spirits or undead), Foundry will begin throwing exceptions:
foundry.js:753 TypeError: An error occurred while rendering TokenConfig 147. Cannot use 'in' operator to search for 'value' in
at PrototypeToken.getBarAttribute (foundry.js:25031:24)
at TokenConfig.getData (foundry.js:81971:34)
at async TokenConfig._render (foundry.js:5812:18)
at async TokenConfig._render (foundry.js:6532:5)
leading to broken functions (such as Prototype Token button on the actor sheet) and rendering scenes the token is moved into inoperable.
How: To Reproduce
Try, for example, to create a skeleton actor based on the template given in the RQ Bestiary. Skeletons have only STR, SIZ, and DEX - no CON, POW, INT, or CHA. When the actor is created with a blank CON, this renders the Prototype Token button inoperable because Foundry begins to throw exceptions - this is because (I surmise) that by default, Foundry presets the token prototype to display attribute bars and having a blank CON (or POW) causes the exception.
Expected behavior
RQG actors are not required to have "all the stats". A perfectly reasonable RQG actor (a ghost, for example), may only have INT and POW. The system needs to negotiate better with Foundry (or Foundry needs to bend to the system) to not cause exceptions when such actors are created and used in the system.
Environment - please paste the information from foundry settings tab "support" button:
Setting the "blank attributes" to 0 (with 0 as the default generator as well) ameliorates Foundry afaict, although it is not canonically RQG (eg, 0 CON and NO CON have difference connotations in RQG).
(When the main villain in your next story is a Zorak Zorani deathlord, and skeletons, zombies, and vampires may play a big role, you start running into these issues :-)).
NOTE: Although I believe there are some systemic issues with such actors in RQG, this is probably actually a Foundry interoperability bug. However, I thought it might at least be a good idea to create an issue here so we could track the solution, even if it means bumping the bug up to the Foundry devs if a more system local solution cannot be found.
RQ "Blank Stats" Can Cause Foundry Fits
When creating prototypes of creatures without some primary attributes (for example, spirits or undead), Foundry will begin throwing exceptions:
leading to broken functions (such as Prototype Token button on the actor sheet) and rendering scenes the token is moved into inoperable.
How: To Reproduce
Try, for example, to create a skeleton actor based on the template given in the RQ Bestiary. Skeletons have only STR, SIZ, and DEX - no CON, POW, INT, or CHA. When the actor is created with a blank CON, this renders the Prototype Token button inoperable because Foundry begins to throw exceptions - this is because (I surmise) that by default, Foundry presets the token prototype to display attribute bars and having a blank CON (or POW) causes the exception.
Expected behavior
RQG actors are not required to have "all the stats". A perfectly reasonable RQG actor (a ghost, for example), may only have INT and POW. The system needs to negotiate better with Foundry (or Foundry needs to bend to the system) to not cause exceptions when such actors are created and used in the system.
Environment - please paste the information from foundry settings tab "support" button:
WORKAROUNDS
Setting the "blank attributes" to 0 (with 0 as the default generator as well) ameliorates Foundry afaict, although it is not canonically RQG (eg, 0 CON and NO CON have difference connotations in RQG).