LordsOfWiki/Notation

Notation for LordsOfWiki

Using Go markup.
Wizard: (black/white)

Summoned creatures:

(etc)

Insane proposals from MoonShadow

If someone draws little square images, I'll do Go-like markup for them. I might even go so far as to make it user-editable, to some extent, by moving part of the symbol-to-image mapping to a Wiki page.
At some point this week I intend to write an image server script. This will let people store images in a dedicated area on the webserver, up to some (small) total size quota. Anyone will be able to upload/remove images in this area. The two could be interfaced..

: I'm loathe to lose facing, but it's kinda hard to represent. -- Vitenka

By "facing" you mean what direction a player's pointing? Well, I agree it's hard to represent with the current markup. But given that we could modify the available graphics, there's no reason why

 Uo  Do  Lo  Ro

(for, of course, a white wizard pointing up, down, left and right, respectively) can't be meaningful and useful.

I'm getting inclined towards (the markup at least) resembling Angband?/AncientDomainsOfMystery?/other Roguelikes. As in: one character represents us as wizards (could be @); any letters represent other creatures; any non-letter characters represent environment, like walls, windows, water, and other things beginning with W. So

 ...######...
 ...#.s..#...
 ......@.#...
 ...#....#...
 .@.######...
 ..d.........

One wizard and his dog try to sneak up to the room in which the other is hiding, having just summoned a snake.

If we're OK for all squares to be represented by 2 characters, then it might be more useful to be able to go:

 . . . # .Ds . . # . . .
 . . . . . .L@ . # . . .
 . . . # . . . . # . . .
 .u@ . # # # # # # . . .
 . .ud . . . . . . . . .

Where uppercase orientation-letters mean "playing for side Black", and lowercase letters mean "playing for side White". Of course, that makes it a bit harder to extend for more than two players - and I reckon it's worth making that available, given we're designing the implementation from scratch :)