In order to best serve the community, a file naming convention must be put into place to better assist end users with locating and obtaining the files they'd be interested in.

For Macro files, the file name convention to be submitted should follow the following rules:

• Prefixed with "Macro-"
• Contains an extremely brief description of what the code is
• Submitters GitHub handle
• Version # of submission (Optional since this is a.. well.. version control type site)
• File extension ends in XML

Example filenames would be as follows:

Macro-F13toF24-Pontiac76-v1.xml

Macro-Better Scrolling-Pontiac76.xml

As mentioned in Observed Effects, the actual content of file submissions are rewritten each time LGS is opened, so, actual XML file formatting and standards are out the window, meaning that the standard XML header isn't required, and "middle of the pack" submissions are valid submissions, so long your opening tag comes along with a closing tag.

For example;

  <macro guid="{5DAFA657-7E0B-4D37-9F7A-FA252ED551E6}" color="4278215935" original="true" name="Left Click" hidden="false">
    <mousefunction xmlns="http://www.logitech.com/Cassandra/2010.1/Macros/MouseFunction">
      <do task="leftclick"/>
    </mousefunction>
  </macro>

Is just as valid as:

  <macro guid="{5DAFA657-7E0B-4D37-9F7A-FA252ED551E6}" color="4278215935" original="true" name="Left Click" hidden="false"><mousefunction xmlns="http://www.logitech.com/Cassandra/2010.1/Macros/MouseFunction"><do task="leftclick"/></mousefunction></macro>`

Just note that the opening tag is macro and there is a closing tag of /macro.