I've changed Mudlet's GMCP code in such a way that Achaea should work properly now. This basically means that we have to run table merge scripts on most GMCP messages. This is clearly not as efficient from our perspective, but I can see benefits for MUD servers and I guess that these need to be respected.
The nex Mudlet update will be available in a few days.
[not a bug] GMCP tables
Re: [not a bug] GMCP tables
update on automatic GMCP table merging: Due to obvious inconsistencies with IRE servers (=some tables must be replaced whereas only a single table, namely Char.Status must be merged) I've decided to use user customizable GMCP table merge policies i.e. by default only Char.Status is now being merged while all other tables are replaced. The user can determine which tables are to be merged by adding GMCP keys to a list of tables that need merging. Tables that are not on this list will be replaced.
Re: [not a bug] GMCP tables
As far as I am aware, that is the only table (Char.Status) that needs merging, the others are given the entire table already. Thank you for working on that change Heiko.
Re: [not a bug] GMCP tables
As of 2.0-rc3, the gmcp.Char.Status table now refuses to update at all. I've built a personal workaround in by setting gmcp.Char.Status to nil after all my scripts that use it have checked it, but the problem remains.
Re: [not a bug] GMCP tables
I don't have this problem... has anyone else ran into this?
Re: [not a bug] GMCP tables
What's your OS? Have you messed with the shipped mudlet-lua files? If you are on Linux, make sure to start mudlet from the mudlet/src directory, so that Mudlet can use the shipped mudlet-lua libs.Sanaki wrote:As of 2.0-rc3, the gmcp.Char.Status table now refuses to update at all. I've built a personal workaround in by setting gmcp.Char.Status to nil after all my scripts that use it have checked it, but the problem remains.
Re: [not a bug] GMCP tables
Haven't messed with them at all, on Kubuntu 11.04, compiled with the QT SDK, running from the src directory. Have seen a near bug-free existence with Mudlet so far from 1.1.0 and on, but so far as I can tell, there's nothing awry on my end here. Feel free to nudge with any ideas, I'm happy to help sort it out if possible.
Re: [not a bug] GMCP tables
Can you please try to reproduce your problem on a clean profile without your scripts? Maybe they've changed something on your server.
Re: [not a bug] GMCP tables
Might also be a JIT related issue JIT is being used by default on Linux if available. If you can please also verify your problem on Windows or provide a demo script that shows the problem so we can test it on Windows.
Re: [not a bug] GMCP tables
Just reproduced it on a clean profile with no preexisting scripts. Added this script to monitor it:
As of right now I have no way to test this on Windows, unfortunately.
On each kill, the event was raised and the table was properly displayed. However, once my xp crossed from 26.7% to 26.8%, the table still displayed it as 26.7%. Killing another hunt produced no change. Trying SCORE (which sends a full fresh table) produced no change. Upon setting gmcp.Char.Status to nil, the next kill sent me my proper xp.
As of right now I have no way to test this on Windows, unfortunately.