Cover v2

[bofhgr]

• Implement Cover Rules

[bofhgr]

see Cover under Combat rules

[bofhgr]

• 4 types of Cover, for each Energy Type
• similar roll to Hunger Check - 10% to 90%
• Is affected & affects aiming - see #6
• The roll for Cover comes first, before the attempted targeted effect's roll
• Q: Who makes the roll? ^^ what does that mean in terms of execution order/functions affected?

[bofhgr]

cover is made by attacker and comes before activation of items (no destcost)

[bofhgr]

Advanced Cover is coming with V12 - perhaps we don't need much till then?

[bofhgr]

Cover v1 complete with the ability to roll for each type of Cover (found under the Effects Tab) Cover v2 will be about integrating Cover automatically in the Aiming & Targeting system coming with v0.9 Early Access

[bofhgr]

confirm the ruling on cover: assuming I have selected a target as part of my activation that has some kind of cover for the type of damage I am about to apply.

Qs:

• Cover only applies when damage is taking place? Can I skip cover roll if the MP activated does not have damage rolls?
• When should the cover roll take place?
• Should the roll be automated on the player's behalf or should we ask the player to press a button?
• Should there be a mention in the chat if the target doesn't have cover (to remind players they could use cover to deflect this type of activation)?
• Is Cover part of the introductory mp / possession / map ?

[bofhgr]

I have cover.initial - perhaps I should expand this to have initial 0 for most types, then cover.total is calculated as part of derivedData and have the cover coming from effects to set a different value. if so, I should add/include the logic of the UPGRADE option to also work in the derivedData step (?)

Similarly, this also applies to the resistances and the way they should be handled.

[bofhgr]

Marking this as Cover v2 Cover V1 implementation is now part of the System and allows simple Cover rolls based on your manually selected Cover value.

[bofhgr]

Cover isn't going to be part of V12 and as of the latest reddit AMA, it also won't be part of V13 - perhaps V14 but not confirmed - so it's going to be quite a long time before official core support for calculating Cover exists.

Do we proceed with a custom Cover implementation ourselves - meaning calculating cover based on visibility on the canvas, calculating degrees for determining % of token that's visible - seems too much effort for little effect - investigate existing modules that might offer this kind of functionality instead.