Skip to main content

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

Wow! I can tell that you put a lot passion to build the game. It is very detailed and has deep complexity.

I would suggest to create a small sample level with less options and simplify the UI a bit, it was quite difficult for me to understand the mechanics. I give it a few tries but the Windows build keep crashing at some point, I will probably try the Linux build as well to check how it goes :).

Very impressive overall! Well done!

(+1)

Thank you very much for your generous feedback!

I would be very grateful to know where (or in which context) the game was crashing for you, since that is something the other commenters have not mentioned to date. Was it whilst editing the instruction graph or during the simulation part? If you saved your graph, I'd love to take a look at it! (The saves should be under e.g. `C:\Users\USERNAME\AppData\Roaming\Godot\app_userdata\MoonshotAttempt2`)

(+1)

The crashes happened in my first tries while using the instruction graph, I was connecting nodes all over the place and probably did something wrong. I’m trying to reproduce it again but I cannot, maybe because I’m a bit more careful making the connections now.

I don’t have a graph saved from those crashes but I do have a log that says the following:

**ERROR**: Condition "!node" is true. Returned: __null
   At: scene/main/node.cpp:1381:get_node() - Condition "!node" is true. Returned: __null
num opponents: 10
**ERROR**: Condition "!node" is true. Returned: __null
   At: scene/main/node.cpp:1381:get_node() - Condition "!node" is true. Returned: __null

I hope it helps!

Again, really well done! the game is awesome!

(+1)

Thanks! I will look into it, but I must admit my precautions against ill-connected graphs are paper thin, its an issue I'd have loved to have addressed with a bit more development time!