pretty slow but i think that's the fastest way to raster tris correctly in Scratch. if these random values are applied to another scratch raster tri, chances are it would break past the square bounds. this happens because those engines don't check for y positions equaling each other. this is because it gets very expensive fast if you aren't careful. still faster than some other raster tri engines at this res.
