This guide is written by Krkljator.CF

I recommend using Mozilla Firefox for browsing this website.

Introduction

Listchecker (pkp.listchecker) or just LC (as in further text) is very good piece of software which allows playing Warcraft III games (especially DotA) on Battle.net with much lowered or even no delay (in contrast to standard battle.net delay which ranges from about 0.5 to 1.0 second!)

I wrote this tutorial as my big contribution to LC! My intention is to spread LC as much as I can and, of course, help people to configure it and solve all common problems. Hopefully, I will make some new DotA LC hosts! But, if you are beginner (noob) at DotA, please DO NOT host any DotA games. No one wants noob DotA hosts!

I have been using LC for about a year now and it works perfectly as since I first installed it. However, it takes some time to configure, but it is worth of effort. I will explain basic options, although the initial guide by Quan Quach is very helpful for using LC too. So, if you are new to LC, I suggest to read the initial guide first –> Listchecker Part I.


UPDATE [August 18, 2009]

Updates and quick links

Here are some quick links to news and common problems:

(1) New patch - 1.24 (info & download links) - Warden is back

(2) Hosting with LC on Windows 7

(3) Hosting with LC on Windows Vista 64-bit

(4) Solutions for recv server error: error=10054 error

(5a) How to properly configure port forwarding #1

(5b) How to properly configure port forwarding #2

(6) LC freezes at connecting to chosen gateway & alternate addresses of the gateways

(7) Failed to hash WAR3 key error and how to re-encrypt CD-keys

(8) What to do when /findbnet doesn’t work?

(9) Settings for Banlist when it doesn’t work properly

(10) What to do when LC causes spikes?

(11) What to do when hosting with LC (or another hosting tool) just won’t work (lags, etc)

(12) Tips for a good host and hosting on WLAN


LC Problem #1 - Error in pickup.listchecker.ini & Basic Options

If your LC reports some kind of error when you type /openbnet or /hostbnet Game_Name, most of the time there is indeed an error in pickup.listchecker.ini even though you think it isn’t. So, I recommend that you just delete pickup.listchecker.ini or entire folder where is LC installed/copied (all files) and
download new files from here. - pickup.listchecker v1.0.592 (01/07/2008) [day/month/year]

01_LC.jpg

Also, you will need to install WinPcap software because Listchecker requires it to work properly. You can download WinPcap software from here.

02_WinPcap.jpg

If you have already got it because you use Warcraft III Banlist, and Listchecker doesn’t detect it for some reason (especially on Windows Vista), just uninstall current WinPcap software and download the latest version and install that.

After downloading new LC files (which works for 1.22 patch and has some new features), extract them using any archive extracting software you got (WinZip, WinRAR, 7-zip) and you will get these 3 files:

  • BNCSutil.dll
  • pickup.listchecker.exe
  • pickup.listchecker.ini

Put those 3 files into a folder named “Listchecker” wherever you want, but I recommend putting it into your Warcraft III folder since LC was made for that game especially. So, if you have Warcraft III installed on C:\Program Files\Warcraft III\, put those 3 LC files into C:\Program Files\Warcraft III\Listchecker\. Next, you will have to configure that tricky pickup.listchecker.ini file.

Unedited pickup.listchecker.ini looks like this:

03_unedited_ini.jpg

I will explain each option in pickup.listchecker.ini file. What you need to change is shown below, and
PLEASE TAKE SPECIAL CARE ABOUT SPELLING!

    BASIC SEETINGS:

  1. bnetnetwork=

    This is gateway’s name/address. Choose your gateway (4 choices):

    • uswest.battle.net
    • useast.battle.net
    • europe.battle.net
    • asia.battle.net
  2. bnetkey1=

    Your Reign of Chaos CD-Key in format: AAAAAA-BBBB-CCCCCC-DDDD-EEEEEE
    Include dashes (-) as shown!

  3. bnetkey2=

    Your The Frozen Throne CD-Key in format: AAAAAA-BBBB-CCCCCC-DDDD-EEEEEE
    Include dashes (-) as shown!

  4. bnetacc=

    An existing Battle.net account’s name on the selected gateway.

  5. bnetpass=

    A password of your Battle.net’s account.

  6. war3dir=

    Address path of your Warcraft III folder. In most cases, this is:
    C:\Program Files\Warcraft III
    D:\Games\Warcraft III

    These are some examples, but if you use a different folder name (eg. German version of XP), it would be:
    C:\Programme\Warcraft III
    or wherever you installed your Warcraft III.

  7. hostport=

    Network port which Warcraft III uses. It is 6112 by default, but since it is original Warcraft III’s hosting port, it can NOT be the same, so you will have to change it to 6111 or some different. If you leave it as 6112, Listchecker will show an error upon starting asking you to change that port.

    8. NOTE: As you can see, all settings are needed to be written after sign =

    For instance:
    bnetnetwork=europe.battle.net
    is NOT the same as
    bnetnetwork=
    europe.battle.net
    (first example will work, second won’t!)

Those were required settings needed for Listchecker to work properly! After modifying, press Ctrl-S or go to File -> Save to save your settings.
Don’t worry about losing your CD-Key(s) and account’s password, because once when they are entered (and saved), just run pickup.listchecker.exe and it will be automatically encrypted so no one can see your private data by opening pickup.listchecker.ini again.

    NOTE: once when your CD-Keys and password are encrypted in pickup.listchecker.ini, you CAN easily change them later. Just save pickup.listchecker.ini again after modifying it and run pickup.listchecker.exe to encrypt them again!

This is an EXAMPLE of how should pickup.listchecker.ini look after inputting all necessarily data:

04_example_of_ini.jpg

After you’ve input all the information, just run pickup.listchecker.exe and see if it reports some kind of error. If yes, check your spelling and all settings again! If there is no noticeable error, just type /openbnet into Listchecker’s “Send command” window to connect to Battle.net. If it says something like below, all your settings are OK.

05_connecting_to_b.net.jpg

If there are some errors, check your CD-Key(s), account’s name and password. Once again, check the SPELLING!

If all that works and you have successfully joined warcraft 3 channel, follow this steps to create a game using LC:

  • start Warcraft III
  • go to Local Area Network

    • 06_war3_LAN.jpg

  • write up your account’s name EXACTLY as you wrote in pickup.listchecker.ini
    (otherwise you might be temporary banned from Battle.net and it would also look like you use a Name spoofer)

    • 07_war3_nick.jpg

  • click on Create Game

    • 08_war3_create_game1.jpg

  • select a map you wish to host (let’s say DotA)

    • 09_war3_map_.jpg

  • finally, click on Create Game

    • 10_war3_create_game2_.jpg

After that, you will see that Listchecker has joined your game with the name pkp.listchecker.

    11_war3_pkp_joins.jpg

Now you can type commands to LC as shown below. You can type it in Warcraft III’s chat window or you can press Alt-Tab or Win Key to minimize Warcraft III and type it into Listchecker’s window directly.

HOSTING COMMANDS are:

/openbnet or startbnet - first command you would type to see if your LC can connect to Battle.net at all.

12_war3_openbnet.jpg

/closebnet - closes connection to Battle.net (won’t exit LC).

/hostbnet Game_Name or /hb Game_Name - hosts a PRIVATE game named Game_Name. You can write any name as long it is not already taken (hosted). If it is taken, Listchecker will write Failed to create game, and if it is available, it will say Your game has been created with success.

/hostbnetpublic Game_Name or /hbp Game_Name - hosts a PUBLIC game named Game_Name. You can write any name as long it is not already taken (hosted). If it is taken, Listchecker will write Failed to create game, and if it is available, it will say Your game has been created with success.

/refreshbnet - manual refreshing, although LC has built-in autorefresh every 15 sec. It is recommended if you want people to join faster.

/pingclients or /pc - pings all players joined to your server. In fact, it is the latency of players and it is always shown no matter if players are behind the router of firewall. After using this command, press Ctrl+V to paste it into Warcraft III’s chat window.

    To get full list of available commands, click on LC and press F1 button.

So, in order to find out if your Listchecker works, create most recent DotA map and name your game something like this: /hostbnetpublic Dota -ap COME! (LC host) and press Enter.

13_war3_hostbnetpublic.jpg

If someone joins, voila! You have successfully configured your Listchecker! GL HF! :D

But if pkp.listchecker doesn’t join your game, turn off your firewall (or permit pkp.listchecker.exe to access the Internet) and try again.

If still pkp.listchecker doesn’t join OR no one joins at all after creating a game, read LC Problem #2 below.

LC Problem #2 - No One Joins My Games!

Make sure:

  • your Internet connection is stable
  • you are successfully connected to Battle.net
  • LC says Your game has been created with success
  • you have created a public game using command /hostbnetpublic Game_Name other than /hostbnet Game_Name

If still no one enters, problem is in the PORT!

    NOTE: If you couldn’t host a game normally (without Listchecker), then most likely you won’t be able to host with Listchecker either!

When you host a game without Listchecker, port 6112 (default Warcraft III’s port) is used and MUST be open/forwarded to the Internet. When you host a game with Listchecker, it uses port specified in pickup.listchecker.ini which is, in most cases 6111 or 6113, and that port MUST be open/forwarded to the Internet too. To check which port does Listchecker use, simply open pickup.listchecker.ini and see which number is after hostport= option. What you need is to to make sure that no other program or game use that ports.

To test for open ports, go to THIS WEBSITE.

14_port_check_website.JPG

It is a free port-check website. Simply write 6112 (Warcraft III port) in the box and press Check. Do the same for LC port - the one specified in pickup.listchecker.ini (let’s say it is the port 6111). If the website says: Success: I can see your service…, there shouldn’t be any problems with the port and you are able to host a game!

But if it says Error: I could not see your service… then you will have to configure your modem/router to accept incoming 6111 and 6112, both TCP and UDP ports. If you aren’t sure how to do that, try turning off any firewall/intruder system on your modem/router and then reboot the device. After that, try to host again (with different game name).

If still nothing, see if you have DMZ host option in your modem/router, and if there is, it solves all your port-problems. Activate DMZ host option and write your LOCAL IP in the box. Local IP is IP of your network adapter connected to modem or router (wired or wireless, doesn’t matter).

This is an example of using DMZ host option on D-Link wireless router:

15_D_Link_DMZ_host.jpg

As you can see, LOCAL IP in this case is 192.168.1.2
If you don’t know your current LOCAL IP, don’t worry - there is a way to find it out too! :P

Open Command Prompt (CMD) by clicking on clicking on Start -> Run -> type CMD and press Enter. Vista users may type CMD into Search box on Start and press Enter. Write IPCONFIG -all in it and press Enter.

16_CMD.jpg

That will show you all network adapters with description. Find your adapter’s IP Address which is connected to modem or router. In most cases, it starts with 192.168… When you find it, write it into your modem’s/router’s DMZ host box and press OK/Apply (reboot the device if it’s necessary).
After doing that, try to host once again (with different game name). Check the ports now at the website mention above.

    If you don’t know how to log into your modem/router and make changes, you are a noob which shouldn’t be the host at all!

If even that doesn’t work, there is one more thing you could try. Hehe! In fact, this is a small trick by me that solved hosting problems for my friend. All you need is… uTorrent! Haha, you read precisely - uTorrent! Download it from here if you haven’t already got it.

It doesn’t matter which version to download (although I recommend the stable one) because you won’t be downloading anything! First, just host a game (like there is no problems with the ports at all), then open utorrent.exe and go to Options -> Preferences (or just press Ctrl-P), and then to Connections. As you can see, there is some port-option (Port used for incoming connections). So, type in the port you need for hosting with LC - that would be 6111 (or whatever is specified in pickup.listchecker.ini) and press OK.

17_uTorrent.jpg

Now, check your Warcraft III to see if someone joined your server. If no one has joined, try changing game name. If it works, I am very glad that uTorrent trick helped! :)
Just make sure you aren’t downloading anything via uTorrent during a game so there wouldn’t be lag in your game because of that.

If even that option doesn’t work, I don’t know what to say… I guess you weren’t born to be the host… :(
Most likely, you use shared Internet connection or something else which is hard to configure for you to be the host. But if you can’t be the host on Battle.net, you can be the host on Hamachi and play with you friends even without original Warcraft III CD-Key(s)! Read below how to configure Hamachi!

LC Problem #3 - LC + Hamachi

Hamachi a is free program that creates a Virtual Private Connection (VPN) between you and other users (friends). Hamachi essentially makes you feel like you are were in LAN next to them! Of course, you can play Warcraft III via Local Area Network with no problems with ports and similar stuff. Just create/join game!
Hamachi is free and can be downloaded here.

18_Hamachi_.jpg

As you can see, that is 1.0.1.5 version - isn’t the latest. The reason I gave you the link to the older version is that 1.0.1.5 version WORKS 100% for Warcraft III. If you use the latest version, it is possible that you might not be able to see the host. So if you have any problems seeing the game created by someone on the Hamachi network, try uninstalling the latest version and using the older version, which has always worked for me.

    NOTE: DO NOT update Hamachi to newer version any more!

If you can host games with LC (and Hamachi), then you can play with multiple networks. What does this mean? This means you can play with your friends who don’t have original CD-Key(s)! When you create a game on the LAN, it is created on the Hamachi network and anyone (with our without a valid cd-key) can join the game!

To do that, follow this steps:

  • start both LC and Hamachi and then start Warcraft III
  • click on Local Area Network, write up name as your account on Battle.net and click on Create Game
  • your friends from Hamachi can join your server via Local Area Netwok (in case they can’t see your server, turn off your firewall or trust their IP addresses - they should do the same
  • after they have joined, you can connect to Battle.net via LC and host private or public game and play all together!

I am sure that your friends from Hamachi will be pleased to play on Battle.net. Nice, right? :D

LC Problem #4 - LC + Banlist

Banlist? What is Banlist? HAHA! I am sure all DotA players know it (some of them have already been banned by it! LOL). In case you have been living under a rock, here is the link to download banlist!

19_WC3Banlist.jpg

There are a LOT of question like:

  1. Can LC be used with Banlist?
  2. How to get LC work with Banlist?
  3. I can’t ban with Banlist while hosting with LC! Why?
  4. etc…

ANSWER is: YES, IT CAN WORK with LC indeed! Read below how.

To get it work with LC, start: Warcraft III, LC and Banlist, and then create a game. When someone joins, you would like to perform some Banlist’s command, for instance: determine players’ origin (country). So, you type /fromall, press Enter but nothing happens? Well, it’s because you hosted a game via Local Area Network and Banlist “thinks” you aren’t connected to Battle.net at all. To persuade it, use LC command /bnet before every Banlist’s command. So, to determine players’ origins correctly, type /bnet /fromall and press Ctrl+V to paste the output from Banlist.

When you combinate /bnet + any Banlist's command, you will get error message from BNET saying:
That is not a valid command. Type /help or /? for more info.

Don’t worry about that. It’s just an auto-answer from Battle.net saying there is no /fromall command or similar to use on Battle.net, but you have it use in that way to persuade Banlist to work with LC correctly!

For advance users of Banlist, there are Phrases! Phrases are similar to macros. With the press of one button, you can output a premediated message, which can be very handy when you are hosting games.
Open Banlist, go to Preferences and click on Phrases.

20_WC3Banlist_phrases.jpg

Here you can assign a hotkey for each phrase (containing Banlist’s command). That way, you can assign, for instance:

  • /fromall to F5 button
  • /ban PLAYER'S_NAME to F8
  • You can even use LC commands assigned to hotkeys, for instance: /refreshbnet to F4, /pingclients to F6.

By doing so, you don’t have to minimize (Alt-Tab) Warcraft III any more!

    NOTE: When you assign Banlist’s command to hotkey, you don’t need to use /bnet before Banlist’s command(s).

EXAMPLES OF PHRASES:

Here are some examples of Phrases that I use with hotkeys - you can use or add whatever Banlist’s command you want.

My F4 hotkey is command from Listchecker used to refresh the game, /refreshbnet and it looks like this:

    Name of Phrase: F4_refreshbnet
    Text to be written:
    /refreshbnet
    ~~/refreshbnet
    ~~/refreshbnet
    ~~/refreshbnet
    an empty line here (Enter)

As you can see, I use ~ to delay future commands for 500 ms (0,5 sec) to avoid being banned from Battle.net for flooding. Also, at the end of “Text to be written”, I added an empty line (Enter) so Banlist can write the last command too. If you don’t add an empty line by pressing Enter, you will have to manually press Enter when commands reaches the end.

When someone leaves during game, I press F8 and the leaver is automatically banned in my local Banlist
(I am not approved host… yet! :) ) and the message is shown To All:
Here is how I do it:

    Name of Phrase:F8_banned!
    Text to be written:
    /ban $lastleaver LEAVER ($state now) after $gametime in game “$gametitle” on $realm ($day/$month/$year), (banned by $nick)
    $shiftenter$lastleaver is BANNED for leaving this game after $gametime! Stay till the end because it is *$state* now!
    an empty line here (Enter)

LC Problem #5 - Chat on Battle.net via LC

When Listchecker is connected to Battle.net, you can chat with other Battle.net users, of course!

Just open Listchecker and start Warcraft III -> Local Area Network -> Create Game and select any map and create it. Use command /openbnet or /startbnet to connect to Battle.net only (without making a server).

When you write commands to LC inside Warcraft III Local Area Network window, all players who joined your server (from Battle.net or Hamachi) SEE your messages! There’s no problem when you type /hostbnet Game_Name or /pingclients but when you whisper to someone, you may want to hide that messages from others. So, to whisper privately, minimize Warcraft III and write it into LC’s box. To whisper to someone, use command as you would on Battle.net: /w PLAYER'S_NAME MESSAGE.

    For instance: /w Krkljator.CF Hello!

21_war3_chat.jpg

The only difference when you chat like that is when using command for reply. The common command for replying to the last person who whispered you is: /r MESSAGE, but it won’t work with Listchecke! The appropriate command in LC for reply is: /re MESSAGE and it works!

    For instance: /re OK, let's play some DotA now!

LC Problem #6 - Changing Country Tag and Default Channel

When you use LC and get connected to Battle.net, default channel you are joining is Frozen Throne FRA and default country tag is FRA. So, if you are Frenchman, it’s OK for you, but for other people, it is not! LOL!

Since you use updated version of LC - pickup.listchecker v1.0.592 (01/07/2008), options countryshort= and country= are no longer used for changing the default channel and country’s tag!

To change country’s tag and default channel properly, perform there steps:

  • start LC (without typing any commands to it)
  • start Warcraft III
  • connect to Battle.net via Warcraft III
  • enter Chat (LC will then automatically collect your country’s information)
  • exit Battle.net
  • now check your pickup.listchecker.ini if there is bnetfrom= option with some code added at the end which contains all your country’s information
  • from now on, every time you connect to Battle.net via LC, you will be joined to your country’s default channel and you will be given appropriate country’s tag

For instance, if you are from Croatia (like me), bnetfrom= would look like this:

    bnetfrom=88FFFFFF1A040000090400004852560043726F6174696100

LC Problem #7 - Multiple uses of LC

Maybe you have a brother or just two (or more) accounts on Battle.net and you would use both accounts without constant modify of pickup.listchecker.ini to change account’s name and password.

There’s no problem with it at all! Just create new folder with a name different that the original LC folder. Let’s say Listchecker_2 and copy all files from first folder to it. In pickup.listchecker.ini, write account’s name and password of your second account (or your brother’s account and save it). By doing so, you have instant access to second account without modifying pickup.listchecker.ini of your first account.

22_multiple_uses_of_LC.jpg

    NOTE: Since you copied both pickup.listchecker.ini and pickup.listchecker.exe to new folder, you will have to permit that new location of pickup.listchecker.exe in your firewall too if you have it turned on (so that second LC/account can work).

If you want to give a copy of LC program to your friend, make sure you DON’T give him your configuration file pickup.listchecker.ini because he would be able to play with your CD-Key(s) and account. But he won’t be able to read that information out from pickup.listchecker.ini file because it is encrypted, unless he is a hacker!

LC Problem #8 - LC on Windows Vista

Some of you maybe use Windows Vista and got unusual errors when using LC. Fix that nasty errors by doing all this:

  1. run pickup.listchecker.exe as an Administrator

    2. Do that by right clicking at pkp.listchecker.exe and choosing Properties. Then click on Compatibility tab and under Privilege level, check Run this program as an Administrator, and finally, press OK.
    Now you can start LC either from pkp.listchecker.exe or shortcut.

    23_vista_run_as_administrator_.jpg

    NOTE: if you can’t check Run as an Administrator box, it’s because you have User Account Control (UAC) turned OFF which automatically removes Run as an Administrator option. So, don’t worry, it’s like you actually checked that box! I recommend turning off User Account Control if it’s still ON (Control Panel -> User Accounts).

    24_vista_turning_off_UAC.jpg

  2. avoid installing Warcraft III to C:\Program Files\Warcraft III

    3. Many users have reported that their LC couldn’t find Warcraft III installation folder even though they had specified war3dir= correctly. This problem is only on Windows Vista, so you will have to either re-install Warcraft III or copy/move Warcraft III folder to somewhere else. For instance, to:
    C:\Games\Warcraft III
    D:\Warcraft III
    etc…

  3. problem with WinPcap device

    4. Even though you do have WinPcap software installed, it might happen that LC reports there isn’t or can’t open it. Fix this problem by re-installing (uninstall and then install again) WinPcap software. I recommend downloading latest version of WinPcap and installing that.
    Download WinPcap from here.

    25_vista_WinPcap.jpg

    NOTE: make sure you run WinPcap installer as an Administrator.

    If that wouldn’t help, try re-installing LC too!
    And if you still have Error : couldnt open winpcap device problem, it’s because of incompatibility of Vista and WinPcap. Try installing older version of WinPcap or search the Internet for answer/fix.
    Or… you can just switch to Windows XP! Hehe!

  4. avoid hosting games with LC via wireless network adapters

    5. Some wireless network adapters (drivers) cause problems to WinPcap which results malfunction of LC. So, if you experience such problems, use wired, or even better, fiber network adapters to access the Internet and host with LC.

FAQ, Tips, Misc, and Other

  1. What are some ways to optimize hosting with LC?

    • it is desirable that host has very good Internet connection (especially upload)
    • make sure your connection to the Internet is stable
    • close all unused active programs
    • stop all downloads (even exit programs like LimeWire or eMule if used)
    • turn off firewall (to avoid all possible problems for players)
    • ping players by /pingcliens or /ps and press Ctrl+V to paste so that everyone can see it

      • If all players have latency (pings) around 50 ms (or less), it would be smooth game for everyone.
      If all players have latency around 70-80 ms (or even more), your Internet connection is slow and you shouldn’t be hosting. But, if there are mixed latency: 30/53/84/68/112/23/77…, then your connection is not the problem. So, you might want to kick those players because they could potentially cause lag for the rest of the players.
      In this case, kick player with latency 112. Since LC sends information packets at 100ms, this is the maximum that you should allow others’ pings to be (BNET sends information packets at 250ms!).

      NOTE: it is recommended to ping several times to see real latency. Sometimes might happen that high latency shows (for individual player) on first pinging, but when you reping, very small latency shows.

  2. What does it mean by failed to hash war3 key?

    I got this:

    Connecting to uswest.battle.net on port 6112
    Connected
    Sending auth info
    Received Ping request
    Sent Ping reply
    Received auth reply
    Calculating checksum
    Failed to hash WAR3 key

    • When LC reports an error Failed to hash WAR3 key, it means you have entered in your CD-Key(s) incorrectly in the ini file.. Most likely, you tried to change them (and failed) when they had been encrypted. Just erase it and write them again like this:

      bnetkey1=WARCRAFT3-ROC-CDKEY-HERE
      bnetkey2=FROZEN-THRONE-CDKEY-HERE

      NOTE: you HAVE TO write them AFTER =, NOT after =e:
      Include dashes (-) as well!
      Once you wrote them, save pickup.listchecker.ini, close it, start LC and data will be encrypted.

    • THE SAME goes for inputting password!
  3. Where can I download standalone Warcraft III 1.22 patch (updater)?

      4. You can download this or any previous patch for Warcraft III - The Frozen Throne (either English version or different) on BLIZZARD’S FTP SITE.

      26_Blizzards_FTP.jpg

      If you DON’T have The Frozen Throne (expansion) installed, but Warcraft III - Reign of Chaos, follow this THIS LINK and download patch.

      If you have 1.21b patch installed, you might want to download updater from 1.21b to 1.22a (7,55 MB), rather than full patch (55,9 MB) which updates to 1.22 version from any previous patch installed.

      Here are quick links for English (US) version of Warcraft III - The Frozen Throne:

    • Partial updater 1.21b -> 1.22a only can be downloaded from here.

    • Full updater 1.22a can be downloaded from here.

      • However, if you have copied version of Warcraft III - The Frozen Throne, or you just re-installed Windows and updater says Couldn’t locate Warcraft III instalation when trying to apply patch, use this link to apply 1.22a patch:

    • Full updater v2 1.22a (English) can be downloaded from here.
  4. What to do when pkp.listchecker joins my game and then leaves immediately, and keeps joining and leaving, thus not allowing me to host a game?

      5. It is quite an unusual problem, so try this:

    • close both Warcraft III and LC
    • once again, check configuration in pickup.listchecker.ini if all settings are written as they should be - maybe there is some text that doesn’t belong there, thus causing this error.
      I suggest deleting it and filling out new one
    • make sure that file BNCSutil.dll isn’t somehow corrupted and it has to be in the same folder as pkp.listchecker.exe and pkp.listchecker.ini
    • turn off any firewall (or check that you properly made an exception for pickup.listchecker.exe in it)
    • make sure that none of other applications use ports assigned for Warcraft III (6112 or any other you assigned in Warcraft III Options menu) as well as for LC (6111 or any other you assigned in pickup.listchecker.ini)
    • re-install WinPcap (try to install different version) and restart your computer
    • try to host again

      If still the same problem persists, try to start LC in off-line mode like this:

    • close both Warcraft III and LC, but now disconnect from the Internet
    • start LC and then Warcraft III
    • go to Local Area Network and create a game - pkp.listchecker should join now, without leaving
    • press Alt-Tab or Win key to minimize Warcraft III, then connect to the Internet
    • connect LC to Battle.net using /openbnet or /starbnet and see if there are any errors while connecting to Battle.net
    • if there are no errors, just type in /hostbnetpublic Game_Name and that should work!

    If pkp.listchecker still joins and then automatically leaves when you create a game in this off-line mode, something else is wrong which you must solve…

  5. What to do when I try to host a game and this comes up in LC:

    Connecting to europe.battle.net, port:6112
    Connected
    Sending auth info
    Connection closed

    • The same goes when connecting to Battle.net via Warcraft III’s button Battle.net.

      • If only one Battle.net Realm is inaccessible to you, then it may just be a temporary connection problem or a temporary restriction. Battle.net access may be restricted (for up to 14 days) for one of the following reasons:

      • Spamming text in the chat channel (often associated with bots)
      • Rapidly connecting/disconnecting to Battle.net (often associated with bots)
      • Repeated attempts to use an invalid CD-Key or an incorrect Battle.net password
      • Repeated use of a third-party programs (hacks)
      • Attempting to connect to Battle.net using an invalid CD key
      • Multiple users connecting to Battle.net using the same IP address

      In other words, Battle.net banned your Internet IP address temporary. So, to solve this, you can just wait (minutes, hours or even days) or you can change your Internet IP address. If you use standard DSL connection to access the Internet, just disconnect from the Internet (either from your modem/router or from your computer), and then connect to the Internet again. By doing that, you will be assigned a new Internet IP address so you can connect back to Battle.net.

      But, don’t do anymore whatever you did when you got banned from Battle.net!

    • Why does LC kicks everyone from my game whenever my brother joins some custom game on Battle.net?

      • The problem is in the shared Internet connection!
        When using the same (shared) Internet connection, you both have the same Internet IP address too. That causes problems because for LC can be only one Internet IP address that connects to Battle.net on port 6112. Thus, second connection interferences with first connection. This problem is only in LC so you can’t play games on Battle.net at the same time, with the same Internet IP address - whenever you host with LC.

        The same thing goes for Banlist. When you first connect to Battle.net with Banlist started, while your brother or friend on the same Internet connection connects to Battle.net as second, and joins to some custom game server, your Banlist will suddenly start monitoring your brother’s/friend’s activity…

    • Suddenly, I can’t open nor edit pickup.listchecker.ini with Notepad? Help please!

      • If opening with Notepad fails, you can open pickup.listchecker.ini with any other text editor like: WordPad, Microsoft Office Word, UltraEdit…
        Your error was most likely caused by some kind of virus so Notepad lost association for opening .ini files. So, open Registry Editor (Start -> Run: regedit)

        27_registry_editor.jpg

        and modify existing setting to match this one: 

        HKEY_CLASSES_ROOT\inifile\shell\open\command
Default=%SystemRoot%\System32\NOTEPAD.EXE %1
HKEY_CLASSES_ROOT\inifile\shell\print\command
Default=%SystemRoot%\System32\NOTEPAD.EXE /p %1
        If you can’t open/edit .bat files with Notepad either, do this too: 
        HKEY_CLASSES_ROOT\batfile\shell\edit\command
Default=%SystemRoot%\System32\NOTEPAD.EXE %1
HKEY_CLASSES_ROOT\batfile\shell\open\command
Default="%1" %*
HKEY_CLASSES_ROOT\batfile\shell\print\command
Default=%SystemRoot%\System32\NOTEPAD.EXE /p %1
    • Is there a way to get a list of available games via LC on my Local Area Network screen, so that I don’t need to log on Battle.net via Warcraft III?

        • Yes, there is!
        To successfully get a list of available Warcraft III games on your Local Area Network screen, follow this steps:

      • first, start LC and then Warcraft III
      • in Warcraft III, go to Local Area Network (and write up your account’s name as specified in pickup.listchecker.ini) and press Alt-Tab or Win key to minimize Warcraft III
      • click on LC and type /findbnet or /fb
        LC will then connect to Battle.net (to gateway specified in pickup.listchecker.ini) and get a list of available Warcraft III (public) games and put it in your Local Area Network screen. It takes just a few seconds
      • now switch back to Warcraft III and you should have a list of available games listed on your Local Area Network screen

        • 28_findbnet.jpg

      • that list won’t be automatically refreshed every few seconds as on Battle.net, thus going upside down, so you will have more time to choose which public game you want to join
      • to refresh the list, just minimize Warcraft III and type again /findbnet or /fb to LC, and switch back to Warcraft III Local Area Network
      • if you want to get a single game on LAN screen (public or private), type in LC this:
        /findbnet Game_Name or /fb Game_Name and that game will appear in your Local Area Network screen, and you can join it (if hosted with that name)

        (e.g.: /fb dota-ap)

Ending…

Yep, you are looking at the END (at last!) of this MEGA TUTORIAL by Krkljator.CF! I know my tutorial is very big, but also very very helpful because it just has it all - starting from basic settings to advanced options. By reading this tutorial in entirety, I am sure you will all become
LC experts! :D

ABOUT ME:

29_about_me.jpg

HAHA! Well… I am just a honest guy who knows many things and tries to help everyone (although I don’t get anything from it - but maybe someone will reward me… some day!).
Hope I helped a lot of people! No one rewarded me or something like that for making this tutorial (which I think is perfect!). I did it all by myself without any benefits, and it took lots and lots of HOURS of my time!!

When posting comments/questions, make sure:

  • you have read my tutorial in entirety
  • DO NOT ask questions that are already answered (in tutorial or in comments) - I WILL NOT answer them again!
  • DO NOT ask questions like this:
    I can’t host! HELP!!! -> that kind of questions will be ignored and deleted.
    State your problem(s) well described!
  • DO NOT insult me or anyone else, stay mannered, otherwise your comments will be deleted you you will be kicked/banned
  • That’s all I ask from you. Thank you!
      • 30_LOL.jpg

P.S.: For any other contact regarding LC and Warcraft III (let’s say you are kind enough to send me your spare valid CD-Key(s) of Warcraft III as BIG THANKS! - HEHE!), you can do that by whispering me on the Northrend gateway - nick is, of course: Krkljator.CF

Or you can send me an e-mail to: krkljator@yahoo.com

THIS TUTORIAL WAS ORIGINALLY FINISHED: 20th of July, 2008.
Many thanks to Quan Quach and Daniel Sutoyo for all the help!

31_END.jpg