#6 MUF bug with @*alias props

[Wixenstyx]

Near as we can figure out, GLOW's MUF engine currently
returns an oh-so-helpful 'Permission Denied' error when
a MUF program attempts to set a property that begins
with '@' and contains the word 'Alias'.

The logic governing such a safeguard is potentially
pretty understandable, but since it's not the sort of
thing that comes up often, it would be helpful if:

1. This issue was documented ingame somewhere,
preferably in the MUF Manual, so that those of us who
have @prop fixations stand a chance of figuring out
what the heck's going on when we run into it.

or

2. The error text returned as the result of such a
safeguard were at least somewhat more informative than
'Permission Denied'.

Incidentally, this safeguard rejects any attempt by MUF
to set an @*alias prop, regardless of how the program
tries to go about it. Setprop and Addprop both fail,
obviously, but using a MUF 'Force' to force a player to
"@set <whatever>=@*Alias:<whatever>" also results in
'Permission Denied.' The only upshot to the force
technique is that the program itself does not error
out, but rather assumes the prop has been set and
continues on.

I'll attempt to attach a text file of the debug we ran
into for your viewing pleasure!

[Wixenstyx]

Logged In: YES
user_id=1175315

Oh, one more thing...

As a W4 player, I CAN just manually set @*alias props
without a problem. (That is, outside the program I can "@set
#8=@guild/Ec/Alias:EC", and it sets the property without
arguing with me.) The safeguard only comes into play when
using MUF to set the properties.