JDRGaming Battlefield 2 server

This is somewhat old news, as it was first reported in October 2017. However, I just found out about it, and it affects my plans for a JDRGaming modern combat server.

Up until a few days ago, I had planned to start running a modern combat server, using the ReviveBF2 client/launcher/server. The idea was to run the server on a trial basis and hopefully attract some interest from fans of my other servers.

Then I learned the Revive Network folks had received a warning letter from EA, which owns the rights to the Battlefield games. EA's main complaint was that Revive Network was distributing Battlefield game client software to anyone who cared to download it.

Background: when Gamespy shuttered in 2015, playing Battlefield 2 online with the official client software became effectively impossible. Enterprising folks found ways to modify the client (and server) software to use new, unofficial master server browsers, and once again online play was possible. Three basic approaches were used to accomplish this: create a new client based on the original (e.g. Forgotten Hope 2); develop patches that modify Battlefield client software (e.g. BF2Hub); or modify the original client and make that available to users. Revive Network chose the latter approach, and that's what earned them EA's letter.

Leaving aside any arguments about rights associated with abandoned software like Battlefield 2, it seems to me that Revive Network could have resolved this issue by simply doing what EA asked: stop making Battlefield game client software available from their site. They could have just switched to the patching approach, so that people with Battlefield clients could modify them to work with the new unofficial master servers. Instead, Revive Network chose to shut down.

With ReviveBF2 and the associated master server no longer available, I started looking for alternatives, and found BF2Hub. It's a free launcher for BF2 that works with most available mods, and automates the process of patching your BF2 client to work with BF2Hub's master server.

My tests with BF2Hub were a complete success. As a result, BF2Hub is now the launcher of choice for all JDRGaming BF2 servers except for Forgotten Hope 2, which has its own launcher. The two launchers don't interfere with each other at all. I've posted the BF2Hub launcher on the JDRGaming Files page.

I am currently testing the Hard Justice BF2 mod for use with BF2Hub. You may notice HJ running on the BF2 server occasionally over the coming weeks. Forgotten Hope 2 is still the default mod for the JDRGaming BF2 server, but I'm considering designating one day per week for modern combat, and Hard Justice is looking like the best option available.

See you on the battlefield!

Due to circumstances beyond my control, all of the JDRGaming game servers will be unavailable on August 30.

A planned local power outage is expected to last from 8:30am to 6:30 pm on August 30. The outage will also affect this web site (jdrgaming.com).

I will post updates on the @JDRGamingStatus Twitter account as events unfold tomorrow.

UPDATE: As of 12:50pm PST, power has been restored and the server is back up. All game servers are back online.

At about 3am PST today (2017Jun01), my Internet Service Provider (Shaw) changed my WAN IP address. Again. This happens from time to time because of the type of service I use. I'm now considering switching to a service that provides a static IP address.

The IP address for all JDRGaming game servers is now 24.80.59.72. Server lists will gradually update, but you can usually hurry things along by clicking an 'update' or 'refresh' button in game clients.

I'll update the alerts at the top of the home page to show the new IP address.

If you have any trouble connecting, please use the 'report a problem' link below the TPU Status box.

At about 2am PST today (2017Jan16), my Internet Service Provider (Shaw) changed my WAN IP address. This happens from time to time because of the type of service I use.

The IP address for all JDRGaming game servers is now 24.80.14.52. Server lists will gradually update, but you can usually hurry things along by clicking an 'update' or 'refresh' button in game clients.

I've updated the alerts at the top of the home page to show the new IP address.

If you have any trouble connecting, please use the 'report a problem' link below the TPU Status box.

Discord is an excellent, free, gaming-centric chat client that you can use on the web or run as a client on your computer.

I've been using the Discord Windows client for a few weeks now and I like it so much I'm switching to it for JDRGaming-related chat. Previously I was using IRC, but that was a bit tricky to set up for users. Discord is much simpler.

So there's now a JDRGaming Discord server, with channels for each of the JDRGaming game servers. You can use Discord or install the Discord client at the Discord web site.

Here's an instant invite for the JDRGaming Discord server: https://discord.gg/5KVyRUv. I've added the Discord invite URL to each of the game servers, so you should see it when you join or during gameplay.

The FH2 development team released FH2 version 2.52 on June 16.

The FH2: 2.5 COOP Map Pack is an attempt to make the new Eastern Front FH2 2.51 maps work in co-op mode. Sadly, none of the four Eastern Front maps works properly with a dedicated server, but the pack also includes a co-op version of Pegasus Bridge, and that map works fine on the JDRGaming dedicated server. I've added the 64 player version of Pegasus Bridge to the map rotation. To play the map, you need to download and install the pack to your BF2 FH2 mod folder. You can find the pack on this site's Files and Downloads page as well.

The FH2: Forgotten Maps Pack is a collection of maps from other mods that have been modified to support co-op play and work with the FH2 mod. About half of the 20 maps work with the JDRGaming BF2 server, and I've added those to the map rotation. The new maps are Operation Aberdeen, Siege of Tobruk Night v3, Mersa Matruh Coop, El Agheila, Sidi Muftah, Fort Capuzzo, Argentan, Carentan, Advance on Foy, Malmedy (Operation Greif), and Operation Nordwind. To play these new maps, you need to download and install four packages to your BF2 FH2 mod folder. You can also find the required files on this site's Files and Downloads page.

UPDATE: a play tester discovered the problem with several of the non-working Forgotten Maps (thanks, Andrew!) The following maps are now working as well: Beda Fomm, Bloody Gulch, Juin 44, Longues sur Mer, and Orscholtz Switch.

Due to problems in the 2.50 release, the FH2 development team released FH2 version 2.51 yesterday.

The JDRGaming BF2 server is now running FH2 2.51. You'll need to run the FH2 2.51 client to play on the JDRGaming server.

The FH2 client launcher should automatically detect the new version and offer to download it.

As always, please let me know if you encounter any problems.

Forgotten Hope 2.5 is up and running on the JDRGaming BF2 server. Please let me know if you run into any issues.

Forgotten Hope 2, version 2.5 is now available.

I originally planned to spend some time evaluating the new version before upgrading the JDRGaming BF2 server, to make sure that co-op play was possible with the new version's maps. Unfortunately, the master server that was used by FH 2.48 is now permanently offline due to recent Denial of Service (DoS) attacks.

The FH 2.5 launcher and client, as well as the FH 2.5 server files, use a different master server. In order to play Forgotten Hope 2 online, everyone will need to upgrade to version 2.5.

The JDRGaming BF2 server is offline while I upgrade the server. I'll post here when the server is back online.

According to the dedicated folks who work on making FH2 maps work in single player (and co-op) mode, none of the new maps (including the western front maps) work in co-op mode. I'm hoping they find the time to knock those maps into shape, because they look interesting: Arad, Dukla Pass, Pegasus, Sammatus, and Seelow Heights.

Meanwhile, several long-standing, global issues with FH2 co-op have been fixed or limited in the new version. For instance, crashes related to deployed emplacements have been fixed. The release notes have additional details.

You can (and should) download and install the new FH2 client files. Note that the new master server is apparently having some issues and you may have trouble getting it to show any servers. If that happens, try using the FH2 web site's server browser to find and join a server.