Every enemy holds executable code. Shoot the enemy to run its code.

Controls:
WASD: Move
Space: Shoot
B: View debug hitboxes

----

There is no special screen when you win.

----

Other credits:

Graph paper image by Jose Camões Silva, CC-BY-2.0, edited by me to have drawings on top of it. https://www.flickr.com/photos/josecamoessilva/16645340674/

Blackboard image by Peter Gargiulo on Unsplash, edited by me to blend it into a horizontally repeating texture. https://unsplash.com/photos/cGNCepznaV8

Background chalk drawings were drawn for me by Elysia. http://alphamethyl.barr0w.net/~elysia/index.html

You can browse the Eval-em-up source code on GitHub. The code directly depends on Raylib, the Racket Raylib bindings, and the Priority Queues package. They may have further transitive dependencies.

---

Solo project for Spring Lisp Game Jam 2023, coded in Racket + Raylib.

I only found out that the jam existed after 5 of its 10 days had already passed, so I had a little bit of time pressure.

Unfortunately I wasn't able to put together the art and the code and the waves for as many unique enemies as I wanted. The published game contains a very limited selection of enemies, but enough for you to get the idea. Other ideas for enemies included:

• A switch with the code `(open)` that you have to hit to progress.
• An enemy that provides shields to the other enemies, with the hit code `(disable-shields)`
• An object that runs `(give-power-up)` to give the player a helpful minion that floats around their ship. The minon would have code that activates on hit to benefit the player.
• A mimic enemy that looks like the power-up object, but actually runs `(give-powre-up)`. See the typo? It would disadvantage the player if it was shot.
• An enemy that darts around rapidly, making it hard to read what the code is.

I most likely won't continue working on this game after the jam ends, but if I did, that's the kind of thing I would add to it.