JUL-13-2025
Inspired by this tweet, I've decided to try and actually set up a version control system for teambuilding in Pokemon Showdown.
My initial thought was to have a separate web-service that could act as the data store for commits, however, that would require building out things like user auth which I don't have a strong interest in doing right now. Instead, my plan is as follows:
I think this combination is a good middle ground between a keeping things not super technical for an end-user, but provides the flexibility to "backup" your data.
This is very much still a work-in-progress, and I'm unsure if it will ever get to a point where it is ready for users. If you are interested in helping out, please feel free to DM me on Twitter or Discord.
In an effort to make it easy-to-use and not too Git-centric, each change will just be saved as an indexed "version". E.g., changes will increment in the order of "v1", "v2", "v3", etc. I still need to think through how to handle removing a version since there is no easy way to "DROP" a commit. Perhaps the data is still stored, but we have a filter list so it doesn't get shown to the user?