impactFrames.testSuite
README.md
impactFrames test suite
Checks impactFrames on this machine: the photosensitivity limiter (twenty flashing impacts inside a second draw at most three full-screen flashes and downgrade the other seventeen, a budget of 0 never flashes, downgrade = false drops instead, the window refills after a second), that every impact style (the slash frame and the held hit pose included) lays its block and takes it off when it ends, that a hit is laid once with its start on the held clock so its drawings step in the shader, that impact frames ride along with juiceKit hits (a stand-in juice module: a mapped preset lays its impact, an unmapped one none, stopping puts Juice.play back exactly), gentle mode, that large-area colours are held below saturated red, that a hit from another player starts at the moment it was sent (and one arriving after its end is dropped), that an unknown style is refused, and that every smear style spawns its ghosts far from the scene and takes them away (stretch hides and shows the object again).
Every impact runs as a dry run (ImpactFrames.setDryRun(true)): the limiter, drawings and timing run in full and nothing is drawn, so the suite is safe to run on a screen a person is looking at. What the blocks look like is checked with presented captures, not here. It leaves the scene's shared style stack alone, restores this player's safety settings without writing their saved store, and does not send a real multiplayer message (it needs two peers; the receive path is driven through ImpactFrames.receive). Run: asset.resolve("impactFrames", "testSuite"):run().