- Forums
- World of Warcraft
- Trade Skills
- Imbued Netherweave Robe Unique?
Imbued Netherweave Robe Unique?Follow
So, I'm wearing an Imbued Netherweave Robe, and try to create another for someone, but it's unique. The other 3 pieces aren't unique, so I'm not sure why this one would be. I don't want to get rid of the one I'm wearing to have to make 2 more to give one away. Anyone else run into this? I don't remember if it's always been that way...
You can do this: Sell the robe you are wearing to a vendor. Quickly make the new robe and trade to another player. Open the vendor buyback window and reclaim your robe.
Just be careful -- an untimely server crash or a disconnect may mean you don't get your original robe back from the vendor.
Just be careful -- an untimely server crash or a disconnect may mean you don't get your original robe back from the vendor.
Thanks Thermalnoise ... that worked. I also got a response back from the GM saying that they were aware of the issue and were looking into ways to fix it. Which essentially tells me that it's a bug, not an intended function.
You would think this is one of those things where it would be easy enough for them to fix after the first person that told them. It's probably a bit on the item that just needs to be flipped and yet it has been this way for entirely too long. It's not a programming issue, it's a simple flag on an object so it can be fixed in a matter of a few minutes. So sad that it has not.
SkibumOnShiva wrote:
You would think this is one of those things where it would be easy enough for them to fix after the first person that told them. It's probably a bit on the item that just needs to be flipped and yet it has been this way for entirely too long. It's not a programming issue, it's a simple flag on an object so it can be fixed in a matter of a few minutes. So sad that it has not.
You seem to be so certain that this is the case. How do you know for certain? ...and how do you know for certain that flipping a flag wouldn't have any other consequences (such as specific code relating to that particular item - or trigger some unwanted result)? Have you actually looked at the code itself? Simple problems do not often have simple solutions, especially in programming.
ohmikeghod the Venerable wrote:
SkibumOnShiva wrote:
You would think this is one of those things where it would be easy enough for them to fix after the first person that told them. It's probably a bit on the item that just needs to be flipped and yet it has been this way for entirely too long. It's not a programming issue, it's a simple flag on an object so it can be fixed in a matter of a few minutes. So sad that it has not.
You seem to be so certain that this is the case. How do you know for certain? ...and how do you know for certain that flipping a flag wouldn't have any other consequences (such as specific code relating to that particular item - or trigger some unwanted result)? Have you actually looked at the code itself? Simple problems do not often have simple solutions, especially in programming.
Flipping a bit would be that simple. I do not know specifically about the programming of this game, but in all of my experience of electronics, logic, and systems, you generally assign both states of a binary function to a single bit. I do not know if I worded that right, but hopefully you get the point. If you have a switch connected to a light, it should be fair to assume that changing the state of the switch would change the state of the light accordingly. In this case, there may be something like a "Is this item unique or not" bit, with case 0 being non-unique, and 1 being unique. Even if it were not this simple, it would have to be this logical, otherwise the changes that *are* made would be nearly impossible.
Well, when I got the email from Blizz telling me their plans to look into I, I didn't really assume that it was a difficult fix, I would guess that it is not. The reality though, is that it's probably on a "hit list" for the developers, and probably WAY down near the bottom.
Quote:
Simple problems do not often have simple solutions, especially in programming.
They do if the programmer is any damn good.
If WoW doesn't use an object-oriented tag system for item properties, then they're more retarded than they appear (which really is saying something).
Quote:
You would think this is one of those things where it would be easy enough for them to fix after the first person that told them. It's probably a bit on the item that just needs to be flipped and yet it has been this way for entirely too long. It's not a programming issue, it's a simple flag on an object so it can be fixed in a matter of a few minutes. So sad that it has not.
While I actually believe that this is the case (the fact is that the game is run by an Oracle database and a bit flag is the most likely case for flagging an item) I also don't think you understand the development process. If developers went all willy nilly and flipped flags any time they saw a problem there would be much bigger issues in the future. Development takes time and process. When you find a bug or a problem you have to open an SCT or SCR or whatever acronym you use for tracking bugs. Then the bug needs to be figured out, a plan to fix the bug needs to be developed, and then finally it needs to be executed. Of course it doesn't stop there because then you would need to test to ensure that the bug fixed the problem and possibly do regression testing to ensure that it didn't break anything else. Even tiny little things like this need to follow a process like that because if they don't then down the line when you are doing more development or fixes for related things, you need to know what has changed. A good comapny will follow their own process for the smallest bugs to the largest, its just stupid not to. So even though it seems and probably is a small change there is still a lot of work involved, and it's not simply flipping a true/false flag.
Quote:
If WoW doesn't use an object-oriented tag system for item properties, then they're more retarded than they appear (which really is saying something).
I don't know for certain how they do things, but my best guess based on what I do know (Oracle backend) is that each item is in a database with all of its specific attributes. That item probably has flags for whatever it is intended to do, for instance a Unique identifier. It wouldn't be object oriented, but rather database oriented. Things like BoE, BoP, Unique, Item Level, and the such are all within the database record for that particular item. So it is safe to assume that flipping a flag would be the fix, but see the aforementioned paragraph for reasons it would take so long.
Edited, Mar 13th 2007 12:46pm by kyansaroo
ohmikeghod wrote:
SkibumOnShiva wrote:
You would think this is one of those things where it would be easy enough for them to fix after the first person that told them. It's probably a bit on the item that just needs to be flipped and yet it has been this way for entirely too long. It's not a programming issue, it's a simple flag on an object so it can be fixed in a matter of a few minutes. So sad that it has not.
You seem to be so certain that this is the case. How do you know for certain? ...and how do you know for certain that flipping a flag wouldn't have any other consequences (such as specific code relating to that particular item - or trigger some unwanted result)? Have you actually looked at the code itself? Simple problems do not often have simple solutions, especially in programming.
This is the best answer I can give you:
TheNuckel wrote:
They do if the programmer is any damn good.
Any program specific code that utilizes individual items should never have been written in the first place and needs to be fixed. I would hope the developers know and adhere to this. Anything that needs to happen to an item will be written in the quest scripts based on item id. This will avoid the unwanted results and allow any use of a particular item to be narrowed rather quickly to determine possible impact.
In the words of Bob the Tomato, sometimes being certain just means highly probable. There is no way I can tell from a players stance that the item is exactly the way they intended the design to be but it is highly probable that as 1) it is allowed to be traded, 2) the item binds on equip - the item should not be labeled as unique.
It would absolutely need testing. I'm not advocating that it should just be changed and implemented immediately.
It's also possible that I'm wrong. Maybe it's a magic robe (pun intended) that once crafted and worn you are then a fashion model that is no longer allowed to create this item for your friends. In that case selling it to a vendor, creating another and then using the buyback feature should cause people to get banned as it is an exploit.
I think it's highly probable that the fix is simple and that the unique flag on the item is unintended. Until proven otherwise I'm certain.
It'll be a case of changing a 1 to a 0 in a database, as mentioned.
The hold-up will almost certainly be beaurocratic in nature. It probably has to go through a whole list of development team meetings and all the changes of this type are scheduled for a meeting in the middle of April when lobster is back on the lunch menu at the meeting agenda.
I doubt that even small changes are made on the basis of one person noticing and having access to the database. Don't forget for consistency even the smallest change has to be rolled out across many server databases in both Europe and US simultaneously. This invariably has to wait for a patch, the notes for which are agreed well in advance.
Why Blizz can't achieve the same consistency in GM rules between US and EU is a mystery, however. For example it is against T&C to scam in the US. You will be investigated, items and gold re-instated and bans and warnings issued. In the EU scamming is simply a part of 'game mechanics' and GMs take no action whatsoever (there are numerous threads in the GM section of the EU official board on this issue).
The hold-up will almost certainly be beaurocratic in nature. It probably has to go through a whole list of development team meetings and all the changes of this type are scheduled for a meeting in the middle of April when lobster is back on the lunch menu at the meeting agenda.
I doubt that even small changes are made on the basis of one person noticing and having access to the database. Don't forget for consistency even the smallest change has to be rolled out across many server databases in both Europe and US simultaneously. This invariably has to wait for a patch, the notes for which are agreed well in advance.
Why Blizz can't achieve the same consistency in GM rules between US and EU is a mystery, however. For example it is against T&C to scam in the US. You will be investigated, items and gold re-instated and bans and warnings issued. In the EU scamming is simply a part of 'game mechanics' and GMs take no action whatsoever (there are numerous threads in the GM section of the EU official board on this issue).
Recent Visitors: 59
All times are in CST
Anonymous Guests (59)
- Forums
- World of Warcraft
- Trade Skills
- Imbued Netherweave Robe Unique?
© 2024 Fanbyte LLC