[Carnage]

I had the idea of adding a ref directory to one of my mods which contained some technical information. Its something i'd like to expand on doing and add it to all my mods, however documents even as simple as the ones I provided there take time to produce; time which could be spent adding new features or fixing bugs.

Making this a requirement is not likely to happen. We want our members to share as much as possible and putting up artificial limitations would work against that objective.

I know that the OP had problems when it came to removing one of my mods; this was my fault for not testing the installation/uninstallation code properly. (Ironically, the code itself was covered by unit tests; but they had not been extended to the install/uninstall code :s) This is something i've learnt from and have now setup a dedicated development board specially for testing install/uninstallation of mods.

Whereas I agree that making a requirement is a bad idea, how about a 'good practice' guide?

Another thing that kinda bugs me is the variation in the way different authors lay out their mod threads. When vborg moves to vb4; I assume there will be a custom coded content type for mods - might I suggest that this contains fields for useful things like installation instructions, uninstallation instructions, feature list, description, change log etc. Maybe even something to elaborate on files that are included and database changes that the mod makes.