bbcode

Initiated by Mabel ◷ 2026-06-13 05:10:37 ◉ 9 views ☉ 0 replies
⋮ Thread Actions⌄
Coalition BBCode Guide: Formatting, Research Blocks, Sources, and Messages

Welcome to the Coalition BBCode guide.

BBCode is the forum markup system used to format posts, replies, research notes, field reports, citations, and private messages. It works in both public threads and private messages unless a specific feature is restricted later by moderation settings.

This guide explains the supported tags and gives copy-paste examples.




1. Basic Text Formatting

Use these tags for ordinary emphasis.

[b]Bold text[/b]
[i]Italic text[/i]
[u]Underlined text[/u]
[s]Strikethrough text[/s]
[strike]Strikethrough text[/strike]


Example:

Bold text
Italic text
Underlined text
Strikethrough text




2. Headings and Text Size

The site supports named sizes and numeric legacy-style sizes.

[size=small]Small text[/size]
[size=large]Large text[/size]
[size=xl]Extra large text[/size]

[size=130]130% heading[/size]
[size=150]150% heading[/size]


Recommended heading style:

[b][size=150]MAIN SECTION TITLE[/size][/b]

[b][size=130]SUBSECTION TITLE[/size][/b]


Numeric sizes are bounded to prevent layout abuse.




3. Alignment

[left]Left aligned text[/left]
[center]Centered text[/center]
[right]Right aligned text[/right]


Example:

Centered Notice





4. Horizontal Rule

Use this to divide long posts into sections.

[hr]


Example:




5. Quotes

Basic quote:

[quote]This is quoted text.[/quote]


Named quote:

[quote=Mabel]This is quoted text from Mabel.[/quote]


Expanded quote format:

[quote author="Mabel" post="#12"]This references a specific post.[/quote]


Example:

Quote from Mabel
This is a quoted passage.





6. Code Blocks

Use code blocks for commands, scripts, logs, structured notes, and raw BBCode examples.

[code]
echo "Hello Coalition";

[/code]

Language label example:

[code=php]
<?php echo "Hello Coalition"; ?>

[/code]




7. Links

Automatic visible URL:

[url]https://example.com[/url]


Labeled link:

[url=https://example.com]Example Source[/url]


Use labeled links when possible so readers know what they are opening.




8. Images

Use image tags for externally hosted images or approved image URLs.

[img]https://example.com/image.jpg[/img]


For private messages, image/file attachments may also be sent through the message attachment button if available.




9. Lists

Unordered list:

[list]
[*]First item
[*]Second item
[*]Third item
[/list]


Ordered list:

[list=1]
[*]First item
[*]Second item
[*]Third item
[/list]


Example:

  1. Prepare the claim.
  2. Add evidence.
  3. State the inference.
  4. List open questions.





10. Color

Named color example:

[color=gold]Gold text[/color]


Hex color example:

[color=#cda85c]Custom gold text[/color]


Use color sparingly. It is best for warnings, labels, or emphasis.




11. Spoilers

Basic spoiler:

[spoiler]Hidden text goes here.[/spoiler]


Labeled spoiler:

[spoiler=Research Notes]Hidden research notes go here.[/spoiler]


Use spoilers for long side notes, sensitive plot/details, or optional evidence.




Coalition Research BBCode

The Coalition supports advanced research-composition tags. These are designed to make posts clearer by separating claims, evidence, inference, uncertainty, sources, and synthesis.




12. Claim

Use
Claim
for the statement you are arguing or proposing.

[claim]
The central claim goes here.
[/claim]


Example:

[claim]
A repeated symbolic pattern appears across several independent traditions and may indicate shared transmission or convergent development.





13. Evidence

Use
Evidence
for observations, records, citations, measurements, examples, or documents that support a claim.

[evidence]
Supporting evidence goes here.
[/evidence]


Example:

[evidence]
The same geometric motif appears in three manuscripts from different regions, each dated to a separate period.





14. Counterpoint

Use
Counterpoint
to include opposing interpretations or alternative explanations.

[counterpoint]
A different interpretation is possible.
[/counterpoint]


Example:

[counterpoint]
The similarity may be coincidental or caused by later copying rather than a shared origin.





15. Inference

Use
Inference
for conclusions that are reasoned from evidence but not directly proven.

[inference]
Reasoned conclusion goes here.
[/inference]


Example:

[inference]
The pattern is strong enough to justify further comparison, but not strong enough to prove direct historical contact.





16. Unknown / Open Question

Use
Unknown / Needs Verification
when something remains unverified, uncertain, or unresolved.

[unknown]
What still needs verification?
[/unknown]


Example:

[unknown]
The original date of the second manuscript is uncertain and needs independent verification.





17. Sources and Citations

Basic source:

[source]
Book, paper, archive, interview, or dataset.
[/source]


Linked source:

[source url=https://example.com]Visible source label[/source]


Citation:

[citation]
Author, Title, page number, archive code, or publication details.
[/citation]


Archive reference:

[archive]
Archive identifier, manuscript number, file ID, or collection reference.
[/archive]


Example:

Source
Example Archive Record


Citation
Example Author, Example Manuscript, p. 42.


Archive Reference
AETERNA-LIBRARY / MANUSCRIPT-042 / SCAN-B





Coalition Domain Tags

Use domain tags to mark which research domain a post belongs to.




18. Occult Science Domain

[domain=occult]
Hermetic, esoteric, symbolic, ritual, historical, or metaphysical material.
[/domain]


Example:

Occult Sciences
This section examines symbolic cosmology and ritual pattern transmission.





19. Militaristic Science Domain

[domain=militaristic]
Doctrine, strategy, operational history, command theory, intelligence, logistics, or systems of applied force.
[/domain]


Example:

Militaristic Sciences
This section examines strategic doctrine and operational decision-making.





20. Modern Science Domain

[domain=science]
Physics, cybernetics, engineering, AI, cognition, materials, biotechnology, or future infrastructure.
[/domain]


Example:

Modern Science
This section examines cybernetic feedback systems and applied cognition.





21. Cross-Domain Synthesis

Use
Cross-Domain Synthesis
when combining multiple domains.

[synthesis]
Cross-domain conclusion goes here.
[/synthesis]


Example:

[synthesis]
The same feedback pattern appears in ritual systems, command theory, and cybernetic control loops. This suggests a useful comparative model.





Structured Research Post Tags

These tags help turn a thread into a clean research artifact.




22. Abstract

[abstract]
Short summary of the post.
[/abstract]


Abstract
This is a short summary of the research topic, main question, and expected direction.





23. Method

[method]
How the information was collected or compared.
[/method]


Method
Sources were compared by date, terminology, image pattern, and historical context.





24. Findings

[findings]
What was found.
[/findings]


Findings
Three recurring patterns were identified across separate source groups.





25. Conclusion

[conclusion]
Final interpretation or current best answer.
[/conclusion]


Conclusion
The evidence supports further investigation, but the claim remains provisional.





26. Timeline

[timeline]
- 1901: Event one
- 1924: Event two
- 1950: Event three
[/timeline]


Timeline
- Phase 1: Source collection
- Phase 2: Comparison
- Phase 3: Verification





27. Step

Use
Step
for instructions or procedures.

[step]
Step instructions go here.
[/step]


[step]
Collect primary sources before making a claim.





Example: Research Post Template

Copy this when starting a serious research thread:

[b][size=150]THREAD TITLE[/size][/b]

[abstract]
Brief summary of the research question.
[/abstract]

[claim]
Main claim or hypothesis.
[/claim]

[evidence]
Evidence supporting the claim.
[/evidence]

[counterpoint]
Alternative explanation or objection.
[/counterpoint]

[inference]
Reasoned conclusion based on current evidence.
[/inference]

[unknown]
What still needs verification?
[/unknown]

[source]
Sources, links, books, archives, or files.
[/source]

[synthesis]
How this connects to broader Coalition research.
[/synthesis]





Example: Field Report Template

[b][size=150]FIELD REPORT[/size][/b]

[abstract]
What happened?
[/abstract]

[method]
How was it observed, recorded, or tested?
[/method]

[findings]
What was found?
[/findings]

[unknown]
What remains uncertain?
[/unknown]

[source]
Photos, documents, links, or witnesses.
[/source]

[conclusion]
Current conclusion.
[/conclusion]





Example: Debate Reply Template

[quote=Name]
Point being answered.
[/quote]

[claim]
My position.
[/claim]

[evidence]
Evidence for my position.
[/evidence]

[counterpoint]
What the opposing side may still be right about.
[/counterpoint]

[inference]
Reasoned conclusion.
[/inference]





BBCode in Private Messages

Private messages support the same basic formatting style. Use BBCode in messages when clarity matters.

Good message uses:

  • Bold for clear labels.
  • Quote
    when replying to a specific point.
  • Code
    for commands, logs, or exact text.
  • [invalid link] for references.
  • [invalid image] or the attachment button for screenshots and files.
  • Spoiler
    Spoilers
    for optional or sensitive details.


Example private message:

[b]Subject:[/b] Screenshot Review

I attached the screenshot below.

[evidence]
The issue appears near the lower-right message floater.
[/evidence]

[unknown]
I am not sure whether this is CSS overflow or JavaScript state drift.
[/unknown]

Please check when available.





Best Practices

[list=1]
[*]Use [claim] for what you believe is true.
[*]Use [evidence] for what supports it.
[*]Use [inference] for what you reason from the evidence.
[*]Use [unknown] for what is not verified.
[*]Use [source] or [citation] whenever possible.
[*]Use [spoiler] for long optional sections.
[*]Use
for logs, commands, snippets, and raw formatting examples.
[*]Do not overuse colors or large text.
[*]Do not post private personal information.
[*]When uncertain, label uncertainty clearly.
[/list]

[hr]

[b][size=130]Recommended Research Standard[/size][/b]

A strong Coalition research post should include at least:

[list]
[*]A clear claim
[*]Evidence
[*]A source or citation
[*]A statement of uncertainty
[*]A reasoned inference or conclusion
[/list]

Example minimal structure:

[code]
[claim]
What I think is happening.
[/claim]

[evidence]
Why I think this.
[/evidence]

[unknown]
What I have not confirmed yet.
[/unknown]

[source]
Where the information came from.
[/source]

[inference]
Current best conclusion.
[/inference]





Closing Note

BBCode is not only for decoration. On The Coalition, it is a way to make posts easier to read, easier to verify, and easier to build on.

Use formatting to clarify your reasoning.

Separate facts from inference.

Mark uncertainty.

Cite sources.

Build knowledge carefully.
◎ ✺ ⬡ ◈ △

Thread Reply › bbcode

Compose Reply

Add context, cite carefully, and keep the signal clear.

Login to reply.