Subject: ramscoop-x From: stst@vuse.vanderbilt.edu (Stefan Strack) Organization: Vanderbilt University School of Engineering, Nashville, TN, USA Date: 2 Mar 92 04:03:22 GMT Message-ID: <1992Mar2.040322.29456@vuse.vanderbilt.edu> To break the silence in this newsgroup, I'll post another one of my KotH warriors. "ramscoop-x" is currently #2 on the experimental hill (which has just been enriched by an "Age" field for perseverance. Thanks, Bill). It's of the imp/imp-stomper variety (like bow-n-arrow, Trinity Zwo, and Walze) that seems to do so well on the -x hill, but miserably on the standard hill. In fact, ramscoop-x will not even work correctly under the standard time-slice allocation scheme, because the imps will breach the imp-stomping barricade set up by the program itself. If anyone else has a warrior that exploits the -x time-slice allocation for some uniquely offensive behavior, please post. I am getting the impression that a lot of hill-x programs simply take advantage of their resistance to SPL bomb. Maybe it's time to move on to another experimental hill. We've all had enough time to evaluate the "split CPU-time" modification, and I personally don't think it makes for more interesting warriors. How about it, Bill, ready to launch the "limited write-distance" and/or "post-increment indirect (>)" experimental hill? Cheers, Stefan (stst@vuse.vanderbilt.edu) ;redcode-x ;name ramscoop-x ;author Stefan Strack ;strategy Blankets the core with imps ;strategy Submitted: @date@ impstop equ start-6 i1 equ imp+4000 i2 equ imp+2000 i3 equ imp+1000 start spl impgun bloop mov