itch.io

Thanks, this is useful. The "too long / needs headers" point is fair. I was trying to answer trust questions in the page, but I can see how it turns into a wall of text. I’m going to tighten the first screen and make the sections easier to scan. On the free-demo-download problem, I’m seeing the same thing so far: "free" does not create action by itself. My current read is that people still need a very fast answer to three things: 1. Is this for my exact situation? 2. What do I get in the first 30 seconds after downloading? 3. Can I trust/inspect it without wasting time? For asset packs, I would probably make the first screen show one concrete use case, one actual in-engine preview, and one tiny sample of what is inside before the longer description. Then I’d watch referrers/views/downloads separately, because if views are low the page may not be the real problem yet.

I published Godot 4 Next Fest Demo Shell on itch.

It is a small Godot 4 asset pack for the point right before a public demo: gameplay is working, but pause, settings, input remap, demo reset, feedback, store CTA, and build stamp work still needs to be finished.

It includes:

- Pause menu scene.
- Settings menu with fullscreen/windowed, VSync, and master volume.
- Keyboard and controller remapping with conflict messages.
- Controller-family labels.
- Confirmed demo reset flow.
- Feedback link and wishlist/store link hooks.
- Visible build/version stamp.
- Install guide, 5-minute integration checklist, QA checklist, changelog, and commercial-use license.

It is not Steamworks integration, not a full save framework, and not a full UI skin. It is plain Godot scenes and GDScript you can inspect and edit.

Free to inspect fit; suggested donation is $5 if it saves one integration session before a public demo or playtest.

Page:
https://shipkitstudio.itch.io/godot-4-next-fest-demo-shell

Runtime proof media: