mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Migrating issues to Github, please follow the new discussion here:
https://github.com/Mudlet/Mudlet/issues/783

This issue needs to be closed and there is no appropriate status, so
will set it to "Opinion" just for migration purposes.

** Bug watch added: github.com/Mudlet/Mudlet/issues #783
   https://github.com/Mudlet/Mudlet/issues/783

** Changed in: mudlet
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1468743

Title:
  Feature Request: Hideable rooms

Status in Mudlet:
  Opinion

Bug description:
  The current Mudlet codebase (2.1 release, 3.0.0 previews) do not have
  the ability to "hide" rooms like, say, the TinTin++ MUD Client.  A
  user had inquired about this facility.
  http://forums.mudlet.org/viewtopic.php?f=13&t=4821

  Whilst it would not be too hard to provide a boolean flag for a room in the TRoom class (or possibly from an implementation detail, there might be merit in doing so in the containing TArea - I have visions in the future of permitting a room to be in multiple Areas {it's coordinates then become an TArea property rather than a TRoom one}) - there might need to be a discussion about:
  * whether a "hidden" room still has exits draw towards it, or if those need to be individually hidden as well
  * under what situation the hide might need to be overridden and whether other aspects of the room need to be concealed
  * as an open source project there is nothing to prevent code changes to "reveal" any hidden data that a MUD might wish to include in a pre-distributed map.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1468743/+subscriptions