Slings and Arrows A Guide to rec.arts.int-fiction for Aspiring IF System Creators I assume that you are either creating, or thinking of creating, a new Interactive Fiction system or language. If so, welcome! Writing your own IF system is a rewarding experience. You might be considering posting to rec.arts.int-fiction to ask questions or to get advice on your new IF system. Unfortunately, people who post about this subject tend to receive negative feedback. This guide is intended to help you deal with the negativity you will receive. 10 reasons why people post negative things ------------------------------------------ a. Some people like being negative. b. Some people don't like others to succeed. c. Some people don't like change. d. Some people have a stake in the existing IF systems and don't want to see a successful new system. e. Some people think that a new system will negatively affect the IF community. f. Some people have built an expertise around the existing IF systems and fear a loss in status if a new system were to gain popularity. g. Some people fear having to learn a new system. h. Some people think that writing IF is a more worthy task than creating IF systems. i. Some people think that rec.arts.int-fiction is for discussions of writing IF only. j. Some people don't like newcomers to the community. Negative things that people will say to discourage you ------------------------------------------------------ "The features you want in your new system are already available in existing systems". (Fallacy: The only reason to create a new system is to implement features not found in existing systems. Fallacy: The only worthwhile new system is one which is fundamentally different than existing systems. Fallacy: The only reason to create a new system is because the existing systems are deficient in some way.) "Games produced with new systems are crappier." (Fallacy: The only reason to create a new system is to create a better system than those already existing. Fallacy: Crappy games hurt the IF community. Fallacy: Artists create art only so others can enjoy it.) "We're not being negative or trying to discourage you-- we're just being realistic." (Beware: Some people disguise their negativity as helpful or neutral advice.) "The consensus is that you shouldn't do it." (Fallacy: The experts are always right. Fallacy: If everone believes something, then it is so.) "Everyone who has said that they were going to create a new IF system has failed." (Fallacy: It is better to not try than it is to fail. Fallacy: It is better to succeed at something else than it is to fail at something you do want to do.) "We are experts in this field, so you should listen to us." (Fallacy: The opinions given by experts are always accurate and neutral.) "Your system will not be popular." (Fallacy: The only reason to create a new system is to have it replace other systems or to have many people use it.) "Instead of making your own system, you should help work on the existing systems." (Fallacy: Ignoring existing systems and creating a new one is a selfish act.) "You should spend time writing IF instead." (Fallacy: Writing IF is a more worthwhile activity than creating IF systems. Fallacy: rec.arts.int-fiction is for IF writers, not IF system developers.) "There is no commercial market for IF." (Fallacy: The only reason to create a new system is to make money. Fallacy: There is no commercial market for IF.) "You should look at the other systems before creating your own." (Fallacy: It is necessary to know existing art before creating new art. Fallacy: Only people knowledgeable about IF systems should create an IF system. Fallacy: Only established members of the IF community should create new systems. Beware: This is used as a barrier-to-entry tactic.) "People will refuse to use a system that {uses language X, uses license Y}". (Fallacy: The only reason to create a new system is to have it replace other systems and to have many people use it.) "Why re-create the wheel?" (Fallacy: Re-creating the wheel is a waste of time with no benefits.) "Everyone is happy with the existing systems." (Fallacy: Everyone is happy with the existing systems.) Advice ------ - You should always feel free to post your opinions about game system design theory. However, if you post before you have published your system (or at least a rudimentary version of it), expect the slings and arrows to start. However, to re-iterate, discussion of IF system design theory is a valid topic of discussion even if you never intend to create a new system. - If you post about a not-yet-developed system, try not to mention what features you expect it will have. People tend to view these posts as being boastful and/or hype. - If you have opinions about existing game systems, in comparison to your own system, try not to mention them. Conversely, try not to mention features of your new system that might be misconstrued as criticisms of the features of existing systems. - You probably have several reasons for wanting to create a new system. However, try not to reveal these reasons except for the ones that will be difficult for other people to criticize. Examples of these safe reaons are: Because I want to. Because it's fun. Because I want to learn language X. Because I want a system licensed under license Y. - The amount of discouragement you receive may be great. Try to avoid getting sucked into overly-long discussions with these negative people to the point that it takes time away from your IF system development. Try to ignore the slings and arrows directed to you. - Realize that it is a minority of people who will respond to your posts. Unfortunately, it is likely that most of these responses will be negative. Please keep in mind that the majority of people actually do want you to succeed.