Just an idea for a purchase-able NPC for the guildhall where guild/alliance members could submit their character builds for easy sharing.
Ideally, could be sorted/filtered dynamically - ie, PvE, AB, Farming, etc, but that could also all be done with naming conventions. Also filterable by date and who submitted, for ease in pruning.
If you submit a build, you can remove it, otherwise only officers could remove builds.
Idea came about this weekend when I was AB'ing and was bored of the build I was running, was thinking it'd be nice to have a place in-game to go and find new builds.
New Guildhall NPC: Build Librarian
1 pages • Page 1
Quote:
|
Originally Posted by Beqxter
Idea came about this weekend when I was AB'ing and was bored of the build I was running, was thinking it'd be nice to have a place in-game to go and find new builds.
|
/notsigned
Builds are currently stored on your localized computer as a series of text files. Check it out in your GW folder or try playing on your characters on a friend's computer. Unfortunately, the way the build templete system is currently coded, the builds aren't "saved" on the server side, so there would be no way to impliment this system without massively recoding the system and putting a lot more server space for data storage.
Builds are currently stored on your localized computer as a series of text files. Check it out in your GW folder or try playing on your characters on a friend's computer. Unfortunately, the way the build templete system is currently coded, the builds aren't "saved" on the server side, so there would be no way to impliment this system without massively recoding the system and putting a lot more server space for data storage.
Wow, this is the first idea I've heard in a long time that's legitimately cool.
As far as feasibility, this wouldn't need to be anything more than one new table to store the build codes in their already-gigantic SQL 2k5 db, and some new sprocs or functions to handle the lookups whenever the NPC's 'inventory' is loaded into memory. Of course, there's probably a bit more to it in their system, but that's the basic idea.
However, since the difficulty of implementation is really up to Anet's team, there's no reason to /sign or /notsign solely based on that. If it's cool, I'd still say it's worthy of consideration.
In other words, /signed. Neat idea, thanks Beqxter.
Quote:
|
Originally Posted by HawkofStorms
/notsigned
Builds are currently stored on your localized computer as a series of text files. Check it out in your GW folder or try playing on your characters on a friend's computer. Unfortunately, the way the build templete system is currently coded, the builds aren't "saved" on the server side, so there would be no way to impliment this system without massively recoding the system and putting a lot more server space for data storage. |
However, since the difficulty of implementation is really up to Anet's team, there's no reason to /sign or /notsign solely based on that. If it's cool, I'd still say it's worthy of consideration.
In other words, /signed. Neat idea, thanks Beqxter.
Z
Also, couldn't Anet find a way to save the text as it shows up when we ping our skills? Not a computer genius by any means, but I thought I would throw that out there.
Also, this idea is great! I definitely think something like this would benefit guilds all over. But gotta watch out for the spies who would join a guild just to steal their builds (assuming they actually have some unique ones, obviously).
/signed
Also, this idea is great! I definitely think something like this would benefit guilds all over. But gotta watch out for the spies who would join a guild just to steal their builds (assuming they actually have some unique ones, obviously).
/signed
L

