PABC Philosophy & Battleboarding Community
PABC / Wiki / General
General

A Guide on Making Profiles

By Logiaa (Owner) · Published 2026-10-30T22:09:47.973Z · Updated 2026-10-30T22:10:31.350Z

> DYNAMIC TEMPLATE NOTICE:
> This guide and the associated profile template are subject to change.
> Whenever an Admin, Staff Member, or the Community passes a new CRT (Content Revision Thread) Proposal, the template and definitions must be updated to reflect the current binding rules.
> Always check the latest official PABC Tiering Scale and accepted CRT decisions before submitting a profile.

PABC Forum Wiki Guide: How to Craft a Profile

Welcome to the PABC Forum Wiki-fandom.
This guide explains how to build a character profile that is readable, evidence-based, and ready for review.
PABC does not accept tier claims based on vibes, impressive wording, dimensional buzzwords, or unsupported declarations.
A character is not automatically powerful because a profile calls them boundless, infinite, beyond everything, or above the narrative.
PABC profiles must show what the source says, what the evidence establishes, and why the conclusion follows.
This guide is a practical drafting manual, not a replacement for the official tiering scale.

1. The Golden Rule of PABC

> Source is Evidence. The Bridge is the Argument. The Tier is the Conclusion.

The source gives you material to analyze.
The bridge premise explains why that material supports a particular claim about the character.
The tier is the narrowest conclusion that follows from the evidence and the bridge.
Do not skip the bridge and jump directly from a scan to a tier.

The four-step evidence method

  1. Quote or identify the source accurately.
  2. Explain the context in which the statement or feat occurs.
  3. State the bridge premise connecting the source to the character and target.
  4. Assign the narrowest classification that the argument actually supports.

What a complete argument looks like

Source: the narrator states that the character erased the entire mapped universe.
Context: the statement refers to the current canon version and is not a dream, metaphor, or hypothetical.
Bridge: the character directly performs the erasure, and the universe is established as a complete spacetime structure.
Conclusion: the feat supports the relevant universe-scale classification for that version and operation.

What an incomplete argument looks like

Source: a character says, 'I am beyond all things.'
Context: the line is delivered during a dramatic confrontation.
Missing bridge: the profile does not identify what 'all things' denotes or whether the line is literal.
Conclusion: the line alone does not establish a high-tier cosmological classification.

2. Tier, Route, Tag, and Special Classification

These terms are not interchangeable.
A tier is a classification result.
A route is the method or framework used to analyze a claim.
A tag records a relevant property, evidence category, or interpretive condition.
A special classification has its own independent qualification requirements.

| Concept | Function | Example |
|---|---|---|
| System A tier | Formal scale and structural classification | 1-A, 2-B, 1-F, 2-H |
| System H route | Accessible first-pass evidence and classification route | H-Physical, H-Structure |
| HΩ route | Specialized methodology for a particular high-end argument | HΩ-IV-B |
| System B tag | Ontological description | B3-RF |
| System C tag | Logical framework description | C-CL, C-PAR |
| System D record | Evidence record and source analysis | 5W+1H |
| System E mode | Debate and review procedure | Standard review or meta-debate |
| System F verdict | Confidence and epistemic assessment | High, Moderate, Low |
| Tier 1-S | Separate PABC special classification | 1-S |

Do not confuse the route with the result.
Using a route does not automatically award the tier associated with a claim.
Do not treat HΩ as a ladder where every higher Roman numeral automatically means a higher tier.
Do not treat Tier 1-S as an automatic consequence of narrative transcendence.

3. Current Canon: Tier 1-F and Tier 2-H

Canon notice

Tier 1-F and Tier 2-H are to be treated as canon for this guide, following the owner's later confirmation.
They are valid PABC tier labels and may be used in profiles, CRTs, and verdicts.
Do not describe either label as merely a hypothetical proposal in a profile prepared under this owner-confirmed update.
The publicly visible consolidated tiering page may lag behind a later owner decision.
If the public page has not yet been updated, cite the owner's confirmation or the latest binding CRT and ask staff to synchronize the public reference.

How to use the new labels responsibly

Use 1-F or 2-H only when the character's evidence satisfies the current binding definition for that tier.
Do not infer the definition from the spelling of the label.
Do not assume that the letter F or H has the same meaning in every system.
Do not invent a definition from another wiki's tiering system.
Do not assume that a new tier is automatically above or below another tier unless the official PABC scale states that ordering.
Record the exact tier name and its applicable subtype where the scale requires one.
Quote or link the binding definition in the CRT.
Explain the feature that makes the evidence qualify for that specific tier.
Explain why adjacent or competing classifications do not fit as well.
Record uncertainty rather than pretending that an unclear case is settled.

Tier 1-F profile procedure

First, open the latest owner-approved definition of Tier 1-F.
Copy the operative qualification language into your working notes.
Identify every required condition in that definition.
Separate necessary conditions from examples and explanatory commentary.
Find a source passage or feat for each necessary condition.
Identify the exact subject, target, scope, and relation involved.
State whether the character creates, destroys, affects, grounds, governs, embodies, or merely perceives the relevant structure.
Do not substitute a title or reputation for the required relation.
Do not assume that a statement about the setting automatically applies to the character.
Show the bridge from the relevant structure to the character's actual capability or ontology.
Compare the claim with the nearest lower classification.
Explain why the lower classification fails to capture the established feature.
Compare the claim with the nearest higher classification.
Explain why the evidence does not require an unsupported promotion beyond 1-F.
Record counterevidence, anti-feats, limitations, and contradictory passages.
State whether the conclusion is direct, interpretive, conditional, or contested.
Use the official subtype notation exactly as written in the binding scale.

Tier 2-H profile procedure

First, open the latest owner-approved definition of Tier 2-H.
Copy the operative qualification language into your working notes.
Identify each required condition and any explicit exclusions.
Do not confuse the letter H in 2-H with System H evidence tags.
System H is an evidence and classification route; 2-H is a tier label.
These are different uses of the same letter.
Do not assign 2-H merely because a profile uses H-Structure or H-Narrative.
Do not treat an H-tag as proof of a tier.
Find evidence that directly supports the defining feature of Tier 2-H.
Identify the exact target or structure to which the claim applies.
Explain the character's relation to that target.
Show why the source supports the tier rather than merely describing a location or cosmology.
Compare the claim with the nearest adjacent tier.
Explain why the evidence is not better classified under that adjacent tier.
Record competing interpretations and any unresolved conditions.
Use the exact official notation and wording from the latest definition.

Tier 1-F and Tier 2-H: quick do / do not

| Do | Do not |
|---|---|
| Treat both labels as canon following owner confirmation. | Call them non-canon or merely proposed. |
| Quote the current binding definitions. | Guess what the labels mean from their names. |
| Prove every required condition. | Use the tier label as its own evidence. |
| Compare adjacent classifications. | Assume the new label automatically outranks every older label. |
| Keep the evidence and bridge visible. | Copy another wiki's definitions. |
| Record uncertainty honestly. | Hide missing premises behind jargon. |
| Distinguish 2-H from System H. | Treat H-Physical or H-Structure as 2-H. |

Required CRT note for these tiers

Tier claimed: [1-F or 2-H].
Binding definition used: [quote or link the current owner-approved definition].
Required condition 1: [condition].
Evidence for condition 1: [source and explanation].
Required condition 2: [condition].
Evidence for condition 2: [source and explanation].
Bridge premise: [explain why the evidence applies to the character].
Nearest lower tier: [classification and reason it is insufficient].
Nearest higher tier: [classification and reason it is not established].
Counterevidence: [list and address].
Verdict requested: [accepted / conditional / contested / rejected].

4. Understanding the PABC Systems

PABC uses modular analytical systems.
System A records the formal tier and structural classification.
System H is the accessible entry route for ordinary evidence and incomplete canon.
Systems B, C, D, E, and F remain analytical modules and are not waived by using System H.

| System | Main purpose | What to include |
|---|---|---|
| System A | Formal tier scale | Tier, qualification, adjacent-tier comparison |
| System B | Ontology | Reality-fiction relations, dependence, identity, structure |
| System C | Logic | Classical or specified nonclassical framework |
| System D | Evidence | Source, context, 5W+1H, reliability |
| System E | Debate procedure | Review method, objections, burden of proof |
| System F | Verdict and confidence | Conclusion, confidence, unresolved alternatives |
| System H | Accessible first-pass route | Physical feats, abilities, structure, narrative, conditions, unrated claims |

System H evidence categories

H-Physical records ordinary physical feats and destructive demonstrations.
H-Ability records special abilities, hax, resistances, and utility.
H-Structure records the relevant cosmological or structural description.
H-Narrative records statements, titles, framing, and narrative roles.
H-Conditional records claims dependent on unresolved interpretation or inconsistent canon.
H-Unrated records claims that cannot currently be classified from available evidence.

System H is not a shortcut to a high tier.
System H is not a replacement for System A.
System H does not waive Systems B–F.
An H record can be useful even when the final tier remains unresolved.
Use the least-demanding defensible interpretation.

System A and System H compared

| Question | System H | System A |
|---|---|---|
| Purpose | First-pass evidence and classification | Formal scale qualification |
| Evidence burden | Proportionate and transparent | More formal for structural and high-tier claims |
| Incomplete canon | Can preserve conditional notes | May leave the tier unresolved |
| Mathematical cosmology | Only where needed | Required when the tier depends on it |
| Matchup use | Readable baseline | Detailed CRT and adjudication |

System migration

A System H entry may be reviewed for a System A classification.
Promotion requires the stricter System A qualification test.
Preserve the original source and evidence when promoting a claim.
Add the bridge premise that supports the formal classification.
Do not rewrite an H-level observation as if it had always been a completed A-level proof.

16. How to Use Tabbers

The owner has confirmed that PABC implements the <tabber> and </tabber> feature. Use tabbers to separate character keys, forms, ability groups, or evidence categories. The basic syntax follows the familiar MediaWiki-style format.

Each tab starts with |-|, followed by its title and =. The tab content follows the equals sign. Add another |-| line for every additional tab. Open the group with <tabber> and close it with </tabber>.

Basic tabber example

```
<tabber>
|-|Overview=
Write the character's general description here.

|-|Base Form=
Write the Base Form profile here.

|-|True Form=
Write the True Form profile here.

|-|References=
List the source references here.
</tabber>
```

Tabber for multiple keys

```
<tabber>
|-|Key 1: Base=
Tier: [Insert tier]

Powers and Abilities: [Insert supported abilities and evidence.]

Weaknesses: [Insert weaknesses and conditions.]

|-|Key 2: Awakened=
Tier: [Insert tier]

Powers and Abilities: [Insert supported abilities and evidence.]

Weaknesses: [Insert weaknesses and conditions.]

|-|Key 3: True Form=
Tier: [Insert tier]

Powers and Abilities: [Insert supported abilities and evidence.]

Weaknesses: [Insert weaknesses and conditions.]
</tabber>
```

Tabber for System H evidence

```
<tabber>
|-|Physical=
List physical feats, targets, and source coordinates.

|-|Abilities=
List hax, resistances, activation conditions, and limitations.

|-|Structure=
Explain the relevant cosmology and structural evidence.

|-|Narrative=
Explain narrative statements and their context.

|-|Conditional=
List claims that remain uncertain or version-dependent.
</tabber>
```

Tabber rules and common mistakes

Always write the tab title followed by =. Always put |-| between tabs. Always close the group with </tabber>. Keep tab titles short, descriptive, and consistent. Use tabbers for genuinely separate content, not to hide a weak argument or bury the tier justification. Keep essential warnings visible outside the tabber when readers must see them immediately.

A code fence displays the syntax as code. Remove the code fence when you want the editor to parse the tabber as an actual interactive component. Do not accidentally place the entire live tabber inside a code block. Preview the result before publishing and test the page on desktop and mobile.

Do not assume nested tabbers work merely because basic tabbers work. Do not copy Fandom's nested-tab parser syntax unless PABC confirms that exact implementation. If nested tabs fail, use separate top-level tabbers. Test tables, images, links, and LaTeX inside tabs. Avoid huge unstructured text blocks and empty tab titles.

17. Profile Drafting Workflow

Identify the character and continuity. Decide whether multiple keys are necessary. Collect primary sources before writing the tier conclusion. Draft the summary in plain language. Record each key separately. List powers and abilities with evidence. Write a bridge premise for each major tier claim. Add applicable System H evidence tags. Complete Systems B–F as required. Check the current System A definition. If using Tier 1-F or Tier 2-H, quote the current owner-approved definition and prove each required condition. Compare adjacent tiers, add limitations and counterevidence, add references, preview the page, and submit the draft to CRT.

18. What to Do

Use primary sources whenever possible. Explain every exceptional claim. Keep character versions distinct. Use the current binding PABC scale. Treat Tier 1-F and Tier 2-H as canon following the owner's confirmation. Quote their exact current definitions when using them. Use System H to organize evidence and System A for formal tier qualification. Complete Systems B–F for their respective analytical tasks. Use tabbers to make long profiles navigable. Include anti-feats and limitations. State uncertainty when the source is ambiguous. Give reviewers enough information to reproduce the reasoning.

19. What Not to Do

Do not tier by vibes. Do not treat a title as a feat. Do not treat a route as a tier. Do not treat an H-tag as a tier. Do not confuse Tier 2-H with System H. Do not invent the definitions of Tier 1-F or Tier 2-H. Do not use a tier label as its own evidence. Do not equate infinity with qualitative transcendence. Do not equate dimensional count with ontological superiority. Do not equate possible worlds with concrete universes without evidence. Do not equate narrative awareness with absolute narrative authority. Do not ignore anti-feats. Do not combine incompatible continuities without justification. Do not use equations as decoration. Do not hide missing premises behind jargon. Do not self-approve a profile or claim acceptance before the review is complete.

20. Common Reasons for Rejection

The source does not support the stated claim. The scan is missing or cannot be located. The bridge premise is absent. The character is not shown to affect the cited structure. The cosmology is described but not connected to the character. The argument relies on metaphor as literal fact. The argument conflates access with control or representation with existence. The argument treats contradiction as automatic power. The argument uses an outdated tier definition. The argument misuses Tier 1-F or Tier 2-H. The argument confuses System H with the tier label 2-H. The profile merges different keys or continuities, omits limitations, makes unsupported HΩ claims, or claims Tier 1-S without passing its separate test.

21. How to Get a Profile Accepted

Draft the page using the template below. Replace every bracketed placeholder. Submit the draft to the appropriate CRT channel with the required draft label. Provide direct links to scans and source coordinates. Defend the bridge premise in plain language. Answer reviewer objections without silently changing the claim. Revise the profile when evidence or interpretation changes. Wait for the required staff or supervisor decision. Do not mark the profile accepted until an authorized reviewer confirms it.

Tier 0 and other exceptional claims must follow the special review process in the current binding rules. Where the policy requires three independent supervisor reviews, obtain all three. Do not replace a required unanimous decision with a poll or informal reaction count.

22. Copy-Paste Profile Template

Copy the code below into the source editor. Replace every bracketed placeholder. Delete fields that genuinely do not apply, but do not delete required analytical fields. Keep the template inside the triple-backtick fence when sharing it as code. Remove the outer fence only when pasting the template into the actual wiki source editor.

```
thumb|400px|Caption for the image.

{{Quote|
"Insert an in-character quote here that encapsulates their personality."
— Character Name
}}

== Summary ==

Character Name is a [brief description of their role in the story]. Under the current PABC Forum framework, this version is classified as [Insert Tier]. [Explain the strongest supported claim and its main limitation.]

== Profile Information ==

Name: [Character Name]
Origin: [Verse Name]
Gender: [Gender]
Age: [Age]
Classification: [Titles, species, roles, and relevant nature]
Continuity: [Continuity or canon version]
Keys: [List profile keys]

== Key 1: [Base Form] ==

This key represents [describe the state or version].
Tier: [Insert current PABC tier]
HΩ Route: [Insert route or None]
System H Tags: [Insert applicable tags]
Powers and Abilities: [Insert abilities with evidence.]
Attack Potency: [Level and bridge premise.]
Speed: [Level and evidence.]
Lifting Strength: [Level and evidence.]
Striking Strength: [Level and evidence.]
Durability: [Level and evidence.]
Stamina: [Level and evidence.]
Range: [Range and conditions.]
Intelligence: [Supported description.]
Weaknesses: [Weaknesses and source coordinates.]

== Key 2: [Awakened / True Form] ==

This key represents [describe the state or version].
Tier: [Insert current PABC tier]
HΩ Route: [Insert route or None]
System H Tags: [Insert applicable tags]
Powers and Abilities: [Insert abilities with evidence.]
Attack Potency: [Level and bridge premise.]
Speed: [Level and evidence.]
Durability: [Level and evidence.]
Range: [Range and conditions.]
Weaknesses: [Weaknesses and source coordinates.]

== PABC System Breakdown ==

=== System A: Formal Tier Qualification ===

=== System H: Evidence Tags ===

=== System B: Ontology ===

=== System C: Logic ===

=== System D: Evidence Record ===

=== System E: Review Procedure ===

=== System F: Verdict and Confidence ===

== Formal Logic and Non-Entailments ==

Approach does not equal identity.
\[
\mathrm{Approach}(x,S)
Rightarrow \mathrm{Identity}(x,S)
\]
[Explain why approaching, accessing, or affecting a structure does not prove identity with it.]

Representation does not equal ontological control.
\[
\mathrm{Represents}(x,S)
Rightarrow \mathrm{Controls}(x,S)
\]
[Explain the difference between representing a structure and controlling it.]

Access does not equal totality.
\[
\mathrm{Access}(x,w)
Rightarrow \mathrm{Controls}(x,W)
\]
[Explain why access to one world does not prove control over the complete domain.]

== Other ==

Notable Victories: [Character, verse, reason, and evidence.]
Notable Losses: [Character, verse, reason, and evidence.]
Notable Statements: [Statement, source, context, and interpretation.]

== References ==
<references />

Category:PABC Forum
Category:[Insert Verse Name]
Category:[Insert Tier]
```

23. Final Submission Checklist

[ ] Character name, continuity, and keys are clear.
[ ] Every major feat has a source coordinate.
[ ] Source context and bridge premises are explained.
[ ] The narrowest defensible tier is selected.
[ ] Tier 1-F and Tier 2-H follow their current binding definitions.
[ ] Tier 2-H is not confused with System H.
[ ] H-tags are used as evidence categories, not tier substitutes.
[ ] Systems B–F are completed as required.
[ ] HΩ route claims are separately justified.
[ ] Tier 1-S is not assumed from narrative awareness alone.
[ ] Counterevidence and limitations are included.
[ ] Tabber syntax has been previewed.
[ ] The page renders correctly on desktop and mobile.
[ ] All placeholders have been replaced.
[ ] All references work.
[ ] The CRT has been submitted.
[ ] The profile is not marked accepted before staff approval.

24. Final Reminder

A strong PABC profile is not the profile with the most impressive tier label. It is the profile whose evidence, interpretation, bridge premises, and conclusion survive scrutiny. Use the new canon labels correctly. Use System H to organize evidence, not to bypass analysis. Use System A to classify the demonstrated structure. Use tabbers to make long profiles navigable, not to hide weak arguments. Be precise, cite your sources, and let the evidence do the work.

***

Reference and implementation notes

The owner-confirmed update supplied for this guide takes precedence over older wording that still calls Tier 1-F and Tier 2-H proposals. The public consolidated tiering page may lag behind that later confirmation. Staff should synchronize the public reference with the owner's updated definitions. MediaWiki's Tabber extension uses tab titles followed by = and separates tabs with |-|. Fandom documents the same basic structure. PABC's own implementation is controlled by the forum owner, so PABC-specific behavior takes precedence over assumptions about Fandom or generic MediaWiki.

External reference: https://www.mediawiki.org/wiki/Extension:Tabber
External reference: https://community.fandom.com/wiki/Help:Tabber
Official PABC tiering page: https://pabc-forum.com/discussion/pabc-tiering-draft-constant-revisions-1
Rule: explain the character-to-target bridge explicitly.
Rule: separate direct evidence from interpretation.
Rule: preserve version and continuity distinctions.
Rule: record counterevidence and limitations.
Rule: use the current owner-approved tier definitions.
Rule: do not confuse System H tags with Tier 2-H.
Rule: preview every tabber before publishing.
Rule: do not treat a route as an automatic tier award.
Rule: choose the narrowest tier supported by the evidence.

Public comments (0)

No public comments yet.

Open interactive Wiki pageBrowse Wiki