0.3.3
Compatibility
Required content
Changes
📦 Stardew Valley Food – Version 0.3.3 Changelog
🛠 Fixes & Improvements
- ✅ Improved overall performance and stability when loading large recipe sets.
- ✅ Fixed multiple broken or unbalanced recipes, especially those referencing missing ingredients.
- ✅ Fixed several translation/localization issues in food item names and villager trades.
- ✅ Cleaned up recipe tags and item conditions to reduce mod conflicts.
🌽 Croptopia Compatibility
- ✅ Full optional support for Croptopia ingredients in applicable recipes.
- ✅ Automatically detects if Croptopia is installed and adjusts crafting behavior accordingly.
- ⚠️ No external mods are required — all integrations are optional.
📦 Stardew Valley Food – Version 0.3.2 Changelog
🆕 Major Changes
-
Replaced all functionality and integration with Farmer’s Delight.
→ No longer required or supported. -
Fully migrated to use Pam’s HarvestCraft 2 (Core + Crops + Food Extended) for all ingredients and food systems.
-
Re-introduced villager trading system:
→ Stardew Valley food items can now be exchanged with villagers based on their profession and trading level. -
Recipes have been completely redesigned for better balance and realism:
→ Simplified placeholder recipes from version 0.2.5 have been removed.
→ Ingredients now reflect logical combinations from Stardew Valley and Pam’s HarvestCraft 2.
✉️ Grandpa’s Mail System Fabic (Forge Is Coming)
Grandpa can still send you random food items via the in-game mail system.
Mail frequency can be configured via data packs.
🧱 Technical & Backend
- Removed all remaining Farmer’s Delight recipe references from datapack files.
- Updated recipe JSON structure to support Pam’s item IDs, including cookingoilitem and saltitem.
- Internal item registry cleanup and food effect consistency updates.
- Confirmed compatibility with Minecraft 1.16.5–1.20.1 Forge & Fabric.
⚠️ Important Notes
- The mod ID has changed from stardewvalley_food to sdvf — this will break any world save that references the old ID.
→ Back up your world before updating.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:8N1pJGur:WBGlgnDn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8N1pJGur:WBGlgnDn"
}

