| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
prometheus-cpp switched to C++14 in April (after we did) so this issue only affects older branches.
|
| | |
|
| | |
|
| |
|
| |
Fixes outdated selection boxes after entity property changes.
|
| |
|
| |
Covers the case where mods insert their callbacks manually into "minetest.registered_<callbacks>" (often to achieve a particular order of execution).
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #12290
|
| |
|
|
|
| |
Otherwise it can happen that these are built as shared depending on the
options passed to CMake, which obviously isn't intended.
|
| |
|
|
| |
Calls to the cache function ended up creating a new texture regardless whether
the texture is already cached.
|
| |
|
|
| |
Fixes #12267 and fixes #12154
|
| |
|
|
|
|
|
|
|
|
| |
If a newly started thread immediately exits then m_running would
immediately be set to false again and the caller would be stuck
waiting for m_running to become true forever.
Since a mutex for synchronizing startup already exists we can
simply move the while loop into it.
see also: #5134 which introduced m_start_finished_mutex
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Keep code and use version check instead, for backwards compatibility
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since b2eb44afc50976dc0954c868977b5829f3ff8a19, a texture defined as
`[combine:16x512:0,0=some_file.png;etc`
will not be sent correctly from a 5.5 server to a 5.4 client due to the
overeager detection of unsupported base modifier `[` introducing a
spurious `blank.png^` before the modifier.
Fix this by whitelisting which base modifiers can be passed through
unchanged to the client, and prefix `blank.png` for the others
(which at the moment is just [png:, but the list may grow larger
as new base modifiers are added.)
|
| |
|
|
|
|
|
| |
Stop scaling images to POT immediately when loaded. The 'combine'
modifier hardcodes X and Y coordinates, and so behaves incorrectly
if applied to a scaled image. Images emitted by generateImage()
are already scaled to POT before being used as a texture, so
nothing should break.
|
| | |
|
| | |
|
| |
|
|
| |
EmergeManager keeps a copy of the BiomeGen that it creates, but
never deletes it.
|
| | |
|
| |
|
| |
Initialize the values properly
|
| | |
|
| |
|
|
|
| |
closes #12100
This time add some asserts so there is no misunderstanding about the NULL-ness of layer->texture.
|
| |
|
|
| |
fixes #12073
|
| |
|
|
| |
[backport: removed devtest change and protocol_version comparison]
|
| |
|
|
|
| |
Instead a warning is triggered if an affected compiler is detected.
closes #12022
|
| | |
|
| |
|
|
| |
see #12000
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Code that relies on `resend_count` was added in 7ea4a03 and 247a1eb, but never worked.
This was fixed in #11607 which caused the problem to surface.
Hence undo the first commit entirely and change the logic of the second.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From November 2021, the Play Store will no longer be accepting
apps which use the deprecated getExternalStorageDirectory() API.
Therefore, this commit replaces uses of deprecated API with the new
scoped API (`getExternalFilesDir()` and `getExternalCacheDir()`).
It also provides a temporary migration to move user data from the
shared external directory to new storage.
Fixes #2097, #11417 and #11118
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Currently translated at 100.0% (1356 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 100.0% (1356 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 3.2% (44 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 3.2% (44 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 100.0% (1356 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 93.2% (1264 of 1356 strings)
|
| | |
| |
| |
| | |
Currently translated at 100.0% (1356 of 1356 strings)
|
