2451b6925f
Renamed "Auto Workbench" to reduce confusion with the "Advanced Crafting Table". Once again I barrowed liberally from Railcraft. This time from the Rolling Machine. You will recognize the new GUI. Auto Workbenches are 100% compatible with vanilla Hoppers, or whatever you want to use to interface with it. It no longer implements ISpecialInventory at all. Even RP2 would work with it now. Implemented the same "Sample Output" vs "Real Output" design that the Rolling Machine uses. If there are enough items to craft multiple times, it will craft automatically. But if there are only enough items for one craft job, you must click the sample output slot to start the process. Separating the display from the output helps reduce the complexity of the code by a large factor. Banned all items that can't stack or that have containers from being used in the Auto Workbench. Supporting these types of items is the major reason the previous version was so buggy. The Advanced Crafting Table does a much better job with that kind of thing, use it instead. Crafting now has a time cost. It take 256 ticks to craft an item. Unlike the Rolling Machine, it DOES NOT require power. Removed ability to pull from adjacent inventories. Its laggy, complex, and unnecessary now. If you need more capacity, use a Hopper or Chute. |
||
---|---|---|
buildcraft_resources | ||
common/buildcraft | ||
.classpath | ||
.gitattributes | ||
.gitignore | ||
.project | ||
build.xml | ||
README.md |
Welcome to Buildcraft on GitHub
Contributing
If you wish to submit a pull request to fix bugs or broken behaviour feel free to do so. If you would like to add features or change existing behaviour or balance, please discuss it with Sengir or Krapht before submiting the pull request.
Reporting issues
Issues are for bugs/crashes, please do not use them to ask general questions. Always include the version you are having trouble with. Or if you're building from source, which source you're building. If you don't, we might assume that you are using latest-greatest and waste a bunch of time trying to reproduce a problem that might have fixed been already. Such things makes for very grumpy devs. Grumpy devs spend less time coding and more time doing stuff that makes them less grumpy.
Compiling and packaging Buildcraft
- Ensure that
Apache Ant
(found here) is installed correctly on your system.
- Linux users will need the latest version of astyle installed as well.
- Create a base directory for the build
- Clone the Buildcraft repository into
basedir/BuildCraft/
- Optional: Copy BuildCraft localization repository into
basedir/BuildCraft-Localization
- Navigate to basedir/Buildcraft in a shell and run
ant
(this will take 2-5 minutes) - The compiled and obfuscated jar will be in basedir/bin
Your directory structure should look like this before running ant:
basedir
\- buildcraft
|- buildcraft_resources
|- common
|- ...
\- buildcraft.localization
|- lang
And like this after running ant:
basedir
\- buildcraft
|- bin
|- build
|- buildcraft_resources
|- common
|- download
|- ...
\- buildcraft.localization
|- lang
Localizations
Localizations can be submitted here. Localization PRs against this repository will have to be rejected.