1
Programming / Re: Grouping the ASCII symbols?
« on: July 20, 2010, 03:41:59 PM »
I tend to lean towards something very similar to the list, with the exception being that I've replaced shops with letters, for clarity -- it's a lot easier to think "where's the blacksmith?" and look for a big blue letter B in a wall, rather than trying to remember if it's number 2 or 3.
I think the items/terrain/features sections tend to be fairly interchangable, though; I personally think there's nothing better than ~ to represent water, for example, though some RLs use that for items. And * is useful for some terrain features, though if I recall correctly it's also used in Angband/ToME (I forget if it's one, the other, or both!) to represent orbs of light, and also in ToME for alchemy essences; not such a big deal though, since the colour chosen usually makes it clear which is which.
So in conclusion, personally I just go for whatever seems appropriate at the time, with a few exceptions set in stone such as # for walls, . for floors, @ for the player (other humanoids are 'p' for person, rather than being confusing with multiple @'s), and so on. As long as things are used in a fairly clear context, then there can easily be some bleed-over between categories without adding confusion.
I think the items/terrain/features sections tend to be fairly interchangable, though; I personally think there's nothing better than ~ to represent water, for example, though some RLs use that for items. And * is useful for some terrain features, though if I recall correctly it's also used in Angband/ToME (I forget if it's one, the other, or both!) to represent orbs of light, and also in ToME for alchemy essences; not such a big deal though, since the colour chosen usually makes it clear which is which.
So in conclusion, personally I just go for whatever seems appropriate at the time, with a few exceptions set in stone such as # for walls, . for floors, @ for the player (other humanoids are 'p' for person, rather than being confusing with multiple @'s), and so on. As long as things are used in a fairly clear context, then there can easily be some bleed-over between categories without adding confusion.