With being able to assign a prefix key for a module in settings, it would work if you are importing someone else's module into your library, however when if you make your own module and try to add it to an existing project you still have a clash of task keys. Because both module and the current project you are working on will have the same prefix keys for task1..task2 etc. This problem would be the same if you imported two different modules from the same user.
The work around is to change the prefix everytime you create a new module, however if you didn't realise this beforehand like me, you will have to manually alter them just like before. So the prefix needs a little more tweaking,
maybe when you go to export a module a prompt will ask you for a unique prefix every time or the first ten characters of the module name is used instead, that way you will never have the same prefix unless you named the exported file name too similar to another. Or username with a random five digit key or something added onto it like dazakiwi57f8ptask1, dazakiwi57f8ptask2 etc
I tried renaming the prefix and re-exporting the module, but its still using the previous prefix i had it at. *sigh*
Also some variables in restrictions in the module are getting randomly swapped with other variable from the main game, this happens with action/execute task too. One of the tasks from the module disappeared completely.