Xian55
commented
6 months ago Gooday!
Thanks for reaching out for help.
To avoid settling in with premature conclusion, I've been trying to ingest the provided log.
If i seeing correctly you are in a somewhat highly contested area, where one or more other players trying to tag murlocks.
Out of the logged 15 possible kills only 9 has been detected as loot. (comparing the Lost Target! with Kill credit detected! counts)
Out of the 9 detected kills, frankly everyone seems to be successful (searching for [LootGoal ] Loot Successful)
Can you check that, you don't have any Lua errors in game ?
- Here's a guide how to toggle it. Then just try to kill a mob to test what happens.
I'm aware that the kill detection has its limitations due, have to compress a GUID value down to 24bit, and because of that, there's a case when multiple mobs sharing the same unique value.
The compressor currently considers the creatureID/npcId and spawnUID(which is consist of time from epoch and an auto incremented value)
Basically parsing a value like this "Creature-0-1465-0-2105-448-000043F59F" and returns with a unique number
function DataToColor:uniqueGuid(npcId, spawn)
local spawnEpochOffset = band(tonumber(sub(spawn, 5), 16), 0x7fffff)
local spawnIndex = band(tonumber(sub(spawn, 1, 5), 16), 0xffff8)
local dd = date("*t", spawnEpochOffset)
return (
dd.day +
dd.hour +
dd.min +
dd.sec +
npcId +
spawnIndex
) % 0x1000000
endThat i can take a look to reduce collision generation (two killed mob share the same generated number).
Are you aware of any high server latency / lagg ?
- Last time i've checked SoD, the server had serious latency issues, event message processing does not account for any kind of latency scenario. Based on the current lua code, i can imagine a scenario where the
UNIT_DIEDevent is received by the client after the player left combat, and all of these are getting ignored.
function DataToColor:OnLeftCombat()
DataToColor.eligibleKillCredit = {}
endAre you playing the game with a steady FPS count ?
- Having highly volatile FPS count can prevent the backend to work properly. Be sure to manually target X FPS, like 15, 30, 60, 90. From previous testing, it shows major improvement in consistency.
This is non related to the looting issue, for me it seems from the log that casting Wrath sometimes does not work properly ?
Can you tell something about that, have you noticed anything ?
adamssullivan
augerT
thejefu
Sattva-108
Description
While killing the bot will sometimes loot and sometimes not loot. There doesn't seem to be any rime or reason. It just kills the mob and then moves on
Addon Version
1.7.50
World of Warcraft Client
Season of Mastery
Reproduction Steps
The bot will kill and then not loot randomly
Last Good Version
No response
Screenshots
No response
Logs
out20231228.log