The files follow no written specification, and so everyone makes their own assumptions... we should write a specification so we can decide what changes can be reliably made. This would also allow external tools (which I do know some use) to generate compatible files, and those are the reason I would like to make the specification broader than what's currently generated by RGBLINK.

To quote @mid-kid:

Honestly I just wanna know dumb shit such as: Will the format allways be '2:4` or should you search the colon and space, can there be more whitespace after the address before the label starts (can the space also be a tab?), are end-of-line comments a thing and how to handle whitespace there.