![]() Otherwise, feel free to look at the changelog. We think we will start to merge breaking compat PR in 1 or 2 weeks. Are you a new user Have a look at our Getting Started, FAQ, and Tutorials pages on our wiki. There are other breaking changes which can happen to master branch, then be careful and don't use on your production builds, switch to stable-0.4 asap. If you compile Minetest from source, you need recent compiler, GCC 5.1 or Clang 3.6 are the minimum on UNIX systems and MSVC 2012 for Windows Visual Studio build. Please update to Debian 9 or latest RHEL/Centos 7 if you are on those distributions, if you use Windows XP, Microsoft told you to update years ago. Direct consequence: Windows XP is not supported anymore, and old distros like Debian 7 or RHEL/Centos 6. Some packets needs a cleanup because they are not properly sent to server which can cause problems in the future.Īnother important point, Master branch now uses C++11 standard. ![]() Minetest 0.5 needs to be done to fix some old problems on core engine especially on network protocol, which maybe needs a full break. In consequence, server owners who uses Github master branch for production servers should now switch to stable-0.4 branch or their server can become incompatible with release clients soon. There is not really a need for it any longer as Minetest 0.5.0 supports a inbuilt mod manager. ![]() We discussed about this but we are not organized on how maintain it separately from master as we are a tiny coredev team :) We stated it's time to take a break and fix some things and add breaking features to core engine.įirst thing server owners should know, we wanted to let a last 0.4.17 happen, which will be a bugfix only release, maintained on free time. Minetest next release will be a breaking compat release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |