[06:36] Join: Metcalf joined #corewars [06:47] MSG: Ping timeout: 245 seconds [06:48] Join: Metcalf joined #corewars [07:23] MSG: Ping timeout: 245 seconds [12:59] Join: Xashi joined #corewars [12:59] Hi [12:59] h [13:15] MSG: Ping timeout: 245 seconds [19:03] Join: Metcalf joined #corewars [19:04] Evening all... [19:07] 'ning [19:09] MSG: Ping timeout: 245 seconds [19:09] Join: Metcalf joined #corewars [19:16] Join: OoS joined #corewars [19:16] MSG: Ping timeout: 245 seconds [19:27] MSG: Ping timeout: 245 seconds [19:28] Join: OoS joined #corewars [19:33] MSG: Ping timeout: 245 seconds [19:45] Join: OoS joined #corewars [19:53] MSG: Ping timeout: 245 seconds [19:53] Join: OoS joined #corewars [20:00] MSG: Ping timeout: 245 seconds [22:26] Join: Lazareth joined #corewars [22:28] hi [22:28] hiya [22:52] Join: Metcalf joined #corewars [22:52] Hi [22:52] Hi there [22:53] Hi Lazareth [22:55] Are you working on anything at the moment? [22:55] not really, just keeping the interest warm [22:56] until I have enough time left over to fully immerse myself in redcode [22:57] :-) [22:57] The last thing I worked on started to look ugly, so I've left it for now [22:58] Heh. The last thing I made was an attempt to marry my backwards coreclear with a scanner. Found out the ONLY thing it was able to detect was itself, meaning it simply delayed the coreclear for an entire coresize linear scan [22:58] Funny stuff happens when you're new =P [22:59] But now you know something's wrong, you can fix it right? [23:00] yeah, I found the error. The loop was set up wrong. Haven't gotten around to rewrite it. [23:02] The idea is kinda simple. Scan at intervals (well, right now it is linear, ineffective but simply for the purpose of practice), and when it finds something start bombing DAT backwards from ten addresses ahead of the place it found something. The coreclear was... backwards from birth, how I made it from the start. Weird newbie code. [23:03] oh, and the coreclear is clever enough to jump over the active code ^^ only thing in the program code I'm proud of. [23:04] activity? oh noes! [23:11] MSG: Ping timeout: 245 seconds [23:11] Join: Metcalf joined #corewars [23:13] :-) [23:13] aww, broke the silence [23:13] All coreclears used to be backward! [23:14] they did? I made it without looking at anything, just thinking. How come they used to be backward? Mine ended up as such because of a coding peculiarity. [23:15] Until the '94 standard, post-increment indirect didn't exist [23:18] oh [23:18] and I used predecrement... which was why it was backward. Didn't know it was the only (immediate) option back then [23:19] Which, I kinda should have guessed, but I've only worked with the newest and not with 88 only [23:20] MSG: Ping timeout: 245 seconds [23:22] Join: Metcalf joined #corewars [23:31] MSG: Ping timeout: 245 seconds [23:31] Join: Metcalf joined #corewars [23:32] * Metcalf is curious about some of Inversed's warriors [23:33] like? [23:34] Monolith [23:35] cant find it with a quick check on any active hill [23:36] '88 [23:37] http://www.koth.org/lcgi-bin/warriorinfo.pl?hill:1:taken:1 [23:37] I'm also not sure what's special about Monster Human Grunt, though I think Inversed gave some clues [23:39] probably a very, very, very long bombing-run .5c stone [23:40] or maybe a type of SoV-stone [23:40] SoV? [23:41] if i had the know-how, id put up a SoV-stone into matlab and search for as long runs as possible.. [23:41] SoV = Son Of Vain [23:41] the most long-lasting warrior ever, an SoB to fight against [23:41] okay :) [23:43] MSG: Ping timeout: 245 seconds