summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Remove ClientMap::m_camera_mutexKahrl2016-02-09
| | | | | All places that lock this mutex are only called by the main thread: ClientMap::updateCamera(), ClientMap::updateDrawList(), ClientMap::renderMap(), ClientMap::renderPostFx().
* FindSpawnPos: Let mapgens decide what spawn altitude is suitableparamat2016-02-09
| | | | | | | | | | | | To avoid spawn search failing in new specialised mapgens Increase spawn search range to 4000 nodes Add getSpawnLevelAtPoint() functions to EmergeManager, class Mapgen and all mapgens Remove getGroundLevelAtPoint() functions from all mapgens except mgv6 (possibly to be re-added later in the correct form to return actual ground level) Make mgvalleys flag names consistent with other mapgens Remove now unused 'vertical spawn range' setting
* Use inventory_image in the first place for inventory item meshRealBadAngel2016-02-08
|
* Cleanup selection mesh code, add shaders for halo and selection boxesRealBadAngel2016-02-08
|
* builtin: Fix `print` crashing on nil "holes".Diego Martinez2016-02-08
| | | | | | | | | | | | | The engine implementation of `print` packs the varargs into a table and passes the table directly to `table.concat`. If you pass any value not supported by `table.concat` (particularly `nil`), the server crashes. This is unexpected behavior, as `print` is supposed to be able to work with anything. This patch changes the implementation so it first converts all arguments using `tostring`, which fixes the issue and makes the custom `print` function compatible with the stock Lua behavior.
* small drawItemStack cleanupest312016-02-08
| | | | | | -> Replace the three bool params with an enum -> Add struct for the static content, leads to less repetition -> cache enable_animations setting
* Use meshes to display inventory itemsRealBadAngel2016-02-07
|
* Use tangent space meshes only when shaders are enabledRealBadAngel2016-02-07
|
* Add admin command which says who the administator is for the server.Splizard2016-02-04
|
* Implement OSX Travis buildsPavel Puchkin2016-02-04
|
* Mgvalleys: fix riverbeds below sea levelDuane Robertson2016-02-02
| | | | | Stop riverbeds from forming plateaus under sea. Minor corrections to random lava/water placement.
* Mgv5/v7/flat/fractal: Move tunnel noise calculation into generateCavesparamat2016-02-02
| | | | | | | | | | Tunnel 3D noises are only calculated when solid terrain is present in mapchunk, avoiding large amounts of unnecessary calculations Change 'int' to 's16' in calculateNoise Change 'i' to 'vi' for voxelmanip indexes for consistency Keep 'u32 index3d' local to a smaller part of tunnel code Mgv7: Don't call CaveV7 if no solid terrain in mapchunk Give 'open' bool a more descriptive name
* Mgvalleys: use standard cavesDuane Robertson2016-01-31
| | | | | | | | | | Replace simple caves with V5 caves, adding unpredictable water and lava settings and massive caves based on subterrain. Remove fast terrain mode and accompanying settings. Remove superfluous temperature/humidity settings. Remove lava/water height setting. Fix errors in humidity handling and remove humidity_break_point setting. Move cave noises to generateCaves. Fix minor formatting/naming issues and use MYMAX/MYMIN/myround.
* Fix OSX building issue caused by ad884f2Pavel Puchkin2016-01-29
|
* Don't pass non-const references to collision methodsest312016-01-29
| | | | | Non const references cause a lot of confusion with behaviour of code, and are disallowed by minetest style guide.
* New timer design.Auke Kok2016-01-29
| | | | | | | | | | | | | | | | | | | | | | | I could honestly not make much sense of the timer implementation that was here. Instead I've implemented the type of timer algorithm that I've used before, and tested it instead. The concept is extremely simple: all timers are put in an ordered list. We check every server tick if any of the timers have elapsed, and execute the function associated with this timer. We know that many timers by themselves cause new timers to be added to this list, so we iterate *backwards* over the timer list. This means that new timers being added while timers are being executed, can never be executed in the same function pass, as they are always appended to the table *after* the end of the table, which we will never reach in the current pass over all the table elements. We switch time keeping to minetest.get_us_time(). dtime is likely unreliable and we have our own high-res timer that we can fix if it is indeed broken. This removes the need to do any sort of time keeping.
* Clocksource: use a better clock if available.Auke Kok2016-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | clock_gettime() is a far better clock than gettimeofday(). Even better than clock_gettime() is that you can select either CLOCK_MONOTONIC, or even CLOCK_MONOTONIC_RAW. These clocks offer high precision time. And the _RAW variant will never roll back due to NTP drift or daylight savings, or otherwise. I've adjusted this code to select the right clock method auto- matically based on what's available in the OS. This means that if you're running a very old linux version, MacOS or other, you will automatically get the best clocksource available. I've tested all Linux clocksources by selectively compiling and running a 10k+ timer test suite. In all cases I confirmed that the 3 POSIX Linux clocksources worked properly, and were selected properly. I've modified the OS X compile path to use the high-res clock source for all time functions, but I can't confirm it works or that it compiles. As for WIN32, I confirmed that the used clocksource is indeed a Monotonic clocksource, so good news: that code section appears to be exactly what it should be.
* Don't print whole json data buffer to errorstream on errorest312016-01-28
| | | | | | `errorstream` must not be overly verbose as clientside it is directly printed onto the ingame chat window. These days, the serverlist can contain > 200k bytes, so better print it to warningstream if the data buffer is too long.
* Translated using Weblate (Italian)Paolo DGZ2016-01-25
| | | | Currently translated at 52.0% (410 of 787 strings)
* Translated using Weblate (Hungarian)Kisbenedek Márton2016-01-25
| | | | Currently translated at 32.4% (255 of 787 strings)
* Translated using Weblate (Dutch)Tobyplowy2016-01-25
| | | | Currently translated at 95.5% (752 of 787 strings)
* Translated using Weblate (Portuguese (Brazil))Ian giestas pauli2016-01-25
| | | | Currently translated at 41.6% (328 of 787 strings)
* Translated using Weblate (Portuguese (Brazil))Ian giestas pauli2016-01-25
| | | | Currently translated at 26.6% (210 of 787 strings)
* Translated using Weblate (Portuguese)Ian giestas pauli2016-01-25
| | | | Currently translated at 23.6% (186 of 787 strings)
* Translated using Weblate (Japanese)Rui2016-01-25
| | | | Currently translated at 43.4% (342 of 787 strings)
* Translated using Weblate (Japanese)Rui2016-01-25
| | | | Currently translated at 42.0% (331 of 787 strings)
* Translated using Weblate (Danish)Peter Mikkelsen2016-01-25
| | | | Currently translated at 30.1% (237 of 787 strings)
* Translated using Weblate (Chinese (China))Jun Zhang2016-01-25
| | | | Currently translated at 34.8% (274 of 787 strings)
* Fix world config menu ignoring `name` in `mod.conf`.Diego Martinez2016-01-23
|
* Backface culling: Ignore setting in tiledef from old servers.Auke Kok2016-01-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | Outdated servers are always sending tiledefs with culling enabled no matter what, as the value was previously entirely ignored. To compensate, we must (1) detect that we're running against an old server with a new client, and (2) disable culling for mesh, plantlike, firelike and liquid draw types no matter what the server is telling us. In order to achieve this, we need to bump the protocol version since we cannot rely on the tiledef version, and test for it being older. I've bumped the protocol version, although that should have likely happened in the actual change that introduced the new backface_culling PR #3578. Fortunately that's only 2 commits back at this point. We also explicitly test for the drawtype to assure we are not changing the culling value for other nodes, where it should remain enabled. This was tested against various pub servers, including 0.4.13 and 0.4.12. Fixes #3598
* Fix compilation warning if compiling for android with c++11est312016-01-23
|
* Fix texture tear issueRealBadAngel2016-01-23
|
* Fix C++11 compilabilityest312016-01-23
| | | | Previous commits broke it... :(
* Liquid flow: Prevent water spreading on ignoreparamat2016-01-20
|
* Allow per-tiles culling.Auke Kok2016-01-20
| | | | | | | | | | | | | | | | | | | | | | | | Backface culling is enabled by default for all tiles, as this is how the lua parser initializes each tiledef. We revert to always using the value from the tiledef since it is always read and serialized. Mods that wish to enable culling for e.g. mesh nodes, now can specify the following to enable backface culling: tiles = {{ name = "tex.png", backface_culling = true }}, Note the double '{' and use of 'name' key here! In the same fashion, backface_culling can be disabled for any node now. I've tested this against the new door models and this properly allows me to disable culling per node. I've also tested this against my crops mod which uses mesh nodes where culling needs to be disabled, and tested also with plantlike drawtype nodes where we want this to continue to be disabled. No default setting has changed. The defaults are just migrated from nodedef.cpp to c_content.cpp.
* EmergeManager: Do not queue duplicate block requestskwolekr2016-01-19
|
* Fix Settings::remove() always returning trueKahrl2016-01-19
|
* Show infotext with description for item entitiesRealBadAngel2016-01-18
|
* Correct overflowing rivers in Valleys mapgen.Duane Robertson2016-01-18
|
* Fix wield item glitchRealBadAngel2016-01-18
|
* corrected minetest.pos_to_string()Pinky Snow2016-01-16
| | | | corrected this bit reflect the function properly.
* Fix error message in settings tab overlapping 'save' buttonRogier2016-01-16
| | | | | | | | | | The save button is now fully functional again when an error message is shown. After an invalid value is entered in the settings tab dialog, the GUI label for the error message that is shown was partly overlapping the 'save' button, so that the top half of the button could not be clicked on.
* Prevent spawning in rivers with valleys mapgen. Remove unecessary whitespace.Duane Robertson2016-01-16
|
* Make ItemStack:set_count(0) clear the item stacksfan52016-01-15
| | | | fixes minetest/minetest_game#786
* Make all mesh manipulators in mesh.cpp work with any vertex typeKahrl2016-01-15
| | | | | | | | | cloneMesh() has to use a switch in order to create a different mesh buffer type depending on vertex type. (Credit: the new cloneMesh was written by RealBadAngel.) To avoid repetitive code, all other methods use getVertexPitchFromType() to automatically adapt the indexing to the vertex type at runtime.
* Add Valleys mapgen.Duane Robertson2016-01-14
|
* Mgv7/flat/fractal: Place biome top node on tunnel entrance floorparamat2016-01-14
|
* Mapgen: Various fixes and improvementsparamat2016-01-11
| | | | | | | | | | | | | Lua_api.txt: Document 'minetest.registered_biomes' Minimal: Remove 'mapgen_air' alias Cavegen: Add fallback node for 'mapgen_ice' Dungeongen: Add fallback node for 'mapgen_river_water_source' Mgv5: Remove unnecessary '#include util/directiontables.h' Add missing 'this->'s in makeChunk() Mgv6: Edit empty line formatting Remove leading spaces in makeChunk() Add missing spaces after 'for' and 'if' Mgv7: Edit empty line formatting
* Mgflat: Set blank default spflags. Unhideparamat2016-01-10
|
* Fix the checking of flags values in the settings tabRogier2016-01-10
| | | | | | | | | | | | Changes: - Accept setting an empty flags-type value in the settings tab if the variable specification permits it - Don't accept substrings of flag values E.g. with values: 'one,two,three', 'hree', 'w', etc. used to be accepted. Not any more - Don't accept flags with random pattern-matching special characters E.g. with values: 'one,two,three', 'on.', '(o)[n]e*' etc. used to be accepted. Not any more.