Log inGet started
Package

twoDKitTests.testSuite

This package holds more than this page lists. See all of its files in its world.

README.md

twoDKitTests

The twoDKit's own tests, written to pass in a fresh install. They check: the 47-tile blob autotiling (mask reduction, every mask mapping to a ground tile, edges differing from the fill); level text parsing (grid size counted from the bottom row, markers, unknown-character reports, round trip back to text, the player start); merged collision rectangles that cover every solid cell once with no overlap; one-way platform end tiles, spike directions and spike hit boxes; the motor against a grid world (standing, variable jump height, coyote time, jump buffer, one-way platforms and drop-through, wall slide and wall jump, dash distance and refill); that the four feels are distinct and that a registered feel inherits from tight; the style catalog (6 tile sets, 6 backgrounds, 6 themes, 4 characters, 3 cameras) and that every shipped material resolves; animation fallbacks for a sheet with only idle and run; and a live Level2D build that registers, lays colliders and a tile mesh, and is stood on by the engine's own raycast.

It leaves alone what needs play mode and a joined player (input devices, Trapline respawns, platform riding, networking): those are checked by playing the showcase. Run it in edit mode: zero tests run --suite twoDKitTests, or tools.use("tests", "run", { suite = "twoDKitTests" }). After updating controlsKit, Trapline or platformsKit, run it again.