Guidelines for Literature

How to Submit a Book:

The short version is to go to the Asset Browser and post your book.

Inside the spoiler is the long version detailing what all those subfields in the Asset Browser are for, and which ones need entries for the browser to automatically flag your book for review in our system.


Formatting Guidelines:

1) One book per asset. One asset per book. Books that are a part of a series should have links to each other in the Body field for easier reviewing.

2) There is no maximum length as far the game engine is concerned, but most ingame books are no more than 15,000 characters. Longer books should be broken up into volumes (and hence different assets).

3) No italics, bold, or underlined text, for the game engine doesn’t support these.

4) Red colored text is accepted by the game engine, but should be rare and only used in special circumstances. AKA, don’t use this in place of italics or other formatting. Ask yourself, why is the author using red ink?

5) Consider that a couple lines in a Word document or a forum page will turn into a sizeable paragraph ingame. The eye is lazy and paragraphs that are too long tend to fatigue the reader. Write like you are writing for a web page rather than a physical book, with shorter paragraphs and more white space.

6) Text can be centered, but typically this is only for use in scrolls and pamphlets, or for formatting title pages.

7) If your book is to have an image associated with it, please include it inline in the text in the Text window, as well as in an attachment to the asset. The file format should be a .tga with transparency for any “white space”.

General Tips and Tricks to Writing for TR:

When talking about the place books have in Tamriel Rebuilt, we are really asking what they do in an Elder Scrolls game, because in the end that is what we are making. Books have a role to play because they carry an enormous potential to build a world beyond the several gigabytes that constitute the game. They can establish things that are far beyond the budget, time limit or skill of any development team (including us) and can often plainly do things that are impossible to describe otherwise. They are necessary, because to some extent they save the fictional world we can portray through our game engine from becoming a facade, transitory and ultimately meaningless.

Keeping the above in mind, it becomes obvious that books, far more than a source of information, are tools. Any worthwhile book seeks to do something; it takes the world as we imagine it and builds upon it, deconstructs it, reconstructs it, changes it, nuances it, … Books always have hidden agendas.

1) Take your time to decide a single subject. Something or anything that interests you.

2) The people around here are more than willing to assist; your work will be reviewed, discussed and suggestions will be made. If something needs to be fixed, fix it. If you don't know how, ask for further assistance. It is most important to be persistent and dedicated. No one is perfect, don't give up.

3) Follow the steps it takes to write a good story. Once you have your subject, outline what you wish to discuss. Use your outline to expound upon your theme.

4) Do the research! You are writing the book, song, scroll, journal or quest. YOU should know the lore that substantiates and supports it, better than most. You should be able to defend your position.

5) PROOF READ your work. If someone else is not available to read your work prior to submission, try the following techniques:

I) Read the piece out loud.
II) Read the piece backwards.
III) Check your grammar.
IV) Check your story's tense. One tense please.
V) Check your spelling. Spell check is helpful, but don't rely on it. (i.e. there, their and they're or to, too and two)

Great Sources of TES lore:
The FAQ at the official forum: (link is external)

The Imperial Library: (link is external)