PoignardAzur

See Pocket

The main semantic interest (beside performance benefits) is the ability to write

if (entity.hasComponent!Foobar)
  entity.component!(Foobar).doThing(...);

Also, apply a system only to entities with the relevant components (example?)

PoignardAzur

Inspired by the board game "Scotland Yard".

The player is invisible, but leaves clues/breadcrumbs that let NPCs guess its path.

The IA can follow simple patterns (eg straigt lines, the player disappearing next to a ventilation duct) to anticipate the player and lay ambushes.

PoignardAzur

Critical hits

Two types of hits: normal and critical.

Every weapon has a "edge", a different way of making crits. (see also Dead Cells)

Edges are related to mechanics of the combat system, eg:

• Parrying,
• Backstabs,
• Dodging,

PoignardAzur

22 - Wrappers
35 - API
39 - Naming
60 - Security
73+74 - Logs
91 - Brevity
98 - Anti-patterns teaching
100 - 10.000 mistakes
104 - Guard rails
109 - Generic solutions

PoignardAzur

DIP - Unique pointers

Rationale

The use case for unique semantics is pretty common:

struct SmartPtr {