I’d appreciate it, as it’s the same every time for me! Even deleting the whole tex directory and re-compiling still appends the colon onto it.
I wouldn’t think anything related to files would be involved. Scrivener, and for that matter MultiMarkdown itself, don’t really care much about what .tex files you have when typing in your own include codes or using the custom settings. It probably has more to do with some variation of syntax—are hyphens used, spaces in key names, etc.
Emma: maybe if you could export your format to a file and attach it I could have a look at it and see if I get the colons as well? Right-click on the format in the compile overview screen to do so (and feel free to PM me if you don’t want it shared publicly).
napaxton: I think your settings look good, but I’d double-check the placement of the “Insert Project Metadata Here” row. Perhaps in MMD6 it doesn’t matter, but it used to be important that stuff like “Title” and “Author” fall between what is now the ‘latex leader’ and before what is now the ‘latex begin’ keys.