HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
luanti-org
luanti
C++2013–2026
luanti-org / luanti

luanti

Luanti (formerly Minetest) is an open source voxel game-creation platform with easy modding and game creation

16Distinct people
17Mentions
0Explicit recommenders
13.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Luanti (formerly Minetest) is an open source voxel game-creation platform with easy modding and game creation

GitHub

Where it is used

No documented product use was verified in the last source check.

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 year17 dated mentions

Observed mentions: 2013-12-10 14:55:59 UTC to 2026-10-18 17:41:28 UTC.

01232013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC220
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

17 sources
I hope it does get fixed, but Apple actually has a bad track-record with another deprecated API, AppleAL (OpenAL). They broke it in a very interesting way in Tahoe where mono-channel audio on Aarch64 (not through Rosetta) did not play and it was broken through all the betas. I believe it actually may still be broken today. The workarounds were either mono-to-faux-stereo channel duplication or switch to openal-soft. OpenGL is an even bigger deal so I don't see a world where it doesn't get fixed, but I also thought exactly the same way with the previous issue. It seems that Apple does not have any older video games in their testing apparatus. Some references on the issue: 1. https://github.com/luanti-org/luanti/issues/16499 2. https://support.sega.com/hc/en-us/articles/39540396560145-Ma...
In macOS 15.8.2 Breaks OpenGL
Luanti (formerly minetest) is open source, written in Lua, has an API with mediawiki docs, and has a vscode extension: https://github.com/minetest/minetest Luanti wiki > Modding intro: https://dev.minetest.net/Modding_Intro SensorCraft is open source, written in Python, and is built on the Pyglet OpenGL library (which might compile to WASM someday) https://github.com/AFRL-RY/SensorCraft /? Minecraft clone typescript site:github.com https://www.google.com/search?q=minecraft+clone+typescript+s... /?hnlog minecraft: https://news.ycombinator.com/item?id=32657066 : > [ mcpi, pytest-minecraft, sensorcraft, ] mcpi supports "Minecraft: Pi edition" and "RaspberryJuice" (~ Minecraft API on Bukkit server) minecraft-pi-reborn is an open source rewrite of "Minecraft: Pi edition" that's written in C++. It looks like there's a glfw.h header in librebo
Read the rest
rn. Emscripten-glfw is a port of glfw which can be compiled to WASM. Glfw wraps OpenGL. Browsers have WebGL. MCPI-Revival/minecraft-pi-reborn: https://github.com/MCPI-Revival/minecraft-pi-reborn docs: https://github.com/MCPI-Revival/minecraft-pi-reborn/blob/mas...
In Approximating mathematical constants using Minecraft
In general, verifying programs is extremely hard, not just because of rice's theorem but because it's so easy to miss a spot, especially for non-trivial bytecode languages like lua's. wasm has no concepts of for loops for example. It's strange that after upstream has given up on the problem as it was too hard, factorio devs have chosen to try to fix the verifier/write their own (not sure which of the two they did). Minetest's loadstring function forbids bytecode entirely: https://github.com/minetest/minetest/blob/9a1501ae89ffe79c38... I wonder why factorio mods need the ability to execute raw lua bytecode. If they don't have it, there would be no need for a verifier. It's quite dangerous in the first place to execute lua code downloaded over the network. JS execution environments have gone through decades of cycles of discoveries of explo
Read the rest
its and fixes. Lua gets those as well but on a smaller scale, and with less staffing to improve security. The main protection is I guess that there is fewer people running malicious game servers.
In Bytecode Breakdown: Unraveling Factorio's Lua Security Flaws
> But it cant really present the million of other types of vulnerabilities, such as mis-configuration, wrong logic in the code, races, etc That's correct. The great achievement that Rust brings to the table is that it gives you the safety of a traditionally dynamic language like Java or JS with native performance. Let's look at it from a security angle. For some domains, the security that Rust provides is enough to create really safe solutions inside those domains. Think of PDF viewers, image viewers, browsers, etc. Here, it takes in untrusted input, parses it, and displays it to the user, and the codepaths where privileged stuff happens, e.g. reading arbitrary files, are only very sparse. In some domains, Rust alone won't be enough. Think of TLS implementations or kernels. Here, almost any logic bug is also security relevant. Ideally you
Read the rest
'd have computer proofs for their security. The language is largely irrelevant, all you need is support for your language in the proof tool. Now, let's look at it from a development angle: C requires you to manually malloc, free and check whether the malloc was successful. Rust does that for you, and although there are no "failible" allocators in the standard library, the language itself doesn't prevent you from writing your own containers etc. that do it, if you really need failible allocators. The bugs that Rust prevents are precisely those kind of bugs that are most annoying to debug. I'm very glad that I don't have to deal with stuff like this [1] or this [2] any more. For the second bug, it wasn't even a crash, it just had weird behaviour. Classical nasal demons. [1]: https://github.com/minetest/minetest/commit/57a461930ba13b0b... [2]: https://github.com/minetest/minetest/commit/1f76808e4fa5a198...
In Orange_slice: Research Kernel and Hypervisor in Rust
This is pretty cool. Props for doing a massive amount of work and creating something open and extensible. -- I just tried reading the code to learn how MineTest does voxel meshing, and it didn't go so well. (Voxel meshing is about turning blocks into triangles efficiently, and it's surprisingly tricky. Mikola Lysenko wrote a great exposition of the problem and several solutions way back in 2012: https://0fps.net/2012/06/30/meshing-in-a-minecraft-game/ ) I was curious which approach MineTest chose, and I still don't know. I think I found the files where the meshing happens, mapblock_mesh.h/cpp. The code quality is... less than perfect. There are 200+ line C++ functions. There's commented out code and preprocessor "#if 0" ignored code. There's a struct that looks important, but it's called "MeshMakeData", and I don't know what it represents
Read the rest
. The comment above just says "Mesh making stuff": https://github.com/minetest/minetest/blob/0a16e53b40d347db7d... The file that seems to run everything, game.cpp, is almost 5000 lines long. -- For an example of really clean game code, check out Quake or Doom 3. Both have: * short and sweet main() methods * comments that guide the reader and explain what does what * clean decomposition * short, readable functions, and... * reasonably small files So far, MineTest, at least in part, took the "big hairy ball of C++" approach. Good luck with future development!
In Minetest – A free, open-source voxel game engine and game

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

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.