From f081a0498147abe6b9c6a635b96f1c86267edeab Mon Sep 17 00:00:00 2001 From: 1Axen Date: Mon, 21 Apr 2025 01:56:40 +0300 Subject: [PATCH] Add docs warning about hook set order --- docs/learn/concepts/component-traits.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/learn/concepts/component-traits.md b/docs/learn/concepts/component-traits.md index 591883d..f27bf81 100644 --- a/docs/learn/concepts/component-traits.md +++ b/docs/learn/concepts/component-traits.md @@ -14,6 +14,10 @@ A (component) ID can be marked with `Tag´ in which the component will never con Hooks are part of the "interface" of a component. You could consider hooks as the counterpart to OOP methods in ECS. They define the behavior of a component, but can only be invoked through mutations on the component data. You can only configure a single `OnAdd`, `OnRemove` and `OnSet` hook per component, just like you can only have a single constructor and destructor. +::: warning +Hooks must be added to a component before it is used with other entities/components for them to take effect. +::: + ## Examples ::: code-group