82
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Oct 2023
82 points (97.7% liked)
Games
16737 readers
404 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
Diablo 1 had a duplication bug through its final release and no one was ever "actioned" for exploiting it. Let people have fun with the game FFS.
I'm kind of surprised that, given the history of the series, they didn't make it a point to have atomic transactions.
I mean, it's not as if it's an unsolved problem.
EDIT: Not to mention that I'd have kind of thought that games like this would have a UUID attached to each generated item, to help deal with scammers and the like.
I think they have but the exploit probably also generated a new uuid. (I have no idea how they implemented but I believe they can track down all the items. )
I mean, it sounds like this involved trading.
There should be two types of interactions involving an item.
First, when the item is initially-created, like at drop time, maybe loot boxes, that sort of thing. That should create a UUID, if the game uses them.
Second, when an existing item is transferred. But the transfer code shouldn't involve creating new UUIDs. And the trading code should only be doing item transfers.
And any code transferring an item should be happening only on the server side, and should be atomic.
I could maybe understand someone figuring out some way to get an item to be generated twice, like at drop time.
But duping items when trading means that either probably code authoritative as to world state that shouldn't be on the client is running on the client, or code that should be atomic isn't. And for the latter case, I wouldn't expect the item transfer code to be able to generate new item UUIDs, because it should be running transfer code, not item generation code.