lizzy's patches for luanti https://git.vlhl.dev/lizzy/luanti/minetest.git/atom?h=0.4.14 2016-05-01T13:32:02+00:00 2016-05-01T13:32:02+00:00 est31 MTest31@outlook.com 2016-03-31T23:52:17+00:00 urn:sha1:ac8bb457aae58867cbb96a5e64d286e7edc18e16 * Fix naming style for methods and classes: Use camelCase for methods and PascalCase for classes as code style demands it. And use sneak_case for methods that are not member of a class. * Replace "* " with " *" for Pointers * Same for references * Put function body opening braces on new line * Other misc minor non functional style improvements 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-12T17:08:17+00:00 Auke Kok sofar@foo-projects.org 2016-03-04T07:18:04+00:00 urn:sha1:37b4f0d34c73de58e0f5d153b7e699dc7430e23d NDT_CONNECTED attempts to connect to any side of nodes that it can connect to, which is troublesome for FACEDIR type nodes that generally may only have one usable face, and can be rotated. We introduce a node parameter `connect_sides` that is valid for any node type. If specified, it lists faces of the node (in "top", "bottom", "front", "left", "back", "right", form, as array) that connecting nodeboxes can connect to. "front" corresponds to the south facing side of a node with facedir = 0. If the node is rotatable using *simple* FACEDIR, then the attached face is properly rotated before checking. This allows e.g. a chest to be attached to only from the rear side. 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-03-09T00:45:23+00:00 Auke Kok sofar@foo-projects.org 2016-03-06T20:02:21+00:00 urn:sha1:4e59fcf5c1e40dee764317a1190dceadc3a77829 I've written several experimental bits of code that revolve around the need for a consistent calendar, but implementing one is extremely hard in mods due to time changes and mods overriding core.get_timeofday(), which will conflict. The second part of the problem is that doing this from a mod requires constant maintenance of a settings file. An implementation in core is trivial, however, and solves all of these problems at virtually no cost: No extra branches in server steps, and a single branch when minetest.set_time_of_day(), which is entirely reasonable. We store the day_count value in env_meta.txt. The use case is obvious: This change allows mods to create an actual virtual calendar, or properly account for seasonal changes, etc.. We add a "/days" chatcommand that displays the current day count. No permissions are needed. It can only retrieve the day count, not modify it. 2016-03-07T21:33:20+00:00 ShadowNinja shadowninja@minetest.net 2015-10-31T00:38:22+00:00 urn:sha1:3ce6642a26d43fd368c24cdfc5460557258fb44f 2016-03-07T21:33:20+00:00 ShadowNinja shadowninja@minetest.net 2015-10-30T23:27:48+00:00 urn:sha1:821551a2669123ac9a476894d65b5efe10026040 2016-03-07T21:33:20+00:00 ShadowNinja shadowninja@minetest.net 2015-10-30T03:38:36+00:00 urn:sha1:2e74e9ee20cee987a7326378c6ab73ec93e25457 2016-03-07T21:33:20+00:00 ShadowNinja shadowninja@minetest.net 2015-10-30T03:26:03+00:00 urn:sha1:0079887b645e0ee441bd2cfcd7874a1148fdd656