Closed brazilofmux closed 9 years ago
Comment #1 originally posted by brazilofmux on 2006-11-28T00:08:57.000Z:
<empty>
Comment #2 originally posted by brazilofmux on 2007-09-20T23:18:19.000Z:
Tweak title.
Comment #3 originally posted by brazilofmux on 2007-09-20T23:55:05.000Z:
<empty>
Comment #4 originally posted by brazilofmux on 2007-10-09T17:36:55.000Z:
<empty>
Comment #5 originally posted by brazilofmux on 2007-10-09T19:07:08.000Z:
Fixed in dev_brazil with r268l. Also, return the first attribute name in %1.
Comment #6 originally posted by brazilofmux on 2007-10-09T19:07:19.000Z:
<empty>
Original issue 59 created by brazilofmux on 2006-09-09T03:27:27.000Z:
On Wed Mar 01 08:51:51 2006, Moleculor reports:
Right, so it's taken me a few days to figure out that this is a bug, but shouldn't @descformat obey the user-defined attributes in reality.setup, just like it obeys user-defined attributes with WOD_REALMS, like it says in the help file? @descformat implies that it takes how the object is supposed to appear to the viewer and makes formatting changes, NOT automatically use @desc as its %0 thingy. %0 should automatically be how it is intended to be viewed. See, if a room lacks a @descformat, your @rxlevel determines how the room you're in (or object, or whatever) appears. If reality.setup defines a user-defined attribute to be used for certain levels, this attribute is used instead of @describe when describing the room. However, @descformat seems to automatically use @desc no matter what when dealing with alternate @rxlevels. This doesn't feel right to me.
[REF: Job 282]