You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A "Cover" column is displayed under vehicle Features -> Actions, but there is no UI to set this value.
The MountableTemplate data model, which includes the cover field, is only mixed into weapon/equipment-type items, but neither of these allow the field to be set in the UI. Additionally, each of these have their own sheet header, neither of which have a "cover" column.
Exporting a working actor from dnd 3.3.1:
but when imported into dnd 4.1.2:
blanks the "Cover" display, and when exported from 4.1.2, the "cover" field is missing from the resulting JSON.
- Move `cover` from `MountableTemplate` to `FeatData` since feats
are the only item type that display this data on vehicles
- Add "Vehicle Feature" type for features and display a cover
field if this type is selected
- Remove `armor` from `MountableTemplate` and define directly on
`WeaponData`, since `EquipmentData` already has armor
- Move to using localization prefixes for mountable labels
- Change cover labels shown on vehicle sheet to remove distinction
between `0` and `null` values
Closes#4929Closes#4931
A "Cover" column is displayed under vehicle Features -> Actions, but there is no UI to set this value.
The
MountableTemplate
data model, which includes thecover
field, is only mixed into weapon/equipment-type items, but neither of these allow the field to be set in the UI. Additionally, each of these have their own sheet header, neither of which have a "cover" column.Exporting a working actor from dnd 3.3.1:
but when imported into dnd 4.1.2:
blanks the "Cover" display, and when exported from 4.1.2, the "cover" field is missing from the resulting JSON.
JSON exported from 3.3.1:
fvtt-Actor-test-vehicle-PaPE3J59L6Wcq8NN.json
JSON exported from 4.1.2:
fvtt-Actor-test-vehicle-T0Nk9Ntj3G34tDCY.json
Env:
The text was updated successfully, but these errors were encountered: