Skip to main content

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

Nice idea, but the commands need some better interface. As it is, it's not very clear what happens because even if I put a 'wait' after a 'thrust' command the engine keeps going. I would have expected the commands to be executed sequentially, not all together.  Good idea, though, and good music!

(+1)

The commands do operate in sequence.

When you give a thrust command you are setting the thrust value for that thruster. To turn a thruster off you'd enter dir_thruster 0.

Oh, then I was confused by the same number "box" being milliseconds, intensity, etc. depending on the command. That's not too clear. I'll try again.