Passive Tutorial - Revision history

Panda at 21:50, 29 July 2023

2023-07-29T21:50:17Z

← Older revision		Revision as of 14:50, 29 July 2023
Line 80:		Line 80:
	Passives$set(llGetOwner(), "myHealPassive", passive, 0);		Passives$set(llGetOwner(), "myHealPassive", passive, 0);
	</pre>		</pre>
			[[Category:Tutorials]]

Panda at 21:48, 29 July 2023

2023-07-29T21:48:13Z

← Older revision		Revision as of 14:48, 29 July 2023
Line 1:		Line 1:
	The passives system is different from the Effects because of legacy memory reasons. Passives may only be applied to players and cannot affect NPCs. Technically passives are converted to Effects in the HUD but they use a different syntax and set of effect IDs for legacy reasons.		The passives system is different from the [[Effect Tutorial\|Effects]] because of legacy memory reasons. Passives may only be applied to players and cannot affect NPCs. Technically passives are converted to Effects in the HUD but they use a different syntax and set of effect IDs for legacy reasons.

	See got Passives.lsl for a list of passive effect IDs (FXCUpd$*).		See got Passives.lsl for a list of passive effect IDs (FXCUpd$*).

Panda: /* Procs */

2023-07-29T21:39:34Z

Procs

@@ Line 31: / Line 31: @@
    (arr)wrapper
+]
 </pre>

Panda: Created page with "The passives system is different from the Effects because of legacy memory reasons. Passives may only be applied to players and cannot affect NPCs. Technically passives are converted to Effects in the HUD but they use a different syntax and set of effect IDs for legacy reasons. See got Passives.lsl for a list of passive effect IDs (FXCUpd$*). Passives can be set by using the Passives$set method. Passives are stored in a 2-stride array of [(int)effectID, (var)effectData..."

2023-07-29T21:28:02Z

Created page with "The passives system is different from the Effects because of legacy memory reasons. Passives may only be applied to players and cannot affect NPCs. Technically passives are converted to Effects in the HUD but they use a different syntax and set of effect IDs for legacy reasons. See got Passives.lsl for a list of passive effect IDs (FXCUpd$*). Passives can be set by using the Passives$set method. Passives are stored in a 2-stride array of [(int)effectID, (var)effectData..."

New page

The passives system is different from the Effects because of legacy memory reasons. Passives may only be applied to players and cannot affect NPCs. Technically passives are converted to Effects in the HUD but they use a different syntax and set of effect IDs for legacy reasons.

See got Passives.lsl for a list of passive effect IDs (FXCUpd$*).

Passives can be set by using the Passives$set method. Passives are stored in a 2-stride array of [(int)effectID, (var)effectData ... ]. Passives remain in the HUD until the HUD is reset by relogging, changing sim, or resetting. Or until unset by the Passives$rem method.

Example of adding 10% additional dodge chance with a passive:
Passives$set(llGetOwner(), "myDodgePassive", [FXCUpd$DODGE, 0.1], 0);

== Procs ==
Just like active effects, passives can have procs: Apply a wrapper when an event is received.

Proc data is stored in array with the following syntax:
<pre>
[
// Triggers
[
[
(int)wrapper_target,
(str)event_script,
(int)event,
(arr)event_args,
(float)max_range
],
...
],
(int)max_targets,
(float)proc_chance,
(float)cooldown,
(int)flags,
(arr)wrapper
]
</pre>