Branching Version Control with Records

[ಠ_ಠ]

When working on competitive multiplayer designs, sometimes a lot of trial and error is required. If you don't duplicate your results and keep accurate records, it can be easy to lose some of the little changes that make big waves in your design's performance.

Instead of storing designs as a flat list, it'd be helpful to have them stored in a tree structure, where the root node of the tree is the name of the design series, and each leaf is a version in that design. Along with each design, store the competitive win/loss/draw and best times for each version, which bubble up to the root node. This would help eliminate a large amount of the manual drudgery that's required to keep up with refining a competitive design that's very similar in many respects, but may have slight variations here and there. For example, I drop and add fuel tanks to account for the length of different courses, or tweak the center of mass based on which side of the course I want my drone to favor.

An example might look like this:

|- Angry Crab. Best Times: Pisces 27.163 (V5) Cygnus 1.26 (V9) 
|   |- v1 (Angry Crab) Best Times: .............................
|   |- v2 (Steroid Crab) Best Times: .............
|- Kingfisher. Best Times: ............
|  |- v2 .............
|  |- v4 .............