Kalbintion

For those who are whitelisted and notice theyre unable to get on, the server is presently off due to a JVM crash (a bit more severe then a regular server crash) and it is being worked on at this time. Please be patient while this matter is resolved. If you already have Joas or my skype information, you can contact us there to keep updated on this issue (if for some reason you checked here and didnt message me or joa on skype to begin with lol)

Everyone has their own methods, but the way I do it is this;
Shut down the currently running server. Rename the current server folder (ABTeam becomes ABTeam2 - this is so I have an emergency backup I can restart at any given time if necessary) Install the new server in a new folder (now there's no folder called ABTeam, I tend to use that for the new one) copy the world (player info, world info) and the DIM folders (quantum info) from the old ABTeam2 folder into the new ABTeam folder. Run the server bat, watch the error messages for anything exciting.  If it didn't start then chase down why, otherwise continue. Log into the server, fly around and look for any obvious problems quickly.  If there aren't any then you're done - this is your old world on the new server environment. There are a bunch of extra things I do after this, but at that point you'll be good.  This stuff is all related to the customization I have (every sysop will have their own version of stuff they do here).
Shut down the currently running server. Check config files, apply changes to config files for bans, disabled items, different behaviour or extra functionality. Disable or remove mods. Run the server again just to make certain it's still OK to start up, then shut it down. Install MCPC+ (to allow me to use bukkit plugins easily) Copy in the plugins directory from the old ABTeam2 directory to the ABTeam directory (MCPC+ and the plugins should only do things the mods don't do so there shouldn't be any difficulty or changes here beyond the copy) Run the server again to make sure it starts up, log in and test a couple of protected regions to make sure they're operating correctly. Open the server back up to the world so the players can get back to destroying it. :|

I'm disappointed this video doesn't mention the command. The command itself is /cofh killall pixie
 
Also, just to save some time for people wondering what other potential biomes it can spawn in, heres a list below from ftbwiki. Keep in mind this list doesnt include all the biomes in aotb but it should give you a much better idea and better range of biomes to pick from
 
From http://ftbwiki.org/Biomes_O%27_Plenty#Gem_Locations
Emerald: Birch Forest, Boreal Forest, Cherry Blossom Grove, Coniferous Forest, Deciduous Forest, Extreme Hills, Forest, Grove, Highland, Jade Cliffs, Maple Woods, Moor, Mountain, Redwood Forest, Seasonal Forest, Seasonal Spruce Forest, Spruce Woods, Temperate Rainforest, Thinned Timber, Timber, Woodland Ruby: Badlands, Canyon, Canyon Ravine, Desert, Dunes, Lush Desert, Mesa, Outback, Savanna, Savanna Plateau, Scrubland, Steppe Peridot: Chaparral, Field, Forested Field, Garden, Grassland, Heathland, Meadow, Meadow Forest, Orchard, Pasture, Pasture Meadow, Plains, Prairie, Shrubland, Thick Shrubland, Thinned Pasture Topaz: Bamboo Forest, Jungle, Oasis, Rainforest, Tropical Rainforest, Tropics Tanzanite: Alps, Alps Forest, Alps Mountainside, Arctic, Frost Forest, Glacier, Icy Hills, Polar, Snowy Coniferous Forest, Snowy Dead Forest, Taiga, Tundra Malachite: Bayou, Bog, Dead Swamp, Fen, Lush Swamp, Quagmire, Sludgepit, Swampland, Wetland Sapphire: Coral Reef, Crag, Hot Springs, Kelp Forest, Mangrove, Marsh, Sacred Springs

Exactly MC, you've got it.  Some people seem to be ok for some time, others are probably ok forever (they'd never post up on the tracker so I wouldn't see them), others have faults within days - it probably depends on where the chunk data is stored in the file what effect an overflow has.  Months is an exaggeration though, before 1.0.9c (not quite two months yet) the GC wires didn't even transfer power at all in most cases - the fix for that is what's caused this over-aggressive passing on of power you're seeing now.
 
So long as the infinite power feeds into an energy cell bank then comes out of the cells as normal TE conduits they should be limited to normal maximums so should stop more than that one chunk from corrupting - in theory.  Sometimes the corruption doesn't happen in the same world - that doesn't make sense to me and I haven't been able to replicate it, but it does seem to be the case for some people - I've seen examples where people have had huge chunks missing out of space stations and things like that (they do tend to be missing rather than garbled when this happens though, so perhaps it's something else).
 
Epic, you're in fact using this bug, yes.  I help a lot on the tracker, this is a semi-common problem, and I'm just trying to make people aware in advance as there's not any going back unless you have a backup - it's a pretty well known among regulars on the tracker but if people don't follow it (most people would have no reason to, it's not that exciting) then they might not know, that's all.
 
Think of it like this;
It's not magic - it's not generating 250 times more than it should be in a legitimate way, it's a bug - if you're willing to exploit it to cheat then you'd be better served just using the creative energy cell. If it's not your server and you can't do that, then you're risking corruption of someone else's server by exploiting a bug to cheat.  If that's not bannable on your server I'd be surprised. If it corrupts everything around your base, it's not that I don't want to help you or punish you for it or anything later on the tracker - it's that there's nothing anyone can do if you don't have a backup, that's all.  No hard feelings or anything like that - that's what I want to avoid because some people have lost a lot of work and are understandably unhappy.  Shooting the messenger doesn't help

Hey, everyone,   Attack of the B-Team 1.0.10b will be promoted to Recommended shortly.     AS ALWAYS, back up your worlds (SSP and/or server) and set your launcher up to "Always Use Recommended Builds"  (or manually select version 1.0.10b) and enjoy!   One thing to note is that you may be prompted about a missing itemid; this is unavoidable due to an internal item rename in Project Red.   The 1.0.10b server can be downloaded here.   Changelog for Attack of the B-Team 1.0.10b;  this is a list of all changes since 1.0.9c:    - Immibis Core has been updated to version 57.2.0.  - MineFactory Reloaded has been updated to version 2.7.6.448.  - Random Things has been updated to version 1.9.  - Galacticraft, Galacticraft-Planets, and MicDoodleCore have been updated to version 2.0.10.978.  - Carpenter's Blocks has been updated to version 2.0.6.  - Mr. Crayfish's Furniture Mod has been updated to version 3.2.9.  - Liquid XP has been updated to version 57.1.2.  - Forge Microblocks has been updated to build 250.  - Witchery has been updated to version 0.16.3.  - Open Blocks has been updated to version 1.2.7.  - Open Mods Lib has been updated to version 0.4.  - Morph has been updated to version 0.7.1.  - Bibliocraft version 1.5.5 has been added.  - Bibliowoods for Biomes O' Plenty version 1.3 has been added  - Bibliowoods for Natura version 1.1 has been added.  - Galacticraft has been reconfigured to ensure that most mod glass blocks work with the oxygen sealer.

Not incredibly hard, you should just be able to download the server files, run it, and have your family connect to the server using the computers internal network IP (typically a 192.168.* number)
 
If you need to find your internal IP address for the machine the server will be on, you can follow these steps to get the info:
 
 
For Windows:
* Press Windows Key and R
* Enter in "cmd"
* click ok or press enter
* type in "ipconfig /all"
* Look for a line with "IPv4 Address" (in some cases you may only have an IPv6 Address, and you would need this value instead)
 
For Mac:
* Run terminal
* type in "ifconfig -a"
* Look for a line with "IPv4 Address" (in some cases you may only have an IPv6 Address, and you would need this value instead)
 
Edit: If for some reason the line of IPv4 Address does not exist on Mac output, it may be under a different header. I am unfamiliar with Mac to a massive extent and am not 100% sure if it prepends the info with the same as windows (last i knew i believed it did but it has been a few years since i did anything with a Mac)

Download new server files. Unzip, copy over world folder from old server. Done.

I'm sure this is a reasonable request if you're intending to pay the developers.  Are you intending to pay for the developers?
 
If you consider for a minute that the main reason they're working on this is because they want to and they're sharing it with everyone because they're being nice.  They're paying for you to be able to play and provide a tool for installation and updates (which took time to write) and paying for your bandwidth costs when you download from them, all to make it easier for you.  They provide even the latest twitchy version if people want to play with it, but they won't call it recommended if it's not ready to be called recommended (this saves many people like me a lot of trouble we'd get from something not being ready, I don't need to pay nearly so much attention because they've got it sorted).
 
I know you're not trying to appear ungrateful, but think about what you're saying here;
The B-Team work with the Technic pack guys to make this stuff available for you to play with (and it is available, just not recommended).  Much bigger groups that should be able to afford it more easily don't bother with that, it's an exceptional interaction with their community.
The Technic pack guys develop and distribute these packs for free - this must be expensive even just for the bandwidth.  The cost in time for the people working on it is time they could be spending doing contracts for actual money - they're choosing to spend it here, for you.  This is no different in effect from spending even more money, for you.
 
The reason not asking about it is policy is probably because of how demoralizing it can be - I don't and have never worked in this team, but in similar situations I've seen similar questions or demands and believe me - when you're doing this for a community because you like them, they like you, it's all "happy fun times" and you get a bunch of guys showing up who make it not fun by making demands on your already stretched time it's really hard to keep bothering (remember you're usually working to be able to pay for all this stuff you're giving away, this is what you do in your free time).  My first reaction when seeing something like this is something along the lines of "Ugh.. you entitled little-" (I'm not saying this about you, I didn't think your post was that bad, but some can be awful and I'm trying to help you understand how another persons mindset might go from the other side of the dev process).
 
 
Now you've read all that you should be able to see what it sounds like and how it comes across - if anyone owes anyone anything, it's you that owes the Technic guys, both for their time and their money.  Your statement can translate to something like "Thanks for the free stuff, but you should give me more free stuff sooner please", which is a little ridiculous sounding when you look at it like that.  Hostility that you see from other forum members when asking about this kind of thing is based around that - if you upset the devs to the point they decide to take a week off or something then you've slowed it down, making things worse for everyone - the devs both who are working with heavier loads now, the devs who are taking a break and may even drop the project altogether if you really struck a nerve, the players who have longer to wait - everyone in the community can suffer for a comment like that, so even if there isn't a rule specifically disallowing it (which, as it was pointed out, there is), it's still a dick thing to do.
 
Sorry to rant about this here, but if even one person understands a little better because of this it'll have been worth it.

Possible solutions:
1) If you're running a 64-bit OS, install only 64-bit java
2) If you're low on RAM, upgrade computer
3) Use mods like Optifine to increase fps
4) Use in-game video settings to lower graphical settings
...

1) [ and ] move up and down in the menu, shift+[ ] move left/right. left clicking, and pressing enter selects the highlighted morph
 
2) CTRL+Q clicking items drops them from inventory.

Origin biomes seem to have them more often than not. But they seem to be on the coastal lines otherwise. And yes, you cannot generate steam in attack of the b-team. The "Steam Dynamo" generates steam, but its for internal use only and does not actually exist as a liquid.

This is a tutorial for an automated animal farm, this design was tested with Pigs, Cows, and Chickens
 
Open the Spoiler for the video tutorial!



 
The Base Building
The farm design itself is a 7x7x7. The bottom two layers are for redstone. So find an area, clear out the 7x7, then surround the inner 5x5 area with a block of some sort (such as glass) 4 high leaving one block on the bottom layer empty on three sides. Then put a roof on it, leaving the center one blank. After that, place slabs on the lower half of the bottom layer of the wall blocks. This will create a 2.5 block high inner area.
 

 
Note: the image above does not have the hole in the center of the roof, but it should be there.
 
The Machines
You will need to make the following machines as well as have the following redstone components:
1 Breeder 1 Grinder 1 Mob Counter 1 Vacuum Hopper 1 Redstone Comparator 2 Redstone Torch 5 Redstone 2 Tesseracts (or additional Energy Conduits and Fluiducts!) 6 Energy Conduits 1 Saw Machine Locations
In one of the open bottom slots, preferably across from another hole, place the Mob Counter so it is counting inside of the farm. Opposite the Counter, place the Grinder. And in the final slot, place the Breeder. In the roof ceiling, place the Vacuum Hopper.
 
At this point it should look similar to the following image

Note: In the image above, across is the Breeder, to the left is the Harvester and the right machine is the Mob Counter. And the Vacuum hopper in the top.
 
Now break out the blocks from the breeder and harvester to the same corner. If possible, save these blocks. Place one of the two Tesseracts in this corner and run the Energy Conduit from the Tesseract to the Breeder and to the Harvester. Place the second Tesseract on top of the Vacuum Hopper and make the Vacuum Hopper output Experience to the Tesseract on the upper portion. This will be the experience output.
 

 
Note: Redstone Energy Conduits are used in the image above, but any conduits can be used. The point of this is to get power to the Breeder and Harvester.
 
Redstone Mechanics
Under this build, clear out a 1 block high area, 2 if you are unable to morph into a bat. Under the Mob Counter, place 1 redstone dust. Then place the comparator so it is facing toward the Harvester. To the right of the Comparator, place one redstone dust and one redstone torch. Make sure to not toggle the Comparator into subtraction mode (the first redstone torch on the comparator would be on in this case) In front of the comparator, toward the Harvester, place the final three dust. This should lead into a block. The block on the opposite side, under the Harvester, will be placed a redstone torch.
 

 
Note: The above image had the base building removed to better show off the redstone placed. It can be difficult to see if the building was left there.
 
Finalizing
Now, you're almost done. We need to block off the cable from being accessed by the animals (and causing a miscount on the Mob Counter, or escaping from the pen) so using the Saw and the blocks you (hopefully) saved from clearing out, cut them down into Panels or Covers and cover the cables up from the inside. Once the energy conduits are covered up, you can then safely place in two of the desired animal (Pig, Cow, Chicken) into the pen then fill up the breeder. This will run for quite some time.
 
Additional Changes
Here is a list of additional changes you do to make this more automated or more efficient.
Auto-fill Breeder from below from your storage system. Place a chest on the back side of the harvester to catch items Then suck those items into your storage  
Be creative! You can use this farm setup to create two additional pens for the cows, chickens or pigs (depending which one you started with).
 
Just see what I did with mine.

This is a tutorial for an automated animal farm, this design was tested with Pigs, Cows, and Chickens
 
Open the Spoiler for the video tutorial!



 
The Base Building
The farm design itself is a 7x7x7. The bottom two layers are for redstone. So find an area, clear out the 7x7, then surround the inner 5x5 area with a block of some sort (such as glass) 4 high leaving one block on the bottom layer empty on three sides. Then put a roof on it, leaving the center one blank. After that, place slabs on the lower half of the bottom layer of the wall blocks. This will create a 2.5 block high inner area.
 

 
Note: the image above does not have the hole in the center of the roof, but it should be there.
 
The Machines
You will need to make the following machines as well as have the following redstone components:
1 Breeder 1 Grinder 1 Mob Counter 1 Vacuum Hopper 1 Redstone Comparator 2 Redstone Torch 5 Redstone 2 Tesseracts (or additional Energy Conduits and Fluiducts!) 6 Energy Conduits 1 Saw Machine Locations
In one of the open bottom slots, preferably across from another hole, place the Mob Counter so it is counting inside of the farm. Opposite the Counter, place the Grinder. And in the final slot, place the Breeder. In the roof ceiling, place the Vacuum Hopper.
 
At this point it should look similar to the following image

Note: In the image above, across is the Breeder, to the left is the Harvester and the right machine is the Mob Counter. And the Vacuum hopper in the top.
 
Now break out the blocks from the breeder and harvester to the same corner. If possible, save these blocks. Place one of the two Tesseracts in this corner and run the Energy Conduit from the Tesseract to the Breeder and to the Harvester. Place the second Tesseract on top of the Vacuum Hopper and make the Vacuum Hopper output Experience to the Tesseract on the upper portion. This will be the experience output.
 

 
Note: Redstone Energy Conduits are used in the image above, but any conduits can be used. The point of this is to get power to the Breeder and Harvester.
 
Redstone Mechanics
Under this build, clear out a 1 block high area, 2 if you are unable to morph into a bat. Under the Mob Counter, place 1 redstone dust. Then place the comparator so it is facing toward the Harvester. To the right of the Comparator, place one redstone dust and one redstone torch. Make sure to not toggle the Comparator into subtraction mode (the first redstone torch on the comparator would be on in this case) In front of the comparator, toward the Harvester, place the final three dust. This should lead into a block. The block on the opposite side, under the Harvester, will be placed a redstone torch.
 

 
Note: The above image had the base building removed to better show off the redstone placed. It can be difficult to see if the building was left there.
 
Finalizing
Now, you're almost done. We need to block off the cable from being accessed by the animals (and causing a miscount on the Mob Counter, or escaping from the pen) so using the Saw and the blocks you (hopefully) saved from clearing out, cut them down into Panels or Covers and cover the cables up from the inside. Once the energy conduits are covered up, you can then safely place in two of the desired animal (Pig, Cow, Chicken) into the pen then fill up the breeder. This will run for quite some time.
 
Additional Changes
Here is a list of additional changes you do to make this more automated or more efficient.
Auto-fill Breeder from below from your storage system. Place a chest on the back side of the harvester to catch items Then suck those items into your storage  
Be creative! You can use this farm setup to create two additional pens for the cows, chickens or pigs (depending which one you started with).
 
Just see what I did with mine.

Anything that can take or receive power in TE you should be careful to connect only once to a GC power source.  In your example - letting the TE conduit (can take in power) touch the solar panel or wire on multiple sides in the same conduit - the panel/wire outputs power to the TE system each time it touches, not an overall calculation like it should be, so if you had a TE conduit going around a wire in a U shape it'd touch it three times and draw however much power is in the wire out three times (this is where the infinite power comes from).  The corruption comes from the fact that this extra power can exceed the limits that it should be able to in the TE system and after a point the number gets so high that minecraft can't store it in the allocated space any more and it rolls into the next byte of the chunk save file.
 
A tesseract would be fine in all likelyhood, use GC cables most of the way and go into the tesseract once only, or just make sure any TE conduit touches whatever wire network you have only once and you'll be fine.

Decompiled the code, looked it over, here's the values i read from it.
Item - Hunger Restored - Saturation Modifier Apple Juice - 5 - 0.6 Apple Pie - 10 - 0.6 Bacon - 4 - 0.6 Bowl of Cereal - 13 - 0.6/0.8 Bowl of Rice Meat - 9 - 0.6 Bowl of Rice Veggie - 8 - 0.6/0.8 Bread & Butter Pudding - 12 - 0.6 Bread Slice - 3 - 0.6 Bread W/ Butter - 6 - 0.6 Bread W/ Nutella - 10 - 0.6 Broth - 9 - 0.6 Butter - 1 - 0.6 Caramel - 1 - 0.6 Carrot Soup - 6 - 0.6 Cereal - 6 - 0.6 Cheese - 6 - 0.6 Cheese Pasta - 12 - 0.6 Chicken Dice - 2 - 0.6 Chips - 6 - 0.6 Chocolate - 4 - 0.6 Chocolate Donut - 6 - 0.6 Chocolate Ice Cream - 3 - 0.6 Chocolate Ice Cream Completed - 6 - 0.6 (Unsure what this is) Coffee Milk - 4 - 0.6 Coffee solo - 2 - 0.6 Cooked Carrot - 5 - 0.6 Cooked Meat - 5 - 0.6 Cooked Mutton - 5 - 0.6 Crisps - 10 - 0.6 Donut (Base) - 2 - 0.6 Egg Bacon - 9 - 0.6 Egg Sausage - 7 - 0.6 Fish & Chips - 11 - 0.6 Flour - 1 - 0.6 Fried Chips - 8 - 0.6 Fried Egg - 4 - 0.6 Fried Rice - 4 - 0.6 Fried Rice Final - 8 - 0.6 (Not sure what this is exactly compared to the above one) Frozen Milk - 3 - 0.6 Grilled Sausage - 8 - 0.6 Hamburger - 6 - 0.6 Hot Chocolate - 4 - 0.6 Hot Chocolate final - 6 - 0.6 (Again, not sure what this is compared to above) Hot Dog - 10 - 0.6 Ice Chunk - 1 - 0.6 Ice Cream Cone - 2 - 0.6 Kebab - 10 - 0.6 Melon Ice Cream - 3 - 0.6 Melon Ice Cream Complete - 6 - 0.6 (Unsure what this is) Milkshake - 3 - 0.6 Muffin - 4 - 0.6 Nutella - 4 - 0.6 Omelette - 3 - 0.6 Omelette Final - 6 - 0.6 (Per before, no idea what this means) Pasta - 10 - 0.6 Pinchito - 7 - 0.6 Pizza Slice - 4 - 0.6 Raw Meat - 2 - 0.6 Raw Mutton - 3 - 0.6 Raw Pinchito - 2 - 0.6 Raw Pizza - 2 - 0.6 Rice - 2 - 0.6 Rice tomato - 5 - 0.6 Salt - 1 - 0.6 Sandwich - 8 - 0.6 Sandwich Bread - 2 - 0.6 Sausage - 4 - 0.6 Sea Weed - 2 - 0.6 Slurpees - 4 - 0.6 Smash Potato - 10 - 0.6 Soda - 2 - 0.6/0.8 Spaghetti - 1 - 0.6 Steak & Chips - 12 - 0.6 Stew - 10 - 0.6 Strawberry - 2 - 0.6 Strawberry Chocolate - 8 - 0.6 Strawberry Donut - 6 - 0.6 Strawberry Ice Cream - 3 - 0.6 Strawberry Ice Cream Completed - 6 - 0.6 (Unsure what this is) Strawberry Jam - 4 - 0.6 Strawberry Milkshake - 3 - 0.6 Sushi - 6 - 0.6 Sweet - 10 - 0.6 Toast - 2 - 0.6 Tomato - 4 - 0.6 Tomato Sauce - 2 - 0.6 Waffle - 3 - 0.6 Saturation Modifiers having two values were unknown (reading obfuscated code is annoying) so they are potential values based on what was read.
 
Also, it seems saturation modifier isn't an important factor in this mod and it boils down to the hunger restored. Also, keep in mind that dividing the hunger restored by 2 will give you the number of meat pops/haunches/etc it restores. Also, since I was reading the code, the names are what is found in-code and may not fully represent the in-game name, but if they're off just a bit they should still be noticeable. If anything was missed, let me know.

The goal of this thread is explain my thought process about creating an auto-crafting system and my experiences along with it.
 
The Primary Objective
Create a repeatable system that can be expanded upon that allows for crafting for all items possible through the use of the crafting table, while avoiding the Crafting Pipes, Crafting Chips, Extended Pipes, etc.
 
The First Design
Going off of the objective, I attempted to create a system using the Cyclic Assemblers that would create a certain amount of items. Using basic redstone mechanics of vanilla Minecraft. I was able to achieve this by using vanilla minecraft chests getting the output of the Cyclic Assembler, and using a comparator to see how many items were made in the system.
 

 

 
As you can see from the images, the top portion of the Cyclic Assembler receives the item input, the Routed Interface Pipe has a "Stock Keeper" card in it with the desired ingredients necessary to craft an item specified by the Schematic in the Cyclic Assembler. This will always keep the necessary items on-hand in the machine. The chest to the right of the machine was a temporary holding area for storage items and would be the input from your storage system into the machine.
 
The Cyclic Assembler is marked to only accept input from the top, and only output to the bottom. This was necessary in this design to prevent unwanted artifacts from occurring. As well as the Cyclic Assembler was marked to have a low redstone signal in order to function. This was key in the design to prevent it from just constantly producing output if redstone was ignored, and to not involve a NOT signal in the event of using a high redstone value.
 
With the Cyclic Assembler outputting into the chest below, the Comparator works on it and will send out a signal depending on the contents of the chest.
 
The First Design Results
This worked pretty well, outside of the fact that for some items that my not want to have a ton of on-hand, such as Machine Frames or other expensive machines, this method would create 124 of them before turning off the machine. One downside to this design is the fact that the chest cannot be opened and thus a Routed Request Pipe is necessary to interact with it, with a Routed Interface Pipe and an Item Broadcaster chip installed on the chest.
 
The Second Design Objective
Learning from what I did in the first design, I set out to come up with a second solution to the problem of: How to limit the amount of items to be slightly more specific, or at least give an option of a lower max output.
 
The Second Design
Again, starting with basic redstone mechanics, and how the redstone comparator works. I ended up replacing the chest with a Hopper, an object that has a lot less inventory space and thus each item counting to a higher value.
 

 
The Second Design Results
This design was much better for limiting output to a certain amount. For items that stack to 64, it was limited to 23 of that item on-hand through the use of the Hopper.
 
The Third Objective
What other storage systems work with the comparator and what values do they output a redstone signal of 2, since this is what is required to turn off the machine.
 
The Third Design
No changes were made to the system as the portion that did the numerical value relied on the Redstone Comparator, using this, I could simply place a container down and then put a comparator to read its contents, and then place as many items into it until the signal power was 2. 2 being the desired strength in the previous designs to turn off the cyclic assembler.
 
The Third Results
Container - Amount Until Signal 2
Hopper - 23
Breeder - 39
Storage Crate - 65
Rancher - 77
Chest - 120
Locker - 120
Secret Trapped Chest - 120
Secret Chest - 120
Bamboo Chest - 120
Koa Chest - 120
Reinforced Chest - 179
Reinforced Locker - 179
Vacuum Hopper - NS
Pattern Chest - NS
Ender Chest - NS
Backpack - NS
Ender Backpack - NS
Deep Storage Unit - NS
Cardboard Box - NS
Crafting Station (BetterStorage) - NS
Strongbox - NS
Hardened Strongbox - NS
Reinforced Strongbox - NS
Resonant Strongbox - NS
Mailbox - NS
Planter - NS
Fertilizer - NS
Veterinary Station - NS
Unifier - NS
 
NS values represents a "No signal" condition. That is, the redstone comparator did not output a signal regardless of the number of items in the container.
 
The Fourth Preface
Using the previous tests values, I could come up with a simple system of limiting certain items to always have 23 on hand using Hoppers, and another container for higher values but it was now onto the stackability.
 
The Fourth Objective
Create a repeatable method of auto-crafting systems that took up as less room as possible but still functional
 
The Fourth Design
Using the fact that the redstone comparator only outputs a signal of 2, making the cyclic assembler responsible for the containers output to be the only one to disable, the system could be stacked horizontally (X/Z repeat) with no gaps inbetween, making the system very compact.
 
That is, stripping the original setup down to the components of the Cyclic assembler, the storage container, and the redstone in the back, this could be stacked on the left or right side of them to create an infinite line and could be stacked vertically in some situations.
 

 


 
More to come to this post as my designs and tests progress.

that "wizard" mod would probably be ars magica 2, if it were to be added, but unlikely unless the B-Team group pushes for it. The guns and mechs from flans still wont protect you from the witchery teleport. Vanilla gear won't be powerful enough. Tinkers' construct weapons could work quite well (Rapier) but you still have the issue of being able to hit the witch as well as not getting teleported to another location that makes it a pain to get to. 1v1 battles against witches seems to be simply out of the question if you have ever been taglocked before. A large group would probably be able to do much more damage to a witch but you would need to be coordinate with them, like an actual military assault team, and that takes time and practice to do so.

How is this relevant on this thread?
There's a Tracker for posting issues!

You can indeed find sacred saplings in dungeon chests, these are as rare as them coming from any source though.
 
@Phoenix - Lumber Axe wouldn't work on it from the base base, as its taller than the max blocks necessary. A harvester from TE won't have an issue with it though, and itd be lag free (ish.....ykno, besides the growth)

There needs to be a blade in the lower slot

They are using the latest version of the modpack (1.0.10b atm) and not the recommended (1.0.9c) you would have to change it to the latest through the launcher's cog icon under the modpack logo.

From what i read there is an item called ball o moss crafted with sticks and vines in the tnt pattern that you throw at regular temple blocks

1.0.10a seems to have a lower spawn rate. I mentioned in another thread that I was there for an hour and only got the 1k pixies, whereas before it was 10s for the 1k pixies. It still isn't entirely resolved but it seems to be less of an issue in the updated modpack version.

in 1.0.10a the bop pixie issue seemed to be lessened but will eventually be there (the rate in which they spawn seemed to be dramatically lowered, i spent about an hour there with only about 1k, whereas before it was 10s for 1k)
 
project red being updated also means that the cpu usage/leaks/etc should be available now as well.

There's a pinned thread, in this exact section, actually that contains the server download for >1.0.10a and another thread for >1.0.10b. For future reference, there will be a "Let's Test" thread in this section for versions that are not marked as recommended. These threads will contain the changelog as well as the download link to the server files.