 |
|
Stop uploading Steve"the mad russian" overtons' scenarios - Printable Version +- Forums (https://www.theblitz.club/message_boards) +-- Forum: The Firing Line (https://www.theblitz.club/message_boards/forumdisplay.php?fid=1) +--- Forum: Combat Mission (https://www.theblitz.club/message_boards/forumdisplay.php?fid=10) +--- Thread: Stop uploading Steve"the mad russian" overtons' scenarios (/showthread.php?tid=38791) Pages:
1
2
|
RE:��Stop uploading Steve"the mad russian" overtons' scenarios - Fredrocker - 01-24-2007 Hey Randy, As we say down here (or is it over here from MD) in Kentucky.... Post All the Scenarios and let God sort'em out...  Do whats right for the club... thats all one can ask... That is all... RE:��Stop uploading Steve"the mad russian" overtons' scenarios - Colonel Talvela - 01-24-2007 RE: Stop uploading Steve"the mad russian" overtons' scenarios - Copper - 01-24-2007 IMO this sets a very unwelcome precedent within the world of CM gaming as a whole. Dont get me wrong I understand Mad Russians views regarding incomplete scenarios that are going through a playtest and may not be 'ready' but pulling the ones that have passed through testing as well stinks to me. I mean where do we go from here.... what if every designer out there mails the Blitz and says we dont want our scenarios that have been released to the wider community available at the Blitz. I personally feel Mad Russian has made a bad decision and should have asked for only the ones that are 'incomplete' in his eyes to be pulled. What are the legal ramifications of us hosting this stuff which is widely available on the internet? I go with Fred on this one... host em all and let God sort them out. RE: Stop uploading Steve"the mad russian" overtons' scenarios - RedDevil - 01-25-2007 I have edited my original post and ask if the members wish me to remove the replies that I have posted that are of disruptive nature or allow the thread to remain as is. RE: Stop uploading Steve"the mad russian" overtons' scenarios - British Tommy - 01-26-2007 Lock the thread and move on. |
){kind=link}