Top-Tier Villain Motivations

Fantasy Guide to Political Structures

A Horse! A Horse! My X for a Horse!

Let's be honest, fantasy authors love their kingdoms and empires. You can throw a rock in a bookshop or a library in the fantasy section and you will 99.99999% hit a fantasy book that will be set in or mention either of those structures. But what are they really? What's the difference between them all? Are there any more examples of structures that would suit your WIP better? Are you using the right terms? Let's have a closer look.

Duchy

A Duchy is a small territory ruled by a Duke/Duchess. While Duchies can be found in kingdoms, some duchies were sovereign states in their own right. Duchies are usually small by land mass but some duchies such as Burgundy were extremely powerful and influential. Independent Duchies were usually apart of a kingdom but grew so powerful that they eventually broke away to become a sovereign state in their own right. An example would be modern day Luxembourg, historic Milan and Burgundy.

Principality

A principality is territory ruled by a Prince/Princess. A principality is typically smaller than a kingdom and in some instances, can be apart of a larger kingdom or be a sovereign state. Principalities have a history of having broken away from a larger kingdom or eventually becoming apart of a kingdom. A principality within a kingdom is ruled by a Prince/Princess, usually an heir of the monarch and can be used to train them up to assume the throne in the future. Examples include Monaco, Liechtenstein and Andorra.

Kingdom

A sovereign state/country that is ruled by ruling King or a Queen. A kingdom is much larger and more powerful than a principality. Kingdoms can be feudal, meaning they are ruled in a strict hierarchy or an autocracy where the monarch rules alone with minimal input from the government or constitutional where the monarch is more of a figurehead and the government has a good chunk of control. Examples include England, Thailand and modern day Spain.

Commonwealth

A Commonwealth isn't a popular choice in fantasy but it is an interesting structure. A Commonwealth in its most basic form is a collection of states that are linked by either a shared culture or history. A Commonwealth can be a politically power or an economic power, with every state allowed to participate as much as they like. Not one state leads the others, it is all one group of equals. A Commonwealth can be a good idea for a group of nations that are more powerful together with them keeping their own independence.

Federation

A Federation is a political structure that is made up of united states or countries that are under a single government but each state is still independent and rules itself. Each state can have different laws, different cultures and economies but they all answer to the single government. Examples include the United States of America.

Republic

A Republic is a territory that is ruled by leaders and heads of state that have been elected on merit and by choice of the people. Republics are not just countries but can also be much smaller areas such as cities. Republics are democratic in nature, with the people having a say in who leads them in accordance to a constitution. There are many kinds of Republic: presidential, parliamentary, federal, theocratic, unitary. Examples of Republics include the Republic of Ireland and the city of Florence.

Protectorate

A Protectorate is a country/region/territory that is independent but relies on a larger, more powerful state for protection either in a military or diplomatic sense. A Protectorate was often used by Empires in order to maintain control over an area without annexing it. There are many reasons a larger state and the protectorate would agree to this, mainly the protectorate is much smaller meaning it is far more vulnerable to attack or it has very little power when compared to other states. A Protectorate allows the territory some power to rule itself but the larger state may feel the need or desire to interfere in the dealings of the territory. Examples of protectorates include the client kingdoms of the Roman Empire like Egypt before its annexation and Puerto Rico.

Empire

An Empire is a collection of nations that are united under one sovereign head of state or government. An Empire is formed by one nation steadily taking control of other nations, either through straight invasion and colonization or acquiring them through marriage and other less violent ways. An Empire is powerful mainly because it can drum up more resources, more influence and more military power. An Empire might impose the traditions, beliefs and culture of its principal nation - the nation that started it all - onto its colonies for better control and feeling of uniformity. Empires never last, that is something to always remember. Empires will eventually fragment due to the vast size and sometimes revolt among the conquered states. Examples of empires include the Roman Empire, the Byzantine Empire, the Ottoman Empire.

How to write a good AO3 summary so people will actually want to read your fic

Summarize your story.  Don’t be vague or coy.  No hiding the pickle.  There are so many fics and so little time.  More people will skip over your fic if they don’t know what it’s about than will be turned away because it’s not about something they’re interested in.  Tell the reader what happens!

A snippet is not a summary.  People like to use lines of dialogue or excerpts to grab the reader’s attention.  Very rarely do these snippets provide enough information to summarize the story.  If you want to showcase a clever line of dialogue or the tone of the fic, include a line, but after the actual summary.

Make sure the summary is clear and written well.  If it is messy and full of errors, people will assume the same of the fic.

Focus the summary on the characters and what happens to them or how they feel about each other.  Fanfic readers come to see the characters they love do things they didn’t get to see in the source material.  Let the audience know what the characters are doing and feeling.

Don’t forget to tell the reader what makes your story unique.  Lots of fics are successful almost entirely because they follow a much-loved trope, so talk about that too (definitely in the tags at the very least), but when staring at the hundredth fic about one character pining for the other and deciding whether its worth it to read another, the reader is going to look for extra details that spike their interest.

Hint at the tone of your fic in the summary.  If it’s light, give the summary a chatty tone.  If it’s angst, make it hurt.  If it’s plot-driven, go matter-of-fact.  If it’s a character piece, meditative and dreamy.  

Don’t contradict yourself.  Don’t write a summary and then immediately undercut your description by trying to soften the blow.  Just get the summary right from the get-go rather than mischaracterizing the work and then backpedaling with “trust me, not as angsty as it sounds” or “this is actually total fluff.  And if it really is as angsty/dark as it sounds, let it be angsty with confidence.  There are readers out there who will love your fic for what it is and will be turned off by a waffling summary.

Don’t reference yourself.   The fic is the star of the summary, not your ego.  Don’t explain why you wrote it (unless you’re listing a short prompt).  And definitely don’t make any self-referential jokes, give your opinions on the characters, use the summary for foreshadowing, or compare it to other fics.  

The summary is not the place for self deprecating humor, false modesty or insecurity.  Don’t say it’s your first fic.  Don’t apologize.  Don’t say that English isn’t your first language.  If you must, do this in the author’s notes, but better to not do it at all.  The worst you might get if you don’t warn for these things is the suggestion you get a beta or some concrit.  Most people will just skip your work entirely.

One paragraph only!  Readers are skimming a list of summaries.  They probably won’t stop to read all of yours.  See points 10-13 for more on this.

Don’t use the summary for warnings.  Warnings are for tags and author’s notes.  Make sure you warn for all possible triggers, but these are reasons for people not to read the fic, not reasons to read it (if they are reasons to read it, then phrase them as part of the summary not as warnings).  Warnings can easily overwhelm a summary to the point that it becomes about why the reader should probably just not read it rather than an enticement to read.

Remember the reader can also see your tags and that tags help the reader find the right fics.  Put any tropes that might be selling points in the tags and leave the summary for information that is unique to the fic/gets at the backbone of the fic.

Remember you have the author’s notes.  This is great place to tell us why you wrote the story, give a long prompt word-for-word, thank your betas, give more detailed warnings, reference inspirations, and gab on about yourself.

The summary is not the place for worldbuilding.  Don’t explain the intricacies of your AU in the summary.  If it’s a very strange world, you get one sentence max to describe that world.  Spend the rest of the summary on the substantive character arcs.  If the reader can’t understand your AU from the text of the fic itself, you’re doing it wrong.

It doesn’t hurt to sell yourself.  Phrase things in a pithy, clever way, let the readers know you’re going to deliver on their favorite trope, and keep the tone confident.  This is the inside flap of your hardback.  This is the summary on amazon.  Think about what would make you buy.  

Do not write “I suck at writing summaries” in your summary.  If you can’t trust yourself to write a summary, why should the reader trust you to write a good story?

someone: hey I noticed this thing you did in your writing!

me, kicking my feet up flirtatiously: oh??? do you want to hear my thoughts on why I did that? do you want a play-by-play of the language choices in every related sentence? do you want an exhaustive breakdown of The Themes???

devotion that corrupts is my favorite btw there's nothing wrong with it ever & it should be encouraged

I think there's something that needs to be said about encouraging readers to leave feedback.

For me it's not about "tell me my writing is amazing and stroke my ego"

It's more about "please engage with me so that I can experience your joy secondhand and foster a connection with you"

I understand that not everyone wants this in their reading experience, some people are shy and a million other reasons why maybe someone wouldn't want to engage and that's perfectly fine!

But what I'm trying to steer away from is being a passive content creator with passive consumers. What I want to steer toward is fostering a community that is essential to fandom. I want to see your reactions because it makes me feel like I'm a part of something.

On encouraging reblogs —

I understand that not everyone is comfortable reblogging, especially explicit content. This is ok!

But just consider that the only reason you were able to enjoy a fic or fanart is because someone else shared it, and by not sharing it yourself you are potentially robbing someone else of the opportunity to enjoy it as much as you did.

As OPs our reach only goes so far and this website relies on reblogs in order for anything to truly get seen by a wider audience.

So that's really it! That's why I encourage these two things at the end of every story I post. Not because I'm trying to be demanding and "make people feel bad" if they don't do it.

I know most other social media sites encourage mindless content consumption and that's just the way of the world nowadays, but I am from a time when community was at the heart of fandom and I just don't want to lose that.

Years and years ago, I read a book on cryptography that I picked up because it looked interesting--and it was!

But there was a side anecdote in there that stayed with me for more general purposes.

The author was describing a cryptography class that they had taken back in college where the professor was demonstrating the process of "reversibility", which is a principle that most codes depend on. Specifically, it should be easy to encode, and very hard to decode without the key--it is hard to reverse the process.

So he had an example code that he used for his class to demonstrate this, a variation on the Book Code, where the encoded text would be a series of phone numbers.

The key to the code was that phone books are sorted alphabetically, so you could encode the text easily--picking phone numbers from the appropriate alphabetical sections to use ahead of time would be easy. But since phone books were sorted alphabetically, not numerically, it would be nearly impossible to reverse the code without exhaustively searching the phone book for each string of numbers and seeing what name it was tied to.

Nowadays, defeating this would be child's play, given computerized databases, but back in the 80s and 90s, this would have been a good code... at least, until one of the students raised their hand and asked, "Why not just call the phone numbers and ask who lives there?"

The professor apparently was dumbfounded.

He had never considered that question. As a result, his cipher, which seemed to be nearly unbreakable to him, had such an obvious flaw, because he was the sort of person who could never coldcall someone to ask that sort of thing!

In the crypto book, the author went on to use this story as an example of why security systems should not be tested by the designer (because of course the security system is ready for everything they thought of, by definition), but for me, as a writer, it stuck with me for a different reason.

It's worth talking out your story plot with other people just to see if there's a "Why not just call the phone numbers?" obvious plot hole that you've missed, because of your singular perspective as a person. Especially if you're writing the sort of plot where you have people trying to outsmart each other.

Ah, yes, I see you’ve taken notice of the fine knight I keep dangling in a big gilded cage above my evil throne. Quite the pretty little ornament the would be savior makes, wouldn’t you agree~?

What? No, it IS a big cage. That’s- it’s the standard size for a knight’s cage I’m pretty sure. NO I’m not going to invest in 500 square feet of dungeon, it’s ONE knight! I’m pretty sure knights live in hovels in the wild anyways which is basically the same- Look, the cage is quite literally gilded. He loves the cage! He loves obediently preening in the cage! Yeah well, when you capture your own knight you can keep it in whatever size castle you want to, but this one’s mine. Especially since you’re so obviously jealous of me and my cute and awesome knight anyway.

Repeat after me:

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

The first draft just needs to exist

The second draft needs to be functional

The third draft needs to be effective

Remember, the second and third can't happen if you don't have something to work with. Your first draft will always be shit compared to your third, but at least it exists. The worst first draft is an unfinished one. The best first draft is a just completed one.

You read books/stories not in their first draft form-- only in their finished form (third, fourth, sometimes fifteenth draft). So stop comparing your first draft with a final one.

So, just write--you can make it better later. Perfectionism is the greatest weight a creator can carry.

Saw someone refer to their hyperfixation as their muse and it’s the best thing ever. No this is not due to a chemical imbalance in my brain I have been touched by the gods with divine inspiration

you ever accidentally create a recurring theme in your writing. you start putting together an outline for something you’ve never written before and get partway through planning, rearrange the pieces, and go “GODDAMMIT THIS IS ABOUT GRIEF AGAIN”? because let me tell you,