Forum Rules and Guidelines
1) Keep plugins small! Having one plugin that does everything pretty much defeats the purpose of making the whole MQ system modular. If your plugin performs several different functions (I'll use auth as an example here, sorry bro: runs any exe file, and controls winamp... those are two seperate functions, and should be two plugins) split it up.
2) Document. Comment your sourcecode, and provide a basic readme file which explains what the plugin does and what commands it adds. This will help others find problems and fix them if you aren't around to do it when a patch or major MQ change breaks your code.
3) When posting your source code, provide an introduction to the plugin in its leading comments, covering what it does (
mq2irc: does it talk to irc in game, or control MQ via IRC like telnet?) and giving a few examples of it's use. A full listing of commands can be left to the readme file.
4) Any source code here will be considered covered under the GPL, just like MacroQuest2. If you don't want to share your source code you MAY provide a link to your precompiled DLL... just don't expect any help maintaining the code, since the devs here are shy of any code they can't see (we don't like viruses, trojans, key loggers, etc.)
5) Plugin code should avoid using inline assembly or non-distribution functions to do their task; most everything can be done with what is already mapped to eqgame already. This also ensures that when a patch hits, when MQ works, your plugin will work too.
6) The posting or requesting of plugins that serve to break MQ Dev and Sony's rules, or are malicous in nature will not be tolerated.
7) As plugins age, maintainers can change hands, if you have an update for a plugin that hasnt been posted on in some time, check with the author. Multiple threads should be avoided.
we lost it a long time ago when it comes to precompilers 
I get what you mean, especially how most of those precomps have VIP MQ2 stuff, and they want nothing to do with this site.
