Git Product home page Git Product logo

buildcraft's Introduction

Welcome to BuildCraft on GitHub

Reporting an issue

Please open an issue for a bug report only if:

  • you are sure the bug is caused by BuildCraft and not by any other mod,
  • you have at least one of the following:
    • a crash report,
    • means of reproducing the bug in question,
    • screenshots/videos/etc. to demonstrate the bug.

If you are not sure if a bug report is valid, please use the "Ask Help!" subforum.

Please only use official BuildCraft releases for any kind of bug reports unless otherwise told to do by the BuildCraft team. Custom builds (for instance from Jenkins) are unsupported, often buggy and will not get any support from the developers.

Please check if the bug has been reported beforehand. Also, provide the version of BuildCraft used - if it's a version compiled from source, link to the commit/tree you complied from.

Please mention if you are using MCPC+, Cauldron, OptiFine, FastCraft or any other mods which optimize or otherwise severely modify the functioning of the Minecraft engine. That is very helpful when trying to reproduce a bug.

Please do not open issues for features unless you are a member of the BuildCraft team. For that, use the "Feature Requests" subforum.

BuildCraft, being an open-source project, gives you the right to submit a pull request if a particular fix or feature is important to you. However, if the change in question is major, please contact the team beforehand - we wish to prevent wasted effort.

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 on discord before submitting a PR (https://discord.gg/v4geqgA).

Do not submit pull requests which solely "fix" formatting. As these kinds of changes are usually very intrusive in commit history and everyone has their own idea what "proper formatting" is, they should be done by one of the main contributors. Please only submit "code cleanup", if the changes actually have a substantial impact on readability.

PR implementing new features or changing large portions of code are helpful. But if you're doing such a change and if it gets accepted, please don't "fire and forget". Complex changes are introducing bugs, and as thorough as testing and peer review may be, there will be bugs. Please carry on playing your changes after initial commit and fix residual issues. It is extremely frustrating for others to spend days fixing regressions introduced by unmaintained submissions.

Frequently reported

  • java.lang.AbstractMethodError, java.lang.NoSuchMethodException
    • A mod has not updated to the current BuildCraft API
    • You are not using the correct version of BuildCraft for your Forge/Minecraft versions
    • You are using the dev version on a normal game instance (or vice versa)
  • Render issue (Quarry causes flickering) - Try without OptiFine first! This is a known issue with some versions of OptiFine.

Compiling and packaging BuildCraft

  1. Ensure that Java (found here), Git (found here) are installed correctly on your system.
  • Optional: Install Gradle (found here). You probably want to install version 4.3.1.
  1. Create a base directory for the build
  2. Clone the BuildCraft repository into 'baseDir/BuildCraft/'
  3. Clone (and update) the submodules into 'baseDir/BuildCraft with 'git submodule init' and 'git submodule update'
  4. Navigate to basedir/BuildCraft in a shell and run one of two commands:
    • ./gradlew setupCIWorkspace build to just build a current jar (this may take a while).
    • ./gradlew setupDecompWorkspace to setup a complete development environment.
    • With Gradle installed: use gradle instead of ./gradlew
    • On Windows: use gradlew.bat instead of ./gradlew
  5. The compiles and obfuscated module jars will be in 'baseDir/BuildCraft/build/libs/<build number>/modules'

Your directory structure should look like this before running gradle:


baseDir
\- BuildCraft
 |- buildcraft_resources
 |- common
 |- ...
 \- BuildCraftAPI
  |- api
  |- ...
 \- BuildCraft-Localization
  |- lang
  |- ...

And like this after running gradle:


basedir
\- BuildCraft
 |- .gradle
 |- build
 |- buildcraft_resources
 |- common
 |- ...
 \- BuildCraftAPI
  |- api
  |- ...
 \- BuildCraft-Localization
  |- lang
  |- ...

Localizations

Localizations can be submitted here. Localization PRs against this repository will have to be rejected.

Depending on BuildCraft

Instructions for depending on BC 7.1.x can be found here (for 1.7.10).

8.0.x hasn't been finished yet, so there are no instructions for depending on it :(

The following instructions are for BC 7.99.12 (1.12.2):

Add the following to your build.gradle file:

repositories {
    maven {
        name "BuildCraft"
        url = "https://mod-buildcraft.com/maven"
    }
}

If you want to depend on JUST the API then do this:

dependencies {
    deobfCompile "com.mod-buildcraft:buildcraft-api:7.99.12"
}

If you want to depend on JUST the lib then do this:

dependencies {
    deobfCompile "com.mod-buildcraft:buildcraft-lib:7.99.12"
}

If you want to depend on the whole of buildcraft do this:

dependencies {
    deobfCompile "com.mod-buildcraft:buildcraft:7.99.12"
}

Where 7.99.12 is the desired version of BuildCraft.

buildcraft's People

Contributors

alexiil avatar asiekierka avatar spacetoad avatar covertjaguar avatar afdw avatar sirsengir avatar krapht avatar aenterprise avatar hea3ven avatar cpw avatar flow86 avatar calenxwx avatar zlangbert avatar psxlover avatar viliml avatar mystise avatar tambry avatar dmillerw avatar sfplayer1 avatar aartbluestoke avatar sandgrainone avatar justwannafly avatar kubuxu avatar cisien avatar ititus avatar tarzanbuzzyman avatar immibis avatar pahimar avatar taelnia avatar davboecki avatar

Stargazers

 avatar ChenPi11 avatar  avatar  avatar Taimander avatar  avatar

Forkers

syming1803

buildcraft's Issues

一个比较影响游戏体验的1.12遗留bug

之前在BC github上反应过,issues#4678
1.12中的靛金刚管道会在箱子满时弹出物品,这在任何以往版本中都是不存在的,应该是bug,这个问题1.18中仍然存在。

1.18.2(弹出物品):

1.18.2_x264.mp4

1.7.10(不弹出物品):

1.7.10_x264.mp4

1.6.4(不弹出物品):

1.6.4_x264.mp4

建筑机BUG

1.门信息、铁质管道朝向、条纹管道朝向、靛金刚管道朝向、钻石管道设置,不会随建筑机朝向的改变而变化;

Minecraft_.1.18.2.-.Singleplayer.2024-06-09.13-49-13_x264.mp4
_x264.mp4

2.建筑机需求列表中不显示应消耗的“管道附着方块”以及“液体”,建造时也不会消耗这些物品和液体。

-.Trim_x264.mp4

3.建筑机在批量建造时,若在放置蓝图前存有所需物品,则只会建造最后一排;若在放置蓝图前建筑机中不含物品,则只会建造第一排和最后一排。

Minecraft_.1.18.2.-.Multiplayer.LAN.2024-06-09.14-43-18_x264.mp4
Minecraft_.1.18.2.-.Multiplayer.LAN.2024-06-09.14-50-35_x264.mp4

BuildCraft API 已在2014年12月10日以MIT许可证重新授权

参见:
BuildCraft#2248
我注意到 1.18.2 BuildCraft API部分代码的许可证重新变回MMPLv1。
https://github.com/CalenXwX/BuildCraftAPI/blob/9efe5972161da7c7726519bbe033c0f395d18a47/resources/LICENSE.API
这里是BuildCraft API所用的许可证,实际上是MIT许可证。

BuildCraft本体除了机器人以外的代码都在1.12.2被AlexIIL重写并改用MPLv2许可证了,没重写的机器人部分也得到了授权改用MPLv2许可证了,说是因为MMPLv1许可证有缺陷。
BuildCraft#3004

仍以MMPLv1开源的1.12.2代码在这里,貌似现在已经不用了,据说编译出jar文件根本没用到这一部分代码。
https://github.com/BuildCraft/BuildCraft/tree/8.0.x-1.12.2/src_old_license/buildcraft

考古学家()

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.