ZYDOBAS - Rubicon Processor 2

First off I'd like to point out that this is not my original creation, it was Kaosadvokit and their JIKUDEG, nor do I wish to take any credit for its design principals. With that being said, onto the main topic.

Hi I'm kloptops, pleased to meet you! Grin

I've been playing rubicon for just under a week, its terribly addictive. Anyhow, here is my first contribution.. its a fix up of the Processor that I found in the Rubicon Search... I began toying with it, because imho its the coolest idea ever, and soon had the idea to output 'DEADBEEF' (A great debugging symbol).

So I spent 5mins writing out the code, and then input it in, started it, wandered off to make a cuppa. Came back to find it had output DEADDDDE. Huh

I was baffled, and wondered if i had really screwed up my code, either in input or in a slight logical error.

I rechecked it, seemed okay to me... so I started it back up. This time watching it, I noticed its stack system was flawed, and required exact timing to pop values off the stack. Otherwise the stack values wouldn't get a chance to be sent up the tube. I spent the rest of the night trying different (crazy) idea's to make it work, I couldn't work it out.

That night I had a brilliant idea, on how to implement it, I had noticed how the original author used comparison operators to push the input code into the machine at a controlled manor, so the next day I spent 40 mins rebuilding it, using the comparison operators... and it worked great! It has however cut down on the prospective stack space, however its not like you'll actually have problems using that much space.

Over the few days of playing with it, I have redesigned most of the little inner workings of it, to bring up to the new physics system. So it no longer uses the old physics system.

Here is a chart I did up (because I had time to waste) to, hopefully, help explain the functions of the program.

Its a handy reference, and its very useful as a key to what the operators are.

While I have been playing with it, I have come up with a small challenge. See who can output the longest Hexspeak (http://en.wikipedia.org/wiki/Hexspeak) with the shortest amount of code... ofcourse taking into consideration of the most challenging words to output.

Here's my contribution...

DEADBEEF - 331302033313022204040020 - KELUPOD

Thanks, and I hope you'll enjoy this level as much as I have... Grin