I also have noticed an increased drop rate on legendaries. Maybe they patched in an increase in anticipation of the item stat overhaul with legendaries coming. Of course the other part of it is the mob density, but I still did not get this many drops when I was farming ACT 3 before.Did they increase drop rates a shit ton? 3 legendaries in one run through Keeps 2 on MP5... they were all shit, but still.
AH was crazy for the first few hours, I sold a few dozen items for a decent amount more than I had been listing them pre-dupe/patch. Even sold a few $100 items on the RMAH. Since then, it's been back to the normal one or two item sales per day. I did see quite a few really nice items max bidded at 1d/11h on the AH. Pretty obvious that Blizzard did not get all of the gold, and some of those lucky enough to keep their gold grabbed a bunch of items quickly.Sounds like they may have made lemonade out of lemons. I'll definitely be keeping an eye on the AH once they get things sorted out.
Have not noticed any difference. I had three drop within 5 minutes yesterday. Did all of paragon level 96 today on MP8 with none. Streaky RNG is streaky.Did they increase drop rates a shit ton? 3 legendaries in one run through Keeps 2 on MP5... they were all shit, but still.
I'm pretty sure that screenshot was confirmed photoshop. Saw it on a couple other websites but I suppose there is no way to confirm. Someone was calculating how long it would have taken to accumulate that much gold using the dupe + max amount of gold you can sell at once + time it took to dupe = something like 2 months of 24/7 gold duping.Did that dude with like.. 700 trillion gold get away with it?
I just started playing again today and my buddy said he got a suspension for duping 70 billion gold, and got rerolled back, but a lot of people that had 2 accounts trading/selling back and forth got to keep it
Also, I just got my HC WD to Inferno Act 3. I need more dps... only 25k isn't enough![]()
I wonder how long this shit has been going on but was just made public jesus christ, titan is an abortion at best.The error is fairly common computer science error and probably related to game developers being very bad at unit testing their code. The "amountToDeduct" was an unsigned integer. Who's max value is 4,294,967,295. So once they increased the gold limit on the AH the code would go something like this:
The issue, however, is goldToDeduct would max out at the value above. So if you put up a value greater than ~4.3b it would list the maximum amount you put up but only deduct the value of the maximum unsigned integer value. And then once you cancel it it would refund you the correct amount you put up and add it to your gold amount but the deduction would still be less than what you listed. In essence giving you free gold.
I'm pretty sure it's been only this patch, since until then the gold limit was far below that.I wonder how long this shit has been going on but was just made public jesus christ, titan is an abortion at best.
I work at a giant corporation, nothing related to copypasta surprises me anymore.I'm amazed at how many of you think they would keep redesigning the wheel and rewriting functions time after time and not just copy what they had before.
While I wouldn't expect much pre-Y2K code being out there, you would be surprised how much code from early 2000s is still being copypastad.
For how much RAM you'd expect a computer to be running Diablo3 to have I was also a bit shocked that they used a uint16. Not like this is 1990 where you need to be really careful to use the smallest data type possible.I'm fairly certain no programmer would just use an unsigned integer... ever...
At work we use uint8_t, uint16_t... uint64_t.
If they didn't use a 64-bit unsigned integer I wonder how they even made it to working for Blizzard. Max value of a UINT64 is 0xFFFF FFFF FFFF FFFF or 18,446,744,073,709,551,615
Even using a 32-bit number would be infinitely better. But a 16-bit unsigned integer.. I am saddened.