Understanding Stardew Valley Expanded Item IDs
If you're working with the Stardew Valley Expanded mod and need to reference items by their internal identifiers rather than their display names, you need a solid reference. The mod significantly extends the base game's item pool, and tracking down the right ID for scripts, save editors, or quest configurations can be a headache if you don't have the right resources. The Stardew Valley Expanded Item IDs are string-based identifiers used internally by the game engine. Each crop, tool, craftable, and NPC reward has a unique ID that looks nothing like its shop name. For example, a regular parsnip is "384" in the base game, but Expanded adds hundreds more items with their own IDs scattered across new regions, events, and craft recipes.
Uncover The Ultimate Collection A Comprehensive Guide To Stardew Valley Expanded Item Ids
There isn't one single official document from the mod authors that lists every item ID in a clean table. The community has assembled references through decompiled game data and GitHub repositories. The most useful starting point is the Stardew Valley Expanded GitHub page, which includes a data folder containing JSON files with item definitions. Those JSON files list the GameItemId field for every entry. I spent an afternoon last year building a personal lookup tool because I was setting up custom events through SMAPI and needed to verify item conditions. The problem is that Expanded items share namespace space with base game items. An item like "Ancient Fruit Seed" exists in both the base game and the Expanded mod, but they may carry different internal IDs depending on which version you're running. That overlap caused my event script to fail for a full evening before I realized what was happening. The workaround was straightforward once I knew what to look for. I pulled the latest Expanded mod source, opened the content.json file in the Data folder, and cross-referenced the ID with the Stardew Valley decompiled XNB files. Any ID above 50000 tends to be Expanded-exclusive content. The base game reserves most IDs below that threshold. It's not a hard rule, but it's a reliable heuristic.
Where to Find the Item ID Lists
The primary source is the Stardew Valley Expanded repository on GitHub. Within that repo, navigate to the Data directory and look for folders named Items, Crafts, or Seeds depending on what category you need. Each file is a JSON array where objects contain fields like "GameItemId", "Name", "DisplayName", and "Category". The "GameItemId" field is what you pass into the game code. Another option is the Stardew Valley modding community Discord. People frequently share spreadsheets and updated ID lists there. These are community-maintained and tend to get updated faster when the mod releases new content. I keep a pinned link to one of those sheets in my notes. If you want a more visual approach, there are item browser tools built for Stardew Valley modders. Tools like the Stardew Valley Item ID Browser or the Content Pannel allow you to search for an item by name and see its ID displayed alongside other metadata. These are useful for quick lookups when you're in the middle of editing a config file.
Get the Full Details
Common Pitfalls When Using Expanded Item IDs
The biggest issue people run into is version mismatch. Stardew Valley Expanded releases updates periodically, and item IDs can shift between versions. An ID that worked with version 1.4 will likely be wrong with version 1.5. Always verify your ID against the exact version of the mod you have installed. Check your mod folder's manifest.json file to confirm the version number. Another problem is the distinction between GameItemId and ItemId. Some references use one term and some use the other. In practice they usually refer to the same numeric identifier, but certain SMAPI hooks and content patches expect one format over the other. If your code compiles but the item doesn't appear where it should, check whether you're passing a string ID or a numeric ID. The game typically expects the numeric form for condition checks. A third edge case involves seasonal and regional items that Expanded adds. Items like the "Desert Rose" or "Mountain Gem" only appear in specific contexts. If you're writing a quest condition that checks for these items, make sure the player has actually visited the required region. I once set up a quest requiring a "Mushroom Log" and spent three hours debugging before I realized the item only spawns in the Ginger Island area during the rainy season. The ID was correct. The contextual requirement was not documented anywhere obvious.
How to Extract IDs From Your Own Game Install
If you want to build your own reference, you can extract the item data directly from your game files. Open your Stardew Valley installation folder and navigate to Content. You'll find files like ContentPatcher patches from the Expanded mod. These patches reference item IDs explicitly. Use a text editor with search to scan for item ID patterns. A more thorough method involves decompiling the game's XNB files using a tool like XeMsDecompiler. This gives you access to the original content files. From there you can cross-reference the Stardew Valley Expanded data files against the decompiled base game files and build a complete mapping. This approach takes about an hour if you're familiar with the process, and it gives you a reference that is accurate for your exact game version.
Best Practices for Managing Item IDs in Mod Projects
Keep a separate lookup file rather than hardcoding IDs into your scripts. A simple CSV or JSON file with columns for ID, name, category, and source mod makes maintenance much easier. When the Expanded mod updates and adds new items, you only need to refresh that lookup file instead of searching through multiple script files. Use constants or enums for the IDs you reference repeatedly. If your project involves multiple mods, prefixing your constants with the mod name prevents collisions. Something like ExpandedAncientFruitSeed instead of just AncientFruitSeed avoids confusion when you're also pulling from base game references. Validate your IDs before deploying. A single wrong item ID in a quest condition can silently fail. The game won't error out. It will just never trigger the expected behavior. I always run a test save with my modified scripts and manually verify that each item reference resolves correctly. It adds maybe twenty minutes to the workflow, but it saves hours of debugging later.
The Stardew Valley Expanded Item IDs reference is essential if you're doing any serious modding work with that expansion. The data is accessible if you know where to look. The main challenges are version accuracy, naming conventions, and the sheer volume of new content. Keep your references current, validate before you deploy, and don't assume an ID stays the same across mod updates.
