87 - [Bug] EQDKP Export (dkp value)
When using headcount to parse my raid logs, it assigns a dkp value to every item it drops. Since i usually don't like doing it middle raid to avoid loss of time, letting eqdkp assign values if the item previously existed on the db, i leave it at the default, 0.
Now the problem is that the same value (0) is exported in the dkp string and when adding to eqdkp, all the items get "filled" with a dkp value of 0, so eqdkp doesn't get the previously value on the db.
Importing a raid with another addon (ctrt for example) works as intended.
| User | When | Change |
|---|---|---|
| Koopie | Sat, 28 Mar 2009 10:54:33 | Create |
- 2 comments
- 2 comments
Facts
- Last updated on
- 28 Mar 2009
- Reported on
- 28 Mar 2009
- Status
- New - Issue has not had initial review yet.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- #2
Koopie Sun, 29 Mar 2009 09:31:35Indeed a missing feature :)
Working just great with that change. Cheers
- #1
Gorofin Sat, 28 Mar 2009 14:00:05It's not a bug, it's a missing feature :). My dirty solution is this one in Exporter.lua around line 1036:
-----------
if ( lootCost > 0 ) then
noteElementContent = noteElementContent .. " - " .. lootCost .. " DKP]]>" -- add cost to note
else
noteElementContent = noteElementContent .. "]]>" -- add cost to note
end
------
instead of
------
noteElementContent = noteElementContent .. " - " .. lootCost .. " DKP]]>" -- add cost to note
------