PyWeek - Nuclear Soda 6 - feedback

This looks like a really cool idea, but it's presented in a way that is too complex for me to fully
comprehend. :/ I think the sheer amount of arrows going everywhere makes things difficult to
understand. Maybe if you had an earlier level with less stuff going on, that would be very
helpful. Keep in mind that things that are obvious for the designer may not be obvious for the
players. I had questions such as, is this a sequence that goes from the left to right, or does it
somehow start at the red box and I should follow some arrow? What does it mean to add directions;
is it a vector kind of thing? Even if you let the robots run, it's not fully clear what's going on
(would be nice to see a representation when you did a step and switched to mind mode). Also,
consider adding icons to avoid having the player going back and forth the manual. In the end,
unfortunately I wasn't able to properly play it due to the complexity.

Note: I almost couldn't play this because the fullscreen was only showing part of the game, and
if I removed it, the window is too big for the maximum resolution of my laptop! :( Luckily
changing the window size in the code worked.

This is a very interesting concept and not something I think I've ever seen before. I'd really
love to see a more complete version of this. My biggest issue with this game is with the mind map.
It is not a very easy thing to read and the README kinda launches all the info at you at once. The
game only allowing fullscreen doesn't help either since you have to switch back and forth
between the game and the README. I really wish there was some kind of gentle introduction in the
game to how the map works and how to read it.

no sound nor music?

Unfortunately, when I run the game (on GNU/Linux), the mouse immediately freezes. I press
ESC, Alt-F4, Crtl-C and just about anything else that might close the game. About two minutes
later it disappears. This is what was printed the first time: Program 1: (1) move memory No. 5 to
memory No. 6 (2) move memory No. 7 to memory No. 6 (3) add memory No. 5 to state (4) move memory No. 3
to state (5) add memory No. 7 to state (6) wait 1 (7) if memory No. 4 == memory No. 0: 2 (8) wait 3 (9)
add memory No. 1 to state (10) move memory No. 4 to memory No. 7 (11) add memory No. 7 to state (12)
rotate memory No. 1 to R (13) move state to memory No. 7 (14) rotate memory No. 0 to L (15) add
memory No. 4 to memory No. 0 (16) rotate state to L (17) wait 1 (18) if memory No. 5 == memory No. 1:
11 (19) rotate memory No. 2 to L (20) rotate memory No. 2 to L (21) if memory No. 0 == state: 3 (22)
move memory No. 1 to state (23) move memory No. 3 to state (24) rotate memory No. 5 to R (25) wait 1
(26) if memory No. 7 == memory No. 2: 22 memory No. 0 = (0, 0) memory No. 1 = (0, 1) memory No. 2 = (1,
-1) memory No. 3 = (0, 1) state = (1, 1) memory No. 4 = (1, -1) memory No. 5 = (1, -1) memory No. 6 = (-1,
1) memory No. 7 = (0, -1) Program 2: (1) move memory No. 5 to state (2) rotate memory No. 0 to R (3)
wait 2 (4) if memory No. 3 == memory No. 7: 3 (5) add memory No. 5 to memory No. 7 (6) wait 2 (7) add
memory No. 2 to memory No. 0 (8) rotate memory No. 3 to R (9) rotate memory No. 1 to R (10) rotate
memory No. 6 to R (11) wait 3 (12) wait 3 (13) rotate memory No. 3 to R (14) rotate memory No. 4 to R
(15) wait 1 (16) if memory No. 5 == memory No. 4: 14 (17) wait 3 (18) rotate memory No. 0 to L (19)
wait 3 (20) wait 3 (21) if memory No. 5 == memory No. 7: 30 (22) move memory No. 7 to state (23) if
memory No. 0 == memory No. 5: 5 (24) if memory No. 2 == memory No. 0: 19 (25) rotate memory No. 4 to R
(26) add state to memory No. 0 (27) add memory No. 6 to memory No. 7 (28) wait 1 (29) if memory No. 0
== memory No. 5: 27 (30) wait 1 (31) wait 2 (32) move memory No. 6 to state ALSA lib
pcm.c:7843:(snd_pcm_recover) underrun occurred ALSA lib pcm.c:7843:(snd_pcm_recover)
underrun occurred Killed

I get the concept, but that diagram was really hard to understand. Different colored arrows
might have helped a bit. Adding a key to the diagram to show what each color means would have
helped, too. Good game for future chess masters.

I just wasn't able to get how the state machine worked from the sketchy documentation.

.

I really just couldn’t figure out how to play this one, and it was very, very slow on my machine.

Good idea.

I'm sorry, the game worked fine as far as I could tell, but it would be unfair for me to rate it when
I wasn't able to figure it out. I think I got the general sense of what you're trying to do, but how
the actual program worked was just beyond me. I thought I understood the instructions, but
when I tried to press N-enter a few times to see if it did what I expected it to do, it never worked
out. I wish I could at least see which step of the program it was currently on.

Pretty complex, but good concept. I'd play this again.

I like the idea, but it lacks explanation and it's therefore difficult to understand what's
going on.

Very interesting concept, but needs much, much more of the ReadMe information to be encoded in
the game itself.

This game is totally unintuitive. I think I would need a two hour tutorial to play, and still
would probably not have much fun...