While already on the website for some time, we forgot to announce the new BIATCH versions on our own website (shame on us!). Anyway, version 1.2A is here with the following improvements over v1.1 RC1

It contains various updates, here are some important ones:
- UDP packet crash fix. Now it's (probably) not possible to crash the server anymore with a malicious UDP packet any more. (see http://www.renegadeforums.com/index.php?t=msg&th=37018&start=0&rid=2 0224)
- Another UDP packet crash fix. Now it's not possible to crash the server anymore with a known malicious UDP packet any more.
- Includes the pointfix, if wanted. Otherwise use the pointbug version in the zip file.

More information can be found in the changelog in the documentation.

You can find the download here:
BIATCH download

And the documentation can be found here:
BIATCH documentation

Please give feedback on the stability of this version, as we have not been able to "properly" test it. It's tested, but only for a very short amount of time, then again, there were not a lot of changes.

As stated in the previous post, we have now posted detailed information about the implications of the migration of the user accounts from our HTTP server to our FTP server.

Today we moved the website from Sep's hosting company in Norway to webspace provided by Trace. We had several reasons for this move, but the main reason is the ping (latency) to Sep's host. As the distance was pretty large it made the website load noticeably slower than it did when it was hosted on our own box. This caused issues for parts of the site that had to communicate with the game servers.
Another reason is that recently we had some downtime and configuration issues, although as far as we know those are now resolved.

While we moved the website we also tweaked some small things like the server querier in the navigation plane. It now shows more up to date information about the map and the player count of the servers. First strike will be included as well as soon as the FS server is working again. Besides this we also cleaned up some unnecessary files, which aids us in future maintenance and development of the website.
Another major change is that we are moving away from hosting a HTTP server on our box. For this purpose, we moved most of the download and user data from our HTTP server to our FTP server. This implies some changes for those who are using webspace or FTP accounts provided by BlackIntel. Details about these implications will be posted on the forums shortly.

In the near future we will add a section for Battlefield: Bad Company 2. Gwynzer is currently working hard to compile a set of useful content for the website. For now everything BFBC2 related can be found on our forums.

The website problems have been resolved. Apparently, our host is migrating some part of their webservers, and our config was not properly migrated along. Everything should now be working again. :)

We are currently having some problems with the website, the forums are not working and attempting to access most pages will result in a "404: Not found" error message. We unfortunately have to wait for our host to fix the issue, we can therefore not give an ETA on when the website will be fully working again.

We are sorry for the inconvenience.

From the 3rd of March, BlackIntel will be supporting the new release Battlefield: Bad Company 2 as a server and clan section.



Due to the fact that DICE haven't released the dedicated server software (boo!) to anyone other than rental companies, we won't be able to host the game on our own serverbox, however we have managed to get a deal with Multiplay for a 32slot server, which will come online from the launch date. BlackIntel has had previous experience using Multiplay as they hosted the Ventrilo 3.0 Server and also a temporary Left 4 Dead 2 server for us.

Gwynzer will be leading the BFBC2 section, and also staying as section lead of the First Strike section due to the games being fairly similar, and that many of our current FS members will also be playing BFBC2 meaning there won't be much work for him.

Read the full news article for more clan information.
More...

It took us the entire day, but we finally left the datacenter and the server should be working again. Unfortunately, the main board broke, and we spent two hours attempting to get a proper replacement board but failed to find any. We therefore installed a board with two major disadvantages: the SCSI controller does not fit, hence some of our disks can no longer be connected. The other disadvantage is that it only supports two RAM modules, whereas we have 4. (2x 2GB and 2x 1GB). We can therefore only use 4GB currently.

We are sorry for the inconvenience and the infrequent updates, but ironically, we do not have WiFi access in the datacenter, and had to cope with the horrible speed of a mobile phone internet within a building with loads of concrete and metal. Even calling Ghostshaw and Goztow from there required us to leave the server room because there was not enough signal inside there... Sigh.

Ah well, we are done now. Temperatures are stable so we are confident it will no longer give problems. We will still have to determine what to do with the hardware we can no longer use.

It seems our server suddenly shut down today, but it never restarted. Currently we are in the dark as to what happened; we can not contact the server in any way. We will only be able to get more information at 9 AM GMT. We will keep you updated in this thread on the forums.


Temporary TS3 server has been setup for us available at this address: 188.40.87.145:9987

As you might have noticed, our Renegade section isn't really getting much players in the server. In order to (hopefully) improve this situation we asked Jelly for a higher nickname than our current A000000A. Jelly granted us the use of his a000000 nick.
This could help our server getting more players, but it will still need the support of our regular renegade players, you!

Oh, btw, thanks Jelly!

As was posted yesterday on the forums already, the server move was finished yesterday at around 13:45. We encountered no real problems so it could be done quickly. We're sorry for the inconvenience the downtime may have caused.