LlDamage - Revision history

Nexii Malthus: Clarify exceptions more directly

2024-08-05T11:51:26Z

Clarify exceptions more directly

← Older revision		Revision as of 04:51, 5 August 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
	* Calls are throttled to a rate of ≤10/30sec per recipient.		* Calls are throttled to a rate of ≤10/30sec per recipient. Exceptions are:
	** ~~There may be some exceptions to this throttle like the recipient being the~~ avatar of the attachment ~~or if the recipient~~ is sitting on the object.		** Recipient is avatar of the attachment.
			** Recipient is sitting on the object.
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Nexii Malthus: Have added another statement about exceptions see https://feedback.secondlife.com/combat-20/p/lldamage-unthrottle-for-cases-where-abuse-is-unlikely -- Also all limits/throttles are up to being changed at any time. We just need to document these changes when they happen or are noticed. Otherwise we'd end up plastering the whole wiki with these notices.

2024-08-05T11:48:29Z

Have added another statement about exceptions see https://feedback.secondlife.com/combat-20/p/lldamage-unthrottle-for-cases-where-abuse-is-unlikely -- Also all limits/throttles are up to being changed at any time. We just need to document these changes when they happen or are noticed. Otherwise we'd end up plastering the whole wiki with these notices.

← Older revision		Revision as of 04:48, 5 August 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
	* Calls are throttled to a rate of ≤10/30sec per recipient. ~~This~~ may be ~~changed in~~ the ~~future~~.		* Calls are throttled to a rate of ≤10/30sec per recipient.
			** There may be some exceptions to this throttle like the recipient being the avatar of the attachment or if the recipient is sitting on the object.
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Ghost Menjou at 10:36, 1 August 2024

2024-08-01T10:36:02Z

← Older revision		Revision as of 03:36, 1 August 2024
Line 38:		Line 38:
	\|also		\|also
	\|notes		\|notes
			\|haiku=
			{{Haiku\|Damage script invoked\|Virtual wounds in the game\|Pixels feel the pain}}
	\|cat1=Combat2		\|cat1=Combat2
	\|cat2=Script		\|cat2=Script

Ghost Menjou at 10:30, 1 August 2024

2024-08-01T10:30:03Z

← Older revision		Revision as of 03:30, 1 August 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
	* Calls are throttled to a rate of ≤10/30sec per recipient.		* Calls are throttled to a rate of ≤10/30sec per recipient. This may be changed in the future.
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Nexii Malthus: Add note about the function call throttle for llDamage which may inhibit some damage-over-time usecases

2024-08-01T09:05:46Z

Add note about the function call throttle for llDamage which may inhibit some damage-over-time usecases

← Older revision		Revision as of 02:05, 1 August 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
			* Calls are throttled to a rate of ≤10/30sec per recipient.
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Nexii Malthus: Add note about being able to go beyond 100 damage via llDamage

2024-08-01T03:29:48Z

Add note about being able to go beyond 100 damage via llDamage

← Older revision		Revision as of 20:29, 31 July 2024
Line 3:		Line 3:
	\|func=llDamage\|return_type=		\|func=llDamage\|return_type=
	\|p1_type=key\|p1_name=target\|p1_desc=The key for the task or avatar that will receive damage.		\|p1_type=key\|p1_name=target\|p1_desc=The key for the task or avatar that will receive damage.
	\|p2_type=float\|p2_name=damage\|p2_desc=The amount of damage to deliver to the targeted task or avatar.		\|p2_type=float\|p2_name=damage\|p2_desc=The amount of damage to deliver to the targeted task or avatar. Unlike collideable damage such as llSetDamage or REZ_DAMAGE, this can be above 100.
	\|p3_type=integer\|p3_name=damage_type\|p3_desc=The type of damage to deliver to the targeted task or avatar.		\|p3_type=integer\|p3_name=damage_type\|p3_desc=The type of damage to deliver to the targeted task or avatar.
	\|func_desc=This function delivers damage to tasks and agent in the same region.		\|func_desc=This function delivers damage to tasks and agent in the same region.

Nexii Malthus: Removed caveat, you can set damage above 100.0 it seems via llDamage, pretty sure I tested this before so it may have been changed in the latest bluesteel version

2024-08-01T03:00:35Z

Removed caveat, you can set damage above 100.0 it seems via llDamage, pretty sure I tested this before so it may have been changed in the latest bluesteel version

← Older revision		Revision as of 20:00, 31 July 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
	* Applied damage is limited to a maximum of 100.0 like any other delivered damage, although llAdjustDamage can be used to exceed the limit through type weaknesses
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Nexii Malthus: Add a note in caveats about the maximum delivered damage being 100.0

2024-08-01T01:18:34Z

Add a note in caveats about the maximum delivered damage being 100.0

← Older revision		Revision as of 18:18, 31 July 2024
Line 10:		Line 10:
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=
			* Applied damage is limited to a maximum of 100.0 like any other delivered damage, although llAdjustDamage can be used to exceed the limit through type weaknesses
	* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.		* Triggering the damage throttle will shout an error to the debug channel and the script will continue running.
	* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.		* The prim containing the script and the prim receiving the damage must both be in damage enable parcels.

Nexii Malthus: Same per llDetectedDamage

2024-08-01T00:58:48Z

Same per llDetectedDamage

← Older revision		Revision as of 17:58, 31 July 2024
Line 28:		Line 28:

	\|constants={{LSL Constants/Damage_Types}}		\|constants={{LSL Constants/Damage_Types}}
			{{LSL Constants/Custom_Damage_Types}}
	\|examples		\|examples
	\|helpers		\|helpers

Rider Linden at 22:33, 7 June 2024

2024-06-07T22:33:08Z

← Older revision		Revision as of 15:33, 7 June 2024
Line 7:		Line 7:
	\|func_desc=This function delivers damage to tasks and agent in the same region.		\|func_desc=This function delivers damage to tasks and agent in the same region.
	\|return_text		\|return_text
	\|spec=~~{{LSL Warnings/Combat2}}~~		\|spec=
	The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.		The llDamage function triggers a damage event on the targeted task. If any scripts in the target process the [[on_damage]] event, they will be fired before the damage is applied or distributed.
	\|caveats=		\|caveats=

← Older revision		Revision as of 20:29, 31 July 2024
Line 3:		Line 3:
	\|func=llDamage\|return_type=		\|func=llDamage\|return_type=
	\|p1_type=key\|p1_name=target\|p1_desc=The key for the task or avatar that will receive damage.		\|p1_type=key\|p1_name=target\|p1_desc=The key for the task or avatar that will receive damage.
	\|p2_type=float\|p2_name=damage\|p2_desc=The amount of damage to deliver to the targeted task or avatar.		\|p2_type=float\|p2_name=damage\|p2_desc=The amount of damage to deliver to the targeted task or avatar. Unlike collideable damage such as llSetDamage or REZ_DAMAGE, this can be above 100.
	\|p3_type=integer\|p3_name=damage_type\|p3_desc=The type of damage to deliver to the targeted task or avatar.		\|p3_type=integer\|p3_name=damage_type\|p3_desc=The type of damage to deliver to the targeted task or avatar.
	\|func_desc=This function delivers damage to tasks and agent in the same region.		\|func_desc=This function delivers damage to tasks and agent in the same region.