16 Things to Include in Every RPG Journal
- Updated: 23rd May, 2007
Here we are at the conclusion of my post series on computer RPG journal design. I will admit, I am a usability freak. The one thing that will wind me up faster than anything on earth is software design that isn’t based around the user. This website makes my skin crawl.
Please, cRPG designers, think about the journal early in your game design. Unless your game has all the complexity of Doom 3, a journal can make or break your game. Here is your cut-out-and-keep checklist of things to consider:
General Points:
- Hired genre-appropriate writer?
- Logged all known quests?
- Category: Trailheads
- Category: Quests in progress
- Category: Quests completed
- Category: Quests on the backburner
- Category: Quests’ area
Quest-specific points:
- Logged all details given in dialogue?
- Logged information source?
- Logged information source location? (if known)
- Logged promised reward? (if known)
- Logged what player has already done?
- Logged where player should go next? (if known)
- Logged known map locations?
- Logged visited vs. unexplored areas?
- Logged acquisition of unique quest object?
- Logged loss/discard and location of unique quest object?
Click on each item to get the detailed explanations. Do you think I’ve missed anything? Do you disagree? Let me know.
[HRODC website found through Experts Exchange]
One Comment