[00:07] Join: Caelian joined #corewars [00:09] sdfklfsö [00:09] stupid me [00:10] no, didnt help [02:27] MSG: Read error: Connection reset by peer [02:29] MSG: Read error: Operation timed out [02:45] Join: Caelian|w joined #corewars [02:45] Join: Caelian joined #corewars [03:20] Join: Caelian_ joined #corewars [03:24] MSG: Ping timeout: 252 seconds [04:38] "my dying words are 'hastur, hastur, hastur...'" [05:08] MSG: Ping timeout: 252 seconds [05:08] Join: Caelian|w joined #corewars [06:52] Join: Metcalf joined #corewars [06:52] Hi :-) [07:01] MSG: Ping timeout: 252 seconds [07:38] hrm. [07:56] MSG: Quit: Ex-Chat [08:44] grtz [08:50] great, 20 hours up straight and my mood is getting more and more depressed [08:51] i still need to squeeze 11 out.. [09:10] MSG: Read error: Operation timed out [09:31] Join: Mizcu joined #corewars [09:46] MSG: Read error: Operation timed out [09:47] Join: Mizcu joined #corewars [10:11] Join: Caelian joined #corewars [10:16] hmm, i have an interesting dilemma [10:16] let us assume we have an warrior with airbag - one that allowes a process to escape into a clear when the mail loop is damaged [10:17] against a stone, the best clear would be d-clear because it is small with gate capable of taking on heavy imps [10:17] against paper, best would be SD-clear [10:18] against scanners, best would be mov >gate, djn {gate -clear because it can wipe a spl-carpeted warrior within reasonable time, unlike d-clear which leaves spl's active [10:19] (spl-carpeted warrior referencing to the main loop) [10:27] Three choices, three answers. [10:50] Join: Core_new_ joined #corewars [11:03] Join: inversed joined #corewars [11:04] hi inv [11:04] Hi Miz [11:05] I was thinking about that airbag dilemma too [11:06] And I decided to write airbag warrior with _both_ d-clear and S(S)D-clear [11:12] parallel or separate? [11:12] separate [11:12] Can't do it in parallel, SD would stun d-clear [11:13] still, the decision making between the two is kinda challenge [11:14] If damaged -> probably by stone -> run d-clear [11:14] else run S(S)D-clear [11:14] i dont think anyone wants to use more than seq/sne/slt - jmnz - jmnz for the decision [11:15] There is no need for extra decision instructions [11:15] If airbag falls, there's one jmp and if bombing run was finished normally, there is another jmp [11:16] so you had that in mind, right [11:16] I have a working version [11:17] But it should be improved/optimised [11:29] Join: Metcalf joined #corewars [11:30] Hi [11:30] Hi JM! [11:30] Hi Inversed [11:30] Is there anything new on the Russian Corewar sites? [11:31] I don't visit them often, they're so lame [11:31] Oh :-( [11:32] The wiki looks interesting, but unfortunately I can't read it [11:33] It featured .33c CMP-scan until I corrected it [11:34] :-) [11:38] MSG: Ping timeout: 252 seconds [11:40] Join: Metcalf joined #corewars [11:46] MSG: Ping timeout: 252 seconds [11:57] MSG: Ping timeout: 252 seconds [11:58] Join: Metcalf joined #corewars [12:46] MSG: Ping timeout: 252 seconds [12:46] Join: Metcalf joined #corewars [13:13] MSG: Ping timeout: 252 seconds [13:52] Join: Core_new_ joined #corewars [14:23] MSG: Ping timeout: 252 seconds [14:58] MSG: Quit: . [18:15] Join: Core_new_ joined #corewars [18:53] MSG: Ping timeout: 252 seconds [20:09] Join: Fizmo joined #corewars [20:09] hi hi [20:10] MSG: Client Quit [21:00] Join: Metcalf joined #corewars [21:07] MSG: Ping timeout: 252 seconds [21:11] Join: Metcalf joined #corewars [21:14] MSG: Read error: Connection reset by peer [21:14] Join: OoS joined #corewars [21:32] MSG: Ping timeout: 252 seconds [22:10] Join: Core_new_ joined #corewars [23:36] MSG: Ping timeout: 252 seconds