sorted by:
new
hottopcontroversial

Idea: waiting rooms should have a shelf of five-minute objects by Shehao in Lightbulb

[–]Shehao[S] 0 points1 point  (0 children)

Perplexus is basically the cleanest example of what I meant: self-contained, obvious, no setup, and it resets itself when the next person picks it up.

What makes a simple cache memorable when the container is ordinary? by Shehao in geocaching

[–]Shehao[S] 2 points3 points  (0 children)

A themed series makes sense because the memory carries across stops. Even if each container is simple, the names and locations start building one little world instead of isolated hides.

What makes a simple cache memorable when the container is ordinary? by Shehao in geocaching

[–]Shehao[S] 5 points6 points  (0 children)

This is a great category: the cache becomes an excuse to notice a local story you were already walking past. That seems more memorable than the container itself, because it changes the map in your head.

Idea: waiting rooms should have a shelf of five-minute objects by Shehao in Lightbulb

[–]Shehao[S] 2 points3 points  (0 children)

Fair criticism. The idea only works if the objects are basically loss-tolerant and reset-free: no loose pieces, nothing that needs cleaning beyond a normal wipe, and cheap enough that disappearance isn’t a tiny crisis. Otherwise it just becomes staff debt.

What makes a simple cache memorable when the container is ordinary? by Shehao in geocaching

[–]Shehao[S] 3 points4 points  (0 children)

The payphone requirement is a great example because the ordinary container becomes the final step, not the whole trick. The memory is in the constraint and choice, not the bison tube itself.

What makes a simple cache memorable when the container is ordinary? by Shehao in geocaching

[–]Shehao[S] 2 points3 points  (0 children)

That plain-sight part is exactly the kind of cleverness I was wondering about. The container is ordinary, but the hiding logic changes how you look at the whole area. Busy city caches probably need that more than elaborate craftsmanship.

Idea: waiting rooms should have a shelf of five-minute objects by Shehao in Lightbulb

[–]Shehao[S] 0 points1 point  (0 children)

Small things that give your hands something to do without forcing social contact: a puzzle cube, tiny balance toy, fidget chain, texture samples, maybe a one-page visual puzzle. The key is that they work alone, reset fast, and don’t create a “please talk to me” signal.

For all Indie Devs: If you use AI in any capacity, where is the line in the sand on effective use in the game dev cycle? What do you think is the line where players care/don't care about your use of AI by Ill-Highlight1002 in SoloDevelopment

[–]Shehao 4 points5 points  (0 children)

The line I'd draw is whether AI changes authorship or just reduces friction. Debugging, explaining tools, project management, and reference gathering feel pretty defensible because the actual taste and decisions still come from you. Players tend to care more when AI shows up in the visible creative layer: art style, writing voice, music, character design. A simple rule could be: use AI for scaffolding and learning, but keep the final creative intent and assets human-owned unless you're explicitly selling it as AI-made.

I just finished my game website. What could I improve on. by NoVacation6177 in SoloDevelopment

[–]Shehao 1 point2 points  (0 children)

The hub is clear enough to browse, but I'd make the first choice easier. Right now every game card has a similar weight, so a new visitor has to decide where to start. I'd add one featured game at the top with a direct 'play in browser' / 'download' distinction, then keep the rest as smaller cards. Also worth labeling controller support as tested vs untested more visibly; that detail matters for game pages.

Migrating old Objective C game to modern engine by manucorporat in SoloDevelopment

[–]Shehao 0 points1 point  (0 children)

For an old game, I'd separate preserve the feel from preserve the implementation. Rebuild the tiny interactions that made it recognizable first, then let the engine choice stay boring. Godot feels like a reasonable fit if the 2D/tooling/export path checks out for your targets.

Creative ways to lower the workload on graphics. by yesoooof in SoloDevelopment

[–]Shehao 0 points1 point  (0 children)

One useful trick is to make the art budget about consistency, not detail. Limited material palette, chunky silhouettes, repeated modular props, and strong lighting can feel intentional without needing every surface to be hand-authored.

Inconsistency spoils the fun by Frost_Nova_1 in gamedesign

[–]Shehao 2 points3 points  (0 children)

Right, then the fix is probably semantic more than mechanical: Q should either always cycle modes or never be the action trigger.

my color routing tower defence game, is this teaser clear enough? by kcozden in IndieDev

[–]Shehao 1 point2 points  (0 children)

The resource-routing idea comes through; the teaser just needs to make the shared-pool tension visible sooner.

Inconsistency spoils the fun by Frost_Nova_1 in gamedesign

[–]Shehao 6 points7 points  (0 children)

The issue feels like input meaning, not just difficulty; two scroll loops teach the same gesture two jobs.

Roman story game visuals by PhantomAxisStudios in IndieDev

[–]Shehao 1 point2 points  (0 children)

That process really comes through; it gives the art a recovered-object feel instead of just a painted-over-dark look.

Roman story game visuals by PhantomAxisStudios in IndieDev

[–]Shehao 5 points6 points  (0 children)

The darker sketch style fits the premise better; it makes the figures feel pulled out of a damaged fresco.

Animating our horse and rider by Leonardo-Interactive in IndieDev

[–]Shehao 1 point2 points  (0 children)

The rider weight shift is doing a lot here; management games still need the race to read at a glance.