EQdkp-Plus - DKP System - Raidplaner - Guildportal - Gildenportal - WoW, Lotro, Runes of Magic home of the EQDKP Plus Projekt

Hi,

I've followed the steps needed in order to get GetDKP up & running.
I can see that dkp_list.lua has been populated with the data from my dkp page (http//guilds.be/tdc/eqdkp/).
Logs also show that everything went well.

However, the ingame mod is [b]not[/b] displaying the data.
GetDKP is just empty ingame, it also tells me it's in "client mode".

I think this part of your getdkp.php output is responsible:
[quote]gdkp_alliases = {
[""] = {
[1] = "Steffen",
},
}[/quote]
You should delete this alias record.

Strange, I have no aliases setup under "CTRaidtracker Import > List Aliases".

I did install an errorgrabber ingame, because I figured that GetDKP might be outputting an error, and this is what I got:

Date: 2008-07-10 13:40:12
ID: 51
Error occured in: Global
Count: 1
Message: ..\AddOns\GetDKP\GetDKPData\dkp_list.lua line 2082:
'}' expected (to close '{' at line 2075) near 'Sign'
Debug:
[C]: ?

I'm going to go see if I can fix my dkp_list.lua this way, but I still need to know why dkp.exe made this fault there...

Success! I have found the cause of this problem.
One of my members had signed up on the raidcalendar using the following note:

["note"] = "Not sure if i can, but most likely i can join raid, so i set myself as "Sign Up""

The double " " obviously confused GetDKP, because as soon as I removed them and saved my dkp_list.lua, it was fixed.
The mod now works properly!

Thanks Kirax for trying to solve this with me.

I do wonder why the GetDKP mod takes so much extra info like raid signups etc.
It doesn't seem to use it for anything...

Hm - I thought that ""-problem has already been fixed...

This extra info is for the ingame raid planer. This feature came with one of the last revisions. You should update your GetDKP if you can't use it (/gdr command).
Nevertheless you can disable this extra info grabbing in the EQDKP PLUS Config ("GetDKP" tab).

Btw: Alias records like the above one can only be deleted directly from the database (e.g. with phpmyadmin).