forked from GitHub-Mirrors/foundry-sw5e
Update default values of temp data
Update defaults to null from 0 to allow descriptor of fields to show
Noted by Bacalla:
8206774843
I followed suit from the HP model, need to test to make sure this doesn't break anything. All the code appears to default to 0 if it is null.
This commit is contained in:
parent
a9b261d397
commit
4d67bef903
3 changed files with 16 additions and 16 deletions
|
@ -1256,14 +1256,14 @@ export default class Actor5e extends Actor {
|
|||
const dfp = data.attributes.force.points.max - data.attributes.force.points.value;
|
||||
const updateData = {
|
||||
"data.attributes.hp.value": data.attributes.hp.max,
|
||||
"data.attributes.hp.temp": 0,
|
||||
"data.attributes.hp.tempmax": 0,
|
||||
"data.attributes.hp.temp": null,
|
||||
"data.attributes.hp.tempmax": null,
|
||||
"data.attributes.tech.points.value": data.attributes.tech.points.max,
|
||||
"data.attributes.tech.points.temp": 0,
|
||||
"data.attributes.tech.points.tempmax": 0,
|
||||
"data.attributes.tech.points.temp": null,
|
||||
"data.attributes.tech.points.tempmax": null,
|
||||
"data.attributes.force.points.value": data.attributes.force.points.max,
|
||||
"data.attributes.force.points.temp": 0,
|
||||
"data.attributes.force.points.tempmax": 0
|
||||
"data.attributes.force.points.temp": null,
|
||||
"data.attributes.force.points.tempmax": null
|
||||
};
|
||||
|
||||
// Recover character resources
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue