HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
OpenTTD
OpenTTD
C++2018–2024
OpenTTD / OpenTTD

OpenTTD

OpenTTD is an open source simulation game based upon Transport Tycoon Deluxe

Games & EmulationScience & EngineeringSecurity & Privacy
Explore on GitHubRead Hacker News discussions
9Distinct people
9Mentions
0Explicit recommenders
8.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

OpenTTD is an open source simulation game based upon Transport Tycoon Deluxe

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2018-02-05 11:35:20 UTC to 2024-02-11 17:07:32 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

What Hacker News says

9 sources
michalc·Feb 11, 2024
I thought it was time I got off my... and starting making an AI (https://github.com/michalc/SupplyChainLabAI - but it does nothing but log a debug message repeatedly at this point, I feel I have a long journey...) But it makes me realise there is another use case for OpenTTDLab that I don't think I considered: regression tests for OpenTTD AIs? Edit: And it has been mentioned to me separately that maybe it could be used as part of regression tests of OpenTTD itself https://github.com/OpenTTD/OpenTTD/discussions/11863#discuss...
In OpenTTD
tony·Jan 26, 2020
If you are interested in the code behind bitmaps / pixel sprites that scale, pan, and zoom, I'd like to offer up OpenTTD. https://www.openttd.org/ Specifically, Viewports, Blitter and Resize handling: Viewport: https://github.com/OpenTTD/OpenTTD/blob/1.9.3/src/viewport.c... Window resizing: https://github.com/OpenTTD/OpenTTD/blob/1.9.3/src/video/sdl_... Zoom: https://github.com/OpenTTD/OpenTTD/blob/1.9.3/src/main_gui.c... OpenTTD is interesting because it can have multiple "cameras" following objects on the screen. e.g. a viewport can be opened to follow a bus or train, zoomed in, while the main viewport is zoomed out. Also I'd like to recommend aseprite (https://www.aseprite.org/), which has even cleaner code with zoom / panning / etc. The GUI itself is also pixel art: https://github.com/aseprite/aseprite/blob/v1.2.16.3/src/rend..., http
Read the rest
s://github.com/aseprite/aseprite/blob/v1.2.16.3/src/app/..., https://github.com/aseprite/aseprite/blob/v1.2.16.3/src/ui/v...
In Responsive Pixel Art
git-pull·Jul 7, 2019
1. Clone the source 2. Try to build it 3. If there are tests, try to run them Just from doing this many times over, I learned a lot about programming. Also fork the repo, then do `git clone <url>` for the original repo, `cd repo`, then do `git remote add yourusername <yourgithubforkurl>` To ease the above process, I created vcspull: https://vcspull.git-pull.com Here is an example of my vcspull file: https://github.com/tony/.dot-config/blob/master/.vcspull.yam... This also helps studying, read code, and also do open source in general since it's easy to setup the original repo and the fork. For generic open source: Download source, check README.md/rst to see if they are testing/development instructions. Check .travis.yml commands, those are showing what packages/steps are taken to build and probably test the code If it's node: do `npm insta
Read the rest
ll` and check the "scripts" in the package.json. Those commands can be run like "npm run <task>" If it has CMakeLists.txt, it uses CMake. Download and install cmake, then do `cmake .`. cmake will let you know if you're missing libraries and those are easy to google package names for. Then `make && [sudo] make install` If it has Makefile.am/autogen.sh... download and install autotools/autoconf/automake. Run `./autogen.sh`, then `./configure` (google for package names of any libraries that show missing headers, .h, or symbols). Then `make && [sudo] make install` If it is python, and there's a Pipfile, download and install pipenv. Then do `pipenv install .`. If it has requirements.txt, `pip install -r requirements.txt` Carried foreward, if the project has anything resembling a package manifest (e.g. Gemfile, composer.json) google them to find the appropriate package manager for your OS. That gets you 75%-100% of the way to running locally a lot of the time. For the more complex projects, they typically have dedicated setup instructions and sometimes very detailed overviews (e.g. https://github.com/OpenTTD/OpenTTD/blob/master/docs/Readme_W..., https://devguide.python.org/setup/, https://www.kernel.org/doc/html/latest/process/index.html) Reading the source of your favorite interpreted programming language can be rewarded, e.g. https://github.com/python/cpython
In Ask HN: How do you read and understand an open-source project?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.