Skip to content

OS-specific scripts to check if the D3 game server you are connected to is buggy.

License

Notifications You must be signed in to change notification settings

ThreeFx/d3servercheck

Repository files navigation

d3servercheck

Program to check if your D3 is connected to a known good/bad server.

There was a bug in D3 Season 21 (at least on EU) which meant that some servers did not submit player's clears to the D3 leaderboards. This script polls your D3 connections and tells you whether you are connected to a known GOOD or BAD server.

Windows

Enable PowerShell execution

In order to run this script you have to allow local PowerShell scripts to run. To do this: Open a PowerShell as Administrator and then enter:

C:> Set-ExecutionPolicy remotesigned

When prompted if you want to change the policy, enter Y and press enter.

Note: This may be a high risk if you are prone to fishing/social engineering attacks. Do this at your own risk!

Running the program

Both MacOS and Windows

Download a ZIP archive of this repository (top-right "Code", and then "Download ZIP"). Unpack it.

Windows

Then right-click d3servercheck.ps1 and then Run PowerShell script. If you cannot run this script check if you did the previous step correctly.

MacOS

Open a terminal (you should be able to search for "Terminal" in Spotlight), and then navigate to the folder where you unpacked the game. Alternatively navigate to the folder you unpacked in Finder and then use the Top Bar: Finder -> Services -> New Terminal at Folder. Then run the script like this:

./d3servercheck.sh

Both OSes

You do not have to start Diablo 3 before starting this program, it will automatically pick up on the game's connections. When running successfully you should see output like this:

Starting d3servercheck
Read servers
Starting checks
no connection to Blizzard game servers detected   <-- You are either not connected to the Blizzard
no connection to Blizzard game servers detected       servers yet, or you are connected to a server
no connection to Blizzard game servers detected       of unknown status
no connection to Blizzard game servers detected
connections: 192.0.2.1 (GOOD)                     <-- You are connected to a known good server
connections: 192.0.2.1 (GOOD)
connections: 192.0.2.1 (GOOD)
connections: 192.0.2.10 (BAD)                     <-- You are connected to a known bad server
connections: 192.0.2.10 (BAD)
connections: 192.0.2.10 (BAD)
connections: 192.0.2.29 (UNKNOWN)                 <-- You are connected to a server of unknown quality,
connections: 192.0.2.29 (UNKNOWN)                     consider adding it to the list
connections: 192.0.2.29 (UNKNOWN)
connections: 192.0.2.1 (GOOD) 192.0.2.10 (BAD)    <-- You have been connected to both a known good
connections: 192.0.2.1 (GOOD) 192.0.2.10 (BAD)        and known bad server. Wait a few seconds for
connections: 192.0.2.1 (GOOD) 192.0.2.10 (BAD)        the old connections to close

Adding servers

You can add servers by adding their IP and the fact whether they are good or bad to servers.csv. The file is in CSV format, meaning "comma-separated values". To append a new server simply add

<YOUR_SERVER_IP>,good

if the server is good, or

<YOUR_SERVER_IP>,bad

if it is bad.

Contributing

Pull requests and issues are welcome! If you have a problem and/or want to add additional servers to the list please open an issue, or submit a pull request directly.

License

This work is licensed under the GNU GPLv3.

FAQ

What about support for MacOS?

The current script works only for Windows. I don't have a Mac or a BSD-device to test on and I also have exams next week, so I won't be able to support Macs in the near future. Hopefully I won't need to and the bug will be fixed soon. If not pull requests are welcome!

Disclaimer

Diablo is a trademark or registered trademark of Blizzard Entertainment, Inc., in the U.S. and/or other countries.

About

OS-specific scripts to check if the D3 game server you are connected to is buggy.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published