(Instructions, restrictions in project) It's been a while, huh? :D I don't know of any recent Codegolf challenges, so I think this is a good things to try to show it off in completeness!! In the literal sense :3 The goal of this is to see, how can we finish it off? Turing Completeness marks completeness in a lot of things, and means that for many other codegolf challenges, this could defeat any other solutions, at the cost of a lot of speed. This of course isn't *easy*, but for the most part, the hard part will actually tend to be writing programs within whatever you make There are many esoteric languages you may take inspiration from -- lots of single instruction Turing Complete languages, but whether or not those are optimal is yet to be decided :> Assuming people decide to go through with any of this, I'll put a leaderboard up for the different categories ^^ Happy golfing!! -- I hope it doesn't take me literal years to share my next project again, and sorry for last time :,D I'm glad I could still stay relatively active via comments!! I do plan to participate in this myself fwiw, although probably only in one category :> Leaderboard: - Theoretical: - @AUnitSquare | 6 blocks; https://scratch.mit.edu/projects/1192482154 - @Tomosclass | 8 blocks; https://scratch.mit.edu/projects/1214377246 - @KayumovMaksim | 10 blocks; https://scratch.mit.edu/projects/1208031781 - @AUnitSquare | 10 blocks; https://scratch.mit.edu/projects/1227761105 - @csheikh30 | 10 blocks; - | 14 blocks; - | 19 blocks; - | 29 blocks; - | 43 blocks; - Practical: - | 9 blocks; - | 12 blocks; - | 13 blocks; - | 13 blocks; - | 16 blocks; - | 16 blocks; - | 19 blocks; - | 23 blocks; - | 68 blocks; - | 83 blocks; - Applied: - | 7 blocks; - | 14 blocks (without keyboard/resting); - | 19 blocks (without keyboard); - | 39 blocks (without keyboard); - | 73 blocks; - | 81 blocks; - | 105 blocks;
