| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Another small general problem: the player is always standing exactly on the
bondary between 2 nodes e.g. Y=1.5 is exactly between nodes Y=1 and Y=2.
floatToInt() and myround() will round +/-n.5 always 'outwards' to +/-(n+1),
which means they behave differently depending on where you are: they round
upwards above sea level and downwards when underground. This inconsistency
comes from the way the coordinates are calculated, independent of the
specific C++ code.
The result is a tiny bit of lost performance when moving underground,
because 1 node level more than necessary is checked for collisions. This can
be amended by adding a tiny offset to minpos_f.Y, like @paramat suggested.
This is not an elegant solution, but still better than wasting CPU.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To determine the area (nodes) where a player movement took place
collisionMoveSimple() first took the old/new player coordinates and rounded
them to integers, then added the player character's collision box and
implicitely rounded the result. This has 2 problems:
Rounding the position and the box seperately, then adding the resulting
integers means you get twice the rounding error. And implicit rounding
always rounds towards 0.0, unlike floatToInt(), which rounds towards the
closest integer.
Previous (simplified) behavior: round(pos)+(int)box, for example player at
Y=0.9, body is 1.75m high: round(0.9)+(int)1.75 = 1+1 = 2.
==> A character's height of 1.75m always got rounded down to 1m, its width
of +/-0.3 even became 0.
Fixed by adding the floats first, then rounding properly: round(pos+box) =
round(0.9+1.75) = round(2.65) = 3.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fix taking damage caused by sneaking over a nodebox gap.
Fix strange behaviour on stair nodeboxes.
Enable jumping from node edges while sneaking.
Enable movement around corners while sneaking on a 1-node-high groove in a wall.
|
| |
|
|
|
|
|
| |
Prevents normal drawtype nodes having transparency.
Avoids clients cheating by using 'x-ray' texture packs with transparent textures.
|
|
|
|
|
|
|
|
| |
Commit cad10ce3b747b721fd63784915e05f12bc488128 altered the parameter
'float_mount_height' but was missing the necessary line in the constructor
to get the altered value from 'params'.
Fixes 3D floatland terrain generating everywhere.
|
|
|
|
| |
(#6058)
|
| |
|
|
|
|
|
| |
Some settings of paramters can cause mgv7 variables to be -inf, nan or -nan.
This can cause massive vertical columns of water to appear above sea level.
|
|
|
|
|
|
|
|
| |
* Fix render order of overlays
* Use C++11 loops
* Fix time_t
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Automatic item and node colorization
Now nodes with a palette yield colored item stacks, and colored items
place colored nodes by default. The client predicts the colorization.
* Backwards compatibility
* Use nil
* Style fixes
* Fix code style
* Document changes
|
|
|
|
|
|
|
| |
Extend documentation, limit area volume
Remove u16 count limitation
* Prevent integer overflow, replace minp/maxp with pos1/pos2
|
|
|
|
|
|
| |
* Verify HudSetParams input when hotbar textures are set
This fix #6011
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, findSpawnPos() did not take the 'mapgen_limit' setting into account,
a small limit often resulted in a spawn out in the void.
Use the recently added 'calcMapgenEdges()' to get max spawn range through a new
mapgenParams function 'getSpawnRangeMax()'.
Previously, when a player respawned into a world, 'objectpos_over_limit()' was
used as a check, which was inaccurate.
Use the recently added 'saoPosOverLimit()' to get exact mapgen edges.
Also fix default value of 'm_sao_limit_min'.
|
|
|
|
|
|
|
|
|
| |
These code be generated by CSM, a modded client or just copy and pasted by the player.
Changes
- Update configuration example and setting translation file.
- Remove colour codes before logging chat.
- Add setting to remove colour codes before processing the chat.
|
| |
|
|
|
| |
Also remove `disable_escape_sequences` since it's not needed anymore.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit 41b7823057bdaddd760f932dce802719301c3a0f.
This reverts commit 7968f1ddaa67432719d5becdda5ca8bec58faa47.
|
|
|
|
| |
You should use tags instead of this branch to track the latest release
|
|
|
|
|
|
|
| |
* Version changes: current dev version is now 0.4.17
* This change permit to have multi branches with various versions
* Dev version is 0.4.17-dev and next release will be 0.4.17
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
This function only removes player meta data,
not player authentication data.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following algorithm was used when selecting contributors:
* Every non-trivial contributor from the current release,
Non-trivial meaning more than X non-trivial commits, not counting documentation/translation changes
* The top Y contributors from the last 4 years.
* Previous contributor means no contributions since a few months before the last release.
In the future this should be automated
|
| |
| |
| |
| | |
Currently translated at 77.6% (795 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 38.1% (391 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 61.3% (628 of 1024 strings)
|
| | |
|
| |
| |
| |
| | |
Currently translated at 48.2% (494 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 79.7% (817 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 12.1% (124 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 11.0% (113 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 10.9% (112 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 90.2% (924 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 94.5% (968 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 84.2% (863 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (1024 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 88.6% (908 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 88.5% (907 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 88.4% (906 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 87.4% (895 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 86.9% (890 of 1024 strings)
|
| |
| |
| |
| | |
Currently translated at 100.0% (1024 of 1024 strings)
|