This guide consolidates Wolfery’s text formatting behavior from two sources:
- Official in-client help commands (
help format,help format info) - Observed behavior, forum posts, release notes, and real-world usage
Where these sources agree, the behavior is described directly. Where they conflict, the discrepancy is explicitly noted.
These features are confirmed by both documentation and observation to work across all general communication contexts.
bold renders as bold text.
Syntax:
**bold**
italic renders as italic text.
Syntax:
_italic_
Known issue:
- Italics may break when quotation marks are included inside the italic span.
- Smart quotes may be coerced into straight quotes, breaking formatting.
- Workaround: move quotes outside the italic span.
++superscript++ renders as superscript.
Syntax:
++superscript++
--subscript-- renders as subscript.
Syntax:
--subscript--
Conflict note:
- Older forum posts describe subscript as unreliable.
- Current help output confirms it as supported.
- In practice, it works consistently in chat and info fields, but should be avoided inside URLs or when ambiguity matters.
strikethrough renders as struck-through text.
Syntax:
~~strikethrough~~
((ooc)) renders as explicitly out-of-character text.
Syntax:
((ooc))
Observed behavior:
- Works reliably in chat, pose, and ooc commands.
- Rendering is stylistic rather than structural.
Single backticks render literal text.
Rendered:
command
Syntax:
`command`
Used for:
- Commands
- Keywords
- Preventing accidental formatting
Bare URLs become clickable links.
Rendered: https://example.com
Syntax:
https://example.com
Markdown-style named links are supported.
Rendered: Link name
Syntax:
[Link name](https://example.com)
Conflict note:
- Forum posts confirm that Markdown link titles are not supported.
- Use only the simple
[text](url)form.
These examples are taken directly from the in-client help output and confirmed by live behavior.
say I will **never** give up!
John says, "I will never give up!"
desc The room is _freezing_ cold.
⌈The room is freezing cold.⌋
pose hears a high pitched ++beep beep++.
Jane hears a high pitched beep beep.
pose 's stomach rumbles. --Growl--
John's stomach rumbles. Growl
pose writes a note: "I ~~like~~ love you."
Jane writes a note: "I like love you."
pose dozes off. ((Phonecall. BRB))
John dozes off. ((Phonecall. BRB))
ooc :suggests typing: `help`
Jane ooc suggests typing: help
ooc Ref img: https://wolfery.com/siteicon.svg
John ooc says, "Ref img: https://wolfery.com/siteicon.svg"
ooc :referred to [this image](https://wolfery.com/siteicon.svg)
Jane ooc referred to this image
Info fields support additional formatting features not available in chat.
These features are confirmed by help format info and forum release notes, and are marked experimental.
text prevents line wrapping at spaces.
Syntax:
<nobr>no break</nobr>
Observed behavior:
- Works reliably in About and Rules.
- Should not be nested.
- Use sparingly to avoid layout issues on mobile.
text prevents formatting from being applied.
Syntax:
<esc>_not italic_</esc>
Conflict note:
- GitHub and other Markdown renderers may strip or ignore these tags.
- They function correctly inside Wolfery info fields only.
Headers must start at the beginning of a line.
Syntax:
# Header 1
## Header 2
### Header 3
Observed behavior:
- Supported in About, Rules, and Notes.
- Not supported in chat or Description fields.
- Description fields may silently ignore headers.
Sections create collapsible blocks in info fields.
Syntax:
[[Section title]]
Content below is collapsible.
Syntax:
[[Limited section]] {
Content enclosed here.
}
Observed behavior:
- Supported and stable.
- Nested sections may behave inconsistently.
- Avoid placing headers inside sections.
Tables structure content into rows and columns.
Standard table syntax:
| Item | Price |
| ----- | ----- |
| Pizza | 40c |
| Drink | 10c |
Headerless table syntax:
--- | ---
No minors | Character must be 18+
No OOC | Remain in character
Conflict note:
- Cell alignment is ignored.
- Rendering varies slightly by client width.
- Still recommended for rules and reference material.
Fenced code blocks display text as-is.
Syntax:
code here
Observed behavior:
- Supported in About, Rules, and Notes.
- Indentation inside blocks is not preserved.
- Not supported in chat.
Chat / Say / Pose / Desc:
- Inline formatting only
- No headers, tables, sections, or fenced blocks
- Formatting should never carry critical meaning
Description Field:
- Inline formatting only
- No headers, sections, or tables
- Best for short descriptive text
About / Rules / Notes Fields:
- Full info formatting supported
- Headers, sections, tables, fenced blocks allowed
- Rendered once and cached
Many info-field features are explicitly marked experimental. Forum posts confirm that behavior may change between versions.
Consensus from observed behavior:
- Conservative formatting survives updates best
- Avoid nesting complex structures
- Do not rely on formatting alone to convey critical rules
If formatting is:
- Expressive → chat or pose
- Descriptive → description
- Structural or instructional → about or rules
When in doubt, favor clarity over cleverness.