summon command/endpoint to support old player damage leaderboard in console

[ffafearitself]

Describe your idea

If a new bool logSummonPlayerDamage is true in config.lua, then upon killing the Pal spawned via summon, then the previous summon damage logs/leaderboard format we used to have will be sent to console.

Example of previous format being spoken of:

[20:24:47][info] [Broadcast] -> [SYSTEM]DG_WORLD_BOSS_BluePlatypus has been killed by Le mange Pal
[20:24:47][info] DG_WORLD_BOSS_BluePlatypus has been killed by 'Le mange Pal' (UserId=steam_7XXX, IP=0.0.0.0, UID=F7974513-00000000-00000000-00000000)
[20:24:47][info] [Broadcast] -> [SYSTEM]Top 6 Damage:
    1. [Mugi's] Le mange Pal: 316759
    2. [La garde impériale] Oztrik3r_57: 102625
    3. [OverKrieg] STban81: 61002
    4. vivien64: 6608
    5. Isane: 2592
    6. Orionn_FR: 14

There is spawnpal_ex and spawnpal_ex_j, but spawnpal_ex doesn't support either of the Summons or Templates folders with the interior .json files. And spawnpal_ex_j only supports the Templates folder.

I believe summon was simply overlooked and forgot to be added in the previous backwards compatibility patch. It would be great if a bool was introduced to config.lua that would support the previous summon damage format that was sent to the console.

Purposes

Custom programs/scripts that were built and parsed the above-posted summon damage logs would be able to use it again. Backwards compatibility was provided for the two other commands, but not for the actual summon command and endpoint.

Expected Behavior

Listed in the "Describe your idea" section.

If logSummonPlayerDamage : true, then instead of having it go directly to the console again, you could also have it go to a new path such as .../PalDefender/Logs/SummonDamageLogs/uniqueid.json like Zvend suggested as well. Either or would work.

Attachments

No response

Priority

High