Menu
▾
▴
#26 cmd-morph within GlowMUF collection
So I've installed everything in order, quite carefully -- everything seems to work just fine...except for the cmd-morph program.
It installed flawlessly, however, when used to create a morph using a description that is an lsedit list, typing !<list name>, nor !_<list name> seems to work, as the prompt suggests it should. I'm wondering if I'm overlooking something somehow, or if it's not attaching the list to the description properly.
Any assistance would be greatly appreciated, thank you for your time.
My apologies, Echartea. For some reason I was never notified of your support request.
I'll take a look at cmd-morph and see what's going on and get back to you.
In what way is it not working?
Is it possible that you were using a client which attaches special meaning to '!'?
Or...you left off the <>, right? That is, if your listname was foobar then you should have typed: !foobar. <foobar> is 'manual syntax' for a required parameter, the <> are not meant to be typed.
It's alright, no worries.
As far as the way in which it's not working, basically I create my new morph, and since I'm using lsedit descs, I plant the listname: in my case, to set my description, I've traditionally used '@desc me={list:femaledelphinian}' so when entering it into the morph, I used '!femaledelphinian' without apostrophes -- since that's the list name.
The yield when using the morph command is that it takes whatever I've set my desc as to <obj>=<listname>.
as far as my client goes, I use SimpleMU -- if it attaches any special meanings to '!' then I'm not aware of it.
I've not heard of SimpleMU behaving that way, either. I'm assuming there's something broken in cmd-morph and I'll track it down. Work has me pretty busy though, so it may take a few days for me to look at it.
It's quite fine -- no rush. Whenever you can get to it is great. Thank you very much for your time.
Ah...
Turns out cmd-morph is dependent on macro-longdesc. Is it possible that macro-longdesc isn't installed? A quick way to check is to type '@register' and see if there is an entry like
list: macro-longdesc(#32FLM2) Ver. FM1.3
If there isn't an entry like that, cmd-morph will not handle lsedit-style property lists correctly.
That would explain it -- no such entry exists on my MUCK. Granted, I'm more of a builder than a coder, and it's more a personal project as opposed to a team-type ordeal, so I'll look to see what I can do about adding that to the database. Thank you very much for your time -- I was right, I would likely have never figured that out on my own.
And after a few quick google searches, macro-longdesc has been added -- that was the problem. After I added that, it works like a charm. Thank you so much!