title placeholder

The goal of IGenericWorldActivityWorker is to operate from a highly leveraged point of view.

To achieve that, it relinquishes awareness about the actual tangible state of the level (where individual agents are, environment queries, etc.), and bases its entire world view from state-indicating (gameplay) occurrences each Crowd Activity worker explicitly broadcasts or notifies its owner.

World Activity Workers can then calculate their next move, and make a decision (based on the strategy it itself follows).

The logic IGenericWorldActivityWorker executes should compliments its relative responsibility down the world-crowd-agent chain by solely being focused on how each FWorldActivity is rolled out, without dwelling inside a specific Crowd or Agent Activity implementation.

ubyte.dev endorses creating GameplayConcepts extending WorldActivityCognition that:

1. Explicitly specify which problem they solve. Example: WorkerStrategyGameplayConcept (included by default) introduces a filtered variant of WorldActivityCognition called WorldActivityStrategy. This concept mandates that these tags always dynamically influence the underlying implementation of a WorldActivity (as its name implies).
2. Explicitly manage their blueprint exposure. Example: WorkerStrategyGameplayConcept introduces BlueprintCallable methods for adding/removing WorldActivityStrategy tags. While this concept is pretty simple, any other concept might require additional encapsulation and/or properties before truly being exposed to the blueprint surface.