What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Why choose GDScript over C#, which models handle better and may use fewer tokens?From this comment
- Which models generate the 3D assets, given models are usually weak at spatial reasoning?From this comment
- What does the development loop look like, and were there shorter paths to the goal?From this comment
- How are assets handled, since that pipeline is the hardest part, and is there a version for another engine?From this comment
- How much context do all those skill files consume versus actual user input?From this comment
What they doubted or pushed back on our summary
- The demo games look lifeless, with weak physics and clumsy character movement, so a playable build is wanted.From this comment
- An attempt to build a Godot RPG with agents failed completely, despite prior success in known domains.From this comment
- The demos undersell the work, but output quality resembles AI slop, and a better tool-like harness is needed.From this comment
- Demos are not real games; they are incomplete and weaker than basic engine examples, so claims are overstated.From this comment
What the maker answered our summary
14 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- GDScript was chosen as Godot's default with better docs, examples and engine integration, though C# will be tried.From this comment
- Assets are a large part of the pipeline, with 2D art converted to 3D and animation still a gap.From this comment
- The demos are raw single-run output meant to prove the pipeline, with a polished playable game planned.From this comment
- The project closes the feedback loop agents lack by letting them verify rendered output instead of blind code.From this comment
What a builder can take from it: Builders should ship a polished playable demo, since reviewers judge raw single-run output harshly regardless of the pipeline behind it. our reading
The title, taken apart our calculation
This post got 337 points; the median for all 1442 posts is 112. In AI and agents (352 posts) the median is 108 points and 49 comments.
When it was posted our calculation
Monday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Mondays it was 3.1% of 7,396. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More AI and agents teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with