nfextra_modules
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| nfextra_modules [2025/01/06 02:04] – tiwaz | nfextra_modules [2025/01/06 13:49] (current) – tiwaz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== General information about modules in NFEXTRA ====== | ====== General information about modules in NFEXTRA ====== | ||
| - | Not all details will be explicitly mentioned here. | ||
| Some general rules that apply for most if not all modules: | Some general rules that apply for most if not all modules: | ||
| * you can trigger them via trigger | * you can trigger them via trigger | ||
| * the modules effect stop when it is deleted | * the modules effect stop when it is deleted | ||
| - | * in most cases where a module expects a single synced object, you can also sync multiple in which case it randomly selects between all options | + | * in most cases where a module expects a single synced object, you can also sync multiple in which case it randomly selects between all options |
| * when syncing groups of units it does not matter if you sync the leader, the group, or each unit from a group or anything in between. It is smart enough to figure it out and adds the whole group and avoids adding units twice | * when syncing groups of units it does not matter if you sync the leader, the group, or each unit from a group or anything in between. It is smart enough to figure it out and adds the whole group and avoids adding units twice | ||
| * most modules effects follow the module if you move it | * most modules effects follow the module if you move it | ||
nfextra_modules.1736129094.txt.gz · Last modified: by tiwaz
Page Tools
