11–20 of 28 posts
Beautiful game, thanks for sharing. Koblas's comment caught my eye and I will definitely be poking around the github actions code to learn how to compile Golang to WASM.
Thank you! Go makes it ridiculously easy: GOOS=js GOARCH=wasm go build -o web/game.wasm
More build info here: https://ebitengine.org/en/documents/webassembly.html
The ship just gets stuck on the end of lvl 2.
For me the third level does not load on the web version. The ship just gets stuck on the end of lvl 2.
You probably did it to try Go, wasm and ECS and I understand that, but if you to make a game seriously, you should have stopped much earlier. In the early stage of the game development you should made 5-10 prototypes using different tech/frameworks and use the best one. I seriously don't see Go+wasm+ESC being the best one for this kind of game.
How can you not go insane if you have to wait 20s for every page refresh.
IMO you chose wrong tech for the job. It is very simple 2D game yet it starts 5s on my desktop and 20s on my phone. If I would to make a simple game and even simplest program starts 20s I would stop right there and choose different technology. You probably did it to try Go, wasm and ECS and I understand that, but if you to make a game seriously, you should have stopped much earlier. In the early stage of the game dev…
A lot of native games take longer than that to load.
IMO you chose wrong tech for the job. It is very simple 2D game yet it starts 5s on my desktop and 20s on my phone. If I would to make a simple game and even simplest program starts 20s I would stop right there and choose different technology. You probably did it to try Go, wasm and ECS and I understand that, but if you to make a game seriously, you should have stopped much earlier. In the early stage of the game dev…
Thinking about what would be the most efficient engine for the game would kill all the fun for me and the project wouldn't exist. :)