my best. 10/433/14

Double checked my solution after recent posts here. Discovered that I had two unnecessary instructions. Removed those and surprisingly everything still runs smoothly. Improved to a 10/445/12

What an annoying puzzle. 10/445/13

13|1040|20 and this is definitely not the way you suppose... I failed to figure out the way to find packet end, so I made a "clock thing" to generate packet end signal. Maybe I have to solve this another day.

Nice puzzle, got 10|848|16, and 748 power with another solution, but that one takes two MC6000. Not sure yet where I can shave off those 2 instructions to reach 14

I went to the following phases:
- ez pz lemon squeezy
- wait a minute, y u no stop?
- impossibru!
- brain.exe stopped working
- holy moly ... yes ... that should work
- I need only ONE more line
- ok, restructure ... optimize
- yes ... Yes ... YES
- GOT IT ... 10/544/14
- noice one, like very much

Good job. Thx for that.

Fun and different kind of problem (compare to builtin levels at least, this is my first workshop one). Got 10/962/17 for those who care. ( I haven't really tried optimizing, I mostly enjoy just solving the task, with few components, but don't care much for power or lines, there is enough optimising needed just to fit the lines in the processors :-) )

haha, excellent idea

@DarkRedman666 You can use other methods of signalling. Such as reading if array value has changed in a loop. Come on, it's not that hard.

Cool! My result: 10|557|14. I can optimize a little more, but laziness

it's very possible, but it's a different way of thinking. It's like a riddle for this game

I check the whole documentation and there is no way to do it, seems like a troll.
I got the idea to use a RAM module but still, since we can't predict the packet size I keep writing in then it blocks and there is no comparison instruction to check packet without "consuming" it.

I heard about XBUS sending a hidden -999 when finishing a packet but even trying this, it doesn't work either.

I haven't finished the game yet, so maybe there's some new tech or something I don't know about, but I don't currently see how that hint addresses the issue I'm having. If you need a MC to write into memory (and from what I can tell, you do), and the MC itself can't determine when a packet is finished, then how does you "write the data directly into memory"? I don't actually know what I'am asking for. I guess nothing, since I don't want you to tell me the answer, but I read the manual back to front and don't understand yet how to solve this one. Maybe playing more of the game will help.

That's indeed the real puzzle, to figure out how to read the blocking XBus without knowing when the packet ends. Try writing the data directly into a memory

Im stuck. This puzzle seems trivial *EXCEPT* i can't figure out how the mc can know when to stop reading the packet. If you have it read indefinitely it locks up when the packet is over, and the packets are variable sizes so you can have it read a fixed number of times, either. So what am I missing so that the MC can figure out when it's done reading and have it start writing?

Nice one :) Got 10/776/15

once I'd finally got a working solution, I got 10/911/18 . Ripe for optimising, given how everyone else seems to be doing!! Took a decent amount of time to figure out any kind of working strategy.
Great challenge this one.

Great!

Tried and and managed to get 10/664/17.

Nice one! After a couple of unsatisfying solutions, I managed to streamline down to 10/459/12. Thanks for creating this!

nice

Nice

Managed 10-496-14....not sure how it works o.O Would love to see a proper solution

not to bad, managed it with 10|802|15

This puzzle is great at isolating a technique that seems impossible when you're preoccupied with other concepts.