WARNING

The templates mentioned in this documentation apply Semantic MediaWiki Properties to pages. As mentioned in the documentation for those templates, any use on pages other than Team pages will result in the entire page being deleted.

DOCUMENTATION

Team pages must all follow and use the same specific layout and templates. These pages serve as a central page for the team that displays teams they can counter and teams that can counter them , as well as be able to automatically generate this information about them on the Team Counter Lists page or any other page the information may be needed on. This technique of only adding the information to the team page and being able to automatically load it in other places makes it easier to modify and add information without having to do it on numerous pages.

Team page concepts

Team pages are meant to hold various team compositions that exist under a specific leader. The page is created with the best variation of the team as the main focus and looks at the most commonly used end game team compositions. It is important to focus on most common team compositions as there are limited number of substitute places available in the template calls. While this can be increased, having a lot of unit images may be distracting or confusing to some people. A good example of how to start is by thinking of the toughest teams to defeat and then viewing each team composition as getting weaker. For example a Commander Luke Skywalker led Rebel team. As of the writing of this, the team variation flow would look like this:

• Typical Team - CLS, Threepio & Chewie, C-3PO (Strongest version)
• Variation 1 = CLS, Han Solo, Chewbacca (Next strongest version)
• Variation 2 = CLS, Chewbacca, Threepio & Chewie

When to split into new team pages

Sometimes it may be best to create a new team page when the main focus of the team starts to substitute too many units or include too many units as substitutes. Here is an example.

• Variation 3 = CLS, Biggs, Wedge (Not recommended to include)

While variation 3 can be an early game team for CLS, what it can counter and what is needed to counter it is going to be drastically different than the other variations. For the most part all of the trio, CLS, HS, and Chewie, team comps can be strong against most of the same teams and the slight differences can be noted in the details for the counter. The better option would be to just create a Team 3v3 - Early Game (CLS Rebels) team that could have all the different variations with Stormtrooper Han, Old Ben, Lando Calrissian, etc.. That way it doesn't water down the comp of the more end-game line up versions of the teams. Also, having Early Game at the beginning of the team name would group all early game teams together in the Team Counter Lists page or allow for excluding any teams with Early Game in it from showing up.

Later down the road if a stronger version of a team led by the same person becomes available the page can be modified to reflect the new changes or a Team 3v3 - CLS (Rebels v2) could be created if there is a large number of new characters that make up that team that are not part of the original pages team.

Teams that have greatly differing line ups and/or greatly differing power may also be better for new pages. For example:

• Team - Bastila Shan (Jedi)
  • Typical Team - Bastila Shan, Kanan Jarrus, Ezra Bridger
  • Variation 1 - Bastila Shan, Grandmaster Luke, Wat Tambor

The typical team for Bastila Shan is more of a mid-game or early game team while the variation 1 is a very end-game team with a Galactic Legend. The teams it would take to beat Variation 1 would look a lot different than the teams needed for the Typical Team. Due to the difference in requirements for the characters on the team and the huge difference in power, it would be best to separate these teams. That would also allow for more slight variations of each team to be included. These slight variations usually mean only substituting 1 or two units on the team with 3 usually being the max.

Plug-n-Play characters

For teams with plug-n-play units you could put that team composition at the bottom of the list. These minor roster changes are usually added to stop certain counters, so it may be important to note in counter details for the team that if includes one of these plug-n-play characters in the lineup it will not work. Likewise if a team is a specific counter for one of the variations of a team make sure to mention that in the counter details also.

Creating the page

If a page does not already exist for the team you are looking to add and it doesn't make sense to add it to an existing page with that lead due to things discussed above you will need to create the new page for the team in the following format; Team 3v3 - leader_name (faction).

• Example: Team 3v3 - Emperor Palpatine (Sith)

Properly formatting the new page

As mentioned at the beginning, it is very important for these pages to follow a specific format in order for them to work properly. The page must follow the layout below. You can copy and paste this layout for a starting point and adjust as needed. All information in all capital letters will need to be replaced and template calls will need the information added. It is highly recommended to use Edit Source to do this.

<div style="float:right;margin-left:10px;">__TOC__</div>
'''[[Team name:: 3v3 LEADER_NAME (FACTION)]]''' is a team led by LEADER that may be seen or used for Grand Arena Championships during their 3 vs 3 format. OPTIONAL BRIEF INFORMATION ABOUT THE TEAM. This team usually consists of 3 of the following characters: 
{{Team comp
 |notice=y
 |lead=
 |lead_lock=y
 |ally1=
 |ally1_lock=
 |ally2=
 |ally2_lock=
 |sub1=
 |sub2=
 |sub3=
}}

== Team Compositions ==
{{Team Variation
 |squad_type=Character
 |lead=
 |ally1=
 |ally2=
 |v1_name=Variation 1
 |v1_lead=
 |v1_ally1=
 |v1_ally2=
 |v2_name=Variation 2
 |v2_lead=
 |v2_ally1=
 |v2_ally2=
}}

== Recommended Abilities and Mods ==
BRIEF INFORMATION ABOUT ALL REQUIRED ZETAS
{{Team Card
 |noGear=y
 |noStats=y
 |noReq=y
 |squad_type=Character
 |leader=
 |leader_abilities=
 |leader_mods=
 |ally1=
 |ally1_abilities=
 |ally1_mods=
 |ally2=
 |ally2_abilities=
 |ally2_mods=
 |ally3=
 |ally3_abilities=
 |ally3_mods=
 |ally4=
 |ally4_abilities=
 |ally4_mods=
 |ally5=
 |ally5_abilities=
 |ally5_mods=
}}

== Is a counter to ==
{{Counter Team
 |5=to
 |3v3=y
 |team_name=
 |type=
 |banners=
 |details=<b>Substitutes:</b> RECOMMENDED SUBS.<br />
<b>Zetas:</b> REQUIRED ZETAS<br />
<b>Strategy:</b> DETAILS ABOUT TURN ORDER,KILL ORDER, AND ANYTHING ELSE IMPORTANT TO KNOW.<br />
<b>Video:</b> LINK (CREATOR) • 
}}

== Can be countered by ==
Following this '''kill order''' has the potential to make battles a little easier when facing this team:<br />
'''[[Team kill order::KILL ORDER USING FULL NAMES AND > < = >= <= TO INDICATE PRIORITY]]'''

{{#ask:
 [[Category:Team]]
 [[Counter team::THIS_TEAMS_NAME]]
 |mainlabel=-
 |?Team name
 |?THIS_TEAMS_NAME counter type
 |?THIS_TEAMS_NAME counter max banners
 |?THIS_TEAMS_NAME counter details
 |?Category:Layout # ERROR, for
 |?Team lead #
 |?Team ally 1 #
 |?Team ally 2 #
 |?Team ally 3 #
 |?Team ally 4 #
 |?Team substitutes #
 |?Team lock #
 |?THIS_TEAMS_NAME kill order
 |?Category:HideName # na,na
 |?Category:Team 3v3 # 3v3,5v5
 |sort=THIS_TEAMS_NAME counter type
 |order=asc
 |format=template
 |template=Counter Team
}}

[[Category:Team 3v3|LEADER_NAME]]

Format breakdown

The first part of the page defines the semantic property for the teams name and gives brief important information about the team. It is very important to make sure that 3v3 is added to the beginning of the Team name assignment. This section does not need a lot of details about how they counter teams because that should be entered as the details for the specific team counters. Either at the beginning or very end you must include the [[Category:Team]] so it will assign the page to that category. It is important to specify the team leader in the assignment of the Category so it will be alphabetized under the letter for the leader instead of Team.

Team Compositions

The next part, Teams Compositions, adds the semantic properties for the units that will be on the team and clarifies which ones can be substituted along with the other options for substitutes. It also loads the images of them and it will transclude the Template:Team Comp page with the submitted information. Click the link for the template to view its documentation.

Team Variations

In the Team Variations section of the page it defines the different team variations people may encounter or use. It just displays images of the units with option to show how many zetas the units will need. It gets the images by transcluding the Template:Team Variation page with the submitted information. Click the link for the template to view its documentation.

Recommended abilities and mods

In this section of the page it defines the required zetas and abilities and then gives a graphical overview of all recommended mods and abilities. For abilities it should have the name of the ability and the type in ( ) followed by the image of the ability material needed. You would use the Template:Icon for displaying the image and resizing the image. Here is an example

{{Icon|Zeta|20px}}

Serve Again (Unique) .

For mods you would use the Template:Mod for displaying the mods. Here is an example of how to use it and format it so Secondaries can be shown.

{{Mod|spd||set|4=28px}} {{Mod|cc||set|4=28px}} {{Mod|spd|arrow|pri|28px}}{{Mod|cd|triangle|pri|28px}} {{Mod|off|plus|pri|28px}} {{Mod|hp|circle|pri|28px}}<br />Secondaries: {{Mod|spd||set|4=28px}} {{Mod|off||set|4=28px}}

Secondaries:

Is A Counter To

In this section you only need to set the teams that can be defeated by the pages team. You do this by transcluding the Template:Counter Team page with the submitted information. Click the link for the template to view its documentation.

Can Be Countered By

In this section you will add the information about the kill order and do an Ask on the semantic data for the team and it will automatically scan the wiki looking for pages that say they are a counter to the team. For the kill order style it in the following format with left being most important to die first and farthest right being the least important:

• Chewbacca > Threepio & Chewie > Han Solo > CLS > Any
• Chewbacca >= Threepio & Chewie > Han Solo = CLS > Any

For the #ask, all of the information in caps must be replaced with the proper information for it to load the data correctly. You can read more about how this works by checking the documentation for Template:Counter Team.

Creating Property pages

After fully completing the page you will need to create the property pages so it will not give errors when trying to retrieve the information. Each page must contain the following:

This property has a datatype of [[Has type::Text]].
<noinclude>[[Category:Property-Counter]]</noinclude>

You can use the following to help you with creating the property pages. You will need to replace team_name with the name given to the team.

Adding countered teams to an existing page

If a page already exists all you have to do it is add more teams it can counter by using the Template:Counter Team. As mentioned above it is added by using the following on the page and adjusting as needed:

{{Counter Team
 |5=to
 |3v3=y
 |team_name=
 |type=
 |banners=
 |details=<b>Substitutes:</b> RECOMMENDED SUBS.<br />
<b>Zetas:</b> REQUIRED ZETAS<br />
<b>Strategy:</b> DETAILS ABOUT TURN ORDER,KILL ORDER, AND ANYTHING ELSE IMPORTANT TO KNOW.<br />
<b>Video:</b> LINK (CREATOR) • 
}}

Technical Details

This section is just for informational purposes and is not part of the directions for creating a Team page.

Template flow

Team Comp

The team page contacts Template:Team Comp and gives it the information for the parameters. Team Comp then sends the supplied information to Template:Team Unit to create the images. Team Unit then transcludes onto the Team Comp page and the Team Comp page is transcluded onto the team page.

Team Variation

The team page contacts Template:Team Variation and gives it the information for the parameters. Team Variation then creates a table and sends the supplied information to Template:Team Unit to create the images. Team Unit then transcludes onto the Team Variation page and the Team Variation page is transcluded onto the team page.

Team Card

The team page contacts Template:Team Card and gives it the information for the parameters. Team Card then creates the specified table, fields, and content with the provided information. If Template:Icon and Template:Mod was sent it will be transcluded to the Team Card page and then the Team Card page will be transcluded onto the team page.

Counter Team TO

The team page contacts Template:Counter Team and gives it the information for the parameters. Counter team then builds a box element and adds the provided information to the proper places. To generate the images for the units on the team the template does an #ask for semantic data about the team and passes the results to the parameters of the Template:SmwCounters page. The SmwCounters page then sends the provided information to Module:Counters which will build the html code needed to display the images. The images will be added to the SmwCounters page which will then get transcluded onto the Counter Team page and then the Counter Team page will be transcluded onto the team page.

Counter Team FOR

The team page will do an #ask for semantic data about the teams that can counter it and then pass the results to the parameters of the Template:Counter Team page. Counter Team then builds a box element and adds the provided information to the proper places. To generate the images for the units it passes some of the provided information to Module:Counters which will then build the html code needed to display the images. The images will be added to Counter Team and then the Counter Team page will get transcluded onto the team page.

Semantic

The following information will be added as semantic properties of the page when created properly. This information is used when you #ask for semantic data so that you can easily create tables and templates using the information it finds.

• Team name = defines the team name of the page
• Team lead = defines the leader of the team
• Team ally 1 = defines the preferred ally of the team
• Team ally 2 = defines the preferred ally of the team
• Team substitutes = defines the substitutes that can be used
• Team lock = defines which units typically should not be substituted
• Team kill order = defines the default/general kill order for the team
• Counter team = defines the name of the teams that the page team is a counter to
• COUNTERED_TEAM_NAME counter details = the details of how the page team counters that team
• COUNTERED_TEAM_NAME counter type = the type of counter the page team is for the team
• COUNTERED_TEAM_NAME counter max banners = the avg max banners the page team may be able to get against the team in Grand Arena
• COUNTERED_TEAM_NAME counter kill order = the kill order for the page team to follow when going against the other team