Show HN: I remade Mortyr's 2093-1944 engine using my own programming language
Hello, HN! Today I want to show my recent project called PanzerMortyr . It's a reimplementation of the engine of the game Mortyr 2093-1944 ( https://en.wikipedia.org/wiki/Mortyr ). The most interesting thing about it is that it's written in my own programming language named Ü, which I developed previously and continue developing. See https://news.ycombinator.com/item?id=45769161 , https://github.com/Panzerschrek/U-00DC-Sprache/ . I have spend almost a year developing PanzerMortyr . It took a lot
Read original source
Source record
Recorded metrics
points · 1 votes
2026-11-04 14:45:08.667Z
cumulative since publication
Research analysis
Project record
Repository: Panzerschrek/PanzerMortyr. Source account: Hello, HN! Today I want to show my recent project called PanzerMortyr . It's a reimplementation of the engine of the game Mortyr 2093-1944 ( https://en.wikipedia.org/wiki/Mortyr ). The most interesting thing about it is that it's written in my own programming language named Ü, which I developed previously and continue developing. See https://news.ycombinator.com/item?id=45769161 , https://github.com/Panzerschrek/U-00DC-Sprache/ . I have spend almost a year developing PanzerMortyr . It took a lot
Observed adoption & comparisons
Source votes: 1 votes (Nov 4, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Nov 4, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “[分享创造] Eavesong - 一个观察自己产品讨论度的自部署服务” (V2EX, Nov 6, 2026); “[分享创造] 做了个开源的「自动日记」： Beayy 在后台记下电脑、手机、手表上的一天，每晚写日总结” (V2EX, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.