- 16,715
- 7,731
Diablo 3 - Reaper of Souls
- Thread starter Agenor
- Start date
-
Guest, did you like the last podcast notification?? Well here's the second one, and for the third podcast! Yep. This Thursday 8-8-24 at 7pm Central
Go here to check out his podcast thread for info on topics and links!Go into the FoH discord and find the Happy Time Fun Hour channel and give it a listen!
Zaphid
Trakanon Raider
- 5,862
- 294
I'm playing a devil's advocate here, but it doesn't have to be designed that way, just a product of systems coliding - you have a way for the game to measure how long has it been since your last lego drop, which they said takes into accout a lot of variables, then you have the loot 2.0 making sure items for your class drop ~85% of the time and last but not least, Kadala drops both lvl 70 and lvl 61 versions of items, which would make her work a bit differently compared to your average mob. I can also imagine they spent some time to make sure the loot isn't too random, because they need to give you items to keep you going.
Let's say they bias the loot table toward your weakest slots, doesn't have to be much, just enough to make an upgrade likely enough and the way the item rolls is still random, so you get your fair share of shitty rings.
Dashel
Blackwing Lair Raider
- 1,833
- 2,931
Well it certainly appears testable. I also dont think anything he's saying is crazy. Reduce the pool of items as much as possible by item level, make sure what you want is in your "random" table, gamble on them. Do you really generate a random table every game? *shrug*
Dashel
Blackwing Lair Raider
- 1,833
- 2,931
But I don't think they bias towards your weakest slot. Because that is the whole point of Kadala. They've said she is the person you go to if you haven't gotten a boot upgrade. Not to mention how would the game determine if this is your "weakest spot." Damage/toughness/healing are all worthless metrics so if they're using that to figure out where you suck at it is flawed logic as it is. I just don't understand why it wouldn't use the most basic of RNG formulas where it: rolls for slot, rolls for rarity. If rare or magic then roll for affix(s)/suffix(s) [with loot 2.0 bias] then roll for range. If legendary roll for which item [again, with loot2.0 bias], roll the fixed stats [loot2.0 bias], roll the random stats [again, loot2.0 bias.]
It is, by far, the simplest and easiest solution. I know that engineering wouldn't allow it to be quite that simple but it isn't too far off from how Marvel Heroes implemented their RNG.
Sir Funk
Molten Core Raider
- 1,251
- 155
Right, but I want to be able to see all of the legendaries from level 11-X that you would be competing with at a given level.
- 16,715
- 7,731
The simplest answer to why it might be complicated is that the game was built from the ground up in a stupid manner and reprogramming it would be a nightmare. Would any of you doubt Jay Wilson came up with this stupid idea?
Also, network communication might be at play here. The less talk there is going on between server and client the better. You've seen how much client-side lag is created just from someone IDing a few things. Think how much loot the game drops now, and how much it used to drop. Imagine the millions of requests per minute "can I drop this?" because the server has the drop table for that game, not the client. Hmmmm, now to boot up a hex editor and find out where the loot table is stored locally...
Console might be the reason why they had to restrict the size of the drop table, even if it is local.
Heh, the clock thing. I was honestly thinking about this the other day. Does anyone remember when the AH/RMAH first came out? You could set your computer's clock ahead a certain amount of time to lock people out of an auction/end it early because it would check local time and not server time.
When they mentioned the 2.5 hour "safety net" for playing, I was wondering about that- if you could just set your computer clock ahead and instantly get legos each time. This would let you get legs instantly and check your "loot table" and actually back up what the guy was saying.
Zaphid
Trakanon Raider
- 5,862
- 294
Or it would go the other way around - the server tells the client "drop this" based on the data it has. Trusting the client with a loot table before 2.0 would be boneheaded. I'm also fairly certain I haven't seen items when I'm lagging.
I assume much of the game was re-programmed and re-engineered with the move to RoS/2.0. With the amount of people playing this game if your client had access to the loot table I don't see how someone wouldn't have sniffed it out of the RAM by now. I guess in a paper-thin defense of client-side loot tables is I've seen, many times, a monster drop an item. The item's graphic is appropriate but the rarity/name/affix+suffix haven't been loaded yet. I would assume this is your client rolling on "Ok drop an axe" then saying "hey server what should these stats be?" accounting for the delay.
I should also note I don't see how this couldn't be exploitable. Just hack the ram space so it just constantly sends "Drop a sword, drop a sword, drop a sword" .... although maybe that is the guy's "special sauce"
I should also note I don't see how this couldn't be exploitable. Just hack the ram space so it just constantly sends "Drop a sword, drop a sword, drop a sword" .... although maybe that is the guy's "special sauce"
*shrug* Attach Fiddler and look at the stuff. Maybe I'll do that tonight just for the hell of it.
Amzin
Lord Nagafen Raider
- 2,917
- 361
So much more is determined on the server side of things with D3, it might be hard to separate that out if the loot table and all are server side as well.
What he said makes sense in a way. It also supports the pattern people were seeing with gambling streaks, although they were saying it was across characters in a game as opposed to just your own character. It should only take a few minutes to get a character up to 11 or so to test this with moonlight ward (although, 20 shards per gamble is an issue). I may be able to try this out sometime but have to farm shards up first, just been dicking around with bounties for a week.
What he said makes sense in a way. It also supports the pattern people were seeing with gambling streaks, although they were saying it was across characters in a game as opposed to just your own character. It should only take a few minutes to get a character up to 11 or so to test this with moonlight ward (although, 20 shards per gamble is an issue). I may be able to try this out sometime but have to farm shards up first, just been dicking around with bounties for a week.
Nola
Trakanon Raider
- 2,983
- 1,427
Errrr.. I'm not biting this. So if a Blade of Prophecy drops and it has shit stats that means I can go to Kadala, gamble away and probably get another one with better or worse stats.
- 5,591
- 19,038
we don't even know if the items he's dropping on the ground are 70 or low level. It would be failry easy to farm those with multi boxing wizards (whcih he admited to doing) in low level games where you restrict the possible loot options. But it's quite a leap to get to 'there is a loot table generated every game for your character and you can use loot limiting to determine what it is'. he has so far not proven that. If all those items are 70 then i'd be willing to say it's possible he's on to the something, but he needs to show a lot more proof, and i'm not talking about doctored up images here =p
That's a good call. He's got 8 Moonlight Wards on his profile page, but only one of them is level 70. 2 are level 60, 1 is level 18 and 4 are level 13.