…ng that with `Uu`, we can safely check for `u` and prepend a `U`. so only prepending one character having no other downsides AND we dont need to take the second character from the match meaning we can drop the `` as well. 2 left.
…and replace those `h=0 h=1 h=1` with `h++`, especially since it was already getting initialized by an arbitrary number, which means the increment of `h` was part of those identical `fillText` calls. hot digity, now all thats left is tweaking the numbers
… function from a declaration into an expression. but of course assigning to `N`, which we only need to have been declared before reading it, suffices for this. _now_ we are ready for the fix which brings us back up to 1024
… was caused by the loop variable being assigned `1` or `-1` depending on the outcome of the affected line. this problem isnt very apparent with the current pixel sizes (though still present) but will be now that we will tweak the numbers a bit
…=function` hack did not work (and i did not test it, or screwed up the test). the `N` binding is only created after the function is invoked, which is too late. oops. anywyas, confirmed that the minified build works now :)
…y to find a byte to be able to fix this bug that nobody would ever notice anyways. but the element number wasnt bound so when the elements would loop, the counter would keep going up. Of course, `%118` is four characters more than i had. Solved it by moving the `match` to the cycle loop. Not happy but perf seems okay on it so meh.