[00:38] hrm. [00:48] MSG: Quit: Trillian (http://www.ceruleanstudios.com [01:36] hrm. [03:02] Join: argiopewe joined #corewars [03:30] MSG: Ping timeout: 255 seconds [03:44] Join: argiopewe joined #corewars [03:56] MSG: Ping timeout: 255 seconds [08:26] Join: Philb joined #corewars [08:28] Join: Philb_ joined #corewars [08:30] Part: Philb_ left #corewars [08:31] MSG: Ping timeout: 255 seconds [08:52] Join: Philb joined #corewars [08:53] Part: Philb left #corewars [10:22] Join: fiveop joined #corewars [11:18] hi folks, peeps and whatnot [12:36] Join: Core_old joined #corewars [13:40] Join: argiopewe joined #corewars [14:33] MSG: Ping timeout: 255 seconds [14:44] MSG: Quit: Lost terminal [14:45] Join: fiveop joined #corewars [15:04] hrm [15:04] greetings all [15:09] grtz [15:14] its nice to see that met and the spoon creatures are getting along well [15:20] MSG: Quit: Trillian (http://www.ceruleanstudios.com [16:13] Join: Fluffy joined #corewars [16:13] :) [16:29] fluffy flounder [16:30] grmpf [16:39] * bvowk mocks touchy fluffy [16:40] I scored my huge nanopit against my valhalla benchmark and infinano.. [16:40] It was a test of an idea, which obviously failed [16:40] and? Any interesting results? [16:40] yeah [16:40] very interesting.. [16:40] most of the warriors really suck.. but some really unexpected gems showed up [16:40] I've already klicked on "Tell me more!" [16:40] ie: the koth I had yesterday [16:41] who's actually still on top.. [16:41] strangely enough [16:41] :) [16:41] but I've got to be going now.. [16:41] going skiing [16:41] Have fun! [16:42] tommorrow I'll process the results :) [16:42] I've been quite astonished to see that I still have warriors on nano. [16:42] me too ;) [16:42] Some seem to have survived your attacks :) [16:43] and how there are 4 of my warriors in the top-50-nano-HoF [16:46] now that you mentioned.. [16:46] continuin the yace-soup [16:46] how long did it already run? [16:47] 16 hours something [16:47] actually, i am starting a new one now [16:47] :) [16:47] the settings still need some fixing [16:48] and ill put it in ramdrive [16:48] So far I never got to the point to have YACE evolve sth. useful. [16:48] I've always given up after the first failures. [16:53] 'thar [16:53] huh? [16:53] heck, if i wasnt so paranoid about security, i could install apache-or-equivalent and let people view the evolution realtime ;) [16:54] why don't you regularly upload the overview-html-file to your homepage? [16:54] that's secure enough [16:54] because it updates once every 10-10 seconds [16:54] 10-20 [16:55] less time when it figures out how to kill stuff [16:56] hmm [16:58] now it runs a cycle per 3-4 seconds [16:58] then adjust the settings to have a really large hill :) [16:58] i think soup of 500 is enough [16:58] i want to do something on the side too [17:00] 141 in benchmark reached [17:00] itll drop by 20 until next benchmark-cycle.. [17:00] send to the hill :) [17:05] oh god i hate these ones [17:05] ok? [17:05] spl.ba # 77, } 37 [17:05] mov.i $ 45, { 79 [17:05] mov.i @ 32, { 78 [17:05] mov.i @ 48, { 78 [17:05] mov.i @ 48, { 78 [17:06] what's wrong with these warriors? [17:06] i dont trust them [17:06] i have dropped the chance for inst-copy to the bottom, but these still appear [17:06] if i have hany higher inst-copy chance, these will flood the whole soul and get stuck like a bubblegum on an 80's hairstyle [17:06] Do they score that bad? [17:07] i am yet to get good scores out of such [17:11] tweak, tweak, tweak, hell [17:12] i really need to start coding that mizvolver , tweaking settings on yace isnt helping [17:12] Why don't you start with modifying YACE? [17:13] 'caus modifying YACE doesnt count as a project for the course on C [17:13] Will you write your own MARS? [17:14] hell no [17:14] ill use exhaust [17:14] :) [17:14] Are there any restrictions for that C programming task? [17:14] i dunno :) , were arent supposed to be making it yet [17:15] hmm [17:23] spl.ab # 0, $ 34 [17:23] mov.i # 39, { 29 [17:23] mov.i < 65, > 78 [17:23] djn.ab $ 78, { 79 [17:24] Yes, 4-liners have the advantage of being less likely crippled by a dat-bomb :) [18:07] wtf.. [18:07] spl.ab # 73, * 33 [18:07] mov.i > 62, { 0 [18:07] div.i $ 30, } 0 [18:07] jmp.ab @ 71, } 62 [18:15] Join: Roy joined #corewars [18:15] Hi all [18:15] Hi Roy [18:17] What are you up to lately? More nano? [18:17] Yes, that's all I have power for. [18:18] Hehe [18:18] I've been reading some about XSS today, and now I'm trying it on some websites [18:20] ts ts ... [18:21] Just fun stuff, nothing harmfull.. [18:23] hmm, more of some very interesting testing [18:24] i am running yace with random fitness selector run for every 5 rounds [18:25] i am expecting horrible waste of cpu-cycles resulting [18:25] Fluffy, stuff like this: http://tinyurl.com/2dftlw [18:26] It is a pity that it doesn't work, because I usually surf with JavaScript disabled :) [18:28] heh grr.. [18:28] ... and even with JavaScript enabled it doesn't seem to work :) [18:28] I only get a page (Daily Mail) with empty search results [18:29] Well yeah, for XSS you need scripting of course :P [18:30] Even after I've enabled my stupid mode AND ignored all bad security signs, it still doesn't work. [18:31] Roy, you really can't expect the "victim" to help you that much ;) [18:32] It doesn't? ah, I only tested in IE [18:32] no, it doesn't [18:33] What was it supposed to do? [18:33] Show a fake news item, inserted by me [18:34] Join: Core_old joined #corewars [18:34] Hi old Core! [18:38] hey [18:38] back from soccer again.. :-) [18:40] You shouldn't so soccer, but cw! [18:40] mm, Miz's nuclear smeltdown-noodles [18:40] typo intentional [18:42] The name of a warrior or a meal? [18:42] meal [18:44] instant shrimp-noodles with triple chili, lime juice PLUS habanero-powder and thai mix [18:45] ... plus a couple of questionable additions, which might cause cancer, right? [18:45] only in the noodles [18:45] Haven't you heart of noodle-induced cancer? [18:45] ;) [18:46] if you want to see questionable things added, come see i make my secret chili-con-carne [18:50] noodle-induced Cancer? brrr.... [18:50] chili-induced.. [18:50] corewar-induced? [18:51] eye-Cancer? [18:51] (which is mostly likely brain-cancer ;) [18:51] * Core_old needs a shower... [18:51] afk [18:51] ;-) [19:08] scores around 140 now [19:23] * Fluffy waves [19:23] MSG: Quit: fluffy.i < 1, # 42 [20:15] MSG: [20:55] 8) [21:51] Join: Kaiser206 joined #corewars [21:51] hi there [21:51] Part: Kaiser206 left #corewars [21:52] by by [22:32] Join: Core_old_ joined #corewars [22:33] hmm, a wall met [22:33] MSG: Client Quit [22:34] 300 cycles with no better result [22:35] MSG: Ping timeout: 255 seconds [22:39] Join: Roy joined #corewars [22:39] Yay, made is Mozilla safe now :) still needs javascript of course http://tinyurl.com/38p6lh [22:39] h R [22:40] still the same focking warrior after the 3000 cycles.. [22:40] maybe time for reboot [22:41] or some twistin' [22:41] Heh, my evolver isn't doing so well with nano [22:41] (or just in general) [22:42] Now scoring around 100 on the hill [22:49] hmm, maybe ill mod yace a bit tomorrow.. [22:49] You did that before? [22:49] only the cfg-file [22:50] Weighing the opcode/modifiers works well for my evolver (upped the scores quite a bit) [22:50] i could specialize yace for the cfg to cut the size just a little [22:51] And I have something like 50% of the time choose a random value between 0-coresize, and other 50% of the time choose a value between -warriorlength/+warriorlength [22:51] (will hopefully increase the change of loops etc) [23:03] printf("dont panic. Dont Panic! DONT PANIC!!! PAAANNNICCCC!\n"); [23:04] for (x=0; x<100; x++) printf(" PAAAAANIIIIIIIICCCC!!!"); [23:04] from Yace's source [23:13] hehe, actually, I've seen that I think :S [23:13] hopefully not, its triggered by failure in making output-file [23:15] Does it also give something like that when reading the cfg? [23:15] I might have seen it there [23:17] nope, it doesnt give specific error when cfg fails [23:18] just blah.blah not set [23:25] zzz << Miz [23:28] MSG: Quit: Lost terminal [23:35] MSG: