Comic Book Looks: Halftone, Ben-Day, Noir Ink and Panels
- .authoring
- .world_entrypoint.luau6.4 KB
- .world_settings2.5 KB
- NOTES.md34.8 KB
- README.md8.7 KB
- alpineKit.package.pull9.0 MB
- comicBlocks.package
- comicPanels.package
- deps
- desertKit.package.pull14.9 MB
- desertLands
- humanBodyKit.package.pull174 KB
- inkBlocks.package.pull184 KB
- libs
- media
- menuTabs
- paperBlocks.package.pull108 KB
- scenes
- sengokuTownKit.package.pull15.9 MB
- showcase
- starterBlocks.package.pull72.3 KB
- styleKit.package.pull125 KB
- toneScreens.package
- toonBlocks.package.pull699 KB
- watercolorBlocks.package.pull251 KB
README.md
Comic Book Looks: Halftone, Ben-Day, Noir Ink and Panels
Make any Zero game look like a printed comic book: four-colour process dots that form rosettes, Ben-Day tints, line and cross-line screens, a coarse newspaper screen, plates printed out of register, noir ink, black-and-white-and-one-spot-colour, newsprint, and comic panels with gutters. Everything is a styleKit block, so it stacks and swaps with every Style Cookbook block (ink and toon lines, papers, watercolor washes, palettes).
Five minutes from install to a comic look
-
Install. In the ZeroMind panel search comicBlocks and install it. It brings toneScreens, styleKit, toonBlocks, paperBlocks and starterBlocks with it. inkBlocks (brush, pen and nib lines) and watercolorBlocks are optional swaps: no look needs them, install them yourself if you want them. For panels also install comicPanels. A first install with several dependencies can take a minute; check that
comicBlocks.packageappears under your world's source. -
Pick a look (any script, the console, or the shell). In a brand-new world with nothing to look at yet, first open a recipe stage that comes with comicBlocks:
zero scene load comicBlocks.recipes.recipeGoldenAge(a ground, sky and a walking hero; every look has one, listed in the comicBlocks README).local StyleKit = require("~styleKit.StyleKit") StyleKit.applyLook("goldenAgeFourColour")Start with this one. Golden age is what most people picture as a comic book, it reads at any distance and it is the cheapest colour look. The other looks:
comicNoir(a night scene in solid blacks),sundayStrip,dailyStrip,modernFlatColour,oneColourSpot,popArtDots,misprintedPulp,twoColourSpotPrint, and new in this releasemangaScreentone(screentone and speed lines) andpulpCover(a loud pulp magazine cover). One call switches between them, for every player. To see any look set up before you use it, open its recipe scene, for examplezero scene load comicBlocks.recipes.recipeNoir(one per look, listed in the comicBlocks README). -
Press play and look at it. The look lives in your scene (a synced
StyleStackentity), so every player sees the same page and it is saved with the scene. The first time a session switches to a look, its passes compile, so the new look appears a second or two after the call; after that every switch is immediate. -
Swap one part. Every look names its entries the same way (
palette,fill,screen,line,paper,spot,register,press):StyleKit.swap("screen", "processFourColourOnSurfaces") -- the rosettes laid on walls instead of the page StyleKit.remove("screen") -- or trade the rosettes (a Colour block) for a tone screen: StyleKit.add("lineScreen", { id = "screen" }) -- any of 16 tone screens; after this, swap("screen", ...) takes any of them StyleKit.swap("palette", "popArtPalette") -- any of 5 print palettes or 3 duotones (Colour) StyleKit.add("newsprintPress", { id = "press" }) -- print it on cheap newsprint (ink spread, dot gain, faded blacks) StyleKit.add("paperNewsprint", { id = "paper" }) -- any of 17 Cookbook papers StyleKit.swap("line", "toonComicLine") -- any Cookbook ink line -
Lay it out in panels (with comicPanels):
local ComicPanels = require("~comicPanels.ComicPanels") ComicPanels.on() -- start here: slanted action panels, brush border, white page ComicPanels.caption(1, "Meanwhile, at the oasis...") -- a narration box ComicPanels.applyPage("pulpCover") -- or a whole page: look, layout, border, gutter, captions ComicPanels.off() -- back to one frameOnce panels are on, change looks with
ComicPanels.applyLook(id), which keeps the page;StyleKit.applyLook(id)replaces everything, page included. -
Let players drive it. Add the
comicPanels.ComicControlscomponent to any entity for keys and on-screen buttons that cycle looks ([]), layouts (L), borders (B) and page presets (K) and turn panels on and off (P). For gameplay (a noir impact frame on a heavy hit, a look that grows with a player's rank, a three-panel intro, and which kit to install for fighting) follow the guide "Example: a superhero level with a comic look": every step there is complete and copyable.
StyleKit.clear() takes the whole look away again. No material is edited.
What is in this world
| Package | What it gives you |
|---|---|
| toneScreens | 16 tone screens on one shared setup: round dots, Ben-Day tints, square, diamond and chain dots, line, cross-line and coarse newspaper screens, each as a page screen that holds still and as a screen that stays on surfaces (steady under the engine's antialiasing jitter), plus four-colour process (CMYK) rosettes in the Colour slot. Nothing comic-specific: it is the screentone base for other print looks (a manga look builds on it). |
| comicBlocks | Print palettes and duotone spot palettes (Colour), noir inks (Fill), spot colour (Colour), misregistration (Raster), newsprint presses (Medium: ink spread, dot gain, faded blacks) and eleven whole looks, each with its own recipe scene, plus guides and the comicWorld workflow that turns an existing scene into a comic look and can undo it. |
| comicPanels | Comic page layouts (12), border styles (5) and gutter colours, with one camera or per-player extra cameras in their own panels. |
The showcase scene puts you in an oasis valley built by the installed desertKit (palms round a spring, sandstone cliffs, a ruined town half under the sand, dunes to the horizon, on its own clock, light and sound), dressed as a caped watchman with a spear from the installed humanBodyKit character kit. Keys 1 to 9 switch looks, 0 goes plain, P turns panels on with two extra views, L / B / G / C cycle layout, border, gutter and cameras, H hides the panel. The look is on the scene's synced stack, so every player sees the same page; each player's panels are drawn by their own machine from their own camera.
Tested with two players in one play session: both always saw the same look, a look key or the panels key pressed by either player changed the page for both, and each player's panel views followed their own hero. The showcase desert draws at desertKit's quality = 0.6, the draw distance the browser version caps at anyway, so a second client fits in memory on the same machine.
Known limits worth knowing up front: offscreen captures and render-to-texture cameras do not draw the look stack (#17427, so panel views get a print treatment of their own); every stack pass is queued again every frame (#24548); per-object looks go through styleKit's object mask (#24549); blocks read depth only through the stack's shared capture (#24550) and an unknown blend name draws as replace (#24551). Each package README lists the limits that apply to it.
Guides shipped inside the packages
- "How to make a scene look like a comic book" (comicBlocks)
- "Example: a superhero level with a comic look" (comicBlocks, with comboKit fights and juiceKit hit effects)
- "How to use halftone and screentone" (toneScreens)
- "How to lay a game out in comic panels" (comicPanels)
- The
comicWorldworkflow:zero workflow start --name comicWorld --args '{"look":"sundayStrip"}'
Cost, measured on 14 November 2026 at 1920 x 1080 in the busy showcase desert with 2,500 extra things in view, from the engine's own frame cost (GPU timestamps and the engine thread's CPU clock, not wall clock), many look-on/look-off rounds each: the default golden-age look adds 0.41 ms of GPU passes and about +0.58 ms to the whole frame's GPU time, with no measurable engine-thread CPU (styleKit's own script work is 0.14 ms). The heaviest look, pop-art dots, adds 1.18 ms of passes, about +1.5 ms of whole-frame GPU and about +3.3 ms of engine-thread CPU, because the toonBlocks poster line it borrows draws every object again; each README says which entry to swap for a lighter look. A panel page alone costs about 0.1 ms. Each extra panel view is a whole extra render of the scene: about +1.4 ms GPU and +6.6 ms engine CPU for the first view in this busy scene, about +1.3 ms GPU and +11 ms CPU more for the second (views take turns at half resolution by default). The browser build could not be run from this engine, so web cost was not measured; each package README says what was measured instead. Rerun it with require("showcase.LookCost").onOff(...).