Press green flag to see how big the matrix is, and edit the size inside the project. In order to take this code put the sprite in your backpack as a package. The matrix library still needs to be optimized, but I have learned the library runs incredibly well at low Matrix Transfer rates
The way this project works is by assigning each item in a 1D array (list) to a coordinate position by giving it an ID. The ID system works by adding the X value and Y value to separate 10000's, then joining them together. For example, X: 350, Y: 243, would be: 1035010243. This allows the values to get parsed correctly. Because the scratch list size limit is 200,000, the realistic limit (with data) is around 400 ² (400x400), but theoretically the limit is around ~440 ² However, because of the way the package is designed, you can create matrixes with boundrys of 9,999, you just have to keep the total amount of list items under 200k. So, the max that works with the X set at 9,999 is 20 for the Y. 5/7 - The library is 71Kb when exported with full functionality - with 161 blocks 5/8 - The library runs at peak 4,180 MT/s on turbowarp, while running quite a bit slower on native at 547 MT/s. This was found with the PopulateRand Function and the Validator. 5/9 - At peak (under 100x100 Matrix Size) I have optimised for 6,389 MT/s on turbowarp, and 3,267 MT/s without. The code can output huge files if needed, as in upwards of 2Mb
