aboutsummaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2024-12-08remove unneeded unwrapAndConvertHolder callfeature/HolderableJake Potrebic
2024-12-08compile fixesJake Potrebic
2024-12-08more improvementsJake Potrebic
2024-12-08Fix compile issuesBjarne Koll
2024-12-07Switch Impl types to HolderableJake Potrebic
2024-12-07Update getKey impls for inlineable typesJake Potrebic
2024-12-07Add ItemMeta customName methods (#11685)Nassim Jahnke
2024-12-05Fix broken joml metadata resulting in kotlin being included on ↵Jason Penilla
compile/runtime classpath (#11712)
2024-12-05Fixup PlayerPickItemEvent docs moreNassim Jahnke
2024-12-05Add new bundle animation (#11708)Lulu13022002
2024-12-05More moving around of hunksdev/1.21.4Nassim Jahnke
2024-12-05Move around patches againNassim Jahnke
2024-12-05Port exact choice improvements (#11705)Jake Potrebic
2024-12-05Finish PlayerPickItemEventNassim Jahnke
2024-12-04call EntityInsideBlockEvent for eyeblossomLulu13022002
2024-12-04properly override push/knockback methodsLulu13022002
This prevent the creaking from being pushed with knockback enchant when it can't move
2024-12-04add missing effect cause, for bee being poisonedLulu13022002
2024-12-04fix asset idLulu13022002
2024-12-04fix componentsLulu13022002
2024-12-04fix item metaLulu13022002
2024-12-04Update setup-gradle actionJason Penilla
setup-gradle v4 validates the wrapper
2024-12-04Apply coordinate offset only to VoxelShapeSpottedleaf
VoxelShape coordiantes generally are an integer + a sum of powers of two between [-1, -3]. Most offsets are generally an integer. As a result, applying an offset to the coordinates generally results in an error of 0. However, coordinate inputs do not follow such trends. Thus, when applying an offset to the coordinate input, there may be some floating point error. By applying the offset to the VoxelShape coordinates, we can eliminate additional floating point error. This change also fixes the inconsistency when using the single AABB, as input coordinates were not offset when using the single AABB as the single AABB is already offset. Fixes https://github.com/Tuinity/Moonrise/issues/81 This specific issue is caused by floating point error resulting in the falling anvil's y position becoming around -8E-17 when it should be 0. While this is still very comfortably in the collision epsilon (1.0E-7), this results in the falling anvil's y block position to become -1 (as the block position is simply the floor of the coordinate).
2024-12-04Updated Upstream (CraftBukkit)Nassim Jahnke
Upstream has released updates that appear to apply and compile correctly. This update has not been tested by PaperMC and as with ANY update, please do your own testing CraftBukkit Changes: c294e05d7 SPIGOT-7975: Fix issue with Pale Sapling growing c9f5a8fdf SPIGOT-7974: Fix Crash for Creaking Heart Block particle
2024-12-04Update readme, set updatingMinecraft to falseNassim Jahnke
2024-12-04Implement assetidOwen1212055
2024-12-04Implement new CustomModelDataOwen1212055
2024-12-03Fix api build script deprecationJason Penilla
2024-12-03Always fork jvm for compile, even when using the Gradle runtime jvmJason Penilla
Fixes spurious build failures from OOM
2024-12-03Update paperweight and Gradle wrapperJason Penilla
2024-12-03Use ConcurrentUtil from Paper repoJason Penilla
2024-12-03Update MoonriseJason Penilla
2024-12-03Update DataConverterJason Penilla
2024-12-03Add back post_teleport chunk ticketNassim Jahnke
2024-12-03Fix jd gson version, move back mc util diffNassim Jahnke
2024-12-03Tests succeed (by removing one)Nassim Jahnke
2024-12-03Compilation fixesNassim Jahnke
2024-12-03Set java launcher for api generate taskJason Penilla
2024-12-03Update generated classesNassim Jahnke
2024-12-03Apply remaining patches, fix APINassim Jahnke
2024-12-03moonriseNassim Jahnke
2024-12-03Even more workNassim Jahnke
2024-12-03Some fixes, start updating CustomModelData APINassim Jahnke
2024-12-03More more more more workNassim Jahnke
2024-12-03More more more workNassim Jahnke
2024-12-03More more workNassim Jahnke
2024-12-03More workNassim Jahnke
2024-12-03WorkNassim Jahnke
2024-12-03Start update, apply API patchesNassim Jahnke
2024-12-03Updated Upstream (Bukkit/CraftBukkit/Spigot) (#11702)1.21.3Bjarne Koll
Upstream has released updates that appear to apply and compile correctly. This update has not been tested by PaperMC and as with ANY update, please do your own testing Bukkit Changes: ed0ec489 SPIGOT-7965: Unknown TransformReason for Hoglins 9db03457 SPIGOT-7964: Fix typo in Deprecation annotation d14119af PR-1082: Add "since" to Deprecation annotations e8a318d4 PR-1067: Add method to get Advancement requirements CraftBukkit Changes: 40dd796db SPIGOT-7971: NotSerializableException on serialize CraftUseCooldownComponent fa85c5e0a SPIGOT-7968: ProjectileHitEvent not trigerred when arrow hits entity b75b792ec SPIGOT-7970: World#getMaxHeight() returning incorrect value 2b9a094bb SPIGOT-7965: Unknown TransformReason for Hoglins fd3f5a380 SPIGOT-7966: Some trees do not generate with #generateTree f2822317c PR-1515: Add a Class reader and Class node argument provider 07abf6852 PR-1514: Add a test case for ClassTraverser a7577cb24 Fix Inventory#addItem not respecting max stack size 066a74e74 PR-1490: Add method to get Advancement requirements 4a1df30e4 PR-1512: Test Art class based on specific values instead of the implementation, to better catch implementation changes 53254c56f PR-1503: Simplify CAS loop to getAndSet e9447dc5e Make BlockDataMeta#setBlockData hide unspecified states dd08a7120 SPIGOT-7960: Fix inconsistency between natural item drop coordinates e9e8ed753 SPIGOT-7960: Improve natural item drop methods Spigot Changes: 60c9969b Rebuild patches
2024-12-01Fix several off-by-one errors in view distance calculationsSpottedleaf
1. For NearbyPlayers, we need to be using the view distance, and not the load distance (which is +1 of the view distance). 2. Correctly clamp tick distance to view distance. Since load distance is +1 of view distance, we need to subtract one from the load distance when clamping. Additionally, add checks inside ViewDistances to ensure that the inputs are in range to catch future errors. Also, clamp simulation distance, as values < 0 or above MAX_VIEW_DISTANCE do not make sense to configure.