FOSS gamedev and creative worlds

I recently updated my copy of Minetest on my Ubuntu 14.04 system by following the instructions listed on Minetest's Github repo under the section "Compiling on GNU/Linux", with the exception of using "-DRUN_IN_PLACE=0" rather than "-DRUN_IN_PLACE=1". The updated copy seemed to be working fine, however whenever I try to change the enabled mods for a world I get an error message:

ERROR: Invalid sequence found in setting parameters

I took a screenshot of the error and uploaded it here: http://i.imgur.com/NOaaA6v.png

The bug is reproducable.

The bug is reproducable when I do the following:

• Run Minetest
• Select a world under the Singleplayer or Server tab
• Click on the Configure button
• Click on the Save button
• Then the error message pops up

I did a little bit of testing, and it didn't matter whether I enabled or disabled any mods or not on the Configuration page, the error message would still pop up.

My operating system is Ubuntu 14.04.

My version of Minetest is 0.4.11-dev (3ea5ed4).

The bug occurs with the use of any Minetest game.

The debug.txt entry that was created when I reproduced the bug is posted here: http://pastebin.com/dSTMxFJE

The same thing happened to me recently after an update from the github repository, in an earlier commit than the one you quoted. I had to manually edit the file 'world.mt' in the 'worlds/<your_world_name>' folder to enable/disable mods.

Everything went back to normal later, probably after another update from github.

Did you sudo make install? Are you using the latest git?

I tried doing a new install and the problem still occurs in the new version.

To do the new install I did as follows:


I then moved the new minetest folder into my folder where I store my standalone applications, and then copied over my Minetest games from the previous installation into the games folder of the new minetest folder.


I then ran the game using the executable in the bin folder, clicked on "Configure", clicked on "Save", and then the error message poped up.

Aren't you supposed to do a "$ make install" at the end (see rubenwardy's post) when you compile with "RUN_IN_PLACE = 0" ?

cmake could mess the build process as well because it's very gifted at compiling with old cached settings rather than the ones you specified on the command line (I don't know if there is a command to remove all the cmake cache). Try to run your latest minetest program with the "--version" option to see if they match your command line options.

mgl wrote:Aren't you supposed to do a "$ make install" at the end (see rubenwardy's post) when you compile with "RUN_IN_PLACE = 0" ?

cmake could mess the build process as well because it's very gifted at compiling with old cached settings rather than the ones you specified on the command line (I don't know if there is a command to remove all the cmake cache). Try to run your latest minetest program with the "--version" option to see if they match your command line options.

When I ran the new install with the version tag it came up with this:



I tried going to the Minetest folder in the terminal and entering "sudo make install" and it did seem to do something. However, when I ran Mintest again, the error still occurred.

After doing make install run it using $ minetest instead of $ ./bin/minetest

It shouldn't make a difference, it is just why run in place = 0 was added, so you can install it in /use/local/bin/. It may also add an icon to the start menu.

rubenwardy wrote:After doing make install run it using $ minetest instead of $ ./bin/minetest

It shouldn't make a difference, it is just why run in place = 0 was added, so you can install it in /use/local/bin/. It may also add an icon to the start menu.

Yep, Minetest now has an icon in the menu, but the error still occurs.