Log inGet started
Package

heatSignatures.package

README.md

heatSignatures (test suite)

Checks heatSignatures's temperature model as a game reads it: the name rules (Heat.classForName: a guard is a person, a crate metal, the forest stream water, a campfire fire, and a scarecrow is not a car), the five shipped climates and Heat.setClimate (put back afterwards), a script-given working engine warming over Heat._tick toward its active temperature and Heat.take removing it, Heat.at inside a person-sized shape against the air outside it, Heat.touch prints that fade and expire (and only ever fade), a HeatSource component registering itself and dropping on despawn, and HeatField packing shapes and publishing the heat input while a thermal block (thermalIronbow) is laid as a local styleKit entry.

Probes are temporary entities placed far from the showcase scene and despawned at the end of each test. The climate and the local entry are restored. It leaves the thermal blocks' look on screen to the sensorBlocks suite.

Run: asset.resolve("heatSignatures", "testSuite"):run().

Known limits

  • The HeatField test needs a drawn view, since HeatField.frame runs from the render feature.
  • Heat._tick is driven by hand, but the render feature also ticks heat between frames; tests do not yield between their own ticks, so the two do not interleave.
  • "a print only fades" fails on heatSignatures 1.0.0: sharedNow() in Heat.module/init.luau adds time.realtime() % 1 to os.time(), whose seconds do not tick together, so a print's age jumps about a second once a second and its strength can rise or go above 1.
  • setClimate writes the synced HeatClimate entity, so other players see the desert climate for one frame while that test runs.