Welcome to our first Monthly Dev Post. Every month one of these posts will be created, to tell you about the latest developments in the world of OpenTTD.

Development

We have been busy the past few months, and development activity has seen a significant increase since the move to GitHub last year. We are approaching our next release, and while this has never been a fixed date, we intend to keep our streak alive to release 1.9.0 on April 1st 2019. (There is currently a debate on whether we can keep that up, we’re currently expecting to accelerate our releases to give you new features more often) Currently we are on our third beta and, if all goes to plan, a Release Candidate (RC) will follow soon. Please test these extensively, so we can make sure the final release will be as bug-free as possible

Highlights

There were many changes this month, but here are a few of the notable contributions that were merged into the master branch in the last month that will appear in 1.9.0:

A more detailed changelog can be found on the download page for our latest beta

NewGRF

The following things will not be part of the 1.9 release, however we’d quite like to get feedback about it from NewGRF authors, so we’re announcing it before the changes are made final and put into the master branch.

The first one is additional information about railtypes, covered in Pull Request #7000, which aims at things like making dual mode vehicles feasible Var4A gets additional information about the railtype the vehicle is on, like speed limit and whether it has a catenary on top. This should allow for graphical changes like whether or not pantographs are raised. Ideally, you would not only be able to query the speed limit of the railtype, but a collection of all speed limits currently affecting the train (like bridges, curves, station approach, etc.) and whether the train has reached any of these. If you have ideas how to use this in a set, please tell us. A new 60+ var is introduced that lets you query the “vehicle is powered” flag as if the vehicle is made for a different railtype With this, you can implement dual power vehicles without knowing all the railtypes present. just ask “if this were an ELRL vehicle, would this vehicle be powered?” On a more general level, introduce a new method to have global variables (in the 00-3F range for Varaction 2, or the 80-BF range for Action 7/9/D) with parameters (similar to variables in the 60-7F range) with this new method, a way in action D to detect whether two railtypes you listed in your railtype translation table were actually mapped to the same or different railtype in the game If for example a railtype GRF according to the Standardized Railtype Scheme is loaded, you can detect this way if different weight classes are modelled in the GRF, or if they are all mapped to the same basic railtype. Then you can set vehicle availability e.g. for heavier wagon loads accordingly, to avoid useless duplicate wagons.

The second one is a change to how vehicle introduction works, covered in Pull Request #7147 In the current system, each vehicle gets its own lifespan (randomized introduction date, reliability curve, retirement date) with the proposed change, all vehicles that get introduced on the same “raw” introduction date get the same randomized values So if you e.g. have a 2-car EMU and a very similar 4-car EMU, you can put them on the same introduction date, and their prototypes will be offered at the same time, they will reach the same peak reliability, and they will go out of service at the same time. Also, you can make all freight wagons of the same generation appear on the same date. If you want to introduce vehicles in a similar timeframe, but they don’t need to share the same introduction date and reliability curve, then you can set their “raw” introduction dates very closely apart (in 1 day increments), and it will get different random values (the game will round the final introduction date up to the next full month, so moving the date by 1 day should have no notable difference)



If you want to give feedback to these proposals, like ideas how to use these in a NewGRF, or further requests, or maybe you see a problem with these changes, please reply to the Issues on GitHub or on the NewGRF Development Forum

Infrastructure

Our infrastructure monkey probably had the hardest piece of work during the past few months, please give him a Banana when you happen to see him.

Our first beta since GitHub migration

We had our first (and second, and third) beta in February. This was a test of the new infrastructure. Azure-Pipelines now generates our releases, which are published on the CDN of DigitalOcean. Our main webpage links correctly to the new infrastructure for this new beta. Many issues were found and solved during this process. A second beta was needed because of a (network) game breaking bug found in beta1 immediately after release.

Building Pull Request / Patch Packs

We produced the first binaries for a Pull Request, in a safe (in infosec terms) way. This took a huge effort, and was what we have been building up to for the last 6 months. This also means we can build and publish PatchPacks now. If you are interested in building and/or publishing your own PatchPack, please contact TrueBrain how to do that (short answer: Azure Pipelines and our CDN are at your service).

Migration to DigitalOcean

We are still on the slow process of migrating everything to DigitalOcean. We make now use of their managed Kubernetes cluster, and switched this month to their CDN. This last change has been a huge step in the migration towards DigitalOcean. The latest downloads (1.9.0-beta3 and nightlies) are now on the CDN. This should drasticly improve download speeds for most people, and increase availability in general.

On OpenTTD/website#48 we are having a talk about how to create the new ‘finger’. The old way of doing is no longer really viable (as it was not maintainable), and we are now looking into new ways to give tools access to all available downloads. We are looking for people that use finger.openttd.org , and are interested in helping out what would work going forward. So far the solution has been a low-tech listing.txt , but building REST APIs or others solutions are up for discussion!

Ponies

A “pony” is a personal pet project of a developer or community member. This section will be used in the future to showcase a project in detail.

Participate yourself

Do you have an interesting Project you are currently working on in relation to OpenTTD? These Monthly Dev Posts are prepared in a branch on our GitHub website project before they are made public on the website. As soon as you are whitelisted as a contributor, it’s as simple as editing the file in the web interface. If you are not a contributor yet, drop by on IRC to become one (make sure you have a GitHub account).