Which mod files does this skill analyze?

This skill primarily targets FavoritesModel.cs, ModConfig.cs, and any implementation involving SMAPI's modData or Data API for JSON persistence.

Is it specific to the Stardew Outfit Manager mod?

While pre-configured for the Stardew Outfit Manager schema, the validation logic and migration patterns are applicable to most Stardew Valley C# mods using SMAPI.

How does it handle save file paths?

It validates that save paths include essential components like the player name, save folder name, and unique multiplayer ID to ensure stability in all game modes.

Can it help with breaking changes?

Yes, it identifies potential breaking changes in data structures and provides template code for migrating older data versions to the current schema.

Does it support the Generic Mod Config Menu (GMCM)?

Yes, it includes validation checks to ensure that any new properties added to ModConfig are correctly registered with the GMCM API.

Stardew Valley Data Validation

Name: Stardew Valley Data Validation
Author: liminalwarmth

byliminalwarmth

•

Game Development

Validates data structures and prevents regressions in save formats and configurations for Stardew Valley mods.

About

The sdv-data-validation skill is designed for modders working on Stardew Valley, specifically focusing on the Stardew Outfit Manager project. It provides automated checks for data integrity across C# models, SMAPI modData conventions, and JSON save files. By enforcing strict schema validation and migration patterns, it helps developers avoid save corruption, ensure multiplayer compatibility, and manage breaking changes when updating mod configurations or wardrobe data structures.

Key Features

Schema validation for FavoritesData and FavoriteOutfit models
Enforcement of SMAPI modData key naming conventions
Verification of multiplayer-safe save file path patterns
2 GitHub stars
Migration logic generation for breaking data structure changes
Automated checks for ModConfig defaults and GMCM registration

Use Cases

Auditing legacy modData keys for migration to standardized prefixes
Adding new configurable options to the Generic Mod Config Menu (GMCM)
Updating save data models while maintaining backward compatibility

About

Key Features

Schema validation for FavoritesData and FavoriteOutfit models
Enforcement of SMAPI modData key naming conventions
Verification of multiplayer-safe save file path patterns
2 GitHub stars
Migration logic generation for breaking data structure changes
Automated checks for ModConfig defaults and GMCM registration

Use Cases

Auditing legacy modData keys for migration to standardized prefixes
Adding new configurable options to the Generic Mod Config Menu (GMCM)
Updating save data models while maintaining backward compatibility