FOR MODDERS AND HACKERS

Signs and fonts

This reference separates stream semantics, data structure, glyph artwork, and Redux presentation. Original inscriptions, graffiti prose, and artwork remain external assets. Numeric glyph identities do not independently establish their visual design in every font variant.

Character-set selection

SIGN-0001Original: EstablishedRedux: Unverified

For ordinary sign bytes, a clear high bit selects Runic and a set high bit selects IBM. The emitted index is the low seven bits. Thus 41 hex selects Runic glyph 41, while C1 selects IBM glyph 41. Raw control recognition occurs separately; a high-bit version of a control is not automatically the same command.

This establishes selection, not fixed-font file packing or the meaning of every compound glyph. Redux's font sheets are derived assets, not original CH files.

Sign container, traversal, and aliases

SIGN-0002Original: EstablishedRedux: Unverified

SIGNS.DAT begins with 33 little-endian offset words, a 66-byte header. 0x42 is the header end, not independent proof of the first block's actual offset. Select the offset by current location. Zero chooses fallback presentation.

A block contains four-byte record headers (location, level, X, Y) followed by NUL-terminated text. Lookup compares level/X/Y because block selection already identifies location. After an unmatched record, a following FF byte ends traversal. The original working buffer is prefilled with FF; this is not a modern bounds check.

A leading raw newline aliases the next record's text by repeatedly advancing six bytes: newline, terminator, next four-byte header. Aliases retain their own coordinates. This convention has no separate stored pointer and does not itself validate the assumed layout or chain bounds.

Readable terrain and generated displays

SIGN-0003Original: EstablishedRedux: Unverified

After dynamic-object precedence, direct inscription lookup applies to terrain 89, 8A, A0, A4, and F8 hex: cross, headstone, ordinary sign, small sign, wall sign. Structural E0/E1/E2 pieces follow north/east/west respectively, then describe the terminal terrain normally. A terminal inscription-shaped tile reached this way is not automatically redispatched as an inscription. Flagpoles, flags, and service symbols use ordinary descriptions.

Missing blocks or unmatched coordinates generate a fallback display. Location 4, level 0, coordinate (11,15) hex has a generated wanted display incorporating up to three active-party names, bypassing stored sign lookup. Exact prose and issuer attribution are not established by those dispatch facts alone.

Text controls and framing

SIGN-0004Original: EstablishedRedux: Unverified
Raw byteOperation
00End text
0ARunic newline, except leading alias convention
8AIBM newline
0DWait for a key, emit no glyph
26, 27Emit the horizontal Runic frame glyph
29-31Expand one of nine sixteen-character frame sequences
OtherSelect charset by high bit; output low-seven-bit glyph

The message window is sixteen columns wide. A sixteen-character macro starts at the current cursor; it is not guaranteed to begin or occupy exactly one aligned row. Newlines and wrapping still apply. Framing comes from the stream, not from an automatic border chosen by terrain. Compound-letter and visual-space designs are font artwork, not multibyte expansion performed by this interpreter.

Dungeon symbols and separate graffiti

SIGN-0005Original: EstablishedRedux: Unverified

The symbolic dungeon view is 22 x 22, centered locally at (11,11), using eight-pixel cell spacing. The one-cell screen margin places the player at text coordinate (12,12). Ladder glyphs distinguish up/down/both; chests and room glyphs are yellow; wall, plaque, special-wall, and hidden-door families stop propagation. Energy fields and fountains use drawing primitives.

Cell family/valueGlyph identity
Passage with opening bitIBM 18 hex
1x, 2x, 3xRunic 2E, 2D, 2F
4xRunic 70
60IBM 19
61, 69Runic 71
68IBM 12
Other 6xRunic 72
Ax, FxRunic 73
B0IBM 7F
Other BxRunic 74
Cx, Dx, ExRunic 75, 76, 77

Graffiti is a separate collection of eleven messages, selected by dungeon-specific first/count metadata and placement coordinates rather than SIGNS.DAT. Its exact prose and every dungeon-to-array association were not reverified in this pass. View cell spacing does not prove fixed-font binary packing.

Other Runic consumers and sky positions

SIGN-0006Original: EstablishedRedux: Unverified

Conversation control 8E hex toggles a high-bit mask. Inventory uses Runic icons, scroll names, and moonstone phase glyphs, while potion names use IBM. Shrine offering/final Codex displays, ending text, and ordinary scroll pickup have Runic paths; special plans pickup is a separate case.

The sky has twelve display cells plus a terminator. Sun position is 17-hour. Moon positions begin at 8-hour and 2-hour; add 24 only if below -12. Write a body only for a position in 0-11, in sun/Trammel/Felucca order. The last write wins on overlap. Dungeon and underground/special-map presentation have separate gates. Omitting the moon-position wrap changes nighttime behavior.

Locate coordinate encoding

SIGN-0007Original: EstablishedRedux: Unverified

Emit Y before X, high nibble before low nibble, mapping 0-15 to Runic A-P. The punctuation is also emitted in that charset. In Wis has outdoor context admission; Sextant additionally requires map zero, a level below 128, and hour 19-23 or 0-5. Do not transfer those item restrictions to every caller of coordinate formatting.

Redux inscription presentation

SIGN-0008Original: EstablishedRedux: Intentional deviation

REDUX DEVIATION: SIGN-0008 — The original emits encoded text into the message window and pauses at each wait control. Redux presents a modal inscription with semantic colors and omits those intermediate waits for a coherent reading view. It resolves aliases into bounded independent buffers rather than trusting sentinel traversal.

Dungeon View's solid-wall presentation uses one north-up 8×8 current-floor map, collapsing the existing 22×22 revealed display occurrences by wrapped source cell. Map and key share the same opaque terrain and geometric feature artwork rather than every original font symbol: solid walls, dotted passages, and distinct Not-revealed hatching. The peripheral party frame/facing arrow preserves the feature beneath it. Additional key entries come only from revealed symbols; paired W-E / N-S edge labels require known same-level wrap adjacency and do not promise a safe route. This improves navigation clarity without expanding reveal authority. VIEW-0003 owns the reveal rules; the Dungeon View widget contract owns the presentation and controls.

An optional per-reading readable rendering is another presentation aid: understood Runic spans become English bitmap lettering while structural artwork, IBM cells, row count, and bounds remain intact. Compound expansions borrow padding, then compress only their own span up to 2:1; they do not omit artwork or rewrite source prose. Translation state is local to the reading and does not grant journal knowledge, alter the stored inscription, or consume game time. Maintainer-only activation instructions remain separate from player Help.