Nerbil

When one of the allied trucks is blown on Airfield Assault first playable map (airassault_fp1.pk3), the bots continue to try to repair the truck barrier (that no longer exists, and can't be built). They eventually give up, but come back to try again, and again. This eventually hurts the axis team because these bot players are focused on these non-functioning engineer objectives.

Very well known method, I think I've been doing it for years on that map. It's an easy way down for allies if you can get them to understand and do it.

Thanks to whoever made this change recently. I noticed and appreciated it. Bots now join to force an even number of players across the teams.

Grave Robbery (graverob_b1.pk3) on jay1 has issues with Bots playing. When bots are on the allied team, they will open the back door with the pulley near the command post on each spawn. Which, effectively lets an axis cov ops come in through the back door. I stood and watched and saw bots open the back door about 10+ times in just a few minutes, each time I closed it after them so as to keep axis out. Maybe change the rotation so that it won't play with few players, and so that it only shows up when bots aren't connected.

It should work fine, my son, JKamino, plays W:ET on Windows 10. Make sure you run the executable in Backward Compatibility mode. He has it running in Windows XP compatibility, and always running as Administrator.

I play at 1920x1200, which is native for my LCD monitor.

On the map "TC Base" (tc_base.pk3), the map time is 15 minutes, but the objectives can't be destroyed until 5 minutes or less are left on the map. I think this timing should be changed, enforce a 5 minute lock on the objectives (the no rushing rule), so that the allies have 10 minutes to complete the map. This map doesn't have any vehicle to escort, no flag to capture, no bridges to build. There is no reason for the map to be 15 minutes long if the objective can only be played during the last 5 minutes. It's a good map, but makes a waste for the allies who have no motivation to move forward. Perhaps it would be best to change the map time to 10 minutes, 5 minutes for no rush, and 5 minutes for obj. Otherwise the total of 15 minutes of the map should unlock the objectives at 10 minutes remaining. Make the map fun for both teams, and give some motivation to play, move forward, and hold territory.

W:ET uses the Quake 3 engine, many articles on Quake 3 config changes. Here's one: https://www.wikihow.com/Color-Your-Name-in-Quake-3

Let's get Helm's Deep back on Recruiting|XP Save server. People know Minas well, but it seems that most don't know Helm's Deep

I just got a response from my ticket with Choopa stating that they have resolved the routing issue. I'm not home to verify right now, but I called my son and he was able to connect. Everyone that was unable to get in, try again now. Outside of the server being full, it looks like connectivity is restored.

Here is the response I got from ServerCentral.com, the same info that Elf received: Subject: [#CSP-646-83650]: BGP Routing Issue on your network Hello, The final hop on your traceroute is the end of ServerCentral's network. We have no visibility beyond that last hop. We have reached out to the party who is responsible for the network beyond that last hop and they have requested you contact them via their website at https://www.gameservers.com/contact/ in regards to any issue you are experiencing. Have a Good Day, Chuck Kern Data Center Operations +1 (312) 895-3005

That company is the actual hosting company for the F|A ET servers, they list the IP address of 8.9.4.227 (F|A Recruiting) as a sample server for ET: https://www.gameservers.com/game_servers/enemy-territory-server.php Can a server admin from the F|A clan complain to them directly?

Awesome, response from somebody Elf. I filled out the form on https://www.servercentral.com/support/contact-us and sent an E-mail to support@servercentral.com. Now, with Elf's new information, send E-mails with your tracert.exe results to: support@gameservers.com

I tried to connect at work (using a different ISP), and I can get through: Tracing route to 8.9.4.227 over a maximum of 30 hops ... (skipping a few lines)... 10 19 ms 19 ms 19 ms ae0-134.cr3-sea2.ip4.gtt.net [173.205.50.237] 11 48 ms 48 ms 48 ms xe-0-3-0.cr8-chi1.ip4.gtt.net [141.136.108.194] 12 47 ms 49 ms 49 ms ip4.gtt.net [173.205.42.134] 13 49 ms 47 ms 49 ms 8.9.4.227 However, from home (through Comcast), it is still failing. Tracing route to 8.9.4.227 over a maximum of 30 hops ... (skipping a few lines)... 6 37 ms 38 ms 51 ms be-10817-cr02.denver.co.ibone.comcast.net [68.86.84.205] 7 62 ms 66 ms 66 ms be-10517-cr02.350ecermak.il.ibone.comcast.net [68.86.85.169] 8 61 ms 61 ms 59 ms be-10563-pe01.350ecermak.il.ibone.comcast.net [68.86.82.158] 9 60 ms 59 ms 59 ms 50.242.150.34 10 60 ms 61 ms 60 ms 0.ae12.cr2.ord6.scnet.net [204.93.204.83] 11 61 ms 60 ms 66 ms 0.ae2.ar10.ord6.scnet.net [204.93.204.81] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out.