> Well, let me start off by saying, nice try on the snippet. At least > you tried. Generally when you release a snippet to the public, you > want to make it so you can just plug the stuff in and go. Well that > doesn't exactly work with your snippet.
Have you actually read the docs that go with most snippets? I know the ones I've seen actually expect you to know what your code looks like and how to modify it. There's tons of stuff wrong > with it, i just took out what i put in and wrote my own. It was > faster that way. Next time you decide to release a snippet, clean it > up so it can go in without having to do recoding on it. No, next time you release a snippet release it EXACTLY like you want. Not only do you NOT have to give out code you wrote, but you don't have to follow any "Specific" Guidelines. > Don't just > pull it straight out of your codebase which probably has stuff that > some muds don't. Most muds SHOULD have things that make them different. Cookie Cutter muds are a dime a dozen. I have made so many changes to the code I've been working on for 2 years now that snippets won't even fit without MAJOR reworking. I thank the original poster for taking the time to post here with a snippet. And heres what a snippet is: PART of the code. Not all of it.. no guarantees it will work, nothing, nada, just a section. > Sorry if i sound mean, just letting you know. > I enjoy reading other peoples code. It gives me ideas, and I sometimes learn new tricks. So don't worry what people say. There is no "Standard" for releasing a snippet. Noone says you have to use it, and no offense, but I haven't seen any of your code floating around lately. So let's not step on others for trying to help out. Sorry if I sound mean, just letting you know. Jef
