Loader

Ooh! Down cobblestone tracks so it sears them back to stone as it goes too!

All TE stuff is limited by connection now, Kalbintion - you can get 6k in and 6k out of a redstone cell by having 3 connections to input and output faces on a single cell. (The easiest way to see this is to set up a few cells in creative all filled to max, have one feed another empty one by one conduit and a second one feeding by say, 5 all joining into 1, then splitting back to 5 to connect at the other end) Daniel, you're miles off hitting any limits with that setup. If you're ever in doubt, check the dynamos themselves - if they start storing power internally then that means they can't get rid of it fast enough (passing it out to an energy cell or whatever) which might mean your energy cells are all full (which is fine, other than the steam dynamo nothing is wasted). You're only hitting limits when the energy cells are emptying and the dynamos still aren't - that would mean they're generating power faster than the energy cells can take it (so there's a bottleneck somewhere in the system).

Yep, a system with a portable tank, fluiduct, some lava source blocks and some pistons could do that. Step in, trigger the pressure plate/tripwire RS-Latch turns on fluiduct, lava pours out of tank into channels RS-Latch turns off inverted piston circuit, releasing lava-falls down the sides (or something equally exciting, perhaps it flows out underneath the channels?)

Fans have quite a large area, and when you place them they face towards you so they can point out in a semicircle if you desire. If it was me, I'd either; Remove some of the fans that are hard to reach and turn the others slightly to push anything that's out of the range of the other fans Just place the fans directly on redstone blocks

They're pretty laggy, but from a decoration perspective sure! I'd still probably fill a portable tank with a cool-looking molten metal then pump it into the channel to do that, though.

PRC Basics The PRC is essentially the kind of computer you could get in the 70's, even down to a punch-card equivalent (PRC Memory card). Machines like this are still used in real life, called PLCs (Programmable Logic Controllers rather than Programmable Redstone Controllers) and you'll find them in all kinds of places where you need very reliable, slightly smart machines - car sensors, factory controllers, all over the place. If you do eventually learn how to use every function one of these in game, you're well on your way to being an electronic engineer. (That's someone who works with designing and building electronics rather than someone who is made from electronics, despite how it sounds) Let's take a look at the interface; "I... nope." ٩(͡๏̯͡๏)۶ Not so fast, my unicode friend! Like anything with a lot of options it seems daunting at first, but let's go a bit at a time. We don't need all of that in there for the purposes of this, we'll just focus on the basics for now. Before we start, a bit of advice: Keep your input and output wires separate until you understand what you're doing. It's entirely possible to have all of your functions together on a single line, but it's also a lot easier to make mistakes and have things activate when you weren't expecting it. Separating the I/O avoids that problem and also allows you more total circuits (because you have all the colours available for both input and output lines, rather than all the colours shared between both input and output). The Passthrough function Essentially like a wire, a signal comes in on one side at a given channel and the PRC passes it back out where you tell it to on what side and channel you desire. Commonly used for simple switching, it's not much of an improvement on the basic wire except for one thing - you can use multiple output channels on multiple circuits, so you could have an orange input going to an orange output and a blue output, so it can be used to group things together or provide a single lever to override all other levers (like an emergency shutdown). Let's try and use it as a lightswitch again, though this time let's do it from a daylight sensor so it's automatic. Here's the setup; (Using F7 to indicate spots where mobs can spawn - red means spawning day or night, and yellow like this picture means spawning only at night) And here's what we've set in the PRC. Note that we've got Orange coming in from the light sensor to the PRC and white going out to the lamps - as long as that matches what the little colour indicators say then that's fine, they don't need to be the same colour. Note also the RedNet Historian, we'll get to that in a minute. Don't be alarmed, I/O U and I/O D are merely ways of saying "Input and Output, Up" and "Input and Output, Down". In this case, we're taking the orange colour from the top of the PRC (I/O U) and using Passthrough to transmit it out the bottom of the PRC (I/O D). The other options are used for more complicated applications, and you don't need to worry about them until you get a bit more confident with your abilities. "Loader, you marbleheaded blockbrain! It doesn't work! The light sensor turns all the lights on during the day, and switches them off at night! This is the opposite of what I wanted!" Ok, Ok, nightlight boy, calm down. This is where you get to see one of my favorite things about RedNet - the ability to tweak a system that doesn't work quite right without moving anything around. Wait, did you say what we wanted was the opposite of passing through the signal? An inverted version of the signal if you will? That brings us to the next simple function. The Inverter Function Let's begin by going back to the PRC and changing the function from Passthrough in the list to Inverter; This should mean that if we've got no signal coming in from the daylight sensor (because it's not detecting daylight) then it will make a signal to send out. If it's getting a signal from the daylight sensor however, it will get rid of it and send none. In short, the inverter will reverse whatever you send it (off becomes on, low becomes high and vice versa). Let's have a look at our toy house now; Wonderful. Let's see it again in the daytime; The lights are off, and the yellow indicators are back to warn us that monsters can spawn there at night-time with this light level. Because the lights will turn on at night-time (and perhaps even in a rainstorm!), we don't actually have any problem there. RedNet Historian Notice anything about the RedNet Historian in the above pictures? Go back now and take a quick look if you didn't. "Is the line moving from the top to the bottom?" That's right! But you get no points for that as you're a voice in my head and have access to the things I know. Shame on you for cheating. When the power is on to the lamps (the white channel), the line moved to the top, and when it was off, the line moved to the bottom. Being able to see what's going on in a channel is a really useful thing when you're trying to find and fix problems in your RedNet circuit. The RedNet meter is cheaper and gives a lot more information (the historian can only read from channel 1, the white channel), but it's hard to argue that the historian doesn't look a lot cooler. There's one more thing that a lot of users like to use that's not very complicated, the T-FlipFlop function. The T-FlipFlop Function "That sounds horrifying, I'm not a technical person! I'm not sure I can understand this!" Fear not, my easily deterred playmate, for you've actually been using an item that performs the task you'll be using this function for regularly in vanilla minecraft - the Lever. The T-FlipFlop can be used in the same way - press it once to turn it on, press it again to turn it off. The thing people like to use this for is mostly making buttons act like levers so their base looks cooler (I like levers plenty, but each to their own, I guess). Because this is a guide for absolute beginners like you, I'll go through how in detail, but try to minimize the explanations why (there's plenty of information on that on wikipedia if you're so inclined, you don't need me for that). "We should steal Melfice's force-field looking armour stand room design! Make it work using that! That'll be awesome!" You sir are a rogue and a cad, but fortunately for us I have asked Melfice about this subject already and he has no objection to me shamelessly ripping off his design to use in this example. Let's begin with the layout from the bottom. As you can see we have the PRC just underneath, with Input and Output split as is good practice for now (Input on top, output from the right hand side). We can see it connecting to a bunch of things down there, let's have a closer look. Ah, the plus shaped connection indicates the 'strong connection' type, which we learned earlier was good for transferring a signal into things (output, as it comes out of the cable from the PRC rather than going into the PRC). It did it on its own, but it's good to note so that if we're ever troubleshooting we can look for bits that aren't connecting as they should. Remember that the block we connect to acts like a redstone block when we give it signal, so we only need to connect the middle one to have an effect on all three. Some blocks won't behave this way (the Glowstone Illuminator for example does not, making it a great choice for a lighting up indicator panel) but this is true for the vast majority of things. Now we've looked at the output, let's go back to the PRC and look at the input. We're using cobblestone blocks to achieve a certain style inside the room upstairs, so we had to manually set the modes on these connections to 'forced connection', transferring a signal into the wires from the cobblestone as the buttons on it are pressed (input, as the signal is coming from elsewhere and going to the PRC). We've set all the colours for input and output cable on the colour rings, so now all is left is to set the PRC to T-FlipFlop on inputs of those colours (its top) to outputs of those colours (its right side). I'm using the same colour for input and output which makes it easier to keep track of, and using the different side to determine if it's input or output - another advantage of splitting I/O to different sides. Let's take a look at that PRC interface. "Loader... there's some wierd stuff there, T's and Q's and things.." Don't concern yourself with that unless you must, padawan, as copying my settings will suffice. If you wish to understand it's actually fairly simple. Q is the output - it's what we want to set. Q# is what the output will be, next time it changes. Q# it set by T when a signal comes in from T. Q# will wait for the CLK signal which lets it know to act now and update, causing Q# to copy itself into Q, then reset itself. To do what we want, we want to both set the change (a pulse to T) and immediately do the update (a pulse to CLK at the same time), so we're using the same colour for both. We don't care what comes next, so we're ignoring Q#, but we want to get the final output so we're using Q for that, see? Simple. Let's have a look at upstairs; A different angle So there you go. The buttons give a signal to the cobblestone block, which is checked by the forced-connections underneath. Those cables feed into the top of the PRC (input side), which do their calculation in the T-FlipFlop function, then output on that same colour on the right hand side of the PRC (output side). The drawbridges receive a signal on their middle block which they pass to the two blocks next to them, causing the wall to rise or lower in a group of three. Let's try it! "Wall goes up, Wall goes down." Finally, you're understanding! I could do this all day.

Absolute Basics "Loader/Agonarch depending on whether I met you on forums or in Minecraft, I noticed you use lots of RedNet instead of most other redstone setups! I never use RedNet, it seems complicated and scary!" Well amalgamation of many peoples voices, it's not as hard as it seems. I'll go through some of the simpler things you can use it for in this thread and you can see how it can replace many things you used to do in more complicated or physically larger ways, often with less server strain! "That's fantastic! This ought to tide me over until I can get Redpower 2 working again!" ...moving on, let me explain what RedNet does. First, let's look a the cable: it's essentially a bundled cable from RedPower or Project|Red, but it's quite a bit cheaper and you get all the connection colours available without a massive pile of wool at the ready. Let's go over the simplest example - a cable connecting a lever to some lights. Here it is with the lever off; And again with the lever on. Note that the signal from the lever passes to both lights as we expected. Wonderful! "But Loader, that seems like ordinary redstone behaviour! I don't see how this saves me any space at all!" Worry not my imaginary compatriot, for if you look closely you'll see that all of those connections are white. The colour of those rings on the cable determines what power goes where. Let's add another lever and change a couple of the colours to something else. To change the colour, simply right click on the little ring by the connection point (the bit that's now orange in these pictures) with a crescent hammer. Note the original white lever is still on, and the lamp I left on the white channel is still on. The new lever I set to the orange channel, and I switched one of the lamps over to the orange channel too - note how the orange channel lamp remains off - that's because the orange lever is also off. Make sense? If I were to switch off the white lever, the white lamp would go off, and if I were to switch on the orange lever, the orange light would go on. Just like a bundled cable, only smaller and simpler (not to mention easier to switch if you need to change colours around the place). That's the absolute basics - next I'll go over how to hide the cable, then a very common application for a PRC, then a slightly more advanced application for a PRC. Hiding Cables/Unusual Connections through blocks "I can't put these cables through microblocks! What is this?! I can't hide them behind walls! They don't even connect!" Ah, you mean when you try to do something like this, they don't stick to the wall? That's the second beauty of these cables - you can choose exactly what, where and how they connect to things they're next to, even if it's not something that'd ordinarily take a redstone signal - like that cobblestone wall right there in this picture? "Yes, that's my problem! I can put the levers directly on a wall, but what if I want to have the destination a little away from where I'm using it?" Go up close to where the wire connects to the wall, and you'll see a little outline of a smaller box come up. Use the crescent hammer to switch between modes. Cable connection mode is just that - it'll only connect to other RedNet Cables. Standard connection mode is its default behaviour, connect to cables and anything that seems technical (this often includes pipes and wires from other modpacks - if they don't accept a redstone signal usually then this will have no effect). Forced connection mode is for receiving signal from a block. With a lever on one side of a wall and a wire forced-connected to it on the other, the signal will pass through the wall. Strong connection mode is for transferring signal to a block. The block it's attached to will act like a redstone block when activated by this mode (any stuff touching it will get a signal). It works! Wait... "If I turn the lever on and off nothing happens now! What's going on? Did I do something wrong?" Good! I was hoping you'd spot that! This is a limitation of minecraft - you can't have cable on both sides of the wall like this, the block update doesn't trigger properly as the block in the middle (the wall) that's acting like a redstone block now didn't change as far as minecraft is concerned. This means blocks immediately next to it will still receive signal, but other objects like cables may not. It's an impossible thing to fix without a lot of extra (lag inducing) checks, so just trust me that it's better for everyone this way for now. All it means is that you must have either the lever on the wall with a cable going to the destination from the far side (forced connection) OR a cable going to a block, connecting with a strong connection and the destination block/machine right on the other side, not BOTH.

You were unusually unlucky, Swift, but you're right about disabling it in versions before 1.0.12a, I don't think BoP has changed at all in the last few versions at least (1.0.9 maybe? It did feel like it got a lot worse with the Necromancy updates in 1.0.11 and 11a to me but I can't say that with any degree of certainty).

The fluiducts work a lot better than the casting channels for that purpose, you can even set them up with a pneumatic servo and use them to filter specific metals to specific casting tables/basins (this is the easiest way to do automation of the smeltery). I'm not sure if the casting channels are still buggy, but even if they aren't they're a lot slower and less configurable than fluiducts.

There's a lot of sweeping statements there, so I need you to clarify a few things for me; This is simply a matter of the code - I might have missed it, but show me where BoP either ignores superflat or specifically only runs on Default and BiomesOP settings. You're calling out the coding ability of PowerCrystals (MFR), Emoniph (Witchery), mDiyo (Tinkers Construct), Sirolf/AtomicStryker (Necromancy) and JoseTheCrafter (Food Plus). I'm not in total disagreement about all of these, but any complaints I'd have about the coding in them I'd point to specific things rather than just calling them lazy in general. Obviously that's a hell of an accusation there, so I expect you to be able to at least read the code well enough to show me where BoP did it the 'right way'. You sure that's not the BoP overridden vanilla plains biome? Place some bonemeal and tell me if you get BoP flowers spawning. I'm pretty sure this isn't correct - last I looked the superflat routines ran after everything else (which leads to certain things being super-common, like MFR libraries when given multiple chances to spawn in a chunk and some things being rare, like TC blacksmiths, it just depends on how they're coded as to whether they get extra 'spawn in chunk' chances or extra 'already spawned in chunk' flags). I vaguely remember that there might be a second village generation pass for some superflat worlds.. if that's the case it could explain what we're all seeing here but that's got nothing to do with what you're saying. It's listed as "Can't Fix" because it's not something anyone here can fix. It might not be something anyone can fix individually, and it's certainly not something that's likely to be fixed. In order to fix it, BoP would have to have some kind of worldgen API that mods would use so that BoP could do village generation at its usual early point in worldgen - that would require a major rewrite of BoP (not likely) for minecraft 1.6.4 (super not likely) and all mod authors to be willing to make their mods require BoP (just no), have two versions of the mod or some kind of switching ability depending on what else is there - a bit of a rewrite to a major rewrite for those mods again on 1.6.4 (super not likely) assuming you could get all those mod authors to work together on it (no way in hell - this, perhaps unexpectedly, would be the hardest part of all). There are hundreds of examples of this problem happening (dozens just here), and even a medium sized server (40-80 players) would be lucky to last a week with all the biome village generation turned on like you're suggesting. It's great that you haven't been able to reproduce it, but people played for months on singleplayer before having any problem. You're just simply not generating enough terrain to expect to run into this problem any time soon. The vanilla biomes being set to village generation=false may be an oversight, or it may be intentional (they're still BoP versions after all), that I'm not sure about. What I am sure about is that you can't just use the config files as pure evidence, go see if B:Exo-Armor-Craftable=false is set in TinkersConstruct.txt and then see if you can actually craft it in game, for example. Does that clear anything up?

That's not right - this setting; B:"Add Biomes To Default World"=true Causes BoP generation to occur on all worlds, not just default and BiomesOP. It's a limitation in minecraft that means this even needs to be in at all (it's a workaround, without it you'd need to generate the world, delete the chunks and then allow it to generate with BoP loaded). It's not picky about whether it's BiomesOP (though with that option off, it will only be possible to use the settings in BiomesOP), default or superflat. I know that's not what it seems like it should be doing from the wording of it, but check the code and see for yourself. 2000x2000 also isn't nearly far enough to guarantee finding a village on a even normal BoP map, though a lot of people do get lucky and find one or two by then. http://biomesoplenty.wikia.com/wiki/FAQs (it's a known complaint, something they're working on and there's even people in the comments on that page complaining that they've found 1 or 2 villages only - remember that's even with all BoP biome village spawning on - it's less common than that here).

You can attach signs to other signs, Daniel, they just float in mid-air.

Mac's don't use the IBM standard keyboard layout, so their version of [ and ] don't do the same thing as yours. Not all the keys are mismatched however - use the morph config file as well as the numbers from this chart to find some that work for you. Let us know what you pick (lots of people have fixed it this way, but no-one's actually reported back with what keys they ended up using). I'd start with 51 and 52 (< and >).

Ironically, it's highly popular because it's highly customisable (Just not in the way we'd need for that)

You can get rid of those dusts by having normal glowstone in your inventory then picking up the metadata glowstone. It'll add itself to the normal glowstone stack and revert to normal glowstone. Beware that this works in reverse, too. If you've got just a couple of metadata glowstone and you pick up normal glowstone, the normal glowstone takes on the metadata and joins that stack. Drop the bad glowstone before picking up the good stuff to avoid this.

No, I was meaning through the addition of another mod like MineTweaker or Custom Recipes. I don't think Flans provides a way to disable those itself.

He's lucky he bolded the important bit, or I would've had no idea what he was trying to say without that added context.

Eloquently put sir. Download the mod from here (remember you need the 1.6.4 version, not the newest version) Put the mod into your B-Team mods folder. Run B-Team.

A lot of mods still misbehave in Java 8, as an FYI (it's probably not that either, but I can't give much more advice than that from this info).

Something with Tinkers construct and Iguana's tweaks (no vanilla weapons, all metal weapons/tools need to be cast), Tinker's mechworks and Tinker's Steelworks, Pam's Harvestcraft & Iguana's Hunger overhall, Myrathi's Obsidianplates would be quite 'realistic' as mods go, I'd look for some kind of hardcore pack with those - something with those will probably be on the right track.

Please post up on the tracker along with the IDConflict.txt file, links to the tracker and traker rules are in my sig.

There are multiple versions of chisels; Carpenters Chisel (for changing patterns on carpenters blocks items) Tinkers Construct Chisel (does a few conversions, notably stone to various stone/chiseled brick types) Chisel Chisel (This one has an inventory and should do iron) Or do you mean the Chisel version of the Chisel isn't working?

The parts pack is a basic requirement of Flans mod, you can't remove it and have any Flans mod vehicles. I suppose the recipes could be disabled - is that what you mean?

With which settings?

The one caveat is the "Open to LAN" option doesn't play quite like a server, so it's not the best choice if you want to take your singleplayer game to multiplayer (it'll work fine for the hosting player though, just like it does in regular singleplayer).