Skip to content

Commit

Permalink
Update 1.21-notes.md
Browse files Browse the repository at this point in the history
  • Loading branch information
TheRealWormbo authored Jul 13, 2024
1 parent 4120d40 commit f4d7e4d
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions doc/1.21-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,11 @@
* 1.21 (enchantments, data pack paths, rendering): https://fabricmc.net/2024/05/31/121.html

### Technical/internal changes
* Remove all random bits of legacy data support code; if we want to support world upgrades from pre-1.20.5 (which seems unlikely), we are going to need data fixer logic, which could also take care of legacy block entity properties, etc.
* Add MixinExtras dependency to allow for less hacky feature/fix implementations, e.g.:
* zoom for Botania bows
* apothecary filling via dripstone
* Use Fabric Mixin instead of the SpongePowered version in Xplat module to take full advantage of both Fabric and NeoForge shipping with that fork
* Use convention tags v2, since Fabric and NeoForge unified their tag systems
* ensure existing resources are tagged properly (e.g. manasteel ingots as `#c:ingots/manasteel`)
* remove platform-specific tags (except for mod compatibility where we know they stay on only one of the loaders)
Expand Down Expand Up @@ -54,9 +56,11 @@
* Figure out if there's an alternative to the variant enum and massive switch cases in `CosmeticBaubleItem`
* Horn/drum variants should be subclasses instead of having a type/variant enum that is being switched over
* Elementium armor pieces (other than helmet) could be merged into `ElementiumArmorItem` with an additional constructor parameter for the pixie spawn chance (instead of duplicating the attribute modifier logic)
* That is, unless they get more varied effects than just different spawn chances (see [this forum thread](https://forum.violetmoon.org/d/270-elementium-toolsarmor-are-they-good-or-do-they-need-a-buff))
* Use customized explosion behavior for key explosions instead of EntityMixin
* Move a whole lot of item data over to components (likely including CCA item components and potentially even some Forge item capabilities)
* Make more registries dynamic/datapackable, e.g. brews
* Make verified multiblocks (alfheim portal frame, terra plate base, enchanter setup, gaia arena without beacon base) datapackable, but with plausability checks

### Feature candidates (potentially breaking changes)
* nice-to-have Patchouli features we could use, that are yet to be merged:
Expand Down Expand Up @@ -95,8 +99,9 @@
* remove ancient debris from Orechid Ignem (replace with Loonium in Bastion Remnant)
* maybe extend biome bonus weight support from Marimorphosis to all Orechid-like recipes
* adjust Orechid stone recipes accordingly (more emeralds in mountains, more copper in dripstone caves, etc.)
* maybe even remove Orechid Ignem as a result and let the regular Orechid handle these recipes with a biome restriction, especially in combination with data-driven configuration
* maybe add data-driven Orechid configurations to replace hard-coded GoG changes (mana cost per input item, operation speed)
* GoG could eventually become a data pack instead of having all kinds of exceptions hard-coded into Botania
* GoG could eventually become an independent data pack instead of having all kinds of exceptions hard-coded into Botania
* Armadillo: add it to Cocoon of Caprice as rare spawn, maybe find something to do with its scutes
* Nether variants/behavior for pasture seed variants (either reuse existing seed types or make new ones to make nylium) and floral fertilizer (spawn mushrooms on nylium)
* Switch ender air collection to use managlass vials and maybe also alfglass flasks instead of glass bottles
Expand All @@ -109,4 +114,4 @@
* Con: Probably an automation headache, since full and half-used flasks do not stack with each other and count as compeltely different items for filtering.
* Adjust order of colored items in UIs to match vanilla sorting (which is different from the order in `DyeColor`)
* Item order in creative inventory for flowers, petals, etc.
* Storage order in flower pouch (needs data fixer to migrate to item components anyway)
* Storage order in flower pouch (~~needs data fixer to migrate to item components anyway~~ item components will be a breaking change, world update support is not planned)

0 comments on commit f4d7e4d

Please sign in to comment.