Standard Format for Team Profiles

Articles about Standard Format Pages	Character Profiles • Verse Pages • Item Profiles • Civilizations Profiles • Team Profiles • Vehicle Profiles • Location Profiles • Powers and Abilities • Verse-Specific Powers and Abilities • Categories • Navigation Templates • Border Template • Common Editing Mistakes • References • Sandbox Creation

Insert a Picture that represents the team, preferably the entire roster, or an Iconic Image in lack of a better option. Standard size is 400px aligned to the right

“

If you wish, you can add a quote related to the team whose profile you are creating

„

Summary

A brief explanation and info summary of the Team and its history, membership, etc.

Members

A list of the character profiles which are members of the Team. Add links to all of the associated pages available in the wiki.
Organise them into incarnations for the team, so they are listed together with their teammates.
Using galleries for character profiles is preferable if they have images.

First Incarnation

Character 1
Character 2

Second Incarnation

Character 3
Character 4

Powers and Stats

Tier: The Team’s overall level on the Tiering System, preferably showing the tiers of both the strongest and weakest members

Key: For teams who have transformation stages/power-ups or who have variation incarnations across the story, insert those transformations/power-ups/incarnations here in bold.

Name: The Name of the Team

Origin: Self-explanatory, the series from which the Team comes from

Classification: Nature of the Team, its Origin etc.

Age: The Team’s age / How long it has last, or lasted

Membership: The Team’s members in numbers, either rough or precise.

Leader: The team's leader/head of operations (if any).

Team Resources/Abilities: Do not include powers from individual members of the team, only include abilities given from equipment, weapons, and other resources the team has access to.

Base of Operations: An area or facility which typically either houses the team and their equipment, or works as a planning room or hideout of sorts.

Attack Potency: The Team’s overall destructive power, preferably listing both the strongest and weakest members.

Speed: The Team’s speed, preferably combat, listing both the fastest and slowest members.

Lifting Strength: The Team’s lifting prowess, preferably listing both the strongest and weakest members.

Striking Strength: The Team’s physical attack power, preferably listing both the strongest and weakest members.

Durability: The amount of attack power members of the team can withstand before being overwhelmed, preferably listing for both the most and least durable members.

Stamina: Self-explanatory, preferably listing both the most and least resilient members.

Range: The distance the character's attacks/abilities can cover, preferably listing the team members with the highest ranged attacks.

Teamwork: Team's effectiveness in coordination with one another, and their experience doing so.

Intelligence: Self-explanatory, preferably listing both the smartest and dullest members.

Weaknesses: Weaknesses / Disadvantages of the Team and its resources as a whole.

Feats: List the team's amazing feats. Coordination feats, resource effectivity feats, battles won etc. You can judge a team's power by its feats. It is possible to add Respect Thread links to the list, as long as they follow the policies on the subject provided on the Editing Rules page.

Notable Team Attacks/Techniques: A list of some abilities the Team uses, by coordination between either two or more members.

Note: Self-explanatory.

Explanations (Optional)

This section can be used to explain the reasons for the assigned power level of a certain Team more in-depth, as well as how the powers and mechanics of the Team fundamentally work. This is particularly useful for more expansive teams.

However, it is very important that you make sure that the text has good grammar/sentence structure, and is easy to understand.

Gallery

If you wish, you can add a gallery containing pictures related to the team.

Notable Matchups

Victories:

Put some notable/good matches that result in the team's victory.

Losses:

Put some notable/good matches that result in the team's loss.

Inconclusive:

Put some notable/good matches with the results still unclear.

References

This is a section where the source references can be shown. To use them, switch to the source editor in the "Preferred editor" menu, if you haven't done so, and add some text to the profile between the <ref> and </ref> tags. It will appear in this section if the <references/> tag is inserted here at the beginning. Note that references will automatically show up in a list.

If multiple pieces of text should refer to the same source, then the reference's code should be modified to <ref name="name">Reference text</ref> to allow multiple uses. Then the named reference can be used later as just <ref name="name"/>. Here is an example of how to properly insert references into pages.

If you use many references within a single page, you can use the code {{reflist|2}} for 2 columns of them, so the layout looks better. If even that isn't enough a scrollbox can be employed by using the code {{scroll box|content={{reflist|2}}}}.

Read this guide if you want an extended knowledge on how to use references. You can also visit the References instruction page in this wiki.

Rules

Wiki enforces the rule that every member of the team roster must have their own profiles separate, for the team profile to be created. This is to ensure the capabilities of the team are indexed appropriately and completely. However, there are exceptions to this rule:

If only certain incarnations of the team are missing files while other incarnations aren't, the profile can still be made listing only the incarnations whose rosters are fully indexed.
In the scenario a few members of the team are inapplicable to receive a file due to being too minor, and by proxy weren't featured prominently as team members, the team profile can still be made with the file noting it only covers the active roster of the team.
In the scenario a few members of the team are inapplicable to receive a file due to being too mundane, the team profile can still be made with the file accounting their statistics and mechanics with respect to the entire team in the profile itself.
In the scenario there are numerous minor or unremarkable members of the team, they may be listed alongside other members of the team, either by their name or designation (e.g., bodyguard, knight, soldier, etc).
Characters from teams that all have identical or nigh-identical sets of Powers & Abilities can have a Team Profile without need of profiles for each of the members, as long as none of them have solo outings more or equally significant to their team appearances. In such a case, the profile should be formatted as a hybrid between a Team Profile and a Character Profile i.e. contain both fields for Character and Team Profile Format.

Additionally, teams must also be official in-verse i.e. referred to as such by characters within the verse, and possess a team name or an analogous term, or be extremely long-lived within the work and clear in formation, as well as being notable and prominent. This is to ensure excessively minor team-ups aren't indexed, and thus bloat the wiki.

Additional Information

If you intend to establish a page for "organizations" within this wiki, kindly adhere to the Standard Format for Civilization Profiles template instead of using the team template. Organizations are better suited to a modified Civilization format, as the Team format primarily focuses on indexing individual team members and their attributes such as Durability and Lifting Strength.

Other Standard Formats

Further Information

Discussions

Discussion threads involving Standard Format for Team Profiles