WeSearch
What reversing, modernising old games tells us about the economic impact of AI

What reversing, modernising old games tells us about the economic impact of AI

Georg Zoeller· ·35 min read · 0 reactions · 0 comments · 9 views
More from Georg's Blog ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

It took about a week, primarily because I can only run a single lane on my workstation due to VRAM constraints, but it got the job done: Faithful reproduction of rendering and game rules in a new Three.js rendering engine. A few days ago I started modernising it into a Total War meets Heroes of Might and Magic like experience that you could actually play without getting a UX aneurysm. But doing so while keeping the original “underneath”.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 6,569 of its stories.

Original article
Georg's Blog · Georg Zoeller
Read full at Georg's Blog →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGeorg's Blog
Canonical URLhttps://this.os.isfine.org/blog/posts/what-reverse-engineering-and-modernising-an-old-war-game-tells-us-about-the-econ/
Publication timeSat, 26 Sep 2026 23:49:01 +0000
Retrieval time2026-09-27T00:00:40.228Z
Last seen2026-09-27T00:00:40.228Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterIc-LDfvlgSNp · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

September 4, 2026 on LinkedIn What reverse engineering and modernising an old war game tells us about the economic impact of the transformer retro games Game Development Artificial Intelligence Reverse Engineering Some observations from my War of the Lance (1989) Code Harness assisted modernisation (WIP) I gave Qwen-3.8-Flash-Next a job: Reverse engineer and port War of the Lance (1989) to modern browsers. It took about a week, primarily because I can only run a single lane on my workstation due to VRAM constraints, but it got the job done: Faithful reproduction of rendering and game rules in a new Three.js rendering engine. A few days ago I started modernising it into a Total War meets Heroes of Might and Magic like experience that you could actually play without getting a UX aneurysm.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Georg's Blog.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Georg's Blog