# Techmino: a falling block game in Lua, shipped for five platforms > Techmino is a Lua falling block game from 26F-Studio that collects various modern block game rules and more ways to play, and publishes itself as an APK, an AppImage, Windows archives, macOS disk images and an iOS app from the same repository. The last tagged release is from 2024, while the repository itself is still being pushed to. **26F-Studio/Techmino** — Techmino:方块研究所唯一官方仓库(Github) - Repository: https://github.com/26F-Studio/Techmino - Website: https://www.studio26f.org - Stars: 921 · Forks: 88 - Language: Lua - License: LGPL-3.0 - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/26f-studio-techmino ## A block game written in Lua and published everywhere Techmino is the official repository of Techmino, from 26F-Studio, described in the README as a collection of various modern block game rules, more ways to play, and some new things added for a new experience. The project description in Chinese names the studio, and the primary language of the repository is Lua. The interesting engineering fact is not the game but the distribution. The download table at the top of the README lists a direct download for every platform: an Android APK, a Linux AppImage, a Windows x86 zip, a Windows x64 zip, a macOS portable dmg, a macOS portable pkg, and an iOS build distributed through the App Store and TestFlight. That table also lists a mirror download for each of them, pointing at the same release assets through a proxy domain. Providing a mirror for every artefact is not something a hobby project does by accident; it says the audience includes players who cannot reach GitHub's release storage reliably, which is consistent with the project's own geography and with the presence of an AUR package and a Gitee mirror of the source. The project is also mirrored on Gitee, and the platform badge in the header lists Android, iOS, Linux, macOS and Windows. The audience is players on any of those, and the maintainers on GitHub and on Gitee. ## main.lua, conf.lua and the parts directory The repository layout is compact and tells you how the game is structured. The top level entries are .editorconfig, .gitattributes, .github/, .gitignore, AGENTS.md, Zframework/, conf.lua, legals.md, license.txt, main.lua, media/, parts/, readme.md, updateLog.txt and version.lua. main.lua and conf.lua are the two files every Lua project of this kind has, the entry point and the configuration. The parts/ directory is where the game's content lives, the rules, the pieces and the modes that the description refers to when it talks about a collection of various modern block game rules and more ways to play. media/ holds the artwork and sounds. version.lua holds the version, and updateLog.txt holds the changelog, which for a game is the document a player actually reads. Zframework/ is the piece that deserves attention. It is a framework directory inside the game repository, which suggests the author treats the game as a host for a general framework rather than as a single self-contained script. A framework of that kind usually provides the loop, the input handling, the scene management and the rendering, and the game is then written on top of it. The presence of AGENTS.md is also telling for a project in this shape. It is the file that tells automated coding agents how to work in the repository, and its existence in a game codebase of this size says the project expects contributions from tools as well as from people. ## Installing from the AUR or from the release assets There are two practical routes for a Linux user, and one for everybody else. The README carries badges for two Arch User Repository packages, techmino and techmino-git. The distinction is the usual one: the first tracks a released version and the second tracks the source tree, so the git variant is what you want if the repository has moved ahead of the last tag, which the release record suggests it has. For everyone else, the release assets are named consistently per platform: ```text Techmino_Android.apk Techmino_Linux.AppImage Techmino_Windows_x86.zip Techmino_Windows_x64.zip Techmino_macOS_portable.dmg Techmino_macOS_portable.pkg ``` Each of those is linked both directly and through a mirror, and the direct links point at the latest release rather than a numbered one, so a download always gives you the current published build. The naming is worth noting for one reason: the Windows build ships as x86 and x64 as separate archives rather than one installer, and the macOS build ships as both a dmg and a pkg. That is the shape of a project that produces its own artefacts in CI for every target rather than shipping one installer that happens to work everywhere. The iOS build is distributed separately through the App Store and through a TestFlight link, which is the normal arrangement for a mobile release and means iOS users do not install from the repository at all. ## Two years of commits after the last tagged release The release list is short and the dates are the story. The recent releases are v0.17.21 on 2024-08-08, v0.17.20 on 2024-08-07 and v0.17.19 on 2024-08-03, and the titles of the first two include a question mark and the word Break, which reads like the author signalling that the release line was being paused. Meanwhile the repository is not archived, and the last push was on 2026-09-16. So there have been commits for roughly two years after the last tagged release. That gap has direct consequences for anyone building from source. The AUR techmino package tracks a released version, so it will give you 0.17.21 or whatever the AUR maintainer last packaged. The techmino-git package tracks the source and will give you code that is well ahead of any tag. There is no third option that gives you a numbered, dated build of the current work, because there has not been one since August 2024. The README also lists the surrounding infrastructure as being in flux. The official website is marked as under reconstruction, the community hub site is marked as unofficial and under construction, and the GitHub wiki is marked as paused. When the wiki is paused, the updateLog.txt file in the repository and the releases page become the primary changelog, which is why they are at the root of the tree rather than buried in a docs directory. ## Licensing, donations and the surrounding sites The licence field on the repository says LGPL-3.0, and the tree carries both license.txt and legals.md at the root. Having a separate legals.md next to the licence is a pattern you see in projects that ship third party content, where the licence of the code and the terms of the bundled assets are different documents. That matters for a game. The repository contains media/ with the artwork and audio, and the project may also include content with its own terms. The LGPL covers the code, and legals.md is where you would look for what governs the rest. The funding section is a PayPal donation button with a note, translated in the README, that a payment method was opened as a trial, that you should keep your own record of the payment, and that there may be some benefits in the future, not guaranteed. That is an unusual amount of candour for a donation section, and it is worth reading as written rather than as a promise. The last thing in the README is a 500 Stars poster image, a celebratory artefact committed to the repository when the project passed that milestone. It is a small indicator of the project's community size and of how the repository is used, and it is the kind of file that sits in the tree permanently without affecting the build. ## Conclusion Techmino suits a player who wants a falling block game with a large rule set across desktop, mobile and iOS from one project, and a developer who wants to read a Lua game codebase that ships as a native application on five platforms. It does not suit a team that needs a tagged release to build from, since the newest tag is v0.17.21 from 2024-08-08 while the repository still receives commits. Before adopting, download the build for your platform from the releases page and check the updateLog.txt file for what changed since 0.17.21, and read license.txt and legals.md in the repository root, since the LGPL terms and the third party content declarations are both in the tree. ## FAQ ### What is Techmino and what language is it written in? Techmino is the official repository of the Techmino project from 26F-Studio, described as a collection of various modern block game rules and more ways to play. The primary language of the repository is Lua, with main.lua, conf.lua and a parts/ directory at the top level. ### How do I download Techmino? The README lists direct and mirror downloads for each platform: an Android APK, a Linux AppImage, Windows x86 and x64 zips, macOS dmg and pkg archives, and an iOS build through the App Store and TestFlight. Arch users can install the techmino or techmino-git AUR packages. ### When was the last Techmino release? The recent releases are v0.17.21 on 2024-08-08, v0.17.20 on 2024-08-07 and v0.17.19 on 2024-08-03. The repository is not archived and the last push was on 2026-09-16, so the source tree is well ahead of the newest tag. ### What licence does Techmino use? The licence field on the repository says LGPL-3.0, and the root of the tree contains both license.txt and a separate legals.md, which is where the terms for bundled third party content are recorded. ### Where can I find the changelog for Techmino? The changelog is in updateLog.txt at the root of the repository, alongside version.lua. The README marks the GitHub wiki as paused, so the repository file and the releases page are the primary sources of release history. ## Sources - [26F-Studio/Techmino on GitHub](https://github.com/26F-Studio/Techmino) - [License: LGPL-3.0](https://github.com/26F-Studio/Techmino/blob/main/LICENSE) - [Project website](https://www.studio26f.org) - [README](https://github.com/26F-Studio/Techmino/blob/main/README.md) - [Releases](https://github.com/26F-Studio/Techmino/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/26f-studio-techmino