Skip to content

Commit 7d05034

Browse files
chore: update changelog
1 parent 23d6a29 commit 7d05034

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

CHANGELOG.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
44
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
55
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
66

7+
## [2101.1.13]
8+
9+
### Added
10+
* An API `CustomMinYEvent` event to register custom `min-y` providers
11+
12+
### Removed
13+
* Remove the previously added support for custom min-y per chunk scanning. This does not effect the global min-y already available
14+
715
## [2101.1.12]
816

917
### Added
@@ -314,7 +322,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
314322
* Periodically, least-recently accessed region data is released from RAM, requiring reload from disk on the next access. Every 300 seconds by default; can be tuned in client config.
315323
* When the large map screen is closed, regions furthest from the player are released from RAM, down to 32 loaded regions by default; also tunable in client config.
316324
* Map zoom-out is limited where the ratio of the number of known (explored) regions to available JVM memory is poor. Limiting zoom-out reduces the number of regions which need to be loaded in memory at a given moment. This can be disabled in client config if you prefer.
317-
* New client config settings are available in the "Memory Usage" section of the client config; tuning them is a trade-off between RAM usage and disk activity. However, even when tuned toward lower RAM usage, the level of disk activity should not be a major concern.
325+
* New client config settings are available in the "Memory Usage" section of the client config; tuning them is a trade-off between RAM usage and disk activity. However, even when tuned toward lower RAM usage, the level of disk activity should not be a major concern.
318326

319327
## [1902.3.20]
320328

@@ -335,7 +343,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
335343
## Fixed
336344
* Fixed a crash with fake player mods which use buckets to pick up water in protected chunks
337345
* Fixed interaction with Fabric mods which do block placement protection by firing the FAPI block break event directly (thanks @TelepathicGrunt)
338-
* Example mod: Bumblezone
346+
* Example mod: Bumblezone
339347
* Architectury currently handles this via its own mixin
340348

341349

@@ -431,7 +439,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
431439
* This means player heads will only be visible to team-mates and allies by default; if you're not in a party team but want to be visible on the map, set your "Location Visibility" to "Public" in team settings.
432440
* Player heads can now be tracked on the map at any range, not just inside the default entity tracking range
433441
* The same visibility restrictions apply as above, via "Location Visibility"
434-
* Added server-side config item `long_range_tracker_interval` which controls how frequently long-range tracking data is sent by the server to clients; default is every 20 ticks (for players who are moving).
442+
* Added server-side config item `long_range_tracker_interval` which controls how frequently long-range tracking data is sent by the server to clients; default is every 20 ticks (for players who are moving).
435443
* Set this to 0 to disable long-tracking entirely
436444
* Be careful about setting this to very low (non-zero) values; it can cause extra server and network load, especially on very busy servers
437445
* Added entity interaction protection as a Team setting

0 commit comments

Comments
 (0)