Placing sieges in guild bank
It’s because they are soulbound for technical reasons. The WvW team are aware of this (admittedly low priority) issue, and will get it working eventually.
we are allowed to transfer the sieges using the drop feature
This is unintended and we’re not actually supposed to be able to do.
Expect that to be fixed rather than being given the ability to transfer them through guild bank or other means.
Northern Shiverpeaks
we are allowed to transfer the sieges using the drop feature
This is unintended and we’re not actually supposed to be able to do.
Incorrect. An ANet developer on the WvW team said that it was fully intended as a work-around to the technical limitation that forces the siege plans to be Soulbound currently.
got a source for that?
Northern Shiverpeaks
thanks.
perhaps I missed the relevant bit but that only mentions the technical issue of making the blueprints account bound rather than soulbound.. it doesn’t address whether the “drop bundle” workaround is approved …or what they think of players using it to share blueprints between accounts(as opposed to their desired outcome, which is within an account)
Northern Shiverpeaks
As I heard, the March patch was supposed to add the account bound status to siege blueprints. Yet they are still soulbound and Anet have not told us why this is still the case.
Remember to buy the officially endorsed GW2 Steel Series Keyboard, it supports macros!
WvW, we only care if it affects the servers we play on.
Perfect Dark [PD] – Yaks Bend
Thanks you two for scouring the developer tracker! Both of those definitely answer the questions about whether it is an exploit or not (it isn’t) and whether or not there are technical limitations involved (there are).
awesome, thanks again. I stand corrected.
Northern Shiverpeaks
You’ll be able to Soon™