Funny guild wars build templates

I guess that's the price for using meta builds in everything.. The issue is not that it's not free is it's server side. The issue is the price. They are charging each template for more than gems how much is it?

Let's be clear, a template file for a char isn't going to be more than 32 kb maybe 64 kb if you have more than 50 templates on a char , a template string is maybe 1 kb at most, counting equipment. If you have 10 chars it's what, kb maybe. There is no version of this where 10Kb costs 1. Even if you add the design cost of the template feature.

I wouldn't mind the whole template feature was locked under a one time price of gems. But the whole cash grab is low. Especially when they put the templates on the server on purpose. Because if they did it locally like in GW1, it would have saved a lot of money for them and for us. And please stop with "the game is free", the game isn't free.

It paid itself with the older players that bought the game when it was not and the ones that have the expansions. The free part is the base game without trading post Such is the nature of the GW2 player-base I guess.

Gotta grind those complaints out after all. Everyone also seems to keep forgetting that Templates in GW1 didn't have to deal with the type of gear system this game has. In fact, it didn't even deal with its own gear system. Build Templates only have to deal with Skill slots and Attribute points GW1 also had 4 weapon slots you could load up on the fly, and for the vast majority of builds the only necessary gear change was a spare helmet with a different rune on it.

Build slots for GW2 could do the external string thing for Utilities and Traits, because those are universal to the profession in question. Gear on the other hand is wildly different, because you're dealing with Bespoke UIDs for the item, and not just the Item ID which there are also way too many to be sane Its THIS that all the problems stem from.

And NO, its not easily fixed They're going with the most viable solution to this whole situation, which is Containers that house the items in question. Legendary gear adds another layer of issues with how its Meta data has to be manipulated. The relationship to the slots wholesale avoids this problem, and the containers make a framework to address a whole set of items as a single bundle. But it still requires you have all the gear you need on that character, and gets stored in the gear panel rather then the inventory.

Trying to make One gear set active across multiple characters is an entirely different problem, and would need something very specific to do it. And thats a new class of Shared slots that have to paradoxically both allow and deny all valid gear combinations for a Class. Making them sharable on a per-class basis is very doable, but kind of defeats the purpose. Separating the weapons gets rid of the biggest conflict for armor, but the weapon compatibility problem across classes remains.

I can think of one solution, but I don't believe the community will fully appreciate the compromise, and would end up just demanding more then its capable of Binding Template items to a special bank tab, and using that as a Pool of gear. This addresses the UID problem, since those items are now pinned down. But it also means at any point removing an item from the pool for any reason like to change its stats or runes breaks ALL the templates its attached to, and will have to be manually updated with the replacement item one by one.

Because I guaranty, if it doesn't go out of its way to make it not-load, players will start running around with missing armor pieces and not realize it. If you deny players are that dumb, you need not look further then this forums to prove their existence Gear stats is the entire justification for the need of Gear templates But its also the reason why Gear templates are ultimately no more useful then what we're already doing, sans Legendary gear.

Many things in gaming were free in the 00s that aren't anymore. We live in the age of "pay to pay" model for some time now. And since most seem really happy to keep "paying to pay" the trend can only continue.

The issue is that "additional storage". Let's be clear. Equipment Templates can also record the customization of legendary items, which can freely change attributes and upgrades. You can equip a single legendary item to multiple Equipment Templates with different attributes and upgrade choices for each.

You can copy and paste an Equipment Template from one tab to another, rename it, or empty it of all items including attributes and upgrades. The latter will return any items not used in other templates to your normal inventory.

Hover your mouse cursor over an Equipment Template tab for a short summary of the Equipment Template stored in it, including weapon types and total stats from the items it references excluding upgrades. Each of your characters will have access to two Equipment Template tabs for free, and the first will be automatically populated with an Equipment Template containing the gear your character was wearing when you last logged in. You can purchase additional Equipment Template tabs from the Gem Store.

PvP equipment works much differently than PvE and WvW equipment, so it will require its own template system. Because this presents different technological challenges, we chose not to delay the release of the completed Build and Equipment Templates. Buy Now. Learn All about Build and Equipment Templates. They are also linked on the main page. All packs for archived builds can be found at this link: Archived Build Packs last updated 26 October Unzip the downloaded file and place the buildpack folder into your Skills subfolder for Guild Wars.

By default, the filepath is:. All builds should follow regular formatting to ensure the correct build information is collected and, in particular, single build pages should have one main skill bar. If you notice a build page that would not or does not get fully collected by the script, please fix the page or note the issue on the build's talk page. Build packs are collected by a Python script which is available at a GitHub repository for reference and community input.