Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
A jam submission

Input ThrustView game page

Submitted by SmoothProcess
Add to collection

Play game

Input Thrust's itch.io page

Results

CriteriaRankScore*Raw Score
How well does the game fit the themes?#54.0094.286
Did you make it in 3 hours (put 5 by default)#64.6775.000
Audio#83.3413.571
Overall#83.6083.857
How much do you enjoy the game overall?#93.3413.571
Gameplay#113.3413.571
Visuals#132.9403.143

Ranked from 7 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.

How long was your dev time?
2h35m

Leave a comment

Log in with itch.io to leave a comment.

Comments

Submitted(+1)

Really challenging and really fun. Fits the theme too.

Submitted(+1)

This game is very challenging and requires A LOT OF patience. That’s good game but I wish I had better UX including display last set of commands, remove each command separately and maybe some hints like length of flame when changing values. I’ve completed only 1st level so I basically scratched the surface, gameplay is ok but needs a lot of improvements. Not a bad game made for 2h35m. :)

Submitted(+1)

Another challenging game by SmoothProcess!
I might need some explanation again on how this works...
Does wait actually wait for X ms before doing the next command?
What does the milliseconds do for the left/right thrust?

Notes:
  1. UI needs some work. I'd rather type in the milliseconds or use a virtual numpad
  2. Seconds, going up in 0.1s intervals, might be easier to play with
  3. I agree. This is very difficult. And frustrating.
Developer(+1)

Yes to the first question.

The number after the thrust commands is the intensity of the thrust. To shut a thruster off you enter dir_thruster 0.

The initial idea was to let the player type in the commands which would make it a lot easier to enter the commands, but I didn't feel like having to parse the players commands so I did it this way.

Submitted

Okay, I understand twice as much now. Thanks for the explanation :)

Submitted (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!

Developer(+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.

Submitted

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.

Submitted(+1)

The game is really cool, even if it was a little bit hard for me xD 

(+1)

incredible game. i think it will be better if the time will be conciderd as seconds i think it will help the game a lot. and the music is REALLY loud. but when i muted it a bit. i realized how genoius this game is