Would be nice if HitBox supported a Polygon shape

Add an option to draw sprites directly from an atlas instead of copying them to a separate bitmap. May require adding 1-pixel borders around sprites when baking so that filtering doesn't access neighboring sprites.

When baking loaded sprites, set GJS.Sprite.atlas to null so that baking is done based on original files. Restore the atlas at the end. Also fix comment on top of function.

The engine should have the following features:

• update particles at variable FPS
• render either as circular blobs, squares or sprites
• creating "splashes" of particles instantaneously
• possibly particle emitters that emit particles over a longer time span
• easy to integrate with the main loop

The code is usable for simple top-down games, but since it is engineered with fairly complex platforming use case in mind, it's overtly complex for that purpose. Think of ways to simplify it and break it down to pieces.

There should be a script that bakes all files in a directory into a sprite atlas and generates a config JS file that will make sprites load from that atlas.

Implement a size manager that would have the following modes:

• Fixed canvas resolution for implementing pixel art graphics, with pixelated rendering (using CSS)
• Auto-resize canvas with fixed aspect ratio, but emulate a fixed coordinate system (manages high-level canvas transformations on behalf of the game rendering)
• Auto-resize canvas with fixed aspect ratio
• Auto-resize canvas without fixed aspect ratio

The manager should respond to resize events from the browser and to requests from the user to change the canvas dimensions.

A simple loading indicator that shows how many sprites/audio samples have loaded would be useful. Could integrate this with main loop templates to get a good starting point for a game.

An object that takes a 2D canvas and applies a screen-shake transform on each frame.

Could be 2 variations: Fixed FPS updates, and non-fixed FPS updates.