hide @power for mortals

[brazilofmux]

Original issue 231 created by brazilofmux on 2006-12-12T16:41:27.000Z:

TinyMUX 2.4.3.32 TinyMUX 2.6.0.17

Reproducible Steps:

Create a player with the hide @power, and the DARK flag turned on. Use another player in the same room to look at the room and the player.

Observed behavior:

Others players can still see them in room contents, has arrived messages, and so on.

Expected behavior:

Players would be unseen in the room contents, unavailable for look, and not trigger the arrived messages.

[brazilofmux]

Comment #1 originally posted by brazilofmux on 2006-12-12T16:41:59.000Z:

There are still several kinds on hiding which not only require the hide @power and the DARK flag, but also require that you be set WIZARD. In predicates.cpp, can_see() uses the Dark() macro which requires the WIZARD flag.

For mortals, the hide @power was originally only for at-a-distance hiding (i.e., WHO list, matching connected players, etc.). Hiding within the same room was specifically excluded.

Should it continue to be that way? I'm not so sure anymore. Then, there is the question of can it get into 2.6 and should it backpatched to 2.4.

[brazilofmux]

Comment #2 originally posted by brazilofmux on 2006-12-12T18:56:46.000Z:

There seems to be some support for maintaining two levels of hiding. The so-called who-hiding or hiding-at-a-distance. And, then then full wiz-powered hiding without a WIZARD bit.

Here's the PennMUSH help topic for @hide -- which corresponds to the behavior in TinyMUX with hide-@powered mortals using the DARK flag.

@hide[/<switch>]

This command enables a royalty, wizard, or player with the Hide power to disappear from the WHO list for mortals. "@hide/yes" or "@hide/on" hides the player, "@hide/no" or "@hide/off" unhides the player. Hidden players are marked as "(Hide)" in the privileged WHO listing.

Mortals can not use the CONN(), IDLE(), or LWHO() functions to find hidden players.

Rhost has implemented @hide as well. What isn't clear yet is whether @hide state is persistent or not. The DARK flag and hide @power are persistent. In any case, before making the behavior of DARK the same for both hide-@powered mortals and Wizards, we need to add a separate WHO-hidden ability...such as @hide, or something close to it.

Doing both of these things is too much to implement and test in the time remaining for TinyMUX 2.6, so the Milestone has been changed to 2.7A.

[brazilofmux]

Comment #3 originally posted by brazilofmux on 2007-08-07T01:31:32.000Z:

Perhaps this gets split out into two powers:

hide -- General WHO hiding but has no impact on being seen when in the same area as others. The current behavior.

dark -- As hide but gives essentially the same capability as a wizard set DARK.

Are there nuances I'm overlooking?

[brazilofmux]

Comment #4 originally posted by brazilofmux on 2007-08-07T02:11:56.000Z:

That seems about right.

[brazilofmux]

Comment #5 originally posted by brazilofmux on 2007-08-25T20:54:19.000Z:

I agree. I think the terminology has plenty of precedent, and 'hide' does not equal 'dark'.

[brazilofmux]

Comment #6 originally posted by brazilofmux on 2007-12-18T03:58:51.000Z:

<empty>

[brazilofmux]

Comment #7 originally posted by brazilofmux on 2007-12-18T04:06:32.000Z:

<empty>

[brazilofmux]

Comment #8 originally posted by brazilofmux on 2008-10-11T19:13:26.000Z:

You should probably also read the PennMUSH help file for DARK and its different applications. DARK ROOMs and THINGs have features which can be utilized to emulate some of the wiz-like features. For example, I think a DARK room prevents things in the room from being seen unless they have the LIGHT flag set on them... or the viewing player has the LIGHT flag set on them (or something like that... it's been a while since I actually logged into a MUSH).

Additionally, I am fairly certain that the @hide STATE is not persistent; however, Penn has the 'ch' command available at login (ch == connect hidden, cd == connect dark), which I believe is available to @hide @power-ed players.

My suggestion is to seek as much cross-platform compatibility as possible before deciding whether or not to add some "new" aspect to this particular item. Just my $.02.

-T

[brazilofmux]

Comment #9 originally posted by brazilofmux on 2008-11-15T15:39:35.000Z:

<empty>