Making the mud more mapper friendly

[Neurrone]

Hi,

Will it be possible to expose room number and area information e.g as prompt variables?

I know about the Mudlet automapper and looking at how its implemented, the author went to some length to get around the lack of this information.

Would really like to get this working for my own client, but can't use Mudlet.

[Nyyrazzilyss]

I'm indifferent to this, i've already created my own. I had asked for vnum display a couple years ago, and the response at the time was 'never going to happen'.

[Neurrone]

@Nyyrazzilyss if the goal was to prevent this from happening, then it seems pretty misguided, since i think pretty much everyone uses yours now.

Would like to talk to you in-game on some of the technical aspects of how you did this, especially augmenting it with area info, if you're willing to share/elaborate.

[Inames]

There's not really anything game-breaking about vnum's being displayed for rooms. It'd be nice to have this available as a toggle to display. The only potential breaking mechanic that I can see is it makes the puzzle of looping rooms and one-ways kinda obsolete... but that's easy to work around anyways, almost every looping/one-way area has already been mapped and made available publicly for people to see...

[shevarash]

I'll file this as an enhancement for now, but I think it needs a little more discussion. I'm not opposed to making it easier for mappers to work, but I need to do a little research to make sure that exposing vnums doesn't have unintended consequences.

[Nyyrazzilyss]

Suggestion: If you do show vnums, perhaps make it internally determined/zone specific? Some zones show, some zones don't. Clouds for example would appear to be one designed with the expectation mapping it would be horrible.