Suppress unnecessary combat log entries (Combat2 2024-03-26.8430092094)
in progress
Thunder Rahja
Every call to llAdjustDamage in an on_damage event results in a CombatLog message, even when:
- the new damage is equal to the current damage, or
- the damage is modified more than once by the same script.
Scripts listening on COMBAT_CHANNEL, and the combat log itself, are subject to spam because of this. Adjustments where the damage does not change should be suppressed, and a script should not trigger more than one combat log entry (the final adjustment) per damage source per on_damage event.
Log In
Kyle Linden
in progress
Thunder Rahja
As of Combat2 2024-03-29.8486222382, the "MODIFY" event has been removed, and "DAMAGE" event has been changed to include a "modifications" collection. Nina showed me this today:
{
"damage": 12.5,
"event": "DAMAGE",
"initial": 25,
"modifications":
[
{
"events":
[
{
"new_damage": 12.5,
"script": "New Script"
}
],
"task_id": "197cc0df-c3bb-9d7d-741e-1e9993d28b8b",
"task_name": "Damage Event"
}
],
"owner": "c5a07167-9bbe-4944-a7b0-a9677afa134d",
"rezzer": "18eb8271-703c-72b0-4b6d-963d61e3cdaa",
"source": "de13170a-1096-7350-7ace-b4bc6150c67a",
"target": "c5a07167-9bbe-4944-a7b0-a9677afa134d",
"type": 0
}