I completely agree. However, you cannot deny never looking at someone else's code. Which means you've used someone else's work.
I don't give that much back out for the same reason. a) I want a unique mud b) I don't want every 13 year old with a compiler claiming credit for my work. The easiest solution? Release your code that you feel is release worthy but not "plug" in-able. Two of the largest code pieces I've released (Saving objects across a copyover and area auditing) are good examples. They reduce the amount of work you would need to do to implement them, but if you don't have a somewhat working brain, you're back to looking for spell snippets. > -----Original Message----- > From: Matt Foltz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 04, 2002 6:27 AM > To: [email protected] > Subject: RE: weapon affects > > > --- Jason Gauthier <[EMAIL PROTECTED]> wrote: > > "It's too bad I don't release any of my code to the > > public." > > > > Give and you shall receive. > > > > Give and what happens is every little snippetized mud > out there uses my code that I actually worked on, and > acts all high and mighty about adding it in. I don't > use snippets, I write all my code from scratch. Sure > I might take ideas from snippets if I'm stuck, but I > don't use them. I've seen snippets posted on here, > and the following day seen them in a mud with the > implementors going "Look what I coded guys, isn't this > cool?" I don't want to see my code used like that. > Plus I like to have a unique mud. I don't want others > like mine out there. > -Matt Foltz > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
