The first bugfix release of the 0.7 series. As usual it fixes lots of bugs and adds a few AI related features (primarily in the API).
Some changes made our handling of AIs more strict which means that some AIs might not function as expected anymore.

Today we have released the third release candidate for 0.7.1. We hoped to release 0.7.1 a few days ago, but some testers found some bugs that were important and non-trivial enough to delay the final release and release another release candidate.

Today we have released the second release candidate for 0.7.1. It contains fixes for a few (very unlikely) desyncs and an assortment of other small fixes.

Today the first release candidate for 0.7.1 has been released. About half of the changes are improvements/fixes for the NoAI API. The rest is an assortment of small bugfixes, but nothing serious.

As many might (or might not) know the number of free IPv4 addresses is nearing it's maximum. Many experts expect that the IPv4 addresses will be exhausted within a few years. As a result of this IPv6 was developed about a dozen years ago. Since 2008 all major OSes have support for IPv6 and (some) ISPs are starting to offer IPv6 addresses. This meant that we had to start thinking about IPv6 support.

This has resulted that a few weeks ago we started making all OpenTTD services accessible over native IPv6, graciously provided by LeaseWeb for which we want to thank them. We also added IPv6 support to the development versions of OpenTTD (the nightlies and trunk) so they are capable of handling both IPv4 and IPv6 side-by-side. At the moment of writing approximately 30% of the servers with an OpenTTD version supporting IPv6 are reachable over IPv6. Even if we look at all servers 3% is reachable over IPv6 (average IPv6 penetration is around 1%).

All in all this means that 0.8.0 will support IPv4 and IPv6, although it will still take a while before we release 0.8.0, and that you can reach all OpenTTD services over IPv6, so no need for IPv4 anymore.