Article 2240 of rec.games.corewar: Path: hellgate.utah.edu!dog.ee.lbl.gov!agate!library.ucla.edu!europa.eng.gtefsd.com!emory!news-feed-2.peachnet.edu!st6000.sct.edu!not-for-mail From: wsheppar@sct.edu (Wayne Sheppard) Newsgroups: rec.games.corewar Subject: Iron Trap source Date: 5 Nov 1993 04:27:29 -0500 Organization: Southern College of Technology, Atlanta Lines: 57 Message-ID: <2bd6a1$ufg@st6000.sct.edu> NNTP-Posting-Host: st6000.sct.edu As promised, here is the source to Iron Trap. And here is an explanation: Using a standard scanning setup, I scan until I come across something. I know that I have something at either the A location or the B location. I drop an spl/jmp bomb at the b-location. Then I increment the CMP line so that the b-location is now pointing where the A-location was ( All this is standard for a cmp scanner ) But before I jump back to the scanning loop, I check to see if the b-location is now pointing at an imp. I then do a spiral stun, which lays an spl 0 carpet at the imp location and at -2667 and +2667. This should stop all of the imps. Then a coreclear mops everything up. Against other types of opponents, I function just like a spl/jmp scanner, but just a little bigger and slower. After every other location is scanned, I execute the spiral-stun, but it is located in such a way that it will not affect my code. To prevent everyone from using this design, I'll go ahead and point out the weaknesses: -Have your decoy include alot of imps. -Use 7-point spiral Sorry if I've lost anyone, I'm typing this at 4:30 AM, and I'm a little tired. ;redcode ;name Iron Trap ;author Wayne Sheppard ;strategy CMPscanner with active imp destroyer dist equ 98 scan equ dist*2 a add d,@x c cmp a+dist,a slt #20,@x djn a,<7000 mov j,@c x mov s,