The Ring of Royal Grandeur (armory) has become the most sought after item in Diablo 3, as its legendary affix is basically mandatory for all end game gearing decisions, given the power of partial Item Set bonuses. The hard part is finding one, as it’s one of the five legendary items that can only be obtained from Act One Horadric Caches. This is good in a way, as it’s the sole remaining item/profit-based reason players have to do *anything* other than RiftRiftRift. (Given the game’s design direction in recent months, I’m frankly surprised the RoRG hasn’t been turned into a Greater Rift Guardian drop.)
Most players hunt RoRGs with brute force, by grinding hundreds of Act One bounties as quickly as possible, which usually means split-farming on Normal difficulty. That’ll work, eventually, but is there a better way? A user in our Diablo 3 community forum named Horadrimm says yes, there’s a trick to it, by following a method players are calling the “Junger Rules.” Quote:
I got 5 RORGS with very minimal effort and so can you!!
How it works: The game has a pity timer, meaning that if you don’t get a legendary within an hour or so it drops one for you automatically. The goal the aforementioned method of farming is to ensure that pity drop is in your horadric cache and not in the world.
What to do:
Do not kill any mobs except those required for objectives. Do not kill goblins. Do not open chests including resplendent chests. Do not destroy breakables (pots, barrels, looting bodies etc). Do not pop fortune shrines. Do not kill mobs from required cursed chest and shrine event objectives until the timer has run out.
Avoiding a legendary drop in the world increases the chance the pity timer drops one in your cache.
First off, the guy who invented this was apparently named Junger, so now it’s called the “Junger Rules.” Which is fine, but how the hell did they avoid the obvious pun and call it the “Junger Games?” So that’s what I’m calling it, since I’m all about obvious puns.
As for the technique, the theory is that since the game has a “pity timer” that increases your chances of finding a legendary item the longer you go without finding one, you can exploit this by obtaining a Horadric Cache after not finding any Legendaries for some time. Hence not killing Goblins, not opening golden chests, avoiding random Elites, etc. This is a sacrifice since it’ll lower your total legendaries found, but boost your chances of finding that all-important RoRG.
Does it work? Some players swear it does, others say it doesn’t. And thus we’re plunged back into the conspiracy theories that are inevitably spawned by item hunting in a game where we don’t know exactly how item drops work. I think the principle is sound, as the pity timer is real, but I’m not at all sure the stated rules are how it should be done.
First of all, we don’t know when items in a Horadric Cache are determined. The Junger Gamers say the legendary pity timer works when you find the Cache, but that seems contrary to what we know about how Horadric Caches determine their item drops. Remember early in RoS, when players were storing Caches up in Normal and opening them on Torment 6? That was a real exploit, easily observed since it caused Imperial Gems to drop from Caches found in Normal. (Which made it seem that items in Caches were determined when the Cache was opened. NOT when it was found.)
Blizzard confirmed that exploit by hotfixing it and adding an internal tag to unopened Caches that tracked what difficulty level they were found on, and the level of the character that farmed them. (So if you find bags with a lvl 70 and open with a lvl 60, all the items will be lvl 70.) Bliz later expanded on that in Patch 2.0.5 when they boosted the chances for legendary items to drop from Caches found on Torment 2 and higher.
Furthermore, Bliz recently confirmed that items from Caches roll their smart drop according to the class of the character that opens the cache. It doesn’t matter who farms the cache in terms of what items drop. That matches my experience and testing as well, as I once farmed a bunch of caches with my DH and my Barb, and then opened them with a WD and got almost all INT gear, plus several Witch Doctor-restricted items.
Legendary Gems were first officially revealed in the Patch 2.1 preview blog back in June of this year. They will be added to Reaper of Souls in Patch 2.1, and are currently undergoing testing on the PTR.
The gems add special bonuses when socketed in rings and amulets (only on Characters and not on Followers), and can be upgraded in power via Urshi, the NPC who appears after Greater Rifts are cleared.
While the developers are calling them “legendary gems” these socketables have nothing in common with regular gems in stats or appearance, and are more analogous to the Rainbow Facet unique jewels of Diablo 2. The main difference in Diablo 3 is that these gems can only be socketed in jewelry, and the way the gems can be upgraded to improve their functions over time.
Legendary Gems Listing
While the Legendary Gems are still undergoing development on the PTR, their stats and bonuses are changing constantly. A major revision was created on July 15, 2014 with new or upgraded stats for almost every gem. The following are the most current details about Legendary Gems.
|Bane of the Powerful|
|Bane of the Trapped|
|Boon of the Hoarder|
|Bliz Note: As was discussed in another thread, allowing this this gem to rank up to +100% pet Crit would likely cause undesired gearing issues and probably be a little out of line.|
|Gem of Efficacious Toxin|
|Gogok of Swiftness|
|Mirinae, Teardrop of Starweaver|
- Socketing Tiamat's Rebuke, Baranar's Star
- Etdlahq Memorial Bar - your shelter from forum…
- Common Core
- The Noodle Compound Bed and Breakfast
- Act 1 Bounties
- Heavens fury and Crit/no Crit
- Walk before you can Crawl(ers): Ray of Frost bug
- RoS: How are you Wizards doing?
- List of PK's
- Tournament: Envious of the Green and Gold
Blizzard is Battling Botters Every DayPosted 22 Nov 2012 by
As we said in the article yesterday, the issue of botting in Diablo 3 seems to be coming to something of a head. Perhaps at least partially spurred by our article, one of the Blizzard CMs finally replied to some botting threads on Wednesday. Mostly they replied by saying “this is not the thread you’re looking for,” and by signing off for the holiday weekend, but in one thread there is an official statement, of sorts.
It’s long and attempts to reassure. Here’s an excerpt, you can read the whole thing if you click through.
It’s something we take very seriously, though. Our developers, support staff, and anti-hack teams are all busting their butts to ensure that your online experience is as free of cheats, hacks, and bots as possible. From the development side, we look at ways to reduce the effects of exploitative behavior on the community and/or prevent certain programs from working outright. This trick here is to make sure that whatever we do doesn’t negatively impact legitimate players, which is actually a very fine tightrope to walk (you saw the complications of that whenever we introduced game limiting)…
The reality to all of this, though, is that even though we devote considerable time, effort, and heart to removing bad behavior from the game, there will always be individuals who excel at coming up with new ways of getting around the roadblocks we put up.
…we have done many things to deter botting and remove those who are botting from the game environment. From the development side — just to name a few things — we’ve implemented game limits and AH limits. We’ve painstakingly removed exploitable monsters, chests, events, and locations, or made adjustments to them so that they would not benefit botters. And we continue to add layers to our reporting systems (I’ll pass on your feedback about adding more, though). On top of that, we have meetings each week with the development team to discuss what more we can do to help prevent this kind behavior (like I said previously, though, most solutions would negatively impact legitimate players…for example, CAPTCHA). From the anti-hack side, we monitor for bad behavior around the clock, and we routinely issue ban waves for verified cases of botting. We’ve also brought legal action against several companies who develop these types of programs.
So, are the botters just that clever, or do you still feel that Blizzard’s security is indifferent and/or incompetent? Or consider this — what if Blizzard’s security measures are amazing, and they’re stopping 95% of would be botters/hackers/dupers/etc. So it’s only a small percent that gets through, but we see those and complain. Perhaps we’re living like the Hobbits in the Shire during the long years before the Return of the King, with our borders protected by unseen ranger guardians we can’t even imagine!
Yes, it’s fun to pretend.
The full post.
Hi guys, I also realise the botting issue is becoming a little out of control. A friend of mine quit playing last night because he is sick of runing into bots all the time, before he quit he gave me all his gears
I was thinking if we could start a movement where all the legit players go play on a pubic game for 15 minutes every time they log into the game and actively report a few botters to blizzard, hoepfully it’ll get billizzard’s attention and reduce the severity of this situation.
Lylirra: An important thing to keep in mind is that we don’t make public announcements every time we action players for cheating, and the reason for this is that we are constantly removing this kind of exploitative behavior from the game — on a weekly basis, sometimes even on daily basis. Public announcements would become tedious if we decided to make one every single time we banned someone for using a bot, a hack, or some other kind of cheat. Instead, we usually will post something whenever we issue a big wave, or whenever we feel like we need to remind players that exploitative behavior is not okay and can lead to a permanent ban from Diablo III.
It’s something we take very seriously, though. Our developers, support staff, and anti-hack teams are all busting their butts to ensure that your online experience is as free of cheats, hacks, and bots as possible. From the development side, we look at ways to reduce the effects of exploitative behavior on the community and/or prevent certain programs from working outright. This trick here is to make sure that whatever we do doesn’t negatively impact legitimate players, which is actually a very fine tightrope to walk (you saw the complications of that whenever we introduced game limiting). From the support side, we make sure that your in-game reports reach our anti-hacks teams. And from the anti-hack side, we take action on players that we are able to confirm to be maliciously exploiting the game, be it through botting or other forms of cheating.
The reality to all of this, though, is that even though we devote considerable time, effort, and heart to removing bad behavior from the game, there will always be individuals who excel at coming up with new ways of getting around the roadblocks we put up. So, it’s a constant battle, but one that we’re willing to fight. If you want to pitch in, you can; the easiest way to do so is by emailing firstname.lastname@example.org or submitting a report through our webform.
And, just for clarity, let me repeat:
- Exploitative behavior is not okay (this includes botting).
- If you are found to be exploiting the game, you can be permanently banned.
- Source: https://us.battle.net/support/en/article/diablo-iii-exploitation-policy
Btw as i read on some bot forum (am not botting just like to read the ban reports:) ) the last public statement called “diablo players banned” was about people using maphack and that zoom out thingy not a massive bot banwave.
Lylirra: It included, but certainly was not limited to, that particular type of behavior. We called it out specifically in the announcement, so it’s nothing new.
Lylirra is one of the only really respected blues, but her response to botting (which I am sure is primarily scripted from management) is extremely weak. Botters and spammers have run rampant since week 1 and from what not only I can tell, but the majority of community as well, is that Blizzard has done very little to actually control, or eliminate them
Lylirra: Not scripted. Not from management. What I wrote is based on my own experiences working at this company for over 6 years. I know almost each and every member of our anti-hack team personally, and I can speak first-hand as to how seriously they treat their role. They work long hours, they invest themselves completely, and they rarely get any praise for what they do because their job is never done.
Yesterday, I spoke with one of the guys on the team for over an hour about how difficult and frustrating it is to keep up with all the different ways that players want to exploit the game. You find a certain kind of automation program and get rid of it, another pops up in its place, and now it’s even harder to detect. Or you know that some players are using a particular type of bot based on intuition and experience on the job, but you can’t prove it beyond a shadow of a doubt. Permanently banning a Diablo III license isn’t something we take lightly, and there’s a lot more that goes into actioning someone for botting than what meets the eye. (Yes, kind of like Transformers, but fortunately with less Shia LeBouf.)
But, to counter your point more specifically, we have done many things to deter botting and remove those who are botting from the game environment. From the development side — just to name a few things — we’ve implemented game limits and AH limits. We’ve painstakingly removed exploitable monsters, chests, events, and locations, or made adjustments to them so that they would not benefit botters. And we continue to add layers to our reporting systems (I’ll pass on your feedback about adding more, though). On top of that, we have meetings each week with the development team to discuss what more we can do to help prevent this kind behavior (like I said previously, though, most solutions would negatively impact legitimate players…for example, CAPTCHA). From the anti-hack side, we monitor for bad behavior around the clock, and we routinely issue ban waves for verified cases of botting. We’ve also brought legal action against several companies who develop these types of programs.
But we agree with you: it’s not enough. Of course, we’re not sure that what we can do will ever be enough (we don’t know if we can eliminate exploitative behavior completely), but we’re willing to try. It’s an ongoing battle, though, not something you win after a couple of quick matches.