There’s a binary counter in the level editor now But now it’s a decimal to binary converter. Actually it would be able to do fractions, but I cut it off because we wouldn’t have use for the fractional part It finds the coefficient part of the full polynomial, (as in the full representation of the binary number in terms of two) and then fills the gaps in, since the coefficient is always either one or zero, it will just see if it’s in the list. If we were converting to terniary, it would need to see what the coefficient actually was, as in 0, 1, or 2 Anyways the reason I need a binary number to decimal is for compression Instead of keeping it as a list of tiles like 10100101010011, we can keep it as a much shorter number, approximately shorter by a factor of log_2(10) ≈ 3.322, so if I had a string ten digits long in binary, you can compress it to about 3.010 digits (depending on the composition of the number, ie: 1111, or 1000 are both four digits long but one compresses to two digits: 16 and the other goes to one: 8) Added binary encoding and decoding for compression, attempted to use a sample scene, attempt failed. attempting to locate bug (may be in the "draw block" block". already have an understanding of how the collision sensing will work (idea of points on surface, sensing for collision) or a bounding box method (put boxes around player, and each segment of the level) \b
