Well, I've gotten myself back in the same situation and I'm not sure what to do to fix it. I updated my condition code and it had some errors in it and now, every time I launch lem, I get the "bind" errors again. I can (again) manually enable/disable the condition in the GUI, but since /lem isn't getting "bound" correctly, I can't call "/lem cond" anymore. I fixed the code and everything works fine on a 2nd character that
had not previously launched the "bad" version of the code, however the character that did is now stuck with those bind errors. I took the "
characters/<charname>.lua" file from the "good" character and copied the contents to the "bad" one, but it's not resolving the issue. I also searched everywhere I could find in the base "lem" directory and can't see where it's causing this to happen on one character and not the other. It's like something outside the "lem" directory is getting updated and I can't clear it. I've attached the contents of the "
characters/<charname>.lua" file that works on one char and not the other. Any suggestions of where to look? It's driving me crazy that every time I make a syntax error in a condition that this happens.
LEM characters LUA file
Code:
-- Persistent Data
local multiRefObjects = {
} -- multiRefObjects
local obj1 = {
["events"] = {
};
["conditions"] = {
["GetMana"] = true;
};
}
return obj1