Hyottoshitara

Wow. Thank you. I understand completely.

I see your games as having two levels of challenge, just like programming in the real world: The first solving problems, and the second competing for efficiency.

Even the first part, solving a problem, can be very difficult, even more so when there is a size limit.

In Opus Magnum, I felt that your removal of the size limit was a good choice from the perspective of opening up the game for people who are more challenged by the first part. Why did you go back on this for EXAPUNKS? Does it seem to make solutions too easy?

What do you think about the idea of having a size limit that is a requirement for viewing and contributing to the leaderboards, but can be exceeded to solve the puzzle?

You piqued my curiosity, what do you mean about turning into a luddite? A surprising comment from someone who makes these sorts of games.

My suggestion is brilliant and you should definitely do it :P

But seriously, in EXAPUNKS, I brushed up against the limit in Alliance Power and Light, and exceeded it in US Government. The second one was frustrating because my solution was only a few lines too long and I ended up "fixing" it with micro optimizations.

I also have a solution for the "IMPORTANT - the big one!" in SHENZHEN I/O that needs something like one more line in one microcontroller.

I want a campaign to escape from the VM you're trapped in.