*** The Official Diablo III Thread ***

Status
Not open for further replies.
I was bored so went and soloed diablo on Normal difficulty and he didn't drop any rares???

My friend said if you've already killed a boss they wont drop rares again. wtf!?

Whole point of diablo is boss runs for items!??!

Can anyone clear this up?

I believe thats only for normal difficulty and obviously character specific.

Someone from the Blizz forums:

I have definitely gotten more rares (yellow) from purple and yellow enemies compared to bosses. Maybe 15 or so, on normal, and I have yet to finish Act 3.

This is how Blizzard want farming to work. You aren't guaranteed ANY rare mobs (purple or yellow) when you start an area, and as they drop better loot than bosses, THOSE are the ones you want to hunt down. So because they aren't guaranteed them, farming becomes more of a farm as you aren't just killing the same boss over and over. Instead, you have to wipe and entire area over and over, which actually makes grinding more fun in a way, as you're not just killing the same enemy the same way over and over.

It adds a new variable - random generation of mobs AND gear, as opposed to just random generation of gear like in D2, where the best stuff dropped from bosses.

Getting only blues is normal. Rare items should be rare, and they are, relatively. Brown (Legendary) should drop once in a blue moon, else why call them Legendary?
 
Doesn't work. =[

And their are like 3 different diablo IP's, how do I know which run to trace?

For example it would be "tracert 1.2.3.4", replace the 1.2.3.4 for the IP in the netstat output, I am in a course at the moment so I can't check what IP it is specifically, but just try all 3 for now.

If you are still having issues, I'll be home at about 18:00 - 18:30 time and I can jump on to mumble or skype or something and talk you through it.
 
I was bored so went and soloed diablo on Normal difficulty and he didn't drop any rares???

My friend said if you've already killed a boss they wont drop rares again. wtf!?

Whole point of diablo is boss runs for items!??!

Can anyone clear this up?

Bosses drop less loot if you've already killed them. And the mechanics of the game have been fixed to make it that just hitting bosses over and over isn't the most efficient way of getting loot, Elites and champions are.

When you hit 60, you get the Nephalem Valor buff from champs and elites, which will give you huge MF bonuses. Then bosses come back into play for good loot. :p
 
How to use tracert:

C:\>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

So just tracert <ip> is fine
 
Just woke up as I played until 5AM this morning. I think I'll help myself to another all-day session! Glad I booked this week off work :)

My first Diablo game and didn't expect to enjoy it this much. I find it's like League of Legends, but PvE and not PvP lol. Not the same type of games but you pick a char with a role, click all over the place, kill minions and you have abilities you pick up as you go. Plus miccing it with your mates of course.
 
Last edited:
For some reason I seem to remember that blizzard went through a period of blocking pings to their WoW servers, it could be that they are blocking it, should be getting a partial map of the route though I would guess.
 
Anyone else's wife/girlfriend getting hacked off with the playing time? I'm getting proper grumpy looks when I slink off to my man cave on an evening.

Met my wife in wow and had a honeymoon to blizzcon :)

The only grumpy look i get is when i have better loot :P
 
The one under 'Foreign address'.

I think that's the right one to try, but I've never done this before. :p

Ok so running "netstat -b" should give some output like this:

Code:
 [diablo3.exe]
  TCP    [I]X.X.X.X[/I]:4321    [B]Y.Y.Y.Y[/B]:1234      ESTABLISHED

You want the Y.Y.Y.Y bit, ignore the colon and the port numbers after it.
 
Ok so running "netstat -b" should give some output like this:

Code:
 [diablo3.exe]
  TCP    [I]X.X.X.X[/I]:4321    [B]Y.Y.Y.Y[/B]:1234      ESTABLISHED

You want the Y.Y.Y.Y bit, ignore the colon and the port numbers after it.

Cheers. Doing my head in now, I'm running C:\>tracert XXXXXX and it's saying the command isn't recognised. :(
 
Cheers. Doing my head in now, I'm running C:\>tracert XXXXXX and it's saying the command isn't recognised. :(

Copy / paste your netstat results for the Diablo III servers in here. Don't paste everything netstat finds, just the stuff relevant for Diablo III. You're definitely missing something getting all those error messages. We can then type the correct command in here and you can copy / paste it into the command window.
 
Status
Not open for further replies.
Back
Top Bottom