Jump to content
  • Sign Up

Build Templates by developer of arcdps fully allowed by ANet


Nafets.1238

Recommended Posts

The developer refers to it as a stopgap measure himself. That said, I think this is great. While it would be better to have this implemented into the game itself, at least build templates now exist and are non-ToS breaking.This has also motivated me to install arcDPS just to test out the build templates

Link to comment
Share on other sites

Example

Quote by Chris Cleary of ANet:

About 2-3 months ago I asked /u/deltaconnected to take down his previously created Build Templates addon to ArcDPS. At the time it was in violation of our rules to distribute it and it had key issues with it when it came to functionality and interaction with the game client.

This release is the result of a multi-month coordination to get his Build Templates addon into a place where I can green-light it for release. Unlike DPS meters, Build Templates is a much more passive user interface addon and thus it could be individually allowed to release outside of the DPS meter Terms of Service rules restriction. If future developers are interested in working with me to create addons, please reach out to me and we can chat.

I'm green-lighting this due to the developer's trustworthiness after months of interaction and willingness to add key restrictions and functionality changes to accommodate my push to keep addons away from becoming a "must have to win" situation (WvW restrictions were not outlined in his post, but they are there along with others).

In their current state, /u/DeltaConnected's build templates are green-lit and safe to use by users (in terms of violating the Terms of Service). I've asked him to run any functionality changes by me before releasing, so hopefully we don't need to worry about things changing in the future in terms of "safe to use".

This is officially unsupported, and ArenaNet will not be able to offer any support for this addon or issues that occur due to use of this addon.

Summarizing:

  • Use of the current iteration of ArcDPS for build templates is safe to use in that it does not violate the Terms of Service
  • ANet considers the developer of ArcDPS to be trustworthy and has worked directly with /u/deltaconnected to ensure the above
  • The app is not supported — if something goes wrong, it's on you.
  • Things can change; it's our responsibility to keep track.
Link to comment
Share on other sites

I've mentioned this elsewhere but still see the gear being eaten warning being taken as something likely to happen:

I don't have GW2's source so I don't "know" where the equip-item function is. Have to find it by scanning for some markers specific to it. It's possible (with some astronomically terrible luck) that equip-item no longer has those markers after a game update and delete-item acquires them, so every time it tries using equip it instead uses delete. Or, because it uses internal client functions in a way that testers and QA never would, some other unforeseen effect due to it's usage.

Link to comment
Share on other sites

@deltaconnected.4058 said:I've mentioned this elsewhere but still see the gear being eaten warning being taken as something likely to happen:

I don't have GW2's source so I don't "know" where the equip-item function is. Have to find it by scanning for some markers specific to it. It's possible (with some astronomically terrible luck) that equip-item no longer has those markers after a game update and delete-item acquires them, so every time it tries using equip it instead uses delete. Or, because it uses internal client functions in a way that testers and QA never would, some other unforeseen effect due to it's usage.

So basically if Anet sends their spaghetti code through a meat grinder, your script might suddenly start pointing to "delete item" instead of "equip item". I think I'll take the risk, even Anet doesn't usually mutilate their code that bad.

Link to comment
Share on other sites

@Pyroatheist.9031 said:So basically if Anet sends their spaghetti code through a meat grinder, your script might suddenly start pointing to "delete item" instead of "equip item". I think I'll take the risk, even Anet doesn't usually mutilate their code that bad.

The assembly the code generates, not the code itself. Option A is to include 'offsets' in the pattern, which are much more likely to break across game updates, and option B is to rely on arithmetic and assignment, which are less "unique" but also less likely to change (more common to add a new member to a class and write new code than modify existing that works)

Link to comment
Share on other sites

as software developer myself, the main problem i find thinking in build templates is deal with changes in inventory size. basically 2 situations a)user save a template, and when click to "load" it, the inventory is full. b)the user deleted, sold, moved a gear piece saved into template. btw, I have not the slightest idea how it's done in Gw2, I'm just theorizing.

and yeah, anything is better than alt+tab to navigator to search for a build.

Link to comment
Share on other sites

a easy "trick" would be instead of a template save a "gear piece id", must work on "find match stats and equip", the template gear list, would memorize the stats of desired gear piece+runes instead of some "piece id", when loading the list, the "finder" will search for pieces that match the desired stats on inventory, and equip it. if didnt find it(cuz user moved or deleted) it will do nothing.

Link to comment
Share on other sites

@deltaconnected.4058 said:I've mentioned this elsewhere but still see the gear being eaten warning being taken as something likely to happen:

I don't have GW2's source so I don't "know" where the equip-item function is. Have to find it by scanning for some markers specific to it. It's possible (with some astronomically terrible luck) that equip-item no longer has those markers after a game update and delete-item acquires them, so every time it tries using equip it instead uses delete. Or, because it uses internal client functions in a way that testers and QA never would, some other unforeseen effect due to it's usage.

Honestly I only took that warning as a sort of "look guys, I'm not ANet and if something I have no control over screws up I can't guarantee the support team will restore your items".

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...