Donate to Codex
Putting the 'role' back in role-playing games since 2002.
Donate to Codex
Good Old Games

DoubleBear ZRPG Design Update

Click here and disable ads!

DoubleBear ZRPG Design Update

Development Info - posted by VentilatorOfDoom on Wed 14 July 2010, 19:02:24

Tags: Brian Mitsoda; DoubleBear Productions

Since his return from his honeymoon Brian resumed his weekly design updates. Here are 3 parts all concerning Experience.

Before I get into an explanation of how the experience system works – and most likely, that’s going to make more sense in the next post – let’s go over some of the unique challenges of creating an experience/quest system in a game that centers on the collapse of society and a game system where absolutely any ally or enemy can die. Well, I think I just touched on the biggest one, so let’s run with that.

So in a lot of traditional RPGs, even in terrible, monster-caked dystopias you’ve got cities full of people and a lot of those people give quests. Some of them can die, but most of them can’t or at least not until you get the dialogue choice to kill them. So, anyhow, the streets are filled with people who you can’t attack for fear of guards who are there to save you from yourselves - your progress will break, you see, if you kill all those people with exclamation points or names over their heads. A good number of these quests are going to be fetch quests sending you out of the Town of Incredibly Safe People into the wilderness where you will risk life and limb and werewolf rape for someone’s missing hat. Find the hat, kill the endless spawns of the monster that’s slightly higher than your level, return the hat, get some kind of reward and selfless/dick response – we’re all familiar with this setup, yeah?
Brian's obviously not up to date. Experience is out, Followers is where it's at.

There are 20 comments on DoubleBear ZRPG Design Update

Site hosted by Sorcerer's Place Link us!
Codex definition, a book manuscript.
eXTReMe Tracker
rpgcodex.net RSS Feed
This page was created in 0.053442001342773 seconds