VCS Friendly File Formats This tweet got me thinking, what Verison Control System (VCS) friendly file formats exist, or can you think of? Here's a pasting of an example of the format Juan from Godot came up with: [gd_scene load_steps=3 format=2] [ext_resource path="res://icon1.png" type="Texture" id=1] [ext_resource path="res://icon3.png" type="Texture" id=3] [node name="Node2D" type="Node2D"] [node name="icon1" type="Sprite" parent="."] position = Vector2( 138, 127 ) texture = ExtResource( 1 ) [node name="icon3" type="Sprite" parent="."] position = Vector2( 782, 109) texture = ExtResource( 1 ) Json isn't the most VCS friendly. YAML has the potential to be, albeit much more complicated, and slower to parse. The above format reminds me of an ini format with grouping, where the group defines the asset, and the key value pairs (kvp) are the asset parameters. It's a nice touch. And ini's are really easy and fast to parse. I like it. Can this be improved? What else can you think of? https://ift.tt/eA8V8J

This tweet got me thinking, what Verison Control System (VCS) friendly file formats exist, or can you think of? Here's a pasting of an example of the format Juan from Godot came up with: [gd_scene load_steps=3 format=2] [ext_resource path="res://icon1.png" type="Texture" id=1] [ext_resource path="res://icon3.png" type="Texture" id=3] [node name="Node2D" type="Node2D"] [node name="icon1" type="Sprite" parent="."] position = Vector2( 138, 127 ) texture = ExtResource( 1 ) [node name="icon3" type="Sprite" parent="."] position = Vector2( 782, 109) texture = ExtResource( 1 ) Json isn't the most VCS friendly. YAML has the potential to be, albeit much more complicated, and slower to parse. The above format reminds me of an ini format with grouping, where the group defines the asset, and the key value pairs (kvp) are the asset parameters. It's a nice touch. And ini's are really easy and fast to parse. I like it. Can this be improved? What else can you think of?

from GameDev.net http://bit.ly/2GiudXn