matanlurey / swlegion-archived Goto Github PK

... to share displayName and description, for example.

I.e. replace Instance of UnitKeyword.

See https://tabletopadmiral.com/static/legion/images/Scout%20Troopers/Sonic%20Charge%20Saboteur.png.

... to allow them to be re-used in different contexts.

It would also be nice to have guidelines on what the dimensions for various assets should be, too.

• Objectives
• Deployments
• Conditions

• https://www.fantasyflightgames.com/en/news/2019/2/5/rebel-with-a-cause/
• UnitKeyword.kDangerSense
• UnitKeyword.kInfiltrate
• UnitKeyword.kQuickThinking

'unhindererd' instead of 'unhindered' keywords on Bossk, Wookiee Warriors, and Environmental Gear. 'Wookie Warriors' instead of 'Wookiee Warriors.'

• https://www.fantasyflightgames.com/en/news/2019/1/17/unsung-heroes-1/
• ... for Imperial Specialists

See https://pub.dartlang.org/packages/swlegion#-analysis-tab-.

Or change description.

The long-form description is too hard to read as a reference.

This will allow users to create armies that only contain units from certain releases, mostly common to exclude pre-release units, or units that are not accepted at a given tournament or match.

• Add <Unit>.wave
• Add class ReleaseWave with various waves in the catalog.
• Add final ReleaseWave currentWave.
• Add <ReleaseWave>.isReleased as a check against currentWave.

... of Unit and Upgrade for ArmyUnit. This will allow making the connection between the mutable and immutable classes more opaque, which means it will no longer require storing the catalog in JSON format to save Army[Unit] instances.