You are not logged in.
Yes, the -=TL=- public server in Texas was nice. Let's see how this server will go. Right now, it's running all non modded maps, but I plan on changing some maps. There are no admins for now, if the server gets popular we'll start recruiting.
Guadalcanal CTF was added to the map pool to have some variety in game play. I think it is a suitable map for capture the flag mode, because you can make full use of the ships to attack and approach enemy main base. It's also a relative big map, so there should not be constant baseraping.
i cant accept it when ppl nadespam the spawn at the 2. axis flag on omaha.
Thanks for pointing that out. I will try to correct Omaha Beach, making no grenades reload on ammo boxes.
Agreed, he will be banned from the server. I am too disappointed with his action, I haven't read the post, yet. He is for sure a very good player, but never thought he would cheat.
Ok, the server will stream to bfkhdb.selaron.de website, if you all prefer. I've talked about this in a previous post on News and Announcements > SiMPLE | BF1942 [FRA] is on BF Tracks:
We've decided not to have the server listed on bfkhdb.selaron.de, mainly because of privacy reasons. If anyone wants to play anonymously in our server, with a different nickname than his usual, he should be free to do so and not have a public website tracking him by his keyhash.
Hi bogdan1970,
You are unbanned from the server, it was a mistake. Sorry for the inconvenience.
Today, we launch a new Battlefield 1942 server in Los Angeles, California. This will be a server with 36 players slots due to some bandwidth constraints. This will, probably, please South American and Asian players, due to their lower ping there. The server will be focused, for now, mainly on capture the flag maps. Update your in-game server lists to see the server. Anyway, server details follow:
Address: 199.195.142.124 Port: 14567
Suggestions are welcome.
Hi Landser,
Your keyhash was in the banlist.con file, even though you were not in the ban list in BFRemoteManager. I can't explain you why it was there, maybe a bug in BFRemoteManager. Sorry for the mistake, your keyhash is now removed from the the banlist.con file.
Hi Denny,
mlohavpimpek was banned for 1 day for attacking enemy main base in Gazala. He is not banned anymore.
Hi WALLY,
You are unbanned, the ban was just for 1 day. Thanks for your understanding.
I have reconsidered and removed your ban, but please make sure you respect the rules and all players. I'm going to quickly remind you the basic server rules, it is forbidden using cheats or hiding inside textures (glitching), no team killing or any disruptive game play is allowed and you cannot attack the enemy uncapturable main base. We will keep an eye on you, if you disrespect in any way, your ban will be much longer. I expect that you from now on play fair. Have fun!
Hi AGO,
I'm sorry your ban will not be removed, for now, because what you did, besides glitching, was unacceptable. The first time you were banned you should have appealed and correct your behaviour.
Banned words disabled. The word "hack" was banned to prevent chatting about cheats. Other banned words had racist or profane conotation.
This one I clinched the gold medal on Tobruk playing as allied the whole round. I rarely get these high scores, so this is kind of extraordinary.
I have saved some screenshots weeks ago. This is a good individual score on Stalingrad against a strong Axis team, GUN|BF crew and TrancePanther were playing as Germans.
Amazing score! Playing as allied in Wake island, which means you had to play defensively, and getting plus 100 score with just 5 deaths is really impressive.
The problem seems to be related with OVH network. At some times of the day, the network gets saturated and the routers start dropping packets. That's why you get those connection problems messages and get booted from the server. The server doesn't crash, it's just the traffic between you and the server that is temporarily broken. Hopefully, those network problems will be sorted out.
Thanks Denny. I'll try to find out the reason.
I wasn't joking. We chose 60 slots because it is the highest even number divisible by 3.
That's the reason.
The recent server crashes are related with the objects (players, vehicles) so a server with a greater number of players could be more prone to crashes, but i've witnessed the server crash with few players. I'm pretty sure the majority of the server crashes are induced by someone.
Hi Denny,
I think I have fixed that problem. Can you test again admin commands with your TeamÇro tag?
Because we prefer the number 60 to number 64.
Hi,
Apologies for the server being down. Yesterday, I had scheduled the server to be down for an hour and it took me almost a day to tweak the server. I'll post a brief announcement on that.
Hi Sentenza,
You were banned for disrupting game play. I will remove the ban, because you seem to have understood your mistake. However, if you do that again your ban will be longer. Please, follow the server rules and respect all players.
You are unbanned, now. It was a 1 day ban.
New server is up and running, its IP address is 188.165.220.115. I'm having some technical problems redirecting the traffic from the old server address to the new one, so don't be surprised if you can't connect or see it in the Gamespy list. You should update your Servers List and join directly from the new IP address.
No, it is "L" in lowercase. If you copy and then paste it in Command Prompt window you can't get it wrong.
I'm repeating it again in detailed steps, click in Start in your bottom left corner, then click Run... (or press Windows key, the key between Ctrl and Alt keys, and R key at the same time), it pops up the Run box, like you see in the image above. Type cmd and press Enter. Now it opens a black window just as in the picture above. Now go to your browser, select and copy (Ctrl + C) this text: ping -n 300 -l 98 188.165.170.241
Right click on the Command Prompt black window and select Paste, the text gets typed in the black window and press Enter. You should see the messages coming up:
Pinging 188.165.170.241 with 98 bytes of data:
Reply from 188.165.170.241: bytes=98 time=55ms TTL=54
Reply from 188.165.170.241: bytes=98 time=54ms TTL=54
Reply from 188.165.170.241: bytes=98 time=54ms TTL=54
That's it. Wait 300 seconds and you'll have your final results, minimum, maximum and average ping values to the server.
We tested the server, yesterday, and still had the same problems, some few lags at times and even connection problems warning messages. This server is not stable as we've desired, so we'll change to another new server. I'll have it ready probably on Tuesday and I'm confident this server will be rock solid (fingers crossed ).
A picture is worth a thousand words:
Unless you don't have ping installed in your Windows operating system, which I highly doubt, you should be able to ping test the server.
Thanks. I had the same connection problems as you had yesterday. I'm going to do further tests today.
Copy and paste this in Command Prompt:
ping -n 300 -l 98 188.165.170.241