Stop describing a preset materializer that does not exist
LoadoutGenerator.IsAvailable's comment claimed a caller passes it to Loadouts.Materialize. No game path materializes a preset yet. The comment now says a spawner is to pass it, and that none does yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
d503f076e1
commit
d90a65a908
1 changed files with 2 additions and 1 deletions
|
|
@ -149,7 +149,8 @@ public class LoadoutGenerator
|
|||
|
||||
// No galaxy means no availability to filter by: every product is on offer. A fixture generates loadouts that
|
||||
// way, so a test can exercise placement and products without standing up a whole galaxy; no game path does.
|
||||
// Materializing a preset passes this to Loadouts.Materialize, so presets and generation share one availability rule.
|
||||
// Loadouts.Materialize takes availability as a predicate; a game spawner materializing presets is to pass this, so
|
||||
// presets and generation share one availability rule. No game path materializes a preset yet.
|
||||
public bool IsAvailable(FactionProductData product) =>
|
||||
Galaxy == null || Galaxy.IsPrelude ||
|
||||
Galaxy.ContainsFaction(product.Manufacturer) && (Faction == null || Faction.Allegiance.ContainsKey(product.Manufacturer));
|
||||
|
|
|
|||
Loading…
Reference in a new issue