Last updated: 16/08/2019
We'll sometimes upload testing builds to the test directory. Please join the discord to properly discuss the changes or check on the status of bugs when downloading these, as they aren't stable and may be updated daily.
Before we properly release a version to the public we need to ensure that there aren't any regressions. Specifically everything that you used to be able to do should still work without crashing or being buggy. While we have some tests internally, these don't cover the entirty of what is possible. Additonally it's a lot harder to run tests with every existing mod to ensure that we remain compatable with them all. This is when we rely on others to check to make sure that newer mods don't crash. Usually just downloading the current prelease build and adding it to a copy of your current world and modset is sufficent for testing (and reporting any new bugs or crashes to github or discord that arise from this).
New features or content
Sometimes before finishing a feature fully and merging it into mainline (so that it can be released fully alongside everything else) we'll upload 'in-progress' features as seperate download files. Unlike pre-release builds, these are very unstable, and may not work between updates or even as a repleacement for the current version. (There are no tests running of this type at the moment. In the future we'll release new engine mechanics and robots here)
BuildCraft 220.127.116.11: prerelease 1
Changelog for 18.104.22.168-pre1:
- [#4468] Stopped buildcraft tiles from uselessly logging that the client lacked ownership information (despite ownership only being used on the server).
- [#4471] Fixed a crash when spawning block breaking particles in an invalid state.