ВЕРСИИ (63)

# 3.1.1 Fixed an issue related to data components. Should be playable, but please report any issues you find.

# 3.1.0 Initial port to 26.1.2. REI and EMI compat is disabled for this version, as they need more fixes.

# 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.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.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.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.6 Fix a crash with Fabric due to a faulty SpriteComponent

# 3.0.5 Fix a bug with RecipeInjector, preventing overriding recipes

# 3.0.5 Fix a bug with RecipeInjector, preventing overriding recipes

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

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

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

## 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

## 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

## 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.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

# 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

# 2.4.1 ## Changes - Fix a crash related to missing classes

The update contains a fix for the latest fabric API version combined with the ability to add Item Components to the output for recipes.

# 2.3.1 ## Changes - Fix loot tables not applying due to wrong data directory (#145) - Update Portuguese translations (#141, thanks Landrozaum)

# 2.3.0 ## Breaking change - The recipe blacklist tag is now under `tags/recipe` instead of `tags/recipes` ## Changes - Fix recipes not being loaded due to being in the wrong directory (thanks Superkat!)

# 2.2.2 - Remove old datagen - Fix recipes using old Fabric API conditions (#142)

# 2.2.1 - Fixed a potential crash regarding loading tags - Now loaded with the DynamicRegistry, which should be more stable

# 2.2.0 Initial port to 1.21

Small update includes some fixes and changes to mechanics for blasting adaptation: ### Features - Adjust blasting adaptation recipes default input amount from 1 to 2 with higher tier output only. - Furthermore there are now options to adjust various aspects of the adaption layers with such documented on the [wiki](https://docs.wispforest.io/alloy-forgery/recipe-adaptation/) - Update recipe syntax to be more uniform between input and outputs which is documented on the new wiki! - **[Major Change]** Add glass recipe for the forge > You can access the config via Mod Menu, in-game with the /owo-config command, or by finding the config file in your instances config folder ### Fixes: - Fix issues with recipes deserialization due to problems with ingredient equality - Add recipe id to error with recipes using tagged output if occurs

# 2.1.3 - Fixed an issue with a bad compat recipe (adamantite_ingot_from_ores)

Update Alloy Forgery to Minecraft 1.20.4

# 2.1.2 - Added an icon when the recipe used in the Forge is higher than the required minimum tier

Contains Backport of Fixes from 2.1.0 - 2.1.1 for 1.20+, check the change log for such for more info.

Fix issues with relation to mods calling craft method to get Recipe output leading to unintended ingredient removal.

This update brings some fixes for Ticking related issues and also adds support for Adapting Blasting Furnace Recipes to work within the forge ### Features - Adapt Blast Furnace Recipes Dynamically to Alloy Forge Recipes (API Information planned for the future) - Reduce the tier of the Deepslate Forge Controller (2 -> 1) - This change was made to make raw ore doubling harder to get. You now need to seek out Prismarine or Blackstone (The Nether) to make a better Forge Controller. ### Fixes: - Fix tick related lag when idle or crafting - Logic and caching was added for recipe checking, which greatly improves performance - Fix mishandling of Fuel Remainders, where stacks would be entirely replaced with the remainders - Various fixes for compatibility recipes, mainly related to common tags

## 2.0.22 - Fix owo-sentinel not working - Port and re-activate EMI plugin - Make REI text more visible in dark mode

- Ported to 1.20 (Blodgharm) - Added localization for Brazillian Portugese (#105, thanks FITFC!)

# 2.0.20 - Fixed a crash related to KubeJS (#102, #103, #98) - Added Spanish localization (es_es, thanks Boxadactle!) - Added Italian localization (it_it, thanks CapoFantasma97!) - Added Taiwanese localization (zh_it, thanks EvanHsie0405!) - Fixed some issues related to raw block recipes and datagen Note: This release marks the end of maintenance for 1.19.2.

# 2.0.20 - Fixed a crash related to KubeJS (#102, #103, #98) - Added Spanish localization (es_es, thanks Boxadactle!) - Added Italian localization (it_it, thanks CapoFantasma97!) - Added Taiwanese localization (zh_it, thanks EvanHsie0405!) - Fixed some issues related to raw block recipes and datagen Note: This release marks the end of maintenance for 1.19.2.

This is a straightforward port to 1.19.4

# 2.0.19 - Added compatability for viewing Alloy Forge recipes via EMI (thanks fzzyhmstrs!) - Fixed some broken ore tags, making some recipes unable to be crafted - Fixed the Prismarine Brick Forge Controller not dropping its block when broken - Fixed an issue where stacked fuel items (I.E. Stackable Buckets) would override the stack when used directly on the Forge Controllers

# 2.0.19 - Added compatability for viewing Alloy Forge recipes via EMI (thanks fzzyhmstrs!) - Fixed some broken ore tags, making some recipes unable to be crafted - Fixed the Prismarine Brick Forge Controller not dropping its block when broken - Fixed an issue where stacked fuel items (I.E. Stackable Buckets) would override the stack when used directly on the Forge Controllers

Port to 1.19.3, no functional differences

## Additions Simplified Chinese translations, by ErrorPower2001 Korean translations, by gyular ## Fixes This build now properly supports new Fabric Transfer API. This resolves a crash that would happen with older versions on 1.19.2 when trying to insert lava into a Forge Controller via fluid pipes or hoppers

This version is a straight backport of 2.0.16 for 1.18.2. Refer to the changelogs from 2.0.14 -> 2.0.16 for the changes contained in this version

## Changes - More fuzzy recipe matching - recipes which accept the same item multiple times no longer need to be spread out across the Forge Inventory (Blodhgarm, #48) - Default recipes for most modded minerals and alloys (Blodhgarm, #63) - Recipe format changes -> inputs can now also use the `count` property (Blodhgarm, #61) - REI integration was updated to reflect the recipe system changes and support recipe autofill in the Forge Inventory

## Changes - The automatically generated forge controller recipes can now be overriden by datapacks ## Fixes - Custom Forges now accept liquid fuel ([#86 on Mythic Metals](https://github.com/Noaaan/MythicMetals/issues/86)) - The lava in the fuel buffer now renders correctly when the block atlas is not 1024x1024

## Changes - Port to 1.19 ## Fixes - Fuel consumption in high-tier forges is now more accurate and works correctly according to the intended formula. This also means they run a bit slower, as an error in the speed calculation was resposible for the fuel issues

Fix REI texture and occasional crash on launch

Fixed forge cache crash

Added support for inserting lava via fluid pipes, added the Prismarine Forge Controller

First port to 1.18.2

Use new owo particle api, remove id remapping data from mixin

Re-add lithium compat, make hoppers stop inserting when the forge is running

Port to 1.18 proper, use new mining levels api

First 1.18 port

Fixed lithium making hoppers unable to extract from forges

Actually make forge controllers mineable

Update to work with latest owo

Made comparator output always be at least one while processing

Fix chunks not saving because I forgot the register the block entity