Hey,
(Hopefully this'll get through OK - can't see the New Ticket link on the
dev.pennmush.org site atm.)
There seems to be a bug in Penn 1.8.3p1 and greater when setting standard
attributes via ATTRIB_SET (&attr, @attr or @_attr). It doesn't happen when
the command is typed from a client, but does when a Thing is @forced to set
the attribute. Instead of getting the flags defined via @attribute, it just
gets set no_command. The problem seems to be that set_default_flags in
attrib.c was changed so that the flags passed as it's second arg take
precedence over the standard attr flags (and it seems that it gets passed
no_command when an attr is set with ATTRIB_SET any way but from the socket).
I can't see that change mentioned in the changelogs, so I'm not sure why it
happened, but it seems it should either be reversed, or changed so it gets
both the standard flags and those passed to set_default_flags.
Hope that makes some sense. Probably shouldn't send these so late at night
;p
Mike
This was found by Whiskey@M*U*S*H, btw, I just helped him debug why it was
happening.
