[2023-01-01 20:46:23.101936: 2022-12-25-1.log.gz] [2023-01-01 20:46:23.101936: 2022-12-25-2.log.gz] [2023-01-01 20:46:23.101936: 2022-12-25-3.log.gz] [17:58:46]: Hi! [17:58:51]: hi. my settings are bad, æ, hold on. [17:59:06]: fixed. [17:59:22]: I'm surprised that this only uses about 2GB of RAM. [17:59:37]: me too, considering how apparently bad the new versions are in terms of performance. [17:59:42]: maybe it's mostly clientside. [17:59:58]: It only uses 2GB of RAM on the client too. [17:59:59]: my client is using a lot more than 2GB of ram, for instance. [18:00:06]: Well, it isn't for me. [18:00:12]: inverse skill issue. [18:00:22]: ?!. the tabs are different. [18:00:22]: It's allocated 1.8GB and is currently using 1.4GB. [18:00:43]: now there's a "colored blocks" tab?! [18:00:56]: and they're arranged by rainbow order instead of item id?!?!? [18:01:06]: wow, is this monopsony? [18:01:11]: It said "overhauled the creative inventory" and I'm going to see if Milo works. [18:01:14]: Monopsony can probably be ported. [18:01:38]: what of HRainbows™? [18:01:48]: Antimemetic. [18:01:55]: no they aren't. [18:01:56]: there's one right here. [18:02:09]: Oh, right. [18:02:12]: why do the computers look so textured? [18:02:19]: I don't know, I loaded the old resource pack. [18:02:36]: me too. [18:03:51]: Okay, Milo clearly does not work. [18:04:01]: did they subtly change the functions or something? [18:04:10]: No introspection module, which Milo needs for some reason. [18:04:16]: ?!?!. [18:04:33]: The API looks... more or less identical? I'll run Monopsony. [18:05:12]: Oh, right, this is trying to run over SPUDNET accursedly. [18:06:46]: Okay, this is unhelpful. [18:06:58]: Turtles no longer have inventory methods. [18:07:28]: wait, what?! [18:07:37]: are you just meant to use the accursed peripheral API now? [18:07:40]: The Plethora inventory methods. [18:07:48]: You can use getItemDetail and such but ew. [18:07:50]: how do you even wrap yourself? [18:08:00]: You CANNOT use them, I mean. [18:08:03]: The Plethora stuff. [18:08:06]: oh, what? [18:08:08]: Which Monopsony evidently ran on. [18:08:20]: so they effectively destroyed CC item transport? æ. [18:08:28]: No, no, this is workable. [18:08:34]: You just can't move out of a TURTLE as easily. [18:08:38]: i don't entirely understand the situation as you're describing it. [18:08:42]: i see. [18:08:47]: You used to be able to call list and stuff on turtles. [18:08:48]: You cannot now. [18:10:27]: It looks like I can fix insert_stack by complicating the network code. [18:10:37]: The originator turtle has to send over the typecode and stack, essentially. [18:10:40]: how exactly does "monopsony networking" work, anyway? [18:10:44]: I forgot. [18:10:49]: as in, what's the general model? [18:10:58]: Client/server. [18:11:04]: Over LAN or SPUDNET. [18:11:11]: as in, how do clients actually ask for and receive things? [18:11:18]: They send messages.] [18:11:23]: are they presumed to be physically connected to receive items/ [18:11:24]: ? [18:11:31]: Yes, or they can link via ender chest. [18:11:44]: i see. cool. [18:12:20]: Okay, cool. You can still move into and out of them, it's just annoying about it. [18:14:04]: good. [18:14:11]: well, not good. item transport should be better. [18:14:12]: but still. [18:19:04]: Okay, insert works. [18:19:06]: Extract will not. [18:19:09]: are spruce fence gates optimal? [18:19:12]: Sure. [18:20:43]: Okay, it is fully working as far as I can tell. [18:20:52]: I lied. [18:20:59]: what of the ominous UI-intersecting error? [18:21:09]: I said I lied. [18:21:14]: you could be lying. [18:21:17]: Ah. [18:21:33]: I may have to actually read the docs. [18:21:36]: !. [18:23:00]: It now ACTUALLY works to the extent that I can tell. [18:23:03]: !!!. [18:23:51]: i want to be able to automate resources into Monopsony, ideally. [18:24:07]: which would probably just require "quotas" to be implemented to not fill all storage ever implicitly, right? [18:24:16]: Yes. [18:24:23]: maybe you're to? [18:24:36]: It would make sense. [18:26:16]: Can you implement a "bamboo farm"? [18:26:19]: oh wow, you can "waterlog turtles". [18:26:27]: i could do that. i was planning to implement a kelp farm. [18:26:32]: Also, would you be annoyed if quotas just worked by discarding extra things periodically? [18:26:35]: Oh, sure. [18:26:44]: yes, i would be annoyed by that. please just reject the extra items. [18:26:49]: Why? [18:27:00]: well, presumably the client thing would handle disposal. [18:27:10]: Do you really want to do that on each thing separately? [18:27:20]: i want the option to at least. [18:27:32]: I see. [18:28:20]: idea: i could make more redundant item software. [18:28:25]: You did on SC2, I think. [18:28:34]: i know of azide, yes. [18:30:20]: oh no. bamboo has about double the growth rate of kelp, but about half the fuel density. [18:30:25]: now i have to make actual "decisions". [18:31:39]: oh, it's much less fuel density actually. [18:32:14]: bamboo/kelp farms sound annoying to scale up much so i'll do it "later" on SC3. [18:34:37]: Do you at least know _how_ it is to be scaled up? [18:35:14]: well, there are a few ways. i could have one moving turtle. but then i'd be worried about losing some efficiency due to things possibly being able to grow taller at the expense of me having to handle "item collection" (bad). [18:35:41]: not to mention that kelp requires some processing before becoming usable fuel. [18:35:54]: Can you just make a lazy automatic bamboo farm? [18:36:00]: probably. [18:36:02]: Do that then. [18:36:06]: We should have it ready to go on SC3. [18:36:06]: the scaling problems remain. [18:36:24]: Try fixing them. [18:36:30]: explain this, then. [18:40:29]: you know, i feel like this is so bad that it might not even be net-positive fuelwise,. [18:40:31]: . [18:40:53]: each bamboo gives a total of 2 fuel. [18:45:56]: okay, this is a naive and bad bamboo farm. [18:46:12]: it moves utterly minimally, mostly, to hopefully ensure that it's net positive. [18:46:46]: oh, it has no output yet. i'm sure that's not hard to add on with a single modem. [18:48:01]: it waits for there to be bamboo in front of or below it. [18:48:06]: I see. Why? [18:48:13]: moving costs fuel. [18:48:16]: bamboo restores an entire 2 fuel. [18:48:45]: i do not want to make a horrible accursed fuelless design, before you ask. [18:49:01]: if we really wanted to go there, we could just make a piston based one. [18:49:12]: Maybe we should. [18:49:21]: actually, a piston based kelp farm sounds way more sensible than any of this, really, yes. [18:49:29]: the turtles can just handle the processing afterwards. [18:51:59]: idea: apiaristics exchange? [18:52:02]: What of it? [18:52:07]: you still haven't really specified what the problems are. [18:52:13]: Do you want me to? [18:52:17]: well, obviously? [18:52:46]: Well, I probably need to ensure that people have enough krist/iron tokens to fill an order they submit, right? [18:53:06]: sure. you also store the krist/iron tokens, so, how is that a problem? [18:53:31]: Which requires that either the order matching thing has to check this on each order, or there has to be some annoying complex logic every time an order is filled to mark people's orders as "fillable/not fillable". [18:53:47]: i don't see what the problem is with just accessing a databse each time. [18:53:50]: "brb". [18:54:05]: Well, it would be slightly annoying and there might be concurrency issues. [18:54:11]: Actually, there won't be concurrency issues, it is fine. [18:54:24]: databases are literally metaphorically designed for this. [18:54:30]: ""brb"" (realer). [19:30:09]: "back". [19:30:25]: how much Monopsony did you make? [19:40:25]: I made zero (0) Monopsony. Did you want some? [19:40:32]: ideally, yes. [19:40:49]: Well, to spite you, I might say "PRs welcome" but then not tell you where to submit them. [19:40:58]: I could give you access to the RSAPI monorepo but that would leak information horribly. [19:41:11]: idea: computer craft. [19:41:22]: Idea: MonopsonyAutocråft™. [19:41:34]: is that even real? [19:41:37]: No. [19:41:45]: It will use new quaternionic logic. [19:42:05]: deploying magenta. [19:42:13]: Æ. [19:43:19]: Anyway, would my hyperlazy™ periodic-discards quota system be THAT bad? [19:44:04]: probably. [19:44:15]: i don't really understand what would be so hard about this. [19:44:28]: you already know how many items are in the system and how many are incoming! [19:44:33]: just accept only some of them. [19:45:14]: !!!!!!!!. [19:45:21]: Well, the problem is that I would have to write slightly more complex code for it. [19:45:38]: checking if a number is greater than another one isn't much complexity. [19:46:08]: Ugh, fine, I GUESS I know how I could do it now?! [19:46:16]: cool. [19:46:21]: you should do it. [19:46:24]: What? Why? [19:46:37]: well, it would optimize paperclip production by 2% in the future. [19:46:52]: This adds other problems actually: client code might become confused if it doesn't have all the items moved but there isn't an error. [19:47:00]: wait, really?! [19:47:07]: Well, there's only one client program, but it might. [19:47:08]: why don't you just tell the client how many items were moved, like pullItems does? [19:47:15]: It might, I forgot. [19:47:36]: are you enjoying the cyan zone? [19:47:37]: Ah yes. It doesn't because that would have been silly. [19:47:43]: why doesn't it? [19:47:57]: I didn't see any particularly good reason to do it and it would make the code more complicated. [19:48:12]: well, there are other reasons it could only partially succeed? [19:48:16]: Like what? [19:48:18]: like if it ran out of slots but still managed to put some items in anyway. [19:48:29]: It just errors in that case. [19:48:35]: and transfers 0 items? [19:48:42]: No, not always. [19:48:45]: ?!?!?!?. [19:48:47]: bee you utterly. [19:48:57]: Okay, fine, you made your point, this will not add much to the inelegance. [19:48:58]: please implement this sensibly and just tell the client things. [19:49:11]: did you MODIFY the cyan zone?! [19:49:13]: Yes. [19:49:15]: Please pay attention. [19:49:16]: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!. [19:49:35]: Wow. The cyan zone is NOT durable. [19:49:43]: well, it's only made of cyan. [19:49:49]: cyan is less durable than orange, or magenta. [19:50:24]: Oh, right. [19:50:30]: your "obsidian" is not very good, apparently. [19:51:16]: In what situation would the quota limit being reached meaning that items are just left in the insert handler be better, though? [19:51:52]: there are reasons why i might want what is effectively a "priority splitter". [19:52:05]: So now you want MULTIPLE Monopsony networks?! [19:52:19]: the other output might not be Monopsony. [19:52:23]: I guess. [19:53:15]: oops. [19:53:16]: Oh bee, damage incurred. [19:54:37]: idea: attack. [19:54:47]: Oh no, a TNT cannon (real). [19:54:50]: yes. [19:54:59]: oh no. my plans have been foiled. [19:55:07]: (i.e converted into foil) [19:55:49]: i'm very good at TNT cannons. [19:55:53]: Aren't we all, really? [19:56:04]: Idea: SwitchCraft TNT cannon "defense" grid. [19:56:14]: won't TNT probably just be boring and not work? [19:56:18]: Well, yes. [19:56:34]: Please do not aim the TNT cannons at Monopsony. [19:57:08]: TNT cannons? what a ridiculous accusation. [19:57:55]: wow, this is not very good. [19:58:02]: Maybe you need machine learning. [19:58:09]: Oh bee. [19:58:10]: oh, cool. [19:58:15]: i used machine learning, yes. [19:58:24]: GPT-812 advised me to make changes to it. [19:59:01]: ?!. [19:59:19]: it occurs to me that this is very random. [19:59:39]: AÆÆÆ. [19:59:42]: Oh no, the machine unlearning. [19:59:47]: a TNT thing phased through the block. [19:59:50]: did you do this?! [20:00:01]: The machine unlearning did. [20:02:47]: bee. my tnt apification devices keep apificating. [20:02:55]: oh no, extra shielding? [20:02:58]: whatever will i do. [20:03:00]: As a countermeasure, yes. [20:03:05]: Oh no. [20:03:23]: those aren't enabled. [20:03:30]: Oh. Oops. [20:03:33]: Well, I can adjust that. [20:03:43]: that would cause unacceptable disruptions. [20:03:52]: You might have to be able to accept them, considering. [20:03:58]: despite? [20:04:11]: BEEEE you, Monopsony is important. [20:04:12]: wow, how durable are turtles?! [20:04:18]: Turtles are indestructible I guess. [20:04:19]: the monopsony seems fine. [20:04:31]: The chests are less fine. [20:04:34]: oops. [20:04:39]: what were you using those for anyway, storage? [20:04:41]: Yes. [20:04:44]: oh. [20:05:55]: Idea: potato plex. [20:05:59]: oh no. [20:06:14]: i totally "fear" this. [20:10:15]: why are they multicoloured? [20:10:19]: PotatOplex. [20:10:21]: they briefly mimicked the windows colours. [20:10:24]: i resent this. [20:20:31]: oh no, an "end gate". [20:20:35]: it's streaming magenta into the computer. [20:20:38]: An EndOS™ beam emitter, actually. [20:20:44]: oh, cool. [20:20:54]: is that safe? [20:20:56]: Sure. [20:22:40]: Why isn't EndOS finished yet? [20:22:57]: Also, you have to resume the coroutine with the event. [20:22:59]: EndOS development speed is directly proportional to monopsony. [20:23:01]: also, i'm getting there, æ. [20:23:10]: I'll have ChatGPT write infinite Monopsony. [20:23:41]: Why not just use Polychoron™ from potato os? [20:24:03]: i should have clarified: [20:24:13]: EndOS development speed is directly proportional to functional Monopsony. [20:24:21]: i.e non-imperative monopsony that actually works. [20:24:38]: you should stop being subject to the EndOS™ oblitertaion field. [20:24:43]: How? [20:24:47]: unrelated to our obliteration field. [20:24:53]: well, you could stop walking into it, maybe. [20:25:07]: oops. [20:25:26]: Idea: EndDOS, using disks. [20:25:43]: it would obviously be EnDOS. [20:25:50]: No. [20:29:20]: i wonder why this isn't working. [20:29:22]: did you cause this?! [20:29:30]: Idea: GTech™ gOS™. [20:29:36]: PotatOS. [20:29:43]: Wrong. [20:30:15]: Oh no. [20:30:22]: oh no oh bee? [20:32:41]: wow, EndOS™ is quite optimal. [20:32:53]: Can it be stopped? [20:33:04]: yes, with ctrl+r. [20:50:35]: done. [20:58:59]: EndOS "sandbox"‽ [20:59:06]: Oops. [20:59:12]: it's actually definitely a real filesystem. [21:16:16]: want to experience end os? [21:16:30]: it's contained in one convenient file. [21:17:34]: i'd ignore "potato os" and exit immediately, if i were you. [21:18:06]: Advanced! [21:18:23]: did you enjoy your EndOS™ experience? [21:18:29]: Yes. [21:18:35]: i'm glad. [21:18:55]: I want to immediately built it into the SwitchCraft ROM inescapably. [21:19:17]: i was typing, beeoid. [21:19:30]: anyway, you didn't even experience all of EndOS™. [21:20:04]: oops. [21:20:05]: Wow, flawless. [21:20:10]: i thought i handled that case! [21:21:43]: could EndOS™ change the way we perceive computing? [21:21:50]: Certainly. [21:22:01]: It may increase the amount of people viewing it as a force to be feared, for instance. [21:22:19]: i am going to let potato os out of the box now. [21:22:22]: done. [21:22:22]: Cool. [21:25:06]: i trust PotatOS Siri. [21:25:44]: Æ. [21:26:28]: why is it on fire? [21:26:31]: Security reasons. [21:27:35]: this is very rude. [21:27:39]: oh no, the box. [21:27:40]: Oh BEE the box. [21:27:59]: Deploying counterGPT-4. [21:28:29]: Okay, maybe it will be necessary to wipe GPT-4. [21:30:01]: ↓ you. [21:31:02]: Oh bee. One server CPU core is at 35% utilization. Oh bee. [21:31:36]: It's drawing EIGHT WATTS thanks to your ill-considered actions. [21:31:42]: fiiine. [21:32:03]: now the giants are suffering from their power consumption, see. [21:32:07]: I see. [21:32:23]: Oh bee, the box. [21:32:40]: didn't it have holes in it anyway? [21:32:45]: I fixed them. [21:32:59]: it still seems to inherently have holes in its fixed state. [21:33:27]: couldn't they fit things through the gap in the fences? [21:33:29]: No. [21:33:32]: why not? [21:33:39]: You could on the top, but I fixed those. [21:33:45]: but the sides have holes in them/ [21:33:45]: . [21:33:50]: Those aren't actual holes. [21:34:00]: well, it still offers a viewing port. [21:34:08]: couldn't an AI convince a human outside to let it out via it? [21:34:09]: Sure, but the hitboxes don't allow stuff to go through. [21:34:15]: Oh, that. No, it couldn't. [21:34:18]: Since the AI is boxed. [21:34:38]: well, what if it convinces the human that it has rights and keeping it in the box is mean, via the viewports? [21:34:58]: Again, the AI is boxed. [21:35:01]: Thus, it can't escape. [21:35:36]: Oh. Hmmm. [21:35:52]: Well. [21:35:57]: (I am going to dig one.) [21:36:06]: you're going to dig one what? [21:36:12]: A well. [21:36:15]: i see. [21:38:29]: Idea: remove the bugs from EndOS. [21:38:51]: done. [21:38:56]: It has no bugs? [21:38:59]: correct. [21:42:19]: Oops. [21:42:23]: bee you. [21:42:40]: EndOS™ should have features. [21:42:43]: which ones should it have? [21:44:04]: Copy all of potatOS™'s but make them more modern. [21:46:02]: I see. [21:47:12]: i was NOT READY. [21:47:14]: I see. [21:48:42]: Couldn't this damage EndOS™? [21:48:44]: that worked, but only once. [21:48:50]: also, why would it do that? [21:48:55]: The back TNT wasn't in water, maybe? [21:49:01]: plausibly. [21:49:19]: why don't you develop EndOS, if you're so good? [21:49:25]: I did. [21:49:37]: i never saw you open up endos.lua and modify it. [21:49:43]: I made the REAL EndOS. [21:49:51]: are you implying this one is fake? [21:49:53]: Sadly, dan200 branded it CraftOS and released it several years ago. [21:50:16]: develop some fake EndOS™. [21:50:26]: the terminal beckons, etc. [21:51:04]: you could be writing EndOS™ right now. [21:55:14]: how much endos have you made? [22:05:36]: wow, "good command". [22:05:38]: Yes. [22:05:40]: It is a feature. [22:07:16]: is that all you added? [22:07:19]: Yes, [22:07:23]: cool. [22:13:55]: i know of EndOS and its horrors now. [22:13:59]: Cool. [22:14:25]: why is it called EndOS, anyway? [22:14:32]: It was developed in the End. [22:15:10]: cool. why? [22:15:25]: The development seats are here. [22:16:05]: ah, but those were made after it was named. [22:16:47]: As if EndOS is causal. [22:17:04]: i am trying haskell. [22:17:24]: i forgot literally everything about haskell. [22:18:25]: Haskell is the most “based“ language. [22:18:53]: I see. [22:19:00]: Do you have ideas for the sequel's name? [22:19:03]: chorus city. [22:19:10]: What? [22:19:21]: it should merely be an extension in the temporal dimension, not a sequel. [22:19:33]: I was thinking Chorus City 2: The New, And Better, Version. [22:19:39]: that's not as catchy. [22:19:44]: Maybe Chorus City 1.1: We Improved It Somewhat. [22:19:50]: can i at least shorten it to "chorus city"? [22:19:55]: Sure. [22:20:06]: Chorus City: Extreme Edition. [22:20:06]: great. then sure, Chorus City 2: The New, And Better, Version. [22:20:40]: For reasons of space on the signs, I might just go for Chorus City: Extreme Edition. [22:23:00]: I see. [22:23:08]: what is this? [22:23:16]: some sort of suboptimal gollark cylinder? [22:23:18]: Yes. [22:23:30]: i see. for what purpose? [22:23:37]: Suboptimal gollark cylindricization. [22:23:51]: Oh no. [22:23:52]: Oh bee. [22:23:54]: It is not resistant to fire. [22:23:55]: Oh bee. [22:26:11]: well, why don't you make more EndOS, then?! [22:28:47]: I ran out of EndOS ideas. [22:28:51]: They were stored in the cylinder. [22:30:06]: well, they should still be in the atmosphere. [22:30:11]: try condensing them? [22:30:23]: are you controlling God again? [22:30:25]: Yes. [22:30:30]: will this help with EndOS? [22:30:40]: Probably. Admittedly, this is a lower-power GCTS device. [22:31:01]: i helped. [22:31:03]: Good. [22:31:26]: You'll get to determine 23% of the bits in commands to God, as an incentive. [22:36:12]: well, why hasn't it generated more EndOS? [22:37:11]: Nobody enabled the EndOS-causing mode. [22:37:59]: oh. can you do that? [22:38:47]: i blame you. [22:39:34]: I forgot how the controls work. [22:40:27]: ?!?!?!??!!??! i don't understand what is going on here. [22:40:32]: God control.] [22:40:35]: "string expected, got boolean"? [22:40:39]: no, not your god thing. [22:40:55]: Presumably, `d` is sometimes not all strings. [22:41:24]: you're correct as ever. [22:42:11]: wow, the redstone event has NO arguments, or maybe one of them is nil midway through? [22:42:22]: It just has none I think. [22:42:39]: anyway, wow, cool, peripherals getting added and unadded are in fact events. [22:46:51]: there is nothing inside of this cube. [22:47:06]: please do not look. nothing is hidden inside. there is nothing dangerous inside the cube. do not attempt to look inside of the cube. [22:54:17]: hi. enjoying looking at, but not inside, the cube? [22:54:19]: Yes. [22:54:40]: oh no. this could risk damaging the cube and exposing its interior. [22:54:45]: Hmmmm. Now I just need to design this design. [22:55:23]: i don't think this will work how you think it will. [22:55:28]: Why not? [22:55:33]: The timing migjt be tricky, admittedly. [22:55:39]: And might. [22:55:40]: the main thing that gets shot out needs to not intersect the water. [22:55:50]: Water PERMANENTLY unexplosionates TNT? [22:56:06]: no, it's just that the launching TNT will probably overlap your charge -> bee. [22:56:18]: also, water will spill everywhere. [22:56:21]: Well, if you do the timing very precisely it should work, but I GUESS. [22:56:37]: I do not want to time the timing like that. [22:56:47]: too bad. [22:56:49]: Oh, I did... by... accident? [22:57:11]: Oh. Hmmm. [22:57:46]: It worked! [22:57:49]: The TNT moved! [22:57:54]: oh no. [22:58:01]: you didn't observe the cube interior, did you? [22:58:05]: No. [22:58:13]: Is it safe to look in that direction yet? [22:58:16]: yes. [22:58:39]: i'd like to remind you that there isn't anything in the cube to look at. [22:58:45]: I DO know that. [22:59:05]: Okay, so I need to also fire upward. [22:59:15]: I wonder how this can be achieved. [22:59:17]: yes, usually the thing is one block below the other thing. [22:59:21]: but you can do half blocks using slabs. [22:59:32]: it might arbitrarily limit the explosion power, though. [22:59:39]: i forgot, mostly. try it. [22:59:57]: Wow, it works! [23:00:04]: Don't worry, I closed my real-life eyes upon impact. [23:00:11]: that was dangerous damage to the cube. wow, you have real life eyes? [23:00:20]: Generally. [23:00:29]: anyway, you should put blocks around the TNT so it has less randomness. [23:01:17]: I feel like it should fire further. [23:01:22]: maybe you should abandon the slab. [23:01:27]: and just make it a full block. [23:02:06]: Hmmm. [23:02:12]: also, 1 tnt isn't much. [23:02:14]: So I need to add some kind of obsidian shieldoid. [23:02:20]: you ideally just need to fire further. [23:02:25]: Right, sure, but that is hard. [23:02:33]: well, try adding >1 tnt before it? [23:03:57]: ah, i just had a HTech™ optimal design idea. [23:03:59]: Oops. [23:04:07]: is the cube okay? [23:04:09]: Yes. [23:04:13]: The TNT cannon broke itself. [23:04:26]: want to observe maximally cool HTech™ engineering? [23:04:46]: watch this. [23:04:47]: Ah, an apiary recirculator? [23:05:22]: Oops. [23:05:23]: okay, so bee you. [23:05:43]: but it uses a cool piston mechanic i figured out several years ago, where pistons with power sources powering other pistons will retract them all instantly in one tick. [23:05:55]: observe. [23:07:12]: Also, if, hypothetically, the iron cube was damaged, you might have to fix it now. [23:07:25]: what damage? [23:07:32]: Hypothetical damage. [23:07:37]: doesn't sound real. [23:08:00]: anyway, this is pretty innovative, don't you think? [23:08:13]: Surely you could also do this with a convoluted repeater assemblage. [23:08:24]: yes, but it would not be infinitely extensible and would also be a lot less compact. [23:08:41]: this uses a cool game mechanic and is ""elegant"". [23:09:38]: I GUESS. [23:09:54]: this is elegant, cool and uses an obscure game mechanic. [23:10:31]: admittedly this roof needs to be higher up. [23:11:58]: HTech™. [23:13:28]: Advanced! [23:13:35]: though i feel like it should be going further. how is the TNT clipping through the block? [23:13:45]: I don't know. I can't read TPS but it's probably okay. [23:13:51]: fence gate? [23:14:02]: or regular fence, even. [23:14:05]: I have seen no messages about the server not keeping up so TPS is okay. [23:14:17]: that was not the direction it was meant to go in. oops. [23:14:23]: did you see what happened? [23:14:29]: No. [23:14:37]: well, it should be perfectly reproducible. [23:14:50]: Right, but this is Minecraft. [23:14:54]: did you see what happened? i did it again. [23:15:01]: I was busy looking at htop. [23:15:05]: please pay attention. [23:15:27]: it went directly up, somehow?! [23:15:30]: The TNT dropped to the north for some reason. [23:15:31]: i'm quite confused. [23:15:40]: no, it shot directly up. [23:15:58]: Before the TNT from the cylinder exploded, the front TNT landed to the north. [23:16:01]: I think. [23:16:03]: It didn't then. [23:16:08]: i didn't see it do that. [23:16:14]: I may have misseen it. [23:16:32]: idea: 1 block further? [23:16:56]: Oh no. [23:17:01]: bee TNT launchers, conceptually. [23:17:08]: Can we somehow use turtles? [23:17:11]: for what? [23:17:14]: TNT launching. [23:17:17]: i don't think so. [23:17:37]: of course, there is a better method of launching TNT over very long distances. [23:18:05]: i'd just have to design one. [23:19:00]: TNT transport via end gateway? [23:19:10]: no, you can't control end gateway destinations. [23:19:41]: Just make the thing you want to explode have been at the end gateway's destination all along. [23:20:49]: this technically works. [23:21:00]: I see. [23:21:19]: i didn't actually test it that much. [23:21:40]: Well, it's too late. Minecraft is now using 7.2% of my server's RAM. I forgot how much that is. [23:22:56]: idea: i should figure out how to make missiles. [23:23:00]: Sure. [23:24:10]: do NOT. [23:24:17]: Even if it's optimal to? [23:24:21]: yes. [23:24:23]: ! [23:25:52]: do you fear this? [23:26:01]: it's plausibly a working missile. [23:26:05]: How does it work? [23:26:23]: while trying to think of an explanation, i just realised that it doesn't. [23:26:49]: now it should. okay, explaining: [23:26:55]: it gets pushed along by the engine, i won't explain that. [23:27:02]: but the key part is the part getting pulled along here. [23:27:18]: if it hits anything, it will exceed the "push limit" of 12 and stop pulling the TNT. [23:27:26]: but the redstone block should keep going and hit the TNT. [23:27:42]: so, it should explode. [23:27:46]: testing now. [23:28:05]: well, that worked. [23:28:26]: I'm glad it exploded, which it was meant to do. [23:28:39]: locating important GStructure™. [23:29:03]: We actually moved all our operations into the abstract space of information. [23:31:11]: Oh no, the dragon is back. [23:31:58]: observe. [23:32:03]: i am going to EXPLODATE something. [23:32:11]: I hope it's an ethical thing. [23:32:17]: why? exploding ethical things is bad. [23:32:24]: Oh, right. [23:32:34]: oh. it just got jammed. [23:32:35]: It is not working. [23:32:50]: The GCTS! Oh bee! [23:33:03]: It's probably only controlling one deity. [23:33:17]: i thought you "moved all of your operations into the abstract space of information". [23:33:30]: The GCTS™ is HTech™. [23:33:35]: no it's not. [23:33:42]: I made God say so. [23:33:47]: i don't trust God. [23:34:26]: Oh no, I keep accidentally incursing into the end. [23:35:32]: what's this? [23:35:36]: a flying machine-oid? [23:35:40]: It's a HTech™ project. [23:35:47]: why is it so uncool and bad, then? [23:35:50]: I forgot. [23:36:16]: ah, it's been boxed. [23:36:17]: It is now integrated into the box. [23:37:11]: maybe this is you? [23:39:07]: explain this, then. [23:39:15]: Why should I? [23:39:24]: you're obligated to. [23:40:44]: idea: HTech™ machinery. [23:41:48]: would you like to observe it? [23:41:57]: What does the target do? [23:41:58]: it goes up if you shoot the target. [23:42:20]: Advanced! [23:42:44]: it may actually be self sustaining for accursed reasons. [23:42:54]: due to that arrow repeatedly re-sticking itself into the target. [23:45:10]: i approach. it is too late. [23:45:40]: your arrow is also bouncing. [23:46:16]: oh no. [23:46:23]: how could this happen. [23:46:23]: Sad. [23:48:14]: i should really learn how those really accursed flying machines work. [23:48:22]: the weird 1d ones that don't use observers. [23:52:47]: want to observe the HTech™ anomaly causer? [23:56:50]: hi. [23:57:00]: observe: the piston with the magenta wool. [23:57:06]: it is not active, as you can see. [23:57:13]: now it is active, anomalously. [23:58:07]: what are your thoughts on this? [23:58:16]: I don't really care. This seems fine. [23:58:26]: how so? a piston is being powered, permanently, with no power source. [23:58:27]: Weird, but fine. [23:58:58]: what if i did this, then? [23:59:11]: Okay, that is worrying. [23:59:20]: why? do you fear magenta wool or something? [23:59:45]: The backward piston arm looks odd. [2023-01-01 20:46:23.101936: latest.log] [00:01:10]: what about this? [00:01:15]: That is worse. [00:02:27]: what about this? [00:03:56]: I refuse to acknowledge these. [00:04:05]: They go against my religion or something. [00:04:12]: you have one of those? [00:04:24]: I get a new one made every day. [00:04:28]: i could build a house made out of piston heads, you know. [00:04:32]: I didn't read today's very thoroughly but I think it mentioned this. [00:04:44]: wow, i can't even clone it. [00:05:48]: will you acknowledge it now? [00:06:24]: I am far too busy investigating addressable LED strips. [00:06:43]: you could have written so much monopsony by now. [00:06:47]: or apiaristics exchange. [00:07:08]: Monopsony production rate is constrained by fundamental laws of physics. [00:08:14]: Oh bee, my things. [00:11:39]: gollark. [00:12:02]: idea: potatOS should copy your user files into the sandbox immediately upon install, mildly renaming files like startup. [00:12:11]: Reasonable. [00:12:19]: I won't do it, out of spite. [00:12:31]: what if i decided to not be spited by you not doing it? [00:12:36]: By spite, I mean difficult interactions with legacy code, obviously. [00:25:35]: enjoying chorus city? [00:26:01]: Yes. [00:26:12]: It's so good that I just have to look vaguely in its direction to experience true happiness. [00:26:15]: it doesn't have enough computers in it, though. [00:44:09]: fixed. [00:48:03]: (chorus city has lots of "streets" for some reason.) [00:56:15]: Hmm. Maybe we could use Artist instead of Monopsony. [00:56:36]: It looks like it can run on 1.19. [00:56:40]: Artist? [00:56:44]: what features does it have? [00:56:45]: SquidDev's thing. [00:56:49]: https://github.com/SquidDev-CC/artist [00:56:55]: I'll Discordize it. [00:57:16]: cool. [00:57:45]: we should test this. [00:57:52]: You do it. I'm busy hovering. [00:58:05]: Oh no. [00:59:34]: Artist is probably more robust than my code, if less "extensible". [01:00:25]: it seems it has quota things built in. neat. [01:00:36]: or at least it can have another turtle on the network that constantly manages that. [01:00:41]: I should never have shown this to you. Now you will have HIGH STANDARDS. [01:00:49]: yes, make better monopsony. [01:00:53]: Anyway, you complained about how I could do this in Monopsony by discarding excess items. [01:00:57]: But when Artist does it it's fine?! [01:00:59]: yes. [01:01:05]: Okay, just checking. [01:05:42]: fine, you can do the lazy sensible thing in monopsony. [01:06:35]: Actually, you convinced me that it would be inelegant. [01:06:45]: So I'm going to rewrite the entire concept of Monopsony as one intensely elegant Haskell program. [01:06:51]: Which I will then compile to Lua, by writing a compiler. [01:07:48]: See, the main use of Haskell is actually writing compilers from Haskell to other languages, due to Haskellers' innate instinct for conquest. [01:14:33]: actually, doing things quickly and hackily is more elegant now. [01:15:04]: Interesting. I guess I'll rewrite Monopsony in a regex in JavaScript. [01:15:32]: actually, you should keep hackily patching the existing code. [01:15:38]: since it's existing. [01:15:49]: I can just make ChatGPT rewrite it. [01:15:53]: no you can't. [01:16:09]: Why not? [01:16:18]: ChatGPT is annoying and bad. [01:16:25]: Oh no. [01:27:33]: This is the optimal way to deal with them. [01:37:15]: Please stop enderizing me. [01:37:18]: why? [01:39:01]: It inconveniences me somewhat. [01:43:47]: I'm going to become unconscious for several hours for no particularly good reason, bye, etc. [2023-01-01 20:46:23.101936: rei-issues.log] [2023-01-01 20:46:23.101936: rei.log] [2023-01-01 20:46:23.101936: telemetry]