3.0.7

• Fixed a duplication issue when feeding buckets into the Alloy Forge by hand (#173)
• Ported the fix for bad RecipeInjector check to 1.21.10, allowing you to override Alloy Forge Controller Recipes

3.0.6

Fix a crash with Fabric due to a faulty SpriteComponent

3.0.5

Fix a bug with RecipeInjector, preventing overriding recipes

Resolve issues with shadow fields within mixins not remapping by removing them

Fix issue with mixin refmap being missing for common side mixins leading to crashing

Changes:

• Change modid to alloy-forgery to be consistent with other WispForest mods

Fixes:

• Fix issues with data loader dependencies not being set leading to issues with forge tiers not being bound
• Fix for issues with forge definitions not loading leading to issues like crashing and such

Alloy Forgery 3.0.0

Warning: This is a big and complex update which could break existing mod compat and datapacks.

This update changes the format used to load custom Alloy Forges with the plan being to allow for the entire mod being configurable with data and resourcepacks. Furthermore, this version brings Alloy Forgery up to 1.21.10 including support for the NeoForge Mod platform. Documentation for the new data format will be available on https://docs.wispforest.io/alloy-forgery/home in the upcoming days.

Changes

• You can now disable input slots inside the Alloy Forge, similar to the Crafter
• Alloy Forge screen now supports dark mode
  • This is configurable in the Alloy Forgery config, accessible from the ingame mod menu, running /owo-config alloy-forgery in-game, or the config folder.
• Reworked the Alloy Forge data format, splitting it up to make it more configurable.

Technical Changes

• Forge definitions are mostly unchanged.
  • Declared in the {datapack_namespace_here}/alloy_forge/controller folder Only require materials and additional_materials like before
• Defining Forge Tiers is now required.
  • Forge Tiers define properties/stats for your different Alloy Forges.
  • Properties available:
    • tier, which is required
    • speed_multiplier, affects smelting speed
    • fuel_consumption_multiplier, affects fuel usage
    • fuel_capacity, affects fuel capacity
    • parent_tier, allows for inheriting properties from a different tier
• Forge definitions require Tier Bindings in {datapack_namespace_here}/alloy_forge/tier_binding.
• These data values bind the stats between a specified controller to a specific tier.
• Alloy Forge screen layout is now code-driven, which means the layout is no longer resourcepackable
• Split up the Alloy Forge screen textures, making them much more configurable

Alloy Forgery 3.0.0

Warning: This is a big and complex update which could break existing mod compat and datapacks.

This update changes the format used to load custom Alloy Forges with the plan being to allow for the entire mod being configurable with data and resourcepacks. Furthermore, this version brings Alloy Forgery up to 1.21.4 including support for the NeoForge Mod platform. Documentation for the new data format will be available on https://docs.wispforest.io/alloy-forgery/home in the upcoming days.

Changes

• You can now disable input slots inside the Alloy Forge, similar to the Crafter
• Alloy Forge screen now supports dark mode
  • This is configurable in the Alloy Forgery config, accessible from the ingame mod menu, running /owo-config alloy-forgery in-game, or the config folder.
• Reworked the Alloy Forge data format, splitting it up to make it more configurable.

Technical Changes

• Forge definitions are mostly unchanged.
  • Declared in the {datapack_namespace_here}/alloy_forge/controller folder Only require materials and additional_materials like before
• Defining Forge Tiers is now required.
  • Forge Tiers define properties/stats for your different Alloy Forges.
  • Properties available:
    • tier, which is required
    • speed_multiplier, affects smelting speed
    • fuel_consumption_multiplier, affects fuel usage
    • fuel_capacity, affects fuel capacity
    • parent_tier, allows for inheriting properties from a different tier
• Forge definitions require Tier Bindings in {datapack_namespace_here}/alloy_forge/tier_binding.
• These data values bind the stats between a specified controller to a specific tier.
• Alloy Forge screen layout is now code-driven, which means the layout is no longer resourcepackable
• Split up the Alloy Forge screen textures, making them much more configurable