Difference between revisions of "RegisterForNiNodeUpdate - Form"
Jump to navigation
Jump to search
m (Cecell moved page RegisterForNiNodeUpdate to RegisterForNiNodeUpdate - Form: Following convention, left out the suffix (owning script)) |
|||
| Line 2: | Line 2: | ||
[[Category:Papyrus]] | [[Category:Papyrus]] | ||
[[Category:Functions-Papyrus]] | [[Category:Functions-Papyrus]] | ||
'''Member of:''' [[ObjectReference Script]] | '''Member of:''' [[ActiveMagicEffect Script]], [[Form Script]], [[ObjectReference Script]] | ||
Activates this item with the specified reference as the activator. | Activates this item with the specified reference as the activator. | ||
Revision as of 22:08, 1 December 2021
Member of: ActiveMagicEffect Script, Form Script, ObjectReference Script
Activates this item with the specified reference as the activator.
Syntax
Function RegisterForNiNodeUpdate() nativeParameters
None
Return Value
None
Examples
; Have the player 'activate' the door
NeatDoor.Activate(Game.GetPlayer())
; Have the player 'activate' the door, bypassing any blocked activation and NOT sending an event to any script
NeatDoor.Activate(Game.GetPlayer(), true)Notes
If the object reference has had activation processing blocked, this will still send the OnActivate event to scripts attached to the object, but will ignore normal processing (i.e. picking up the object, opening the door, etc). Unless, of course, you have the abDefaultProcessingOnly parameter set to true, in which case no event is sent, and the block flag is ignored.