Above all, this exercise should be transferable to other projects.įull Disclosure: I am not an OpenTTD contributor, nor am I a community member. Instead, I will pick and choose the key ideas that an aspiring contributor may want to dig in to. It's not practical to take apart over 200,000 lines, especially for an actively developed project. This project deviates from my usual practice of documenting every line of code. Add an active, intermediate-difficulty project to my library of decoded work.Share steps that beginners can follow to take apart any large open-source project.(alongside Outpost, and Global Domination - thanks, dad!) I lost many hours playing this after opening it for Christmas in 1994. In this post, I want to explain in a bit more details how we got here and how it works.OpenTTD is a free, open-source recreation of the Chris Sawyer masterpiece: Transport Tycoon. Well, I guess in a sense this post is also a fundraiser )Īs you might understand, this changes the multiplayer experience drastically, and we felt that waiting 6 more months to deliver that to you is not fair.Īs a result: we are releasing 12.0 early! If this changes, we will let you know, and run some kind of fundraiser. This currently covers our infastructure cost, and we currently foresee no issues going forward. Thanks to many of you, we see regular donations. The above will just work, for everyone, as long as you have a working Internet connection.ĭepending on your connection, there are some extra infrastructure costs to us, but we hope to cover that increase with donations. There is no need to setup port-forwarding, or anything like that. Playing together are now just four simple steps:Ģ) You set the server to invite-only or public.ģ) You share your invite-code with your friend.Ĥ) Your friend joins your server based on the invite-code. You no longer need to configure anything in your home network. In summary: 12.0 makes setting up multiplayer games painless. With 12.0 in feature-freeze, it is time to talk about what is in 12.0, and why we release early. This means more trains can go through the same area at a time. Other trains can still go into the same area, as long as they won’t touch the reserved pieces of track.
When a train wants to pass a path signal, the path signal finds a way to where the train is going, and blocks off (reserves) just those pieces of track. When a train wants to pass a block signal, the train asks the block signal to find all other signals on the other side, and turn them to red. It was the only type of signal in the original game, and if we removed them, then old saved games would stop working.Īs for why path signals are generally better than block signals, the reason is that path signals don’t reserve entire blocks, but only pieces of track. The simple answer is, because they always were there. One question would then be, if path signals are better, why are block signals then in the game? The reason for hiding the block signals by default is to make it easier to choose a signal.įor almost all players, path signals are the easier choice, that will cause fewer issues in your network. This is the one change in version 12 that has by far caused the most questions everywhere, so let’s talk a bit more about it, and show some examples of simple signal setups for path signals. It was implemented in pull request #8688, for those who want to see the development history. In OpenTTD version 12, we changed rail signals building UI only shows the Path Signal types by default.
0 kommentar(er)
