Since last update my oset has been wonky.
I find objects when you are copying them from an existing object to make a new one,
well this has problems. When you do this, all seems fine, how ever. When you go into the
"ed" part of it, things go bad. I edit the ed of one of my signs, to save time I copied an existing sign into a new vnum online using ocreate <new vnum> <old vnum> <name>, all the item stats etc transfered fine, even the "ed" which was fine as I can edit those.
So I go and type: oset sign ed sign
Then I am thrown into the buffer, and it shows me the old sign text from the original item, so I do the usual /c to clear it and begin my new sign ed. I then when done use /s to save said "ed" but then I find that instead of replacing the original it has simply created a new ed with the same name, ick..fine I delete them all off it, and start with a new one, now it won't save the "ed" at all....

Odd to say the least...

Would 'oset <vnum> ed sign' be more reliable?
Certainly a strange result either way, but goes a long way towards demonstrating why offline editing is so much better.

I'm having some trouble figuring out what happened. Ryan, can you please post the exact sequence of commands you did? I need more details to narrows this one down.

* I had an area vnums assigned to me.
* I created all my rooms, mobs, objs.
* I installed the area.
* Then I notice I need some signs...

First I created a "template sign" sorta, it was the first sign.
Standard stuff, for creation purposes.
ocreate <vnum> <name>
oset sign ed sign
Do my sign stuff, then /s
Then I folda <area name.are>
I then used ocreate <new vnum> <first sign vnum> sign
for I dunno 8-10 other signs....I go off and drop them all off.
Then I instaroom on all of them, keeping in mind proto. then folda,
then go to first one, and set it to proto, then start to mod the ed.
Now since the update, I can not save the ed part of the sign anymore.
When in the editor.
I would go to the first sign to mod.
Then oset sign ed sign
When this happened it created a second instance of the trigger name "sign"
That was before the update, since the update I can't save the ed function.
So I guess it was buggy before but its worse now...?
Before was an easy solution, delete the first ed and make a new one, now
this is not really a solution as it wont save any text.
Maybe I have it corrupted, shrug I could try a rebuild...

Ok. I think I found this one. If so it was a massive screwup on my part.

In mud.h, locate this:

template< class N > extra_descr_data *set_extra_descr( N *target, string name )

Replace that entire template with this:

template< class N > extra_descr_data *set_extra_descr( N *target, string name )
{
   extra_descr_data *desc = NULL;
   list<extra_descr_data*>::iterator ied;

   for( ied = target->extradesc.begin(); ied != target->extradesc.end(); ++ied )
   {
      extra_descr_data *ed = *ied;

      if( ed->keyword.find( name ) != string::npos )
      {
         desc = ed;
         break;
      }
   }

   if( !desc )
   {
      desc = new extra_descr_data;
      desc->keyword = name;
      target->extradesc.push_back( desc );
      ++top_ed;
   }
   return desc;
}

When I went to replicate this I found that the prototype object itself was not even receiving the description data. Fixing the template corrected that, and since this template is used in editing extra description settings for object indexes, object instances, and rooms, it should correct this defect in all 3 places. But I want to know what happens in your scenario when this template is corrected before I commit the change.

Ok no probs here on the signs now. Issue is resolved on that one.
Thanks again.

It will still crash if you have a bunch of rooms that are not finished. Example:
I was up late last nite building, made a bunch of rooms in prep for todays build.
All I did was simply goto <vnum> and then when I had gone to all I thought I would
be working on the next day, I folda <area name> and went to bed.
I get up log in, and start building, going through rooms that had already had things
done to them, ie descriptions etc. Fine no probs, but when I went to link one of the
premade and not finished rooms by an exit, it crashed. So I waited, logged back in
and tried goto <vnum> crash again. So I guess I was wrong last nite when I said
that this fix took care of the building issues I had. No rush on this, I can go into
the area file and mod it from there, just reporting the effects so far I have noticed.