-
Notifications
You must be signed in to change notification settings - Fork 8
Migration (for future use)
The Silly Sim Tracker extension includes tools to help you convert older data formats to the newer, improved structure.
Early versions of the extension used a different JSON structure that mixed world data with character data. The newer format separates these concerns, making it cleaner and more maintainable.
{
"current_date": "2025-08-10",
"current_time": "14:30",
"Alice": {
"hp": 75,
"mp": 50
}
}{
"worldData": {
"current_date": "2025-08-10",
"current_time": "14:30"
},
"characters": [
{
"name": "Alice",
"hp": 75,
"mp": 50
}
]
}Location: Silly Sim Tracker settings Action: Click "Migrate to New Format" Scope: Converts all messages in the current chat Safety: Includes confirmation dialog
Steps:
- Open SST settings
- Find "JSON Format Migration" section
- Click "Migrate to New Format"
- Confirm when prompted
- Wait for conversion to complete
- Check notifications for results
Command: /sst-convert
Scope: Converts all messages in the current chat
Safety: Includes confirmation dialog
Steps:
- Type
/sst-convertin any chat input - Confirm when prompted
- Wait for conversion to complete
- Check notifications for results
The migration tools are intelligent and won't re-process data that's already in the new format.
All your existing data is preserved during migration - nothing is lost.
- World data fields (
current_date,current_time) move toworldDataobject - Character data moves from object keys to
charactersarray - Character names become explicit
namefields
Before:
{
"current_date": "2025-08-10",
"current_time": "14:30",
"Alice": {
"hp": 75,
"mp": 50
},
"Bob": {
"hp": 100,
"mp": 30
}
}
After:
{
"worldData": {
"current_date": "2025-08-10",
"current_time": "14:30"
},
"characters": [
{
"name": "Alice",
"hp": 75,
"mp": 50
},
{
"name": "Bob",
"hp": 100,
"mp": 30
}
]
}
- When starting a new campaign (fresh start)
- When experiencing data organization issues
- When wanting to use newer extension features
- When collaborating with others (new format is clearer)
- Legacy format still works perfectly
- No functionality is lost with old format
- Migrate only when you want the benefits
Both migration methods include confirmation dialogs to prevent accidental conversion.
Migration updates messages in place but doesn't delete the originals - you can always see the change.
Already migrated data is automatically skipped, preventing double-conversion.
If any message fails to migrate, the process continues with others and reports the error.
- Check that JSON data is valid
- Ensure messages contain sim codeblocks
- Look for error messages in notifications
- Check browser console for details
If some messages migrate but others don't:
- Check the failed messages for JSON errors
- Verify they contain sim data
- Try migrating individual messages by editing them
There's no direct undo, but you can:
- Use version control if you have it
- Manually edit messages back to old format
- Keep backups of important chats
- Backup important chats if you're concerned
- Check that your JSON data is valid
- Ensure you understand the new format
- Verify that cards still display correctly
- Test that new data generation works
- Update any system prompts that reference format
- Coordinate with collaborators about format choice
- Consider migrating when starting shared campaigns
- Document which format you're using
The migration tools make it easy to upgrade to the cleaner, more maintainable data structure while preserving all your existing tracking data.