[01:25] MSG: Quit: Lost terminal [01:41] MSG: Quit: Ping Timeout [01:46] weird problem with pmars - using switch like -d 10 results in an error, output shows the help text [01:46] any idea? [01:46] mindistance 100, max length 100 and it works [01:46] coresize 8000 [01:48] oha [01:48] found it [01:50] some wilkies use FOR decoy... but why the error with a MINDISTANCE < 100 ? [01:50] hm [04:53] MSG: Quit: Trillian (http://www.ceruleanstudios.com [07:48] Fluffy: html-manual is now complete (you asked for explanations to "every window") [10:59] Join: Fluffy joined #corewars [10:59] :) [10:59] ahoi [11:06] a hoi a hoi [11:13] * Fluffy has the feeling that someone might have seen too many pirate movies. [11:13] aye [11:17] what ar ye talkin ye land lubber [11:21] can i get the compiled warrior in pure loadfile format, without the rest like "Program xy by yx" and warnings, etc? [11:21] ising pmars [11:24] okay, i'll parse it [11:24] yup [11:25] 'workin on an automated verify function [11:47] Join: Altair joined #corewars [11:47] Hi Altair [11:47] co-hi [11:47] Altair: Are you new to corewar? [11:49] http://en.wikipedia.org/wiki/Corewar might be interesting [11:49] yes, nice entry there [11:49] better than the german one [11:52] Altair: I should have read the logs ... you've been already here :) [12:07] anyone knows, how pmars fills empty operands? JMP +1 ---> JMP $+1, $0.... DAT #1 ---> DAT #0, #0.... is it just the same adress mode? [12:08] DAT #0, #1 of course [12:08] an empty B-field in JMP/SPL is filled with "$ 0" [12:10] and for DAT it should be $ 0, too [12:10] I mean the A-field for DAT [12:21] Join: fiveop joined #corewars [12:45] yeah, thanks... the verify option is extremely useful [12:45] except for some special cases, the new ASM looks good (tested with some warriors from K'stuhl [12:53] why not all? [12:54] Label:OPC is not properly recognized yet, and n m FOR 0...ROF... has a problem, because n is removed by the FOR handling routine [12:55] (Label column nospace opcode) [13:00] looks like a construct like lab n FOR 0 .. ROF at the start of the program is common to get a label that points to source_start - 1 ? [13:01] if this is true, what points the label to, if this is in the middle of the code? [13:37] i use for 0 rof when making comments or testing other structures on code [13:38] but you dont put labels before that and use it, but some koenigstuhl warriors do [15:21] MSG: Quit: Leaving. [15:37] MSG: Quit: Ping Timeout [15:55] Join: Fluffy joined #corewars [15:56] :) [16:18] * bvowk beats fluffy [16:29] damn. [16:39] why? [16:39] I'm innocent! [16:39] * ares looks astonished [16:53] the first time, that fluffy claimed to be innocent [16:53] That doesn't make it less true! [16:59] heh [17:00] I was just hoping that since my evolvers had conquered my benchmark kill that I was going to actually get on nano ;) [17:00] they made a really funky clear [17:00] How long did it take to create that warrior? [17:01] but sadly, the benchmark hill doesn't look anything like the actual hill it appears [17:01] well, actual productive evolving time was likely 4 or 5 hours.. [17:01] but it tends to wander off and navel gaze [17:01] so it took about a day [17:01] 6 processors [17:02] its funny watching the scores, because they start crappy, then its all ties, then someone figures out how to kill, then they go way up, then slowly go down, until someone comes up with a new and exciting way to kill, and then they shoot up again.. then down.. [17:03] Cool. Then why don't put that graph onto your homepage and update the data in realtime? [17:03] Do I repeat myself? [17:03] Do I repeat myself? [17:21] heh [17:21] you do [17:57] Join: Roy joined #corewars [17:57] Hi! [17:57] Hi Roy! [17:58] * Roy survived another vacation [17:59] That probably mean that you don't have any new warriors for nano [18:00] * ares waves [18:00] MSG: Quit: . [18:01] No sorry.. [18:02] I did have a great idea for a new nop warrior while skiing, but I now doubt it'll work [18:02] But going to try it anyway [18:02] Good luck [18:03] Has something to do with airbag, haven't touched those for two years or something [18:03] But I still like the cleverness of them ;-) [18:43] Join: John joined #corewars [18:43] Hi :-) [18:44] Hi test tube [18:44] err ... [18:44] Hi John :) [18:44] Hi Fluffy :-P [18:45] I hope you're not set to verbose [18:45] Of course I am [18:45] I had three ideas to improve the same basic bit of code [18:45] I like it to see how busy you are on nano :) [18:46] Just trying some combinations [18:46] I didn't actually get on though :-( [18:46] Yes :( [18:46] but lotds is now 3rd! [18:46] Hi John [18:46] Hi Roy [18:47] Roy, are you set to verbose for the 94nop hill? [18:47] No :( [19:30] Join: gnik joined #corewars [19:30] hi there [19:30] Hi Gnik :-) [19:30] Hi [19:31] hi [19:31] You seem to be doing pretty well on the nano hill :-) [19:32] I'm pretty sure impossible will get you into the hall of fame [19:33] MSG: Client Quit [19:33] :-( [19:33] Join: gnik joined #corewars [19:33] Trouble with the webirc client? [19:34] i have problems with my isp these days ... [19:34] Oh :-( [19:34] it seems that i had a good idea, but that was so far the only successful warrior ... [19:35] I thought you'd had a few on the nano hill [19:35] Impossible has an impressive percentage of ties [19:36] Are you new to Corewar gnik? [19:38] more or less, i gave it a try a year ago [19:40] I've only noticed your warriors on the nano hill, have you tried some of the others? [19:40] Oh, forgot the tiny hill! [19:40] I was glad to discover the nano hill, that made it easier for me to develop warriors (without all the qscan etc. stuff) [19:40] :-) [19:41] It can still be pretty tough [19:41] I'm struggling with my new warrior today :-( [19:41] I tried the beginner hill and i had a warrior on the 94nop [19:41] Nano hill is the busiest at the moment [19:42] Usually the '94nop hill is busy too [19:42] I had some ideas for nano, but none of them turned out to be good enough [19:42] I take it you've seen the stuff on http://corewar.co.uk/nano.htm ? [19:42] Don't give up on the ideas completely [19:42] yes, nice site ;) [19:43] Put them to one side and have another look one day [19:43] Thanks [19:43] yes, that's probably a good idea [19:43] It needs a lot of work though [19:44] I thought burp was going to push off the last of the dragons :-( [19:46] I've heard a rumor that issue 2 of nanoWarrior will be ready soon :-) [19:47] do you think nano papers can compete with evolved warriors ? [19:47] Oh that's great to hear! [19:47] Let me know, if you need an article/warrior concept for it [19:48] Yes, have you seen the nano paper on infinano? [19:48] gnik: They can. One of the warriors on nano@SAL is a nano paper :) [19:48] gnik: any contribution would be greatly appreciated [19:48] which one ? [19:48] Yes, which one? [19:48] won't say, but i'll send all of my nano warriors to Koenigstuhl from time to time [19:49] ... as soon as they've been pushed off [19:49] :-) [19:50] john: is it a good idea to publish impossible in nanowarrior now ? [19:50] ... and Staphylococcus aureus is 3rd on infiniano [19:51] gnik: there is a change publishing it while it's still on the hill might hurt it [19:51] change EQU chance [19:51] * Roy starts to think a selfreplicating airbagged bomber isn't such a great idea [19:51] no, it will be hurt because I'll probably add it to my benchmark [19:51] Because several people will add it to their benchmark [19:51] ;) [19:51] :-) [19:52] I've got a quickstart nano benchmark for yace here http://corewar.co.uk/yacenano.zip [19:52] It contains no hill warriors ;-) [19:52] I'm planning to send another warrior, based on the concept of impossible to nano, so probably i should wait with publishing it ... [19:53] yes! ... until it is pushed off [19:53] * Roy has Yace warriors with all the koenigstuhl warriors...! [19:53] ..benchmark.. [19:54] Roy: You should leave out the last 50..80 warriors [19:54] But I have another warrior I could publish in nano warrior. [19:54] :-) [19:55] first spl 1, <0 [19:55] There's an article which contains a selection a new warriors which a couple of paragraphs about each [19:55] silk spl @0, gnik: Then send it to with subject 'Koenigstuhl entry' and you'll soon find it at the nano Koenigstuhl [19:55] mov.i }-1, >-1 [19:55] go mov.i @-3, <-3 [19:55] loop jmp {-1, }0 [19:56] mhmm, maybe i should use a proper irc client [19:56] * John tries to step through the code in his head! [19:57] gnik: What's the value of pStep? [19:58] jmp {-1, }0 has got to be the neatest instruction I've seen for a while! [20:02] Heh that is really cool indeed! [20:03] not bad, not bad [20:04] Join: Altair joined #corewars [20:04] Hi Altair [20:04] Hi [20:06] fluffy: pStep is an arbitrary value, like 42 ... [20:06] Hi Altair [20:06] sry "[12:47:50] Altair: Are you new to corewar?".....................i got up at that time so....... [20:06] hi @all^^ [20:07] gnik: 42 doesn't score very well. At lot depends on the actual value(s) used on nano [20:07] ^^ [20:07] but 42 is so lovely [20:07] not for the warrior in question [20:08] faithful 42 always so cheerful and all [20:08] sad.^^ [20:08] But its the answer fluffy... [20:08] yes, I know [20:08] 42 is too close to CORESIZE/2 [20:09] Try something like 13 or something [20:10] isn't good either [20:10] I tried !{0-79} ... [20:11] yay, yace smashed explorer [20:11] ?? [20:12] had too high priority, ate all power [20:12] No.. my idea suckes (again) [20:12] Mizcu: do I need to reduce something in that CFG file? [20:12] and I can't even spell sucks.. [20:13] 151 in 2 minutes [20:13] (and changed benchmark) [20:13] Mizcu: 152.03 in 5 hours ;-) [20:13] John: dunno, havent made extensive research on the setting so far [20:15] I can't see anything in there to reduces Yace's priority [20:16] John: it can be changed from taskbar [20:16] Ah, okay [20:21] 156.. [20:25] are you kidding me? [20:25] there's a nano paper?1 [20:25] ! [20:25] There are multible nano papers, but even one on the hill ;-) [20:25] Hi Bvowk! [20:26] the on the hill part is what I found shocking [20:26] hey met [20:26] what's wrong with a nano paper? [20:26] Nano paper hurt LotD, that's what wrong with nano paper :-P [20:27] unimpressive real-scores [20:27] You mean more than the 276.1 from Trypanosoma brucei? [20:28] :-( [20:30] Wow, stormy weather currently...! [20:31] whoa, Roy is here [20:31] I was here all the time...! [20:32] nothings wrong with nano paper, but I didn't think it would be possible on the nano hill [20:32] That's what I wanted you to think Bvowk! [20:37] hehe [20:38] heh, i got Roy in a lock [20:39] Huh? [20:40] Overloaded him with code [20:40] Yes :) [20:40] * Roy made a TODO.txt for when his head is clear again [20:43] hrm [20:43] what the hell.. i dont trust this barely-modified benchmark anymore [20:44] my current nano benchmark is obviously far far from the mark [20:44] bvowk: Take the top50 from infiniano [20:44] john: when will nanoWarrior #2 get released ? [20:46] gnik: I believe mid-January [20:46] who's currently in charge of the CoreWarrior? [20:47] sf writing most of it [20:47] Fluffy: Fizmo, Neo and me :-( [20:47] and how far is it from being published? [20:48] Too far :-( [20:49] MSG: Quit: CGI:IRC [20:49] What CoreWarrior really needs are more people helping to create it. [20:49] you should make assignments [20:49] John: Can you be more specific? [20:51] Well it's usually created by a couple of people submitting articles (which are always in short supply) [20:51] And someone else who writes the introduction, summary of what's been happening on the hills, etc, etc. [20:52] hmm [20:53] Writing an article for CoreWarrior is very time-consuming [20:55] So is writing warriors :( [20:56] what teh sheet [20:57] evolver just churned out something that gets 153 against the top-50 nanoinfi [20:57] * John wonders how it would score on the nano hill [20:57] Does anybody want to see my latest (failed) attempt to writing something completly new for the 94nop? [20:58] yes [20:58] Yes, me too :-) [20:58] I'll post it on r.g.c then, its a self replicating airbagged bomber (kinda) [21:00] John, how long are you planning to stay here? [21:02] Ill let Yace churn a moment more, to see if something good arrives [21:02] I'm planning to go in about 5 mins [21:02] hmm, Nano Bob VII didn't do very well :( [21:02] Because I have to be up at 3am [21:02] It's time to change the name [21:03] I wonder if its worth to send this one right now [21:03] yes [21:07] blah, ill get last position or something [21:07] oyu'll never know until you've submitted it [21:08] i missaw one modifier [21:08] yay, second last [21:08] John won't like that! [21:09] Hmmm... [21:09] Its on r.g.c [21:09] * John gets ready to kick someone [21:10] Hmmm... looking at this - http://sal.math.ualberta.ca/warrior.php?key=nano&id=1117&t=4496&sortby=score&dir=asc [21:10] And it looks like I should kick Fluffy! [21:11] Send one quickly Fluffy!! [21:11] MSG: Quit: Ping Timeout [21:11] No, my generator needs serveral hours to "create" a new one. [21:12] * Fluffy runs away and hides behind bvowk [21:15] * John waves to LotD :-/ [21:15] the aged king is dead! Long live the king! [21:15] Thanks, Mizcu ;-) [21:16] Still congrats John, you beat Shutting :) and earned a good place on the HoF [21:16] Thanks Roy [21:16] * Fluffy congrats John [21:16] Now we've got to watch out for Zul passing us! [21:17] I wonder how long it take to have the first +1000 nano warrior [21:17] long enough [21:18] * Fluffy waves [21:18] * John bets it will be Bombus Sylvestris [21:18] * John waves [21:18] MSG: Quit: fluffy.i < 1, # 42 [21:22] sheesh, an assault on nano [21:23] Time for me to go too [21:23] * John waves [21:23] * Roy waves to John [21:23] MSG: Quit: jmp {-1, }0 [21:23] * Roy also waves AT John (sigh...) [21:37] not good, not at all.. [22:44] * Roy waves [22:44] MSG: [23:18] Warrior against top-50 nanoinfi: 131.86 points, 4214 wins, 4525 losses, 3511 draws.