![]() ![]() I'd like to see the project return to a state allowing sever owners to do that.Įdit: and before someone tells me that 0.4.17 doesn't exist yet, I should point out that I have a client right in front of me that reports 0.4.17 as its version. If you downloaded the Minetest Engine source code in which this file is contained, you probably want to download the Minetest Game project too. That's what I used to do, server-side, until the breaking changes started comming in. This was the state (with a few exceptions I believe) before 0.5.0 was being worked on. What I want to see happen is for the network protocol to become stable again during further development after the official release, so that servers (including mine) can use the latest dev versions as much as possible. ![]() I understand the network breakage is necessary for 0.5.0 and I'm not really troubled by it yet. Play by yourself, locally with your friends, or online with dozens of players on a server. You can mine 31,000 blocks down, or build 31,000 blocks up. All my players are still on 0.4.16 or 0.4.17. Just download a game or connect to a server. There are a lot of server-side performance enhancements and other good stuff in the dev versions beyond the last stable release, but I cannot upgraded my server to use them because of network incompatibility. Thus, if the latest version on Github changes the network layer then a server cannot upgrade to it immediately without cutting players off, and instead must wait for players to update first, which can take a long time.įor a real example, take my own server. Most players (99% probably) don't have the ability to update their client at will. So i guess i should decide what mapgen bugfixes should be applied. We can't just do a point release because a lot of compatibility breakage has already happened and started immediately after 0.4.16 was released, all we can do is take 0.4.16 stable and add bugfix PRs to it. Also, some nasty forked Android apps may not update to 0.5.0 so we have a rare chance now to encourage mobile players to switch to the official app (which hopefully will be worked on and improved before 0.5.0 is released), there will be more encouragement if servers move to 0.5.0 earlier than later.įor 0.4.17 let's not put too much work into it, just 0.4.16 stable plus a few major bufixes, no features. For example enforcing CSM restrictions (flavours) is only possible in 0.5.0. However i do not want to encourage people to stay on 0.4 as there are good reasons to encourage people to move to 0.5.0 as soon as possible. The idea of 0.4.17 was to provide a final 0.4 version for those who want to stay with 0.4 for a while. Rust is now built with llvm and seems to be much more consistently built, it might be that my troubles with rust-nightly will have ended.Hmm stujones has a point. The multi-player aspect you have covered with at least your kids playing together though you might find yourself on the game too. I think your kids will like the environment and detail and uniqueness as it is right now. It looks like most changes are major bug fixes and a few new modding api features. There has been mention of mods or addons and other such concepts for making unique servers as is done with Minetest. One for minetestgame will probably be added. So far, it seems that the world is algorithmically created and many details are involved. I can imagine that a public server will enhance gameplay too, I look forward to further advancements in this game's development. The latest release of Veloren requires a login for the public server gameplay which I don't believe I have tried yet because I cannot recall any password I may have used there, so i hope I haven't. Right now I have only spent significant time playing Veloren alone on my own box. ![]() The variety and interaction of a public minetest server adds a very substantial amount of depth to the game. First as Voxellands which no longer exists but its lineage was not known to me, then actual Minetest as singleplayer on my own box. Since then I have played minetest quite a lot. It is cool to see how much it has progressed in such a very short time. ![]() I happened across Veloren when it was little more than an idea and a blog. As opposed to minetest, I believe that any default options are fine and no fiddling is needed to get the most optimum result. I am not sure exactly where the issue with rust was but Veloren uses the nightly version which is much more "cutting edge" and this may be part of the trouble. I have had some difficulties with rust-nightly so until this recent package was made available I couldn't build it to see how it had advanced. ![]()
0 Comments
Leave a Reply. |