: I am deeply offended. Blowing goat is one of my favorite pastimes.
: Ok, I've gone past my spam quota, so I will post a useful opinion. It is very valid to criticize someone over email, but why call Jveenhoff a "gay ba$tard". That will merely annoy him, and despite what Redink seems to claim to believe, he doesn't want more contraversy (I've tested... I think). The ideal email to send is an clean, honest critique stating that the mod wasted plenty of download time, and you are very disappointed. I don't know why people seem to prefer angering people to shaming them.
: Yes, I recognize the validity of your complaint Redink, and to some degree I concur, but there is no reason not to complain in public, unless the complainer believes his argument to be too weak to stand up to public scrutiny.
: Also, why would anyone call you "Gay", Jveenhoff? That's sort of like wearing a sign saying, "I am either a 13-year-old or a strange homophobe."
My response was only to Tal's post, and not Jveenhof's issue whatsoever. Usually, when somebody negatively critiques D-Mods in any manner, somebody else will say "I bet you couldn't make one" or something similar. My response was to that general attitude, and not to the stupid 133t kiddies who e-mail Jveenhof. They obviously have problems.
Well, Tal was half right actually, IMHO. There is a hugh difference between criticizing and spamming. Yea, I've played d-mods on here that blew, but have never e-mailed the author to tell him. If I were to e-mail the author, I would criticize the d-mod, I wouldn't criticize the author or make suggestions on his sexual preferance. On the other hand, don't make your e-mail address public knowledge unless you are prepared to deal with @ssholes. So, like I said, Tal was half right; just ignore the jerks who criticize YOU, and heed only the comments referring to your d-mod that will actually help you become a better author. In addition, if your going to e-mail the author to say his work sucks, at least explain why so the author can improve on the issues you have. Criticize author=bad. Criticize d-mod=good. What JVeenhof recieved was spamming. Correct me if I'm wrong, but isn't that what made Silencer leave the community and leave behind an unfinished project that looked to be a ground-breaking d-mod? And you know what? The same wuss that e-mails to simply say it blows, will never e-mail to congradulate. Saying it sucks requires an explaination.
: Well, Tal was half right actually, IMHO. There is a hugh difference between criticizing and spamming. Yea, I've played d-mods on here that blew, but have never e-mailed the author to tell him. If I were to e-mail the author, I would criticize the d-mod, I wouldn't criticize the author or make suggestions on his sexual preferance. On the other hand, don't make your e-mail address public knowledge unless you are prepared to deal with @ssholes. So, like I said, Tal was half right; just ignore the jerks who criticize YOU, and heed only the comments referring to your d-mod that will actually help you become a better author. In addition, if your going to e-mail the author to say his work sucks, at least explain why so the author can improve on the issues you have. Criticize author=bad. Criticize d-mod=good. What JVeenhof recieved was spamming. Correct me if I'm wrong, but isn't that what made Silencer leave the community and leave behind an unfinished project that looked to be a ground-breaking d-mod? And you know what? The same wuss that e-mails to simply say it blows, will never e-mail to congradulate. Saying it sucks requires an explaination.
I thought I made it clear that my rant was on the general aspect of people telling other people they shouldn't criticize unless they've tried it themselves... sigh. I suppose it wasn't in direct response to either Tal's or Jveenhof's posts, looking back on them. I decided to write a rant, and its my site, and I thought I might as well try it :)
: I thought I made it clear that my rant was on the general aspect of people telling other people they shouldn't criticize unless they've tried it themselves... sigh. I suppose it wasn't in direct response to either Tal's or Jveenhof's posts, looking back on them. I decided to write a rant, and its my site, and I thought I might as well try it :)
And my post wasn't so much directed at you as it was just my opinion on the whole thing. I like ranting myself. Need a weekly rant column? I understood what you said, agreed in principle, but had to add my preverbial 2 cents. One can not simply ignore constructive criticizm and expect to improve. That was your point. Expanding on that I wanted to point out that "you suck" doesn't help Jveenhof or me or you fix anything. I could go on, but than I'd be ranting, and its not my site :)
: Well, Tal was half right actually, IMHO. There is a hugh difference between criticizing and spamming. Yea, I've played d-mods on here that blew, but have never e-mailed the author to tell him. If I were to e-mail the author, I would criticize the d-mod, I wouldn't criticize the author or make suggestions on his sexual preferance. On the other hand, don't make your e-mail address public knowledge unless you are prepared to deal with @ssholes. So, like I said, Tal was half right; just ignore the jerks who criticize YOU, and heed only the comments referring to your d-mod that will actually help you become a better author. In addition, if your going to e-mail the author to say his work sucks, at least explain why so the author can improve on the issues you have. Criticize author=bad. Criticize d-mod=good. What JVeenhof recieved was spamming. Correct me if I'm wrong, but isn't that what made Silencer leave the community and leave behind an unfinished project that looked to be a ground-breaking d-mod? And you know what? The same wuss that e-mails to simply say it blows, will never e-mail to congradulate. Saying it sucks requires an explaination.
Brilliant summation. Does anyone disagree...?