Darn it
For a game that will automatically tell you you’ve already unlocked a dye, you’d think it wouldn’t let you consume a recipe with a character that doesn’t know that particular craft. Oddly, it does. Maybe this is harder to code than the dye check? Can anyone from Anet enlighten us?
OP, you might want to change your subject, to what this thread is actually about.
Go back to the Legendary Npc. There you can buy your unlock recipes with karma and with some gold. No need to go through support.
Go back to the Legendary Npc. There you can buy your unlock recipes with karma and with some gold. No need to go through support.
True and it’s not like 5 gold is that much, but, I don’t want to pay it, twice. This system is flawed and has needed fixing since the game came out. Would it really be so hard to code it so that when you open a recipe it goes to the toon that has the ability to use it? or simply fix it so that the recipe can’t be opened until it can be used? This isn’t a new complaint it’s something that should have been addressed long ago.
It’s time that they make all recipes account bound, i.e., they unlock on all your characters when you double click them.
It’s time that they make all recipes account bound, i.e., they unlock on all your characters when you double click them.
So true
What got me was the fact these boxes contain recipes, so I expected there to be recipes like that can be purchased from the TP or from karma vendors for certain things, but no, it automatically adds these recipes to the char you open the box on( Yes, I made the same mistake as the OP).
What got me was the fact these boxes contain recipes, so I expected there to be recipes like that can be purchased from the TP or from karma vendors for certain things, but no, it automatically adds these recipes to the char you open the box on( Yes, I made the same mistake as the OP).
Contact support. They can often (but not always) assist folks via a customer support ticket.
Go back to the Legendary Npc. There you can buy your unlock recipes with karma and with some gold. No need to go through support.
True and it’s not like 5 gold is that much, but, I don’t want to pay it, twice. This system is flawed and has needed fixing since the game came out. Would it really be so hard to code it so that when you open a recipe it goes to the toon that has the ability to use it? or simply fix it so that the recipe can’t be opened until it can be used? This isn’t a new complaint it’s something that should have been addressed long ago.
The system isn’t flawed. This was user error. If anything the system penalizes user error.
It hasn’t been addressed because, honestly, it’s the user’s fault when they use the item on the wrong character. They gave you a very cheap way to rectify the mistake that you made.
Pesonally I don’t like calls to idiot-proof things to the degree you’re asking for. What if I want to use the item on a character that doesn’t currently have weaponsmithing? What if I was planning to do the collection first, and pick up weaponsmithing after? What if I just wanted to consume to item (as I did) so that I can make gifts on my main, and then buy a second one for my weaponsmith to make the final item after I’ve made all the material components on that main, who happens to have huntsman leveled in stead?
It’s fine as it is. You made a mistake. You pay a very minor penalty for your lack of attention.
Attempts to completely idiot proof the game lead to stuff like having to click extra buttons every time I want to buy certain items, salvage certain rarities, force people to pick up very specific items or methods of play, and in general are a bigger waste of time than the benefit they pay out, as they only benefit inattentive and mistake prone players.
I’d rather the game run efficiently and let me make decisions and mistakes than hold my hand and bombard me with confirmation boxes and forced decisions to safeguard me from myself.
I’m an adult. I can own my mistakes if I make them.
Writer/Director – Quaggan Quest
https://www.youtube.com/watch?v=ky2TGPmMPeQ
Support fixed it for me, thanks CS.