Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

Wow, thank you for the reply with such details!

Sure, I'll take notes from that.

Because currenly I'm thinking should I create new page for one of the game from game jams and do everything from scratch ,just keepig the idea. Or maybe do all the updates to the original page, but keep legacy build(exe) as option if someone would like to play it.

(1 edit) (+1)

Glad to help. 

If it is an exe, you can keep it in the same page, that's even better. At least initially.

There's a sweet spot of complexity of a page.
Ideally people only find relevant stuff, better to progressively move old information out of the page.

Clean up old staff it's also interesting suggestion.. No one needs old not relevant info, people most likely came to play the game, not digging the artifacts.

(1 edit) (+1)

All that said, I would strongly recommend you do webgl builds, whenever possible.
Sometimes it is even worth sacrificing features, just to get people playing your game.

Yeah, sure. Agree on wbgl builds. I do Godot as well, so no problems there.

Sacrificing features is interesting btw... I mean in the way, for example if there some hard staff to process or draw, maybe it worth to cut it on web builds but remain for os builds.

(+1)

It helps thinking about quality settings. 
Webgl is your low specs target: If it runs in webgl, it runs everywhere.