I think that won't really affect anything except for when you're trying to revert back to a previous version of that custom module you're working. As long as you have that same kind of 'module_id' you should be fine.
Hey, thanks for the answer! I am not sure that piece of code is for versioning. I tried the following:
Use the snippet in a template
change the local module (adding 1 field)
snippet updates
the page that uses the template with the module still has the old snippet
checking that page --> the new field shows up
putting the new snippet in the template --> all content for that module is lost, default values are shown
putting old snippet again --> content shows again
What this tells me is to never update the snippet on the page, because all module content will be lost. However, I would like to understand what exactly that piece of code
I realise this is an older question, but my understanding of the module_### is that it's an index into a database row, so, if you have two of the same module with the same id on a page/email/etc, then you'll get the same content in both.
I know that when I add two of the same module onto a html page, I need to make sure the ids are different.
This is just my current mental model, but I hope it helps you as well.