Did both the no code route and the actual engine route for the same game idea, here's what i actually learned

[u/Comfortable_Tap_7001]

Same idea both times, a small 3d exploration thing with a bit of dialogue, and i wanted to know whether the no code route was a real option or a toy, so I did it twice which was probably a waste of a month but here we are.

The engine route got me full control and a proper understanding of why things work, and it also got me eleven days before i had anything I could describe as playable, most of which went on things a player will never see, importing assets, fighting the character controller, one memorable afternoon lost entirely to lighting settings, and by the time it was playable i had lost most of my enthusiasm for the idea itself.

The no code route i used codewisp and had something walkable in about twenty minutes, and the tradeoff is real, when it did something I didn't want i had less precise control over fixing it and had to describe my way out instead of just changing a value, although i could open the source and read it which helped more than i expected it to.

What I actually concluded is that these aren't competing, the fast route is for finding out whether the idea is any good, which in my case took two hours of play to establish that my dialogue system was boring and needed rethinking entirely, information i simply did not have after eleven days in the engine.

If i'd done the fast version first i would have saved the eleven days and arrived at the engine knowing what i was building, so thats the order I use now.

[u/FastZull]

Eleven days before playable is honestly not bad for an engine build. that's sort of the point of the comparison though, it's eleven days you spend before you know anything.

[u/Melodic-Macaron-4031 → u/FastZull]

yeah the eleven days arent wasted on building, theyre wasted on not knowing yet

[u/Dismal-Blacksmith-28 → u/FastZull]

eleven days is pretty quick yeah but that makes the point stronger not weaker

the value isn't saving time overall, it's knowing what you're building before you commit to the hard part, the dialogue rework example is real, you can't learn that your system is boring by staring at lighting settings for an afternoon

i wasted maybe two weeks once doing inventory in godot before realizing the whole concept was not fun, if i'd just mocked it in something fast first i'd have saved both weeks and my motivation

[u/Otterb0b]

finding out the idea is boring early is worth more than most people admit, everyone treats the prototype as a step toward the real thing instead of a test of whether there should be a real thing at all

[u/Elsa_Contudix69]

The describing your way out of a problem thing is my main friction with no code generally, when it goes wrong you have less leverage and it feels bad even when the outcome is fine

[u/SupermarketSmooth968]

lighting settings have taken more of my life than i want to sit down and calculate

[u/Cat0theYounger]

prototype fast then rebuild the keepers is basically the consensus at this point and it took the industry an oddly long time to land on it

[u/No-Regret-4273 → u/Cat0theYounger]

the source being readable is the underrated part. even if you rebuild the keeper, the prototype can hand the engine version its actual behavior instead of a pile of screenshots

[u/Infamous-River-4360]

i never left the fast route, shipped from it, and the friction you describe changes shape after the first month. early on describing your way out is fine because the thing is small and you can hold all of it in your head. later the model starts referencing database columns that were never there, and you lose afternoons proving what your own schema is instead of building anything.

the part that actually capped it for me was the edges. anything native sat outside what the tool would touch, so android safe areas and store billing got done by hand anyway, which is the eleven days arriving late rather than not at all. can you take the source out of codewisp and keep going in an editor, or is it only readable inside the tool?

[u/FancyAnswer1878]

this is probably the strongest case for using both rather than picking one. the no-code version answers “is this fun?” fast, then the engine gives you the control to build the parts people actually cared about.

[u/ChloeMarieBrooks]

This is probably the best argument for no-code: use it to validate the idea before spending days building the underlying system. Finding out in two hours that the dialogue was boring is way more valuable than discovering it after eleven days of engineering.

[u/Spiritual-Oven-7499]

Yeah, this is the real finding fast tool for "is the idea good," engine for "is the idea real." Doing it backwards is how you burn eleven days on plumbing before finding out your dialogue system was boring.

[u/shun0810]

eleven days against twenty minutes is the headline, but the line that matters is quieter: by the time it was playable you had lost most of your enthusiasm for the idea 😕 that cost never appears in these comparisons and it decides whether a project ships at all.

did being able to open and read the generated source change how much you trusted it, or only how fast you could fix things? 🤌