Skip to content
Version 2.11.0
2.11.0 latest releaseRelease snapshots start with the next framework release.Changelog →
↓ Get the launcher

CombatEvent.EntityBuffsSeeded record

An entity’s COMPLETE buff set arrived as one snapshot — an AOI appear (SyncNearEntities``Entity.buff_infos) or the local player’s EnterScene entity (spec-from-talent-buffs, 2026-09-26). Snapshot semantics: Buffs REPLACES whatever the consumer held for TargetId — buffs it held that are not listed are gone, listed ones are current. Raised once per snapshot — including an empty snapshot when a set WAS held for the entity (so a consumer can clear); an empty snapshot for an entity with nothing held (a mob/NPC appearing buff-less) raises nothing — and INSTEAD of per-buff BuffChanged events: a town crowd of 30 players × ~120 buffs is 30 events, not thousands. Live changes afterwards arrive as per-buff BuffChanged events exactly as before. By the time this event fires, BuffsFor already returns the new set. A snapshot the client could not decode completely is skipped (no event, held set untouched).

Lifecycle after a seed: a later live delta for a seeded buff arrives as Refreshed (or nothing, if identical), never Applied; its expiry arrives as Removed. A consumer that needs the “first application” of a buff must treat its presence in the seed as that application.

public record EntityBuffsSeeded : IEquatable<CombatEvent>

Public Members

Section titled “Public Members”
name description
EntityBuffsSeeded(…) An entity’s COMPLETE buff set arrived as one snapshot — an AOI appear (SyncNearEntities``Entity.buff_infos) or the local player’s EnterScene entity (spec-from-talent-buffs, 2026-09-26). Snapshot semantics: Buffs REPLACES whatever the consumer held for TargetId — buffs it held that are not listed are gone, listed ones are current. Raised once per snapshot — including an empty snapshot when a set WAS held for the entity (so a consumer can clear); an empty snapshot for an entity with nothing held (a mob/NPC appearing buff-less) raises nothing — and INSTEAD of per-buff BuffChanged events: a town crowd of 30 players × ~120 buffs is 30 events, not thousands. Live changes afterwards arrive as per-buff BuffChanged events exactly as before. By the time this event fires, BuffsFor already returns the new set. A snapshot the client could not decode completely is skipped (no event, held set untouched).
Buffs { get; set; } The complete buff set; empty when the entity carries none. Read-only (the same instance BuffsFor returns until the set next changes).
TargetId { get; set; } The entity whose buff set was seeded.

See Also

Section titled “See Also”