Should I make a conlang? A Flowchart

[torylltales]

I made a flowchart!

If you can't see it, I'll try to write it out.

 

Should I make a conlang?

1. Why should I?

A. Because I want to -> Go to 2.

B. To flesh out my story / worldbuilding -> Go to 2.

C. Because Tolkien did it -> NO.


2. How much time do I want to spend on it?

D. I shall make it my life's work -> YES

E: As much as I need for my story -> YES, BUT ACTUALLY NO

F: Not too much -> NO.


My basic point: conlangs are an art form in their own right, but if you're not willing to put in the time and effort then it's probably better not to.

There is no story that suffered for the lack of a conlang, but many stories that were made worse by the addition of an unnecessary conlang.

There is no story that cannot be told without a conlang.


Make a conlang if you want to make a conlang. Don't make a conlang if you think it will make your story cool, or because you think you need to  in order to be a serious fantasy writer.
 

 

Disagree? FIGHT ME.




 

Comments

(frozen comment)

[epistler]

Well, I have to admit that is definitely one of the more impressive examples of completely missing the point I've seen in a while.

(frozen comment)

[(Anonymous)]

Then could you explain another way, please? Because the comparison you're implying is pretty clear to me.

(frozen comment)

[epistler]

Okay, now you're just being obtuse. Fine - here it is again without the metaphors since you seem so determined to misinterpret them: If you wouldn't pay someone to do a job for you if they were incompetent at it, then you shouldn't be expected to pay money for a book written by an incompetent who didn't do their job properly either. In either case someone is offering a service they expect money for, and thereby implying that they know what they're doing.