lizzy's patches for luanti https://git.vlhl.dev/lizzy/luanti/minetest.git/atom?h=0.4.14 2016-03-29T17:59:14+00:00 2016-03-29T17:59:14+00:00 sfan5 sfan5@live.de 2016-03-29T17:55:39+00:00 urn:sha1:8f43aaf6ae5bf0d0e0809999308d84d9ece6eb6a Writing an u8 to verbosestream writes a char, not it's numeric value. 2016-03-20T01:27:57+00:00 ShadowNinja shadowninja@minetest.net 2016-03-19T16:08:24+00:00 urn:sha1:93887043d9443ba6627fea68921994d0f1896517 Changes: * Fix indentation. * Pass strings by const reference. * Merge Strfnd and WStrfnd into one class instead of copying them. * Remove trailing spaces. * Fix variable names. * Move to util. * Other miscellaneous style fixes. 2016-03-15T16:20:09+00:00 est31 MTest31@outlook.com 2016-03-14T09:18:29+00:00 urn:sha1:af30183124d40a969040d7de4b3a487feec466e4 The legacy init packet (pre v25) sends information about the client's password that a server could use to log in to other servers if the username and password are the same. All the other benefits of SRP of protocol v25 are missed if the legacy init packet is still sent during connection creation. This patch adds an option to not send the v25 init packet. Not sending the v25 packet means breaking compat with pre v25 servers, but as the option is not enabled by default, no servers are affected unless the user explicitly flips the switch. More than 90% of the servers on the serverlist support post v25 protocols. The patch also fixes a bug with greying out of non compliant servers being done wrongly, the min and max params were mixed. 2016-03-15T04:55:49+00:00 est31 MTest31@outlook.com 2016-03-09T02:12:22+00:00 urn:sha1:e0151d1054c9923630b8ae9cdae36efa261756d3 * No function overloading * Adhere coding style and with method names following lowercase_underscore_style * Use std::string in external API, handling these is much more fun 2016-03-14T08:44:28+00:00 HybridDog ovvv@web.de 2016-01-04T16:21:33+00:00 urn:sha1:c0b6986e3875e6f42682c78fd5db0080a7bae651 Only set back position when sneaking if player wasn't teleported by adding and using a bool "got_teleported" to player it fixes #2876 2016-03-12T17:08:17+00:00 Auke Kok sofar@foo-projects.org 2016-02-25T08:16:31+00:00 urn:sha1:e737b1c271c9d957651ef2201bb820e4465358bf We introduce a new nodebox type "connected", and allow these nodes to have optional nodeboxes that connect it to other connecting nodeboxes. This is all done at scenedraw time in the client. The client will inspect the surrounding nodes and if they are to be connected to, it will draw the appropriate connecting nodeboxes to make those connections. In the node_box definition, we have to specify separate nodeboxes for each valid connection. This allows us to make nodes that connect only horizontally (the common case) by providing optional nodeboxes for +x, -x, +z, -z directions. Or this allows us to make wires that can connect up and down, by providing nodeboxes that connect it up and down (+y, -y) as well. The optional nodeboxes can be arrays. They are named "connect_top, "connect_bottom", "connect_front", "connect_left", "connect_back" and "connect_right". Here, "front" means the south facing side of the node that has facedir = 0. Additionally, a "fixed" nodebox list present will always be drawn, so one can make a central post, for instance. This "fixed" nodebox can be omitted, or it can be an array of nodeboxes. Collision boxes are also updated in exactly the same fashion, which allows you to walk over the upper extremities of the individual node boxes, or stand really close to them. You can also walk up node noxes that are small in height, all as expected, and unlike the NDT_FENCELIKE nodes. I've posted a screenshot demonstrating the flexibility at http://i.imgur.com/zaJq8jo.png In the screenshot, all connecting nodes are of this new subtype. Transparent textures render incorrectly, Which I don't think is related to this text, as other nodeboxes also have issues with this. A protocol bump is performed in order to be able to send older clients a nodeblock that is usable for them. In order to avoid abuse of users we send older clients a "full-size" node, so that it's impossible for them to try and walk through a fence or wall that's created in this fashion. This was tested with a pre-bump client connected against a server running the new protocol. These nodes connect to other nodes, and you can select which ones those are by specifying node names (or group names) in the connects_to string array: connects_to = { "group:fence", "default:wood" } By default, nodes do not connect to anything, allowing you to create nodes that always have to be paired in order to connect. lua_api.txt is updated to reflect the extension to the node_box API. Example lua code needed to generate these nodes can be found here: https://gist.github.com/sofar/b381c8c192c8e53e6062 2016-02-23T13:24:21+00:00 nerzhul loic.blot@unix-experience.fr 2016-02-23T09:58:13+00:00 urn:sha1:147425483a9e1afa2a2a4d9c0d5fa8b68d105644 2016-01-23T15:33:24+00:00 Auke Kok sofar@foo-projects.org 2016-01-21T22:40:24+00:00 urn:sha1:735e3b70596e16d04de1edcd878deec3c539c6ed 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 2016-01-09T21:24:22+00:00 ASL97 asl97@outlook.com 2015-12-07T09:39:48+00:00 urn:sha1:106d4b7d05cfbba901abd540113991042d77bc97 2016-01-04T06:50:39+00:00 gregorycu gregory.currie@gmail.com 2016-01-04T05:15:50+00:00 urn:sha1:e7e9171f37730c34dd687aa2b9ca5392aa41e46b