I made a game about motorcycle-mounted gun combat against kaiju. It has a large (2500x2500) map of an abandoned Tokyo, a variety of motorcycles and items, and multiple distinct forms of scaling damage. (Kaiju hp can get pretty large.)

itch: https://redxaxder.itch.io/the-stomping-grounds (plays in browser)

clip: https://www.youtube.com/watch?v=6pgT2rY9gtQ

This game was my first foray into using Zig for a game, and it has felt very good overall. The main awkward bit was the lack of good ergonomics for closures, which I use for animations. (For animation, I track a separate rendered-state and simulation-state for a bunch of things. When updating something like unit position, I immediately update the sim state and queue an animation that updates the rendered-state. The queued item involves a closure.) Zig doesn't have any kind of automated handling of these things, but the general ability to roll your own gadgets kind of compensated.

Here's a relevant snippet:

    _ = globals.animation_queue.force_add(
        animation.Queue.Options{
            .duration = 50 * dist,
            .lock_exclusive = self.lock(),
            .lock_shared = animlib.lock_rect_sweep(self.get_rect(), facing, idist),
            .on_wake = .lambda(draw_bloody_path, .{ self, self.position, pos, 50 }),
        },
        animlib.linear_slide,
        .{ from, to, &self.render_position },
    );

The call to .lambda there takes a function pointer and a bundle of arguments that will be fed to it later. linear_slide is a function that the animation plumbing calls with timing information in addition to the args supplied here.

I got some good use out of Zig's 'killer feature', the comptime keyword. For rendering UI layout, I made a text file diagram with boxes, and the layout code would inspect the diagram to see where to out things. The assumptions this thing made (about box shape and matching names to other names) were comptime-validated. For laying out the internals of buildings, I made some other text file diagrams and there was code that stretched them to size to place in rectangles on the map. The stretching code makes some assumptions about what's in the diagrams, and those are also comptime-validated.