Internal logic of ICs is not analog, so comparators are not a thing. Also, you can use the redstone torch in the debug menu as constant out. Is this specific for a version of the mod? Because I only have button and switch in there.

I've been working on a frame quarry, and as such the main platform is rather large (13x13) to fit the inchworm drives. However, whenever the main platform moves, my client locks up indefinitely. I even left it on overnight to see if it would ever unlock - no dice. Nothing ever pops up in the log, so it's really hard to try and debug, but I'm pretty sure it's just the frames trying to render too much at once and my poor CPU having a mental breakdown. The rendering might just have to be optimized, or it could be a deeper bug.

This bug does NOT freeze the server, by the way, just the client. I have my pack running on a dedicated server, on the same machine, and it handles moving the frames just fine, and people can still play while my client is frozen, it's just the rendering that's causing an issue.

Screenshots of the frame quarry: https://imgur.com/a/IBIANHG OS: Linux (Kubuntu 20.04) CPU: Ryzen 5 PRO 1500 Quad-Core RAM: 16GB (6 Allocated to MC) GPU: Radeon R7 240 Launcher: MultiMC version 0.6.11-1344 Mods list: https://gist.github.com/kd8lvt/c14e17eaa219f6901652258db5c17a1c

Forgot to mention

Did you ever come to a resolution on how to fix this issue?

YABBA barrels will only request a single stack of items at a time even if they have a large amount more free storage.

Steps to reproduce the behavior:

1. Create a storage network with a number of chests that have item responder chips set to an empty blacklist with priority 0, a YABBA barrel with an item responder chip set to receive a specific item with priority 5, and a single chest with an item extractor chip set to an empty blacklist.
2. Insert more than a stack of the item that the barrel is set to receive into the extractor chest
3. Many of the items will be routed to the chests in favour of the barrel even if the barrel has enough space for them all

I would expect in this scenario for the items to fill the barrel before being put into the chests

• CCL Version: CodeChickenLib-1.12.2-3.2.3.358-universal
• FMP Version: ForgeMultipart-1.12.2-2.6.1.81-universal
• MrTJPCore Version: MrTJPCore-1.12.2-2.1.4.43-universal
• ProjectRed Version: ProjectRed-1.12.2-4.9.4.120

YABBA barrels will only request a single stack of items at a time even if they have a large amount more free storage.

Steps to reproduce the behavior:

1. Create a storage network with a number of chests that have item responder chips set to an empty blacklist with priority 0, a YABBA barrel with an item responder chip set to receive a specific item with priority 5, and a single chest with an item extractor chip set to an empty blacklist.
2. Insert more than a stack of the item that the barrel is set to receive into the extractor chest
3. Many of the items will be routed to the chests in favour of the barrel even if the barrel has enough space for them all

I would expect in this scenario for the items to fill the barrel before being put into the chests

• CCL Version: CodeChickenLib-1.12.2-3.2.3.358-universal
• FMP Version: ForgeMultipart-1.12.2-2.6.1.81-universal
• MrTJPCore Version: MrTJPCore-1.12.2-2.1.4.43-universal
• ProjectRed Version: ProjectRed-1.12.2-4.9.4.120

Can you update the gradle version (gradle 2.x don't support java 1.8, and isn't supported by newer versions of IntelliJ) ? You should also update the project generator, because it is no longer compatible (I only tested with IntelliJ, it still works but with a lot of manual configuration). There is also a problem with JEI, two versions are downloaded, and the version that is in build.properties (4.15.0.+) needs a higher version of forge (which uses Userdev3)

I know this mod is no longer maintained, but I would like to add my own features, and I can't get the project to work.

Project Red is not abandoned. It is being actively ported to 1.15 by myself. 1.12 is not supported anymore. Gradle 2 absolutely supports Java 8, However, due to the newer version of Java used by later versions of Intellij, the project cannot be imported anymore.

I'm also wondering if you've abandoned this mod, or if you just don't have the time to develop it ? Also if you don't want to change the project for the moment, I'd like to know which version of IntelliJ it should be open with, and the right version of java (java 1.7 ?).

Can you update the gradle version (gradle 2.x don't support java 1.8, and isn't supported by newer versions of IntelliJ) ? You should also update the project generator, because it is no longer compatible (I only tested with IntelliJ, it still works but with a lot of manual configuration). There is also a problem with JEI, two versions are downloaded, and the version that is in build.properties needs a higher version of forge (which uses Userdev3)

I know this mod is no longer maintained, but I would like to add my own features, and I can't get the project to work.

this happened to me once, i was breaking routed interface pipes (with an item responder chip inside), other pipes broke fine but then 1 random pipe, as soon as i broke it the server crashed. game version is 1.6.4. i haven't seen the code behind the pipes but i assume the crash is something to do with the multipart tiles, maybe when it's revaluating the 'parts'. i also thought it might be because the pipes were in different chunks, but mine were in the same chunk so thats not the issue.

I haven't actually measured it, but a one-tick repeater in traditional redstone is definitely slower than this. Vanilla redstone ticks are actually 2 game ticks (1 game tick = 1/20th of a second, 1 redstone tick = 1/10th of a second), and I suspect the D latches are expecting the latter. It'd be nice if the pulse either output a 2 redstone tick pulse, or better yet, was configurable.

But I also feel like the intermittent behavior of the D latches is probably unintentional, and potentially an indication of a larger bug in its code. I searched through this codebase, but I'm unfamiliar with Scala so I couldn't find any of the logic for the pulse gate. If anyone's more familiar with this codebase, knowing where that code is would be a good place to start. For now, I've just added 2-tick repeaters in series after all my pulse generators and it seems to have fixed it.

+1 This keeps happening to me, too.