Skip to main content

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

Xenosurgeon keeps to the jam’s rules because GDevelop is genuinely the engine, not a wrapper around something else. The game is a GDevelop 5 project (game.json) built and exported by GDevelop’s own exporter. Its 3D world, physics (the Physics 3D behavior’s Jolt world), HUD layer, input mapping, audio resources and post-processing all run on GDevelop’s runtime. The surgery logic is JavaScript loaded as source files of a GDevelop events-functions extension, a feature GDevelop provides for exactly this, and the scene’s events call it.

As regards AI, please read the games's description on Itch. I absolutely use AI and I carefully declare exactly how and when I used it. 

I absolutely used AI, and would highly recommend it unless your goal is to test your rapid coding skills.

I code in my day job all day long and only enter jams to test my ability to make something fun, not my coding ability. I am very comfortable with my skill as a SWE, so for me, these jams are not about making code but about making a game.

I know that rankles some but that’s okay by me. Hate the AI usage?  Rate it down come ratings time.

Oh I was mainly concerned about the fact that majority of your games mechanic runs on javascript code, which gdevelop tries to avoid in the game jam. You have a very visually impressive game, though.

(+2)(-1)

I made a huge change to the build. moved everything that could live in GD into GD. It's a bit huge for GD, but it works. I was stuck with three limits, all are now extensions. They hold, basically, jsut the things that are soft-body physics based. I stayed with GDs Physics engine, but had to poke it a bit to get to have the squirmy feel I needed =] 

Deleted 2 days ago