imported>Dawning
mNo edit summary
the mass documenting
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DLog|Chungus|wowowowowowowowowowoowowow}}
'''<code>DLog</code> formats a single in-character "D's LOG" lore entry — a styled line giving a subject's name and a "bypass state" description, used for boss/entity lore on dungeon pages.'''
__TOC__


<syntaxhighlight lang="wikitext" style="overflow: auto;">{{Dlog|Chungus|wowowowowowowowowowoowowow}}</syntaxhighlight>
== Overview ==
This template prints one stylised log line in the form <code>[D's &lt;type&gt; LOG: &lt;subject&gt;] BYPASS STATE: &lt;text&gt;</code>, wrapped in a <code>dlog</code> styled box. It is the recurring "data log" flavour element used across dungeon/boss pages such as [[Anubis Lair]], [[Abyss Of Demons]], [[Aurora Sanctum]] and [[Celestial's Province: Part 1]] to reveal (or redact, with <code>???</code>) lore about each boss.
 
== Parameters ==
{| class="wikitable"
! Parameter !! Required? !! What it does !! Example
|-
| <code>1</code> (first unnamed) || Optional in practice || The "log type" word shown between <code>D's</code> and <code>LOG</code>. In current usage this is left blank, giving <code>[D's  LOG: ...]</code>. Provide a word to label the log. || (usually empty)
|-
| <code>2</code> (second unnamed) || Required || The subject of the log — typically the boss/entity name shown after <code>LOG:</code>. || <code>Kurvaros</code>
|-
| <code>3</code> (third unnamed) || Required || The "BYPASS STATE" text — the lore body, or <code>???</code> / <code>Collecting Data...</code> when redacted. || <code>???</code>
|}
 
== How to use ==
1. The three values are positional (unnamed), separated by <code>|</code>, in this order: log type, subject, bypass-state text.
2. In nearly all live uses the first value is left '''empty''' — note the double pipe right after the template name: <code>{{DLog||Kurvaros|???}}</code>. The empty slot is the log type.
3. Put the entity/boss name as the second value.
4. Put the lore (or a redaction placeholder like <code>???</code> or <code>Collecting Data...</code>) as the third value. Long prose is fine here.
5. Because the values are positional, do not skip a pipe — every entry needs all three slots even if the first is blank.
 
== Copy this ==
<syntaxhighlight lang="wikitext" style="overflow:auto;">
{{DLog||subject|bypass state text}}
</syntaxhighlight>
 
== Example ==
{{DLog||Valerion|In a kingdom ravaged by eternal night, the Voided King raised a single knight out of the rust to protect the fading light that remained.}}
 
<syntaxhighlight lang="wikitext" style="overflow:auto;">
{{DLog||Valerion|In a kingdom ravaged by eternal night, the Voided King raised a single knight out of the rust to protect the fading light that remained.}}
</syntaxhighlight>
 
== Tips & notes ==
* The leading double pipe (<code>||</code>) is intentional — it leaves the log-type slot empty, which is how every current page uses it. If you supply a first value, it appears as <code>[D's &lt;value&gt; LOG: ...]</code>.
* The "D" in the output is rendered with heavy combining/glitch characters by the template; you do not type those yourself.
* For unrevealed lore the convention is to use <code>???</code> (or <code>Collecting Data...</code>) as the third value.
* Parameters 2 and 3 are required by the template's source (they use <code>{{{2}}}</code> / <code>{{{3}}}</code> with no default); omitting them shows the raw <code>{{{2}}}</code>/<code>{{{3}}}</code> placeholder text.
* Related: dungeon/boss page layout templates and {{tl|Sound}} (voice-line audio buttons that often sit beside these logs).

Latest revision as of 11:55, 20 June 2026

DLog formats a single in-character "D's LOG" lore entry — a styled line giving a subject's name and a "bypass state" description, used for boss/entity lore on dungeon pages.

Overview

This template prints one stylised log line in the form [D's <type> LOG: <subject>] BYPASS STATE: <text>, wrapped in a dlog styled box. It is the recurring "data log" flavour element used across dungeon/boss pages such as Anubis Lair, Abyss Of Demons, Aurora Sanctum and Celestial's Province: Part 1 to reveal (or redact, with ???) lore about each boss.

Parameters

Parameter Required? What it does Example
1 (first unnamed) Optional in practice The "log type" word shown between D's and LOG. In current usage this is left blank, giving [D's LOG: ...]. Provide a word to label the log. (usually empty)
2 (second unnamed) Required The subject of the log — typically the boss/entity name shown after LOG:. Kurvaros
3 (third unnamed) Required The "BYPASS STATE" text — the lore body, or ??? / Collecting Data... when redacted. ???

How to use

1. The three values are positional (unnamed), separated by |, in this order: log type, subject, bypass-state text. 2. In nearly all live uses the first value is left empty — note the double pipe right after the template name:

[D̷̛͖̲̜̤̭̤̬̏͑́̌̇̽͛̊́̕̚͜'s LOG: Kurvaros] BYPASS STATE:  ???

. The empty slot is the log type. 3. Put the entity/boss name as the second value. 4. Put the lore (or a redaction placeholder like ??? or Collecting Data...) as the third value. Long prose is fine here. 5. Because the values are positional, do not skip a pipe — every entry needs all three slots even if the first is blank.

Copy this

{{DLog||subject|bypass state text}}

Example

[D̷̛͖̲̜̤̭̤̬̏͑́̌̇̽͛̊́̕̚͜'s LOG: Valerion] BYPASS STATE: In a kingdom ravaged by eternal night, the Voided King raised a single knight out of the rust to protect the fading light that remained.


{{DLog||Valerion|In a kingdom ravaged by eternal night, the Voided King raised a single knight out of the rust to protect the fading light that remained.}}

Tips & notes

  • The leading double pipe (||) is intentional — it leaves the log-type slot empty, which is how every current page uses it. If you supply a first value, it appears as [D's <value> LOG: ...].
  • The "D" in the output is rendered with heavy combining/glitch characters by the template; you do not type those yourself.
  • For unrevealed lore the convention is to use ??? (or Collecting Data...) as the third value.
  • Parameters 2 and 3 are required by the template's source (they use {{{2}}} / {{{3}}} with no default); omitting them shows the raw {{{2}}}/{{{3}}} placeholder text.
  • Related: dungeon/boss page layout templates and {{Sound}} (voice-line audio buttons that often sit beside these logs).