| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 5 months |
| seen | Sep 30 '12 at 9:29 | |
| stats | profile views | 1 |
|
Sep 30 |
accepted | Preventing item duplication? |
|
Sep 30 |
comment |
Preventing item duplication? Yes, all items need to be checked that they aren't duplicated. As for your second solution, it wouldn't work well in terms of combating duping. If a new unique ID is set, how would the server tell if the item is duped or not upon pickup? |
|
Sep 30 |
comment |
Preventing item duplication? The way I see it is like this: Each "item" in the stack would need a separate instance to dignify their unique ID. That means, a stack of 5 potions that previously was 1 instance, with an integer of 5 for the quantity, is now 5 instances (somehow all merged into a List). I should also note, items don't automatically gets categorized. I can have one stack of 5 potions, and another stack of 12 potions, with two separate unique IDs. |
|
Sep 30 |
comment |
Preventing item duplication? Because in a stack of items, each item isn't its own instance. It's technically one item, with a quantity (5, in the main post). |
|
Sep 30 |
comment |
Preventing item duplication? I feel like that's the only real solution (albiet, it'll be rough on the server). |
|
Sep 30 |
asked | Preventing item duplication? |
|
Jul 31 |
accepted | Best practice for saving items? |
|
Jul 26 |
revised |
Best practice for saving items? edited tags |
|
Jul 26 |
awarded | Scholar |
|
Jul 26 |
accepted | Figuring out card possibilities for a Scopa card game |
|
Jul 26 |
asked | Best practice for saving items? |
|
Jan 9 |
awarded | Student |
|
Jan 9 |
asked | Figuring out card possibilities for a Scopa card game |