FOSS gamedev and creative worlds

You should note that the sqlite database should never be copied on-the-fly, because the copy can get corrupted if minetest writes to the original at the same time. Personally I have ended up with a corrupted copy at least once. It will load just fine, but many parts of the world can be complete rubb...

redcrab wrote:3Gb ram.. server only.
What is your system recommendation ?

Well, it requires like 100M of free RAM, so that should be plenty...

Another random crash but not of the same type

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

ERROR: StaticObjectList::insert(): id already exists


That is a known bug.

std::bad_alloc usually means you have ran out of free memory.

It might be because all memory is validly used or because of some infinite memory consumpting loop (which would be a bug).

How much RAM do you have?

This was write on the command line when redirecting the primary output to a text file (something was still written to the console): If you want to do it that way, you should redirect both, stdout and stderr: minetest &> log.txt But Minetest always writes a log file called debug.txt, which should be...

Apparently gemstones is using a function in the Lua API which isn't contained in the latest Windows build.

Currently there is no way to get the player's camera direction from Lua, which makes making bows impossible. That'll go on the to-do list.

It would seem you get a segmentation fault while it is pre-rendering the cubes in the inventory to textures. My guess is that your GPU drivers fail. Not really much you can do except go buy a card which has a non-broken driver... Well, you could modify all the Lua scripts to not use the inventorycub...

dannydark wrote:As far as I know the weapons don't make any difference in 0.4 currently, its just the same as punching I think.

True. Will be fixed when I get my lazy ass up (eh, down?) again to work more on 0.4.

kahrl wrote:Hmm. Shouldn't weperms.txt be per-world? I'm not sure if the mod directory is guaranteed to be writeable.

There should probably be minetest.get_worldpath() for this kind of usage?

Is this, by any chance, an Athlon XP machine? 8) Intel Celeron ;) Well, that old Celeron has the same problem as an Athlon XP - it does not support some instruction that the distributed Minetest, Irrlicht, zlib or whatever uses. I guess it is SSE2, but don't know. The build configuration of Minetes...

They do spawn, but they immediately despawn.

Is this, by any chance, an Athlon XP machine? 8)

Indeed; WTF is "SandEye Studios"?

The problem is not in minetest, the problem is in texture packs. They should include the mod name now as does the default mod.

It does not make sense to add a modname automatically to images of a texture pack because they could want to provide other textures for other mods too.

Case closed.

Texture caching is not currently implemented because there are more important things to do.

neko259 wrote:

celeron55 wrote:Lol, Europe is not a country, didn't you read what the OP said?

Telling my country is too much deanonimising :3

I think you are not the only person of your country. 8) (I actually know your country, because I have unlimited admin god powers!)

Lol, Europe is not a country, didn't you read what the OP said?

I'll have to add my 2c.. I have a very extensive world I used with the 3 versions and using them with the 4 devs doesn't work right. celeron55 is correct to worry. You can build all you want in the dev versions but don't build if you worry about losing them lol. 0.4 is supposed to be able to load 0...

But even the current version can write corrupt worlds when judged by a later version or the 0.4 release version. That is the problem that I am concerned of. Basically I could always write everything to be compatible, but it always has a small performance and complexity penalty. Even the current 0.4 ...

I just want to note that 0.4 can still have changes that will break everything. That is what the -dev means. I wouldn't start such a project using it. And no, backups are not a solution in every case.

Bug confirmed and has been fixed already in github. Wood chopped down in old worlds will not work for crafting in 0.4.dev-20111204-1, altough it works in new worlds. Will be fixed in next snapshot build. (also applies to many other materials)

It is somewhat doable, but not very fancily. Off the top of my head without any testing: minetest.register_on_generated(function(minp, maxp)) local amount = math.random(0, 50) for a=0,amount do local pos = { x = math.random(minp.x, maxp.x), y = math.random(minp.y, maxp.y), z = math.random(minp.z, ma...

These are just random incompatibilities between different 0.4 development versions. You need to always use the same version as the server when using development versions.

Here you can ask questions about modding and post your mods. Be careful when running other people's mods. Somebody could make a mod that deletes all your files. However, connecting to a server which runs mods is always completely safe for the client (no guarantees, though). Also, please note that th...

This has been already fixed.

0.4 is not properly network compatible with 0.3 otherwise either so it does not make sense to make it work texture-wise. Deal with it and now stop posting these useless "bug" threads.

Anyway, Jachoo: thanks for noting this stuff out - nobody else would have done it. I didn't yet even think about MapBlock, Map and Player metadata or a database interface. Actually, Map metadata doesn't need to exist if there is a database interface, I think. It would be per-world anyway. Also, as o...

Well, as you seem to know pretty well what you need, I suggest making that happen. 8) It's not like I would have infinite time in my hands. I am still busy extending the scripting interface and what I currently am doing isn't even included in your list. There is an *enormous* amount of things to do....

I would be glad if Jachoo would try implementing this stuff using the modding API and report back to me if the API lacks some necessary functions or features to make it possible (so I can add them).

Rename existing debug.txt (= backup & remove), start the game so that you see the glitches, stop the game and post resulting debug.txt in here.