Dye Color Options for Weapons...Please!

[WarTactics.6725]

Dye color options for weapons... Please! …

I like spending real money on this game for the fashion wars!

 

Thanks,

WarTactics

 

[Randulf.7614]

A dev comment as to why not

I can't give you specifics or anything (they'd be very tedious to compute even if I still had access to the code), but GW2's codebase is very much an evolution of the codebase used for GW1. We did not start over, or anything crazy, but nor did we use the GW1 code unchanged.

Huge chunks of gameplay code were added, removed, or refactored so heavily as to be effectively-new (even things you might think would be the same, like inventory). The core rendering and networking capabilities had some significant reworking to support new features, but a lot of the fundamentals remained the same. The very low-level stuff, such as the classes we use to manage collections of data, do math, sort things... those didn't change much and some files might even be identical to the ones in GW1, except maybe for some copyright or header date changes.Essentially if you view the code as a vertical stack of functionality, with very-game-specific gameplay code at the top and generic data structure/algorithm stuff at the bottom, the closer something is to the top the more likely it experienced significant tweaking at some point during GW2's development.

To address the specific topic of this thread (dying stuff)... what I recall (so I might be wrong) is that the decision to dye armor but not weapons was a design one (in the sense we chose to do it, not that there were insurmountable technical issues), and made pretty early. We wanted a much richer dye system for GW2 than we had in GW1. This would require some changes to the way that the source art was authored, which increased the complexity (and thus time) of doing so. That additional complexity pays off best for armor, which is more visible on-screen than weapons generally are, and so (I think) it was decided that we wouldn't bother authoring dye support into the weapon art. Eventually this decision would have led to code changes or optimization relying on that assumption, and we arrive at where we are today.

As with all things, it could be made possible to dye weapons with sufficient code and art resources sunk into it. But it would be a nontrivial undertaking (and probably a non-trivial patch download!) tore-author all the existing source art with appropriate metadata for dye channels.(Please keep in mind that all of this is from memory from a longtime ago, so I may be forgetting/misremembering/et cetera some things.)

Tldr: it would require an immense amount of work on a very old code designed not to have it and need a monster patch 

Edited February 1, 2023 by Randulf.7614

[Arianth Moonlight.6453]

no thanks. Dyes on armor are already ridiculous at this point. No need for more.

[Inculpatus cedo.9234]

3 hours ago, Randulf.7614 said:

A dev comment as to why not

I can't give you specifics or anything (they'd be very tedious to compute even if I still had access to the code), but GW2's codebase is very much an evolution of the codebase used for GW1. We did not start over, or anything crazy, but nor did we use the GW1 code unchanged.

Huge chunks of gameplay code were added, removed, or refactored so heavily as to be effectively-new (even things you might think would be the same, like inventory). The core rendering and networking capabilities had some significant reworking to support new features, but a lot of the fundamentals remained the same. The very low-level stuff, such as the classes we use to manage collections of data, do math, sort things... those didn't change much and some files might even be identical to the ones in GW1, except maybe for some copyright or header date changes.Essentially if you view the code as a vertical stack of functionality, with very-game-specific gameplay code at the top and generic data structure/algorithm stuff at the bottom, the closer something is to the top the more likely it experienced significant tweaking at some point during GW2's development.

To address the specific topic of this thread (dying stuff)... what I recall (so I might be wrong) is that the decision to dye armor but not weapons was a design one (in the sense we chose to do it, not that there were insurmountable technical issues), and made pretty early. We wanted a much richer dye system for GW2 than we had in GW1. This would require some changes to the way that the source art was authored, which increased the complexity (and thus time) of doing so. That additional complexity pays off best for armor, which is more visible on-screen than weapons generally are, and so (I think) it was decided that we wouldn't bother authoring dye support into the weapon art. Eventually this decision would have led to code changes or optimization relying on that assumption, and we arrive at where we are today.

As with all things, it could be made possible to dye weapons with sufficient code and art resources sunk into it. But it would be a nontrivial undertaking (and probably a non-trivial patch download!) tore-author all the existing source art with appropriate metadata for dye channels.(Please keep in mind that all of this is from memory from a longtime ago, so I may be forgetting/misremembering/et cetera some things.)

Tldr: it would require an immense amount of work on a very old code designed not to have it and need a monster patch 

And this quote is from long ago, so there's way more work involved now. 

[Peter.3901]

Some weapons would look awesome, but can't imagine the work involved to remake all of them to fit this functionality. 

[Mic.1897]

Would rather the resources be spent elsewhere tbh

[Freya.9075]

Ah, yes. I’ve always wanted a green and yellow super weapon. Oh wait

[Fuchslein.8639]

But then they couldn't do so many Sets who Look almost identical besides the colors and effects. How dare you ask anet to make an effort.