Prompted by the tragic loss of Armadillo, albeit at the ripe old age of 292, I submitted Lobot, a dumb JMP bomber/core clearer. Lobot takes reductioninsm to the extreme, not even bothering with a dedicated bomb instruction. Nothing fancy, nothing new, and the "JMP -2" makes for a fairly inefficient bomb, so I was quite surprised to find it among the top 3 on the standard hill. Speaking about complex programs, I have mixed feelings: if I had enough time, I'd love to play with elaborate code. Then again, it's also nice to whip together a small gem while on the john :-). The answer is to either keep two rule sets (as we have it right now with the standard and experimental hill), one for each mood swing, or to *somehow* strike a golden balance between allowing complex algorithms and requiring a small target size. I feel that the pendulum has swung a little to far in the "complex" direction with the current hill-x (I speak out of complete ignorance, never having submitted to the current hill-x). But perhaps somebody can take Bill's challenge and make it to the top with less then 100 lines of code? -Stefan (stst@vuse.vanderbilt.edu) ;redcode ;name Lobot ;author Stefan Strack ;strategy Small JMP bomber/core clearer ;strategy Submitted: @date@ mov -2,<0 loop add #3039,bombptr bombptr mov bomb,3038 ;bomb will land here, turning into a core clearer bomb jmp loop end bombptr -------- P.S.: I've been asked how the @date@ in my programs expands to the current date/time. This is not a feature of the KotH server, but is done at the sending end. I use this "KotH submission" shell script, invoked with the warrior filename as argument: rm sed.cmd echo "s/@date@/`date`/" > sed.cmd sed -f sed.cmd < $1 | mail wms@iwarp.intel.com