Skip to content

Instantly share code, notes, and snippets.

@SnosMe
Created December 22, 2020 11:32
Show Gist options
  • Save SnosMe/151549b532df8ea08025a76ae2920ca4 to your computer and use it in GitHub Desktop.
Save SnosMe/151549b532df8ea08025a76ae2920ca4 to your computer and use it in GitHub Desktop.
Full markup (found so far)
=============================
Bold text
<b>{TEXT} or <bold>{TEXT}
Italic text
<i>{TEXT} or <italic>{TEXT}
Text color
<rgb(113,178,95)>{TEXT} boring rgb, can have space after comma
<magic>{TEXT} some colors are defined in UISettings.xml
<red>{TEXT} some colors are embedded in C++ code
<colour:yellow>{TEXT} "colour:" part is optional
Text size
<size:29>{TEXT} size as if text was shown at BaseResolution (UISettings.xml)
<smaller>{TEXT} @TODO relative size
<bigger>{TEXT} @TODO relative size
Inline image
<<id>> example "Press <<xbox_button_a>> to enter a message"
example "<<HBG02>><<HBGAt>><<HBG03>><<HBGAy>>" Harbinger glyphs (UISettings.xml)
Nesting/replacement field rules
<...>{{TEXT}} double pair of { } is required if TEXT contains replacement fields {0} {1} {2}
example "<default>{{{0}% chance for maps ...}}"
can also have double pair even without replacement fields, it's not an error
<...>{TEXT} single pair of { } if TEXT does not contain replacement fields
nested formating works in both cases
Conditions
<<set:STRING>> used before condition to set state
example "<<set:MS>><if:MS>{Мучительный}<elif:FS>{Мучительная}"
<if:STRING>{TEXT} Naming convention for Grammatical gender conditions
<elif:STRING>{TEXT} MS, MP, FS, FP, NS, NP
<else>{TEXT} M - masculine, F - feminine, N - neuter
S - singular, P - plural
Russian:
ZY - genitive singular feminine
ZX - genitive singular masculine
ZZ - genitive plural
Set scoped state
<set:STRING>{TEXT} example "foo <set:ZX>{{{0}}} bar"
-------------------------
Useful research resources
- Metadata/UI/UISettings.xml
- Dat files: ClientStrings, Words, FlavourText, NPCTextAudio
- define("PoE/Item/Markup") in main.js on pathofexile.com
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment