Minetest 0.4.11

[paramat]

Optional snow biomes for mgv6 using the pinetrees is planned for next stable release (as long as the MTgame team still approves).
Mgv5 is in but is considered 'unstable': it may still change subtly but we will try to minimise any changes. So if you start a mgv5 world you have to be prepared for possible discontinuities in future.
The biome API is also unstable and is about to be improved in a backwards-compatible way. You should continue to use 0.4.11 stable until i write my post explaining the new features and how to make it blend seamlessly with your existing worlds, this will involve a slight rewriting of your biome registrations.
Now that we have a simple grass biome as default in mgv5 and mgv7 you will now need to add:

Code: Select all

minetest.clear_registered_biomes()

immediately before registering your own, otherwise the default biome will interfere with your registered biomes.

[Thermal_Shock]

^I'm looking forward to your posts explaining the new system paramat. Biome support from the engine has been the biggest item on my wishlist.

Also thanks to the devs for continuing to grow Minetest into an even more powerful engine. The changelog has a lot of exciting stuff.

[coconut]

I find so awesome the new pine tree, thank you!
Im waiting for the snow biome now :D
happy new year guys :D

[SAMIAMNOT]

Now all my games and worlds and mods should be fully compatible with this, right? Checking before I upgrade...

[MoNTE48]

Android build by ME!!!
viewtopic.php?f=42&t=9389&start=125

[leeminer]

I love the changes. My only small criticism is the texture for the hand. For me it looks worse than the previous version.

I love the particles that appear when chopping things.

[rubenwardy]

I love the changes. My only small criticism is the texture for the hand. For me it looks worse than the previous version.

I love the particles that appear when chopping things.

That may be a bug, see 'odd wield items in 0.4.11' topic.

[fjlv9000]

when i use all mi mods it says the fire mod on default cant run(failed to open init.lua)

[CraigyDavi]

when i use all mi mods it says the fire mod on default cant run(failed to open init.lua)

What's the full error? (check the debug.txt file)

[fjlv9000]

17:02:28: ERROR[main]: ========== ERROR FROM LUA ===========
17:02:28: ERROR[main]: Failed to load and run script from
17:02:28: ERROR[main]: D:\Users\VIT2600\Desktop\minetest-0.4.11-win32\bin\..\games\minetest_game\mods\fire\init.lua:
17:02:28: ERROR[main]: ...p\minetest-0.4.11-win32\bin\..\builtin\common\strict.lua:18: attempt to index global 'debug' (a boolean value)
17:02:28: ERROR[main]: ======= END OF ERROR FROM LUA ========
17:02:28: ERROR[main]: Server: Failed to load and run D:\Users\VIT2600\Desktop\minetest-0.4.11-win32\bin\..\games\minetest_game\mods\fire\init.lua
17:02:28: ERROR[main]: ModError: ModError: Failed to load and run D:\Users\VIT2600\Desktop\minetest-0.4.11-win32\bin\..\games\minetest_game\mods\fire\init.lua

this happens when i activate all mi mods

[rubenwardy]

Please provide a list of all your mods. Also, where did you download Minetest from? (Please link to the page.)

[ShadowNinja]

attempt to index global 'debug' (a boolean value)

This happens when I enable all of my mods.

One of your mods is nuking the Lua debug library. Look for a line like "debug = false" or "debug = true" in one of your mods and notify the mod maker of the issue. They should be using locals and even then they shouldn't shadow a builtin Lua library ("local DEBUG = true/false" should do).

EDIT: You can find the offending mod by setting WARN_INIT to true at the top of "builtin/common/strict.lua". Look for a line like "WARNING: Global variable 'debug' created at path/to/some/mod/init.lua:123" before the error message and report the issue with that mod.

[Marshall_maz]

Thank you for updating the Ubuntu ppa :) Just one question , why did the package name change again ? This will make it tricky for people who don't know how to go and look for the package name and wonder why their minetest is not updating.

For info sake Ubuntu peeps , the 0.4.10 version package name was minetestc55. Now it is just minetest again. So after you added your correct ppa you will need to remove minetestc55 first and then install minetest. It won't update normally.

So finally I can play on my Ubuntu box , and I must say guys , great work to all who works on this. Using 0.4.11 stable on my Ubuntu 14.04 and it's has MUCH better fps than 0.4.10 did. Super smooth. Great work guys and thank you very much !!! :)

[BlauerEisRegen]

Hi, I wanted to play minetest on ubuntu 14.10, but there is only minetest 0.4.10.. when comes the update for ubuntu 14.10? :(

[Calinou]

Hi, I wanted to play minetest on ubuntu 14.10, but there is only minetest 0.4.10.. when comes the update for ubuntu 14.10? :(

If you are using the packages, it will come when you upgrade to Ubuntu 15.04, which is not released yet.

Please use this script to use the latest version on Ubuntu 14.10.

[jp]

Simpler solutions...

Copy-paste that in your console for update to 0.4.11 stable (only for >= ubuntu 14.04) :

Code: Select all

sudo add-apt-repository ppa:minetestdevs/stable && sudo apt-get update && sudo apt-get upgrade

For 0.4.11-dev (daily newest but unstable, that works both for >= ubuntu 14.04 and 12.04 only) :

Code: Select all

sudo add-apt-repository ppa:minetestdevs/daily-builds && sudo apt-get update && sudo apt-get upgrade

[Linuxdirk]

when comes the update for ubuntu 14.10? :(

As far as I understand Canonical’s release cycles: Never.

[dgm5555]

Using ubuntu 14.04: I removed minetest 0.0.10 with:-

Code: Select all

sudo apt-get remove minetestc55

Then attempted to reinstall with:-

Code: Select all

sudo add-apt-repository ppa:minetestdevs/stable && sudo apt-get update && sudo apt-get upgrade

Unfortunately although it adds the ppa key, it didn't actually install
I had to install it from the terminal with

Code: Select all

sudo apt-get install minetest

However WAY WORTH THE EFFORT of figuring what to do it's much smoother!!!

Unfortunately I get errors which seems to be with the core code when attempting to change config settings on any worlds (even a brand new one)

Code: Select all

10:40:47: ERROR[main]: MAINMENU ERROR: Invalid sequence found in setting parameters
10:40:47: ERROR[main]: stack traceback:
10:40:47: ERROR[main]: 	[C]: in function 'set'
10:40:47: ERROR[main]: 	/usr/share/minetest/builtin/mainmenu/dlg_config_world.lua:192: in function 'handle_buttons'
10:40:47: ERROR[main]: 	/usr/share/minetest/builtin/fstk/ui.lua:118: in function 'handle_buttons'
10:40:47: ERROR[main]: 	/usr/share/minetest/builtin/fstk/ui.lua:155: in function </usr/share/minetest/builtin/fstk/ui.lua:148>

And gedit complains when opening the debug.txt file:-
"The file you opened has some invalid characters. If you continue editing this file you could corrupt this document."

[Marshall_maz]

Using ubuntu 14.04: I removed minetest 0.0.10 with:-

Code: Select all

sudo apt-get remove minetestc55

Then attempted to reinstall with:-

Code: Select all

sudo add-apt-repository ppa:minetestdevs/stable && sudo apt-get update && sudo apt-get upgrade

Unfortunately although it adds the ppa key, it didn't actually install
I had to install it from the terminal with

Code: Select all

sudo apt-get install minetest

The upgrade command didn't work because there was no package with the same name but older version already
installed at that moment. Removing and re-installing is required due to the package name change. The upgrade command will only update a package with the same name already installed that have a newer version available.

[dgm5555]

@Marshall_maz I don't quite understand. I would have thought the apt-get remove minetestc55 would have removed it. Was there something else I should have done. Is this why I'm getting the config fault?
This is going to be pretty confusing for 99% of ubuntu users...

[dgm5555]

And I may have spoken too soon about the smoothness, I just managed to fly into a non-loaded hole in the ground and fly around underneath the world. Cool, but not quite what should be possible.
Would be a really fun idea for a mod though, if you could temporarily stop loading and/or mapgen, and just fly around what was already there...

[Marshall_maz]

@Marshall_maz I don't quite understand. I would have thought the apt-get remove minetestc55 would have removed it. Was there something else I should have done. Is this why I'm getting the config fault?
This is going to be pretty confusing for 99% of ubuntu users...

You removed minetestc55 , which you had to do because the new one has a different package name.
So at that point there was no minetest installed on your system at all anymore. So there is nothing for the upgrade command
to upgrade. Hence you had to manually install it again. The upgrade command only upgrades packages already installed on your system. It doesn't automatically install every package from a PPA you added , as this will cause
chaos as you can imagine. Upgrade command is not an install command , it simply upgrades packages already installed on your system. Hope I explained good enough ?

If the package name wasn't changed , then you wouldn't need to remove it and neither would have to manually
install it again. The upgrade command would have upgraded it cos there would have been a package with the same name already installed with newer version available. This is the way apt works and has nothing to do with minetest. The problem is caused though by mintest devs changing the package name.

The same thing happend from 0.4.9 to 0.4.10. Then it changed from minetest to minetestc55.
That's why I asked the question a few posts up why they are doing this cos it is definitely causing confusion
for users who don't know how to check the package name and what to do when it changed.

[dgm5555]

Duh. I usually run install and update as separate lines, and this time copied @jp's line which didn't have an install. I guess it should have been:

Code: Select all

sudo apt-get remove minetestc55 && sudo add-apt-repository ppa:minetestdevs/stable && sudo apt-get install minetest && sudo apt-get update

Next question is there an easy way to get the application shortcut back in the application list (which worked brilliantly for .10), or do I have to keep executing .11 from a terminal?

BTW another couple of bugs:-
1. The server/admin player is white with no head.
If you change the texture (eg with [mod] Wardrobe) the player gets a head back (both with F7 and viewing from client version). However after a little while the texture is forgotten and goes back to the white headless thing. Steve has a head, but display of new texture is also dropped after a little while (again both for F7 and viewing from server).
Previously (at least for single player mode) the texture remained until changed or game exit.
2. Masses of 'warnings' from lua are displayed in the chat text (eg warnings about assignment to undeclared global variables), which weren't displayed in .10. I've turned off chat completely just to get rid of them, but is there a way to keep chat working without all the warnings and error messages (I'm happy with looking for them in debug.txt if I want to)?
3. Some of the mods fail to function in .11 when they worked fine in .10

PS Sorry, as I'm sure a lot of hard work has gone into it, but I'll probably only give .11 another few days trial and will most likely be going back to .10 for the moment since it doesn't seem to like my Ubuntu 14.04

[dgm5555]

Just a thought, is there any way of installing .10 and .11 on the same Ubuntu system, that way I can have the stable version to play with and still test .11
[EDIT] I just had a really horrible thought, I have no idea how to get back to .10 Can anyone please help with this?

[TenPlus1]

best way is to uninstall the latest daily version and re-install the stable...