Hello everybody. I have built minetest from the git repository but a strange thing is happening: the lightening is flickering all around the environment and the sun and moon are crossing the sky every second. Does some one have a clue about what is the problem?

\o/ Uhooooool... Minetest working perfectly after recompiling with default flags! Within uncountable hundreds of software packages built by myself, it is the first time that my high optimization setup lead to a logical failure other than an entire crash of an application. Living and learning.

VanessaE: You are right then. I reduced instead of increasing the variable's value to 1. Taking into account the GCC documentation I think that `-O3' or `-mtune=atom' are the trouble makers, since the other flags are superfluous.

kaeza: It will need too much debugging, and perhaps it is not reproducible. I think it doesn't worth. I'm happy with my now functional Minetest. Besides that, developers tends to ignore bugs relating compiler optimization (but I think, by obvious reasons, that is not the case for GCC, though).

One interesting thing to record is that no time_speed value can reproduce the flickering frequency that I was experiencing with the previous build. With the sound build when time_speed is sufficiently high, the sun doesn't show up and it is almost like eternal night with a translating moon. With the broken build I was seeing both celestial bodies crossing the sky at the same time and numerous lighting flicks per se

cond. What an amazing and crazy world a compilation error can generate. I can't believe that the resulting code was logically valid (the machine and the operating system thought it was a correct program) but the physical behavior was intuitively wrong. It is an unlikely scenario in my personal conception.

I guess he only used the 6 base flowers for color - red from rose, orange from tulip, yellow from yellow dandelion, blue from geranium, violet from viola, and white from white dandelion. Nothing to get black?

oitofelix: we don't really currently have resources to implement encryption using the design principles of minetest (minimal, multiplatform, reasonably easy to compile on windows); and before that, protocol rework should be done anyway

You are just thinking about common cases; only about your case. There is people on dictatorial countries that cannot even play this game and talk about what they want. Is there a constant surveillance from the government even, and especially, in the US. Minetest is free software and it will develop a lot in the next years and people from numerous countries and with the most diverse interests will come in. We cannot predict what

Oh. If you are restricting murder, you are restricting something bad, which is a good thing to do. If you restrict software, the software is the same whether it is restricted or not, and whether it is good/bad is determined by how it is restricted. Those things don't go together in the same argument

I do wish it would be called something else both minetest nether version and the eventual sky. I mean there are so many names to choose for the hell land and the skylands but the modders being close minded will just call it nether and skyland or go the extra mile in and call it aether

hmmmm, if you play 0.3 you have a pretty nice game that has lots of issues; in fact the issues are so much that you dont really care anymore; when we devolp the game now and fix issues, people start seeing all the other small things and are complaining about it

hmmmm: they're upset because no fake colored lighting, to them, translates into no colored lighting of any type or form. Maybe that wasn't adequately explained, but leaving over that issue is just childish.