The legacy code added in commit
d879a539cd - "Add minetest.swap_node"
for sending the whole mapblock to older clients on the case of a node
modification with swap_node, had the problem that the block chosen to be
sent to the client was referenced with node coordinates and not with
block coordinates, resulting in getting the wrong block sent to the client.
Entity positions are serialized as F1000. Disallow placing
entities outside safe borders with the minetest.add_entity
call.
Note that this patch only enforces those boundaries for
placing entities, moving entities that move outside boundaries
aren't affected.
Thanks to @nanepiwo for pointing this out.
Fix regression since commit:
915807f8db "Rename doc/mapformat.txt and update doc to match SRP changes"
And add an underscore to doc file name to make it more readable.
1. Do two renames:
* SER_FMT_CLIENT_VER_LOWEST -> SER_FMT_VER_LOWEST_WRITE
* SER_FMT_VER_LOWEST -> SER_FMT_VER_LOWEST_READ
Now the two define values are consistently named with the _WRITE defines
SER_FMT_VER_{HIGHEST,LOWEST}_WRITE, and to better point out what the two
serialisation versions actually are for.
2. wrap some lines in doc/worldformat.txt, and point out that the node
timers are serialized at a later point, as this can cause confusion about
what now happens (if one doesn't strictly read the if block's conditions).
3. some whitespace fixes in NodeTimerList::serialize, and one new comment.
The documentation file contains not just information about the
map itself, but also about further files inside the world's
directory.
Documentation didn't reflect recent SRP addition, now it does.
Modders are now able to select the range of ore column height,
and the midpoint at which they 'grow' starting from.
This commit adds three new parameters for the 'sheet' ore type:
column_height_min, column_height_max, and column_midpoint_factor.
clust_size is now deprecated for this ore type.
After this, it should hopefully not record line numbers anymore,
so the diffs of updatepo.sh runs are smaller. Well, this is theory,
lets see how it will turn out to be in practice.
Currently translated at 97.7% (264 of 270 strings)
This is a combination of 9 consecutive commits by the same author.
Their messages in chronological order are:
Translated using Weblate (Indonesian)
Currently translated at 79.2% (214 of 270 strings)
Translated using Weblate (Indonesian)
Currently translated at 80.0% (216 of 270 strings)
Ini merupakan istilah dan tidak perlu diterjemahkan
Translated using Weblate (Indonesian)
Currently translated at 89.6% (242 of 270 strings)
Penerjemahan
Translated using Weblate (Indonesian)
Currently translated at 94.8% (256 of 270 strings)
Penerjemahan
Translated using Weblate (Indonesian)
Currently translated at 95.9% (259 of 270 strings)
Mencari persamaan makna
Translated using Weblate (Indonesian)
Currently translated at 96.2% (260 of 270 strings)
Penerjemahan
Translated using Weblate (Indonesian)
Currently translated at 96.6% (261 of 270 strings)
Mencari persamaan makna
Translated using Weblate (Indonesian)
Currently translated at 97.0% (262 of 270 strings)
Penerjemahan
Translated using Weblate (Indonesian)
Currently translated at 97.7% (264 of 270 strings)
Istilah tidak diterjemahkan
Its obvious that "u16 command" is inside every packet, therefore this
commit removes all mentions of the command, if non-array like notation
is used. We already didn't add "u16 command" to new packets or removed
it at packet changes, so now we remove it from existing packets.
Use in-place locale directory if that exists, and
static one (RUN_IN_PLACE or CUSTOM_LOCALEDIR) doesn't exist.
Report to errorstream if neither static nor in-place locale
dirs exist, and report successfully found paths to infostreem.
Fixes two bugs:
-> Regression of commit [1] where if we use RUN_IN_PLACE=false,
but don't make install, locales aren't found. One might
think this is no regression, as its no bug, but all other
paths (mainmenu, etc.) are detected properly.
-> Regression of commit [1] where locales don't work on windows.
References:
[1]: Commit 645e208673 "Use CUSTOM_LOCALEDIR if specified" by @ShadowNinja
