Log inGet started
Package

artsTD.package

Newest version

README.md

artsTD

Arts TD is a multiplayer tower defense where every race is a way of making art. This package is the game itself: the eight art races and their towers, the enemy roster and its medium prefixes, tower fusion into hybrids, the campaign maps and waves, saved progress and the shared session that keeps a room of friends on one map.

What is in the game

  • 8 art races, each drawn by the look published for its medium (see "How the races look"): Watercolor, Ink, Pencil, Toon, Anime, Comic, Paper Cutout and Pixel, with 4 towers each (32 race towers), every tower with 3 upgrade tiers.
  • The neutral Studio with 4 towers any race can build: Easel Bolt, Canvas Cannon, Lantern Watch and Turpentine Mister (slows).
  • Hybrids: any two towers of different races fuse into a hybrid. There are 448 combinations across all 28 race pairs, 12 of them hand-made specials worth discovering.
  • Enemies named "<medium> <enemy>" (Watercolor Goblin, Ink Knight) and hybrid enemies in two media at once (Watercolor Ink Goblin); every wave set has at least one hybrid.
  • 6 campaign maps with ramping waves, upgrades, selling, gold, lives, a next-wave preview, wins and losses with star ratings, and saved progress.

How the races look

Every race's towers and enemies are drawn by mediumKit's published renderer: watercolor by watercolorBlocks, ink by inkBlocks, pencil by pencilBlocks, toon by toonBlocks, anime by animeBlocks, comic by comicBlocks, paper cutout by paperBlocks and starterBlocks, pixel by retroMaterials. Each look is gated to the objects in that medium, so the map keeps its own look. A hybrid tower shows both parents' models, each in its own medium.

Open scenes/gallery.scene (the Gallery of Media) and press Play to see all eight media and four hybrids at once, on towers and on a parade of over a hundred enemies.

Choosing your art

Pressing Paint on the title opens the race picker every time: all eight races, the ones you have not unlocked shown locked, your current one marked. The Your art button at the top of the level select and of every battle (key P, or the gamepad's View button) opens it again at any time to switch. Each player picks for themselves, so two players on one account (two windows, a desktop and a tablet) can paint in different media in the same match. A player who joins late gets the room's map, towers, fused hybrids, gold and lives from the synced session.

Frame budget: the target and what was measured

Target: 60 fps on the desktop app, 30 fps on the web. artsTD.budget holds it on every player's machine. Once a second it reads the frame time, and when frames run long it renders the scene and the art-medium looks at a lower resolution (down to 55% on desktop, 50% on the web), climbing back to full resolution when there is room. Enemies cast no shadow, the Gallery of Media moves half of its parade each frame, and mediumKit 1.0.3 spreads its watcher's checks evenly over frames.

Where it was measured: the Gallery of Media (16 tower models: the eight races' towers and four two-model hybrids; 112 walking enemies in all eight media and four hybrid pairs, all on one screen). Native desktop app, development build, window 2097x1409, on a shared machine that was also running the editor and agent tools. Wall time per frame on that machine (40 to 140 ms) mostly measures the other work on it. The numbers below are the engine's own CPU and GPU time, and the rate the engine reports it would hold with the machine to itself.

SettingsRender scaleEngine CPUGPU passesRate with the machine to itself
Desktop profile, before this pass (full resolution)100%21.6 ms51.4 ms27 fps (GPU bound)
Desktop profile, as shipped (governor on)55%19.6 ms20.1 ms51 fps (CPU bound)
Web profile (low quality looks, 30 fps target), run on the desktop app55%20.6 ms17.5 ms49 fps

What this means, honestly:

  • Desktop, 60 fps: not reached on this machine. The governor brings the GPU from 51 to 20 ms. The engine estimates 51 fps here and is limited by the CPU. Most of the remaining CPU time is the development build and the editor and agent tooling running beside the game (state snapshots, publish reminders), which a shipped build does not run. The gallery's own script is 0.5 ms. Whether a release build on a quiet machine holds 60 fps was not measured.
  • Web, 30 fps: not measured in a browser. No browser engine was connected. The web profile run on the desktop app estimates 49 fps, above the target, but a browser's WebGPU and a weaker device are different, and nothing here measured them.
  • Tablet: not measured. No tablet was connected.
  • At full resolution most GPU time is the medium looks' full-screen passes (pencil about 15 ms, toon 5, ink 3, watercolor 1.5, the rest under 1 ms each), plus styleKit's object mask and culling (about 13 ms). They all scale with the pixel count, which is why the render scale is the lever.

What was tested, and what was not

Status
Desktop app, keyboard and mouse, gamepad, touch (simulated input)tested on this desktop in earlier passes
Window sizes from a sideways phone to an upright tablet (build menu 1 to 5% of the screen)tested by resizing the desktop window
The level select: from the title (Paint), after picking or cancelling a race (keys Enter and Esc), from the pause menu and from the results screentested on this desktop, each route showing the parchment map with each map's best result
The fourth tower of every race: on sale, built, upgraded to tier 3, drawn as its own modeltested on this desktop
Gallery of Media framing (all 12 towers and the parade in one shot) and its legend leaving with the gallerytested on this desktop
Two live fusions (parent A becomes the hybrid in place, parent B is removed, hybrid ready within 0.1 s on the host)tested on one desktop client
Win, quit, restart, twice: race, palette, stars, maps won and best result per map kept; a worse win does not overwrite the besttested on one desktop client
The web build in a browser (any input)not tested and not measured: no browser engine was connected; "web profile" above is the low tier run on the desktop app
A tabletnot tested and not measured: no tablet was connected
A second player seeing the same hybrid, and two players picking different races in one matchnot tested with two clients: the machine had too little free memory for a second game client. The hybrid lands in the synced session state every player reads, and each player's race is announced separately, but no second player was watched receiving them

Modules

PartModule
Races, colours, media, towers, enemy traitsartsTD.races
Race and hybrid towers on turretsKit + build menuartsTD.towers
Enemies with generated models, prefixed kindsartsTD.enemies
Fusing two towers into a hybrid (fusionKit)artsTD.hybrids, artsTD.fuse
Campaign maps, waves, starsartsTD.maps
Saved progress (saveKit)artsTD.progress
Room state, players and their races, map switching, resultsartsTD.session, artsTD.Session
Title, race picker, level select, "Your art" buttonartsTD.flow
Painting towers and enemies in their mediaartsTD.painter
Juice and sound on build, upgrade, combine and sellartsTD.feel
The Gallery of MediaartsTD.gallery
Holding 60 fps (desktop) / 30 fps (web) by render resolutionartsTD.budget
BootartsTD.game
Map sceneryartsTD.scenery

The scene scenes/arts.scene builds the battlefield with towerDefenseKit and spawns the synced ArtsSession; scenes/gallery.scene is the Gallery of Media.