AcesOyster

Post a picture of the GUI when using the tool station, attempting to add redstone to a tool.

Well, an official update to PR has just been released, which I think fixes this (don't quote me). I imagine that update will work its way into the next AotBT release.

Honestly, I reckon that's the sort of thing best left to the clever designers. If you give people a block for every function, what's the point in playing the game? You could easily create a remote system using blocks like coloured wool as keys, and so change which TE3 pipe fed the player interface. Sure, it wouldn't allow the same control as a routed request pipe, but you'd feel like you'd achieved a lot more for doing it. I did a little mining support system in a video, and that took a little bit of design work. It'd have been far less satisfying if I had just crafted a single block and had done with it.

crafting pipes do not actually craft anything. Documentation on those is now available on the ProjectRed wiki. Cyclic assemblers are a simple automatic crafting system.

Likely problem is that your conduits are sharing space with some microblocks at some point, which can cause buggy behaviour. The same can happen with all TE3 pipes.

The word stable is used ambitiously these days anyway

It doesn't take a lot of playing to realise the 0 is only visible on items that are damageable. It is a bug, I posted it to the tracker a long time ago but no-one took any interest.

Out of interest, was the previous exclusion of mechworks due to conflicts, or a gameplay decision?

yeah, the pack specifically lacks a pump to encourage people to not be so boring

PR Dyed trees are buggy as anything at the moment. They way they decide if they have room to grow is really out of whack, so they don;t get along very well with MFR.

Coloured wool, if pulverised, has a chance of producing the relevant dye. A truly renewable solution to dye production.

Your best bet is a lava fabricator. However, if you plan to use it to run a generator, that won't help you.

Pretty sure there is. There are two compressors, one called an electric compressor, and another one I forget the name of. I have definitely crafted and used both.

Regardless, some system specs may be nice. It's not like this post gives anyone any unique insight against the range of identical threads out there. What are you running it on, and perhaps you can have a look at what it is that's maxing out on your system during the spikes?

Not that I in any way approve of this post, but if you want help, you should perhaps try posting in an easier to read font, not all bold, and cut the underlining rubbish. You're only going to irritate people as it is.

I did once, but I no longer have the world file. All I can say is that it's definitely possible.

Reading that changelog, he pretty much fixed everything I disliked in the mod. So excited for the next release build

Yeah, MFR machines don't have wrappable inventories, rather, they wrap the inventory adjacent to them. You need a chest next to them, then extract from that.

And if all of that's correct, sometimes you just need to relog

Derp on my part. Didn't actually read what the offending file was, but just assumed it was the mapwriter config file. Silly me

make note of the world seed, then you don;t run the risk of dodgy generation borders.

Alright then, this is beyond me - I am sure someone else has seen this exact problem before in the bug tracker, so I suggest you look there for similar crash reports.

%appdata%.technicmodpacksattack-of-the-bteamconfig to find configs and click the gear in the launcher underneath the attack of the b-team thumbnail to reset the pack.

First piece of advice - backup worlds frequently. Second piece - There are threads with semi-solutions to this all through the forum and bug tracker. They all have side effects however. I think the bug tracker had the best solution I've seen.

Yep that, very easy to fix probably. As said in the first line, there's an erroneous space somewhere in your config for Mapwriter. If this error message is correct, deleting the mapwriter config and resetting the pack should fix it.