Hi. When I start a particular mud file, I get an error message:
line 8 MUSHclient\worlds\constants.lua was not found
I assume this is a problem with an include somewhere, but I don't know how to troubleshoot it. It gives a line number, but no file name. I've searched all of my plugin files and none of them reference constants.lua.
If I move constants.lua to \worlds it just gives me another error about a different line number, so that doesn't solve it. Where would I begin to find the problem?
I'm using a chat window plugin and one of my own. I moved that folder out and deleted them from the plugins to load in the client, but the message still happens.
I open the mud file, I get the constants not found message. I copy constants.lua, paste it into the worlds directory. Then I get the tag error. If I remove the plugins directory altogether, I still get the tag error. (I initially get an error that the two plugin files that I use aren't there, and not loaded, but just the first time.) I also deleted the scripts file(which is empty), which gives me an error about that file not being there, but I still get the tag error.
Those two that I quoted before are the error messages in their entirety. The constants.lua missing one if that file is in the plugins directory, and the tag error one if I copy it into the worlds directory.
If I delete my plugins before uninstalling them in the client (with the mud file open) then I get this error:
Line 5668: \worlds\plugins\ToggleButtons.xml contains an invalid path. (Not loaded)
But only once, and only when the plugins are deleted, like I mentioned.
You are clearly using a plugin which has 5668 or more lines (that's a lot!).
It is completely out of my control what goes wrong when plugins fail. Instead of posting here you need to contact the plugin author. Failing that, examine the plugin and see what the problem is. Failing that, stop using the plugin.
So if I uninstall (remove) the two plugins that I load (neither of which are over 500 lines), and completely delete the plugins directory, there is still a possibility of a plugin loading?
I just want to make sure I understand what "using a plugin" means. When I open a mud file, I do file->plugins, and the little box pops up with nothing in it. Is there some other way to "use a plugin"?
I went through every plugin in the plugins directory looking for a constants.lua include, and couldn't find one. To the best of my knowledge, this is the only place where plugins are saved. But even if they snuck in somewhere else, if they exist at all does it matter if they aren't in the little plugins box? If they aren't being loaded why would they cause an error message?
I just want to make sure I understand what "using a plugin" means. When I open a mud file, I do file->plugins, and the little box pops up with nothing in it. Is there some other way to "use a plugin"?
Well, no. But I don't understand where these messages are coming from.
Well there's the 5k+ line file. The constants.lua include was there, so I modified the path and that solved that error. I still get the line 6 tag error though, which in that file line 6 is just a comment with the mushclient homepage.
I wouldn't think posting the 5k+ line file here would be prudent, but I will if there aren't any suggestions about the tag error.
I've gone through and I don't see any elements without proper tags. I can post just the world element, or any specific element, etc.
And I was playing with the path to try to get it into the plugins directory.
Removing that line solves the problem though, so thank you very much. I'm curious how that got there to cause a problem and if it not being there is going to cause any future problems?
I didn't even realize the .mcl files were editable in that manner, so I've never even opened it.
Quite interesting, and I'm glad I found this thread. It has been happening to me for a long time, and I know I'm not the only one. Mine happened to appear in the Aardwolf.mcl file. Nick, have you been putting things in places they shouldn't be??!
Commented out the line just in case it turns out to be game-breaking, but seems fine so far!