Guild Wars 2

Additional consideration.

* Sharing (chat links? codes? urls?)
Sharing should be done by pinging the template in chat, as well as by allowing copying and pasting URL.

Also a feature to copy and paste text to and from chat history would help a lot in this area. Since some web site that contain build may have long URL.

* Viewing (seeing some else’s vs. seeing your own)
Again by pinging the template. Similar to GW1.

* Saving (notepad vs. local vs. account vs. web)
Saving to local. Or if save to account, then have an option to download, upload template. (I think it would just add more burden to ANet to save to account.)

* Building (one spot in UI vs. multiple spots)
Multiple. One in wardrobe. Another in traits.

* Websites (third-party sites should work with in-game)
A must.

* APIs (Could expose an API to third-parties)
Would be very nice.

* PvP vs PvE vs WvW (each mode requires different configuration options)
Yes, the template should have an indication of which build is use for which mode.

 Start with two basic templates. These should be two independent templates.
1) Skills and traits template.
2) Wardrobe and dye templates.

Common Template features.

• A preview features.
• File name.
• Note section. Where user can put in notes about the template.
• Options to save, and load.
• Saving would be to local client computer. Or at least a feature to download and upload the templates if the templates are saved on the server.
  • My opinion, I think it would be more of a burden to A Net having to store these data on their server. Also, for build collectors, this would allow them to store as much build as they please.

Skills and traits template features:

• Template must include healing, utility, and elite skills.
• Current weapon skills should be included, but can be left out initially.
  • There is no need to remember the actual weapon, just the base weapon type. Ex, Scepter main hand, focus off hand.
• Include traits stats.
• Include traits skills.

Wardrobe and dye template features:

• Remember the skin of each piece of armor and outfits.
• Remember the dye selections for each piece of armor and outfits.

Template file structure:

• The template files can be a simple XML, or ini text file.
  • In the case with XML, the data can be listed in plain English along with some XML code so the server will know how to interpret the data.
  • In the case with a text ini file, the data can be listed under its classification section.