d2jsp
Log InRegister
d2jsp Forums > Diablo II > Archives > Softcore USWest 2011-13 >
Service
> Associate I Am Not Disappointed In You > No One Will Get A Refund!!!
1235Next
Closed New Topic
Member
Posts: 20,016
Joined: Jul 18 2005
Gold: Locked
Trader: Scammer
Warn: 60%
Sep 8 2011 10:30pm
No one will get a refund unless you can prove who switched the 08 Valk... This is the very reason I always named my items and kept control of the name. As you all know I quit D2 and gave control of the name to one of Jsp most trusted users Mickey Aka Temptress.. Talk all the shit about my items you want but nothing of mine ever poofed.. :)
1. Legit: An item is legit, by definition, if it has never been duped. It is an entirely unique, one-of-a-kind item with its very own item code (more on item codes later).

2. Perm: An item is perm, by definition, if it has been duped without an item code. In general, the only way this is possible is if the item was duped no later than the 1.09 patch. Starting with 1.10, Blizzard implemented item codes (again, more on this later). The exception to this rule is the duping of "virgin bases." If a white (normal) item is duped without ever having been made into a runeword, it will be perm. This is because only rare, magic, unique, and runeword items have item codes. If an item is made into a runeword and later cleared out with a hel rune, it still has an item code.

3. Item Code: Implemented by Blizzard in the 1.10 patch. Any items duped now will have identical item codes. Whenever 2 items with the same item code are in the same game (I believe it can even be on the same ip), they "clash" and "poof." This makes it impossible to perm dupe without altering item codes (some say certain sites can do this allowing them to perm dupe, I personally have no idea if this is true or not). Any item that was perm receives an item code identical to the new item and thus becomes unperm if it is duped. When clashing an item, you are attempting to find an unperm of the same item code, not merely the same name. Some people don't understand this very well, so here is an example:

In 1.09, a valk is duped. There are 5 copies, Valk A, Valk B, Valk C, Valk D, and Valk E. Valks A, B, C, and E are duped in patch 1.10. They are now unperm. Valk D, while still being a dupe, is not unperm because it does not have an item code that has any duplicates. Alternatively, the possessor of a duped "Valk A" might think their valk is, in fact, perm. They clash it against known unperm copies of Valks B, C, and E without any poofing. They need to clash it against another "Valk A" inorder to poof it.

Now multiply the number of post .09-duped valks, add the fact that you don't know which is which, and you will see why clash testing will never truly be effective in ascertaining an item's validity.
I would like to add that item codes are entirely different from item levels(ilvl), and there is no way to see an item's item code.
Member
Posts: 5,679
Joined: Dec 19 2007
Gold: 2,344.00
Sep 8 2011 10:31pm
Quote (TheChosen @ Sep 9 2011 04:30am)
No one will get a refund unless you can prove who switched the 08 Valk... This is the very reason I always named my items and kept control of the name. As you all know I quit D2 and gave control of the name to one of Jsp most trusted users Mickey Aka Temptress.. Talk all the shit about my items you want but nothing of mine ever poofed.. :)
1. Legit: An item is legit, by definition, if it has never been duped. It is an entirely unique, one-of-a-kind item with its very own item code (more on item codes later).

2. Perm: An item is perm, by definition, if it has been duped without an item code. In general, the only way this is possible is if the item was duped no later than the 1.09 patch. Starting with 1.10, Blizzard implemented item codes (again, more on this later). The exception to this rule is the duping of "virgin bases." If a white (normal) item is duped without ever having been made into a runeword, it will be perm. This is because only rare, magic, unique, and runeword items have item codes. If an item is made into a runeword and later cleared out with a hel rune, it still has an item code.

3. Item Code: Implemented by Blizzard in the 1.10 patch. Any items duped now will have identical item codes. Whenever 2 items with the same item code are in the same game (I believe it can even be on the same ip), they "clash" and "poof." This makes it impossible to perm dupe without altering item codes (some say certain sites can do this allowing them to perm dupe, I personally have no idea if this is true or not). Any item that was perm receives an item code identical to the new item and thus becomes unperm if it is duped. When clashing an item, you are attempting to find an unperm of the same item code, not merely the same name. Some people don't understand this very well, so here is an example:

In 1.09, a valk is duped. There are 5 copies, Valk A, Valk B, Valk C, Valk D, and Valk E. Valks A, B, C, and E are duped in patch 1.10. They are now unperm. Valk D, while still being a dupe, is not unperm because it does not have an item code that has any duplicates. Alternatively, the possessor of a duped "Valk A" might think their valk is, in fact, perm. They clash it against known unperm copies of Valks B, C, and E without any poofing. They need to clash it against another "Valk A" inorder to poof it.

Now multiply the number of post .09-duped valks, add the fact that you don't know which is which, and you will see why clash testing will never truly be effective in ascertaining an item's validity.
I would like to add that item codes are entirely different from item levels(ilvl), and there is no way to see an item's item code.


i really wish i could sit here an read all of this but.
:wacko:
Member
Posts: 21,350
Joined: Mar 9 2008
Gold: Locked
Trader: Scammer
Warn: 70%
Sep 8 2011 10:32pm
:(
Member
Posts: 30,384
Joined: Jan 29 2008
Gold: 10,921.27
Sep 8 2011 10:32pm
unless no one switched it...

it is possible that it was a VERY rare copy of the 08 valk, so whoever had it, any of the 3, or all of the 3, assumed it was perm considering it passed considerable clashes and games....

i understand that doesnt prove anything, but when people want to believe someone and have a little bit of evidence, they jump on it.
Member
Posts: 20,016
Joined: Jul 18 2005
Gold: Locked
Trader: Scammer
Warn: 60%
Sep 8 2011 10:32pm
Here not so much to read:

In 1.09, a valk is duped. There are 5 copies, Valk A, Valk B, Valk C, Valk D, and Valk E. Valks A, B, C, and E are duped in patch 1.10. They are now unperm. Valk D, while still being a dupe, is not unperm because it does not have an item code that has any duplicates. Alternatively, the possessor of a duped "Valk A" might think their valk is, in fact, perm. They clash it against known unperm copies of Valks B, C, and E without any poofing. They need to clash it against another "Valk A" inorder to poof it.

Now multiply the number of post .09-duped valks, add the fact that you don't know which is which, and you will see why clash testing will never truly be effective in ascertaining an item's validity.
I would like to add that item codes are entirely different from item levels(ilvl), and there is no way to see an item's item code.

Member
Posts: 38,544
Joined: Oct 25 2008
Gold: 300.00
Sep 8 2011 10:33pm
Quote (TheChosen @ Sep 8 2011 09:30pm)
No one will get a refund unless you can prove who switched the 08 Valk... This is the very reason I always named my items and kept control of the name. As you all know I quit D2 and gave control of the name to one of Jsp most trusted users Mickey Aka Temptress.. Talk all the shit about my items you want but nothing of mine ever poofed.. :)
1. Legit: An item is legit, by definition, if it has never been duped. It is an entirely unique, one-of-a-kind item with its very own item code (more on item codes later).

2. Perm: An item is perm, by definition, if it has been duped without an item code. In general, the only way this is possible is if the item was duped no later than the 1.09 patch. Starting with 1.10, Blizzard implemented item codes (again, more on this later). The exception to this rule is the duping of "virgin bases." If a white (normal) item is duped without ever having been made into a runeword, it will be perm. This is because only rare, magic, unique, and runeword items have item codes. If an item is made into a runeword and later cleared out with a hel rune, it still has an item code.

3. Item Code: Implemented by Blizzard in the 1.10 patch. Any items duped now will have identical item codes. Whenever 2 items with the same item code are in the same game (I believe it can even be on the same ip), they "clash" and "poof." This makes it impossible to perm dupe without altering item codes (some say certain sites can do this allowing them to perm dupe, I personally have no idea if this is true or not). Any item that was perm receives an item code identical to the new item and thus becomes unperm if it is duped. When clashing an item, you are attempting to find an unperm of the same item code, not merely the same name. Some people don't understand this very well, so here is an example:

In 1.09, a valk is duped. There are 5 copies, Valk A, Valk B, Valk C, Valk D, and Valk E. Valks A, B, C, and E are duped in patch 1.10. They are now unperm. Valk D, while still being a dupe, is not unperm because it does not have an item code that has any duplicates. Alternatively, the possessor of a duped "Valk A" might think their valk is, in fact, perm. They clash it against known unperm copies of Valks B, C, and E without any poofing. They need to clash it against another "Valk A" inorder to poof it.

Now multiply the number of post .09-duped valks, add the fact that you don't know which is which, and you will see why clash testing will never truly be effective in ascertaining an item's validity.
I would like to add that item codes are entirely different from item levels(ilvl), and there is no way to see an item's item code.


<3 Tom
Member
Posts: 34,362
Joined: Feb 8 2009
Gold: 0.00
Sep 8 2011 10:33pm
zzz whyd u have to use the same title tom

:rofl:
Member
Posts: 6,725
Joined: Jul 2 2009
Gold: Locked
Sep 8 2011 10:33pm
Member
Posts: 5,679
Joined: Dec 19 2007
Gold: 2,344.00
Sep 8 2011 10:34pm
Quote (TheChosen @ Sep 9 2011 04:32am)
Here not so much to read:

In 1.09, a valk is duped. There are 5 copies, Valk A, Valk B, Valk C, Valk D, and Valk E. Valks A, B, C, and E are duped in patch 1.10. They are now unperm. Valk D, while still being a dupe, is not unperm because it does not have an item code that has any duplicates. Alternatively, the possessor of a duped "Valk A" might think their valk is, in fact, perm. They clash it against known unperm copies of Valks B, C, and E without any poofing. They need to clash it against another "Valk A" inorder to poof it.

Now multiply the number of post .09-duped valks, add the fact that you don't know which is which, and you will see why clash testing will never truly be effective in ascertaining an item's validity.
I would like to add that item codes are entirely different from item levels(ilvl), and there is no way to see an item's item code.


i know your most likey right im just wayyyy to ADHD to read that.
Banned
Posts: 2,031
Joined: Jul 14 2011
Gold: 0.00
Warn: 50%
Sep 8 2011 10:34pm
heres my view

clash testing cannot prove an item to be perm, it can only prove an item to be unperm :)
Go Back To Softcore USWest 2011-13 Topic List
1235Next
Closed New Topic