Good Old Games
Donate to Codex
Putting the 'role' back in role-playing games since 2002.
Odds are, something you like very much sucks. Why? Because this is the RPG Codex
News Content Gallery People Games Companies  
Forums About Donate RSS Contact Us!  

Pete Hines interview at eToychest

Visit our sponsors! (or click here and disable ads)

Pete Hines interview at eToychest

Interview - posted by Vault Dweller on Sat 25 February 2006, 16:05:55

Tags: Bethesda Softworks; Elder Scrolls IV: Oblivion

eToychest has posted an interview with Pete "Y'know" Hines. Here is a couple of more interesting questions.

We've seen in the demo movies that the citizens of Tamriel have schedules and being in the right place at the right time can open up new quests for the player. My question is, are there any mutually exclusive quests because of temporal differences, or will the player eventually be able to "see" everything given enough persistence?

We tend not to lock off content from the player like that and, given enough time, you can pretty much see and do just about everything in the game. That’s not to say it won’t take quite a bit of time and effort to do so. It’s a very, very big game.
Which means that that "in the right place at the right time" concept is meaningless in Oblivion.

How will Oblivion's story unfold? In Morrowind, your dialog choices usually amounted to "Yes", "No", and "Yes, but it'll cost you". Will Oblivion's interactions be more robust?

We’ve changed it quite a bit from the way it worked in Morrowind. So it’s much more of a dialog tree system and less one that centers around only picking topics out of a list. How the story unfolds is up to you and many times we give you more than one path through a conversation and it’s up to you to decide how it proceeds.
Would be nice if true.


Spotted at: RPG Dot

There are 8 comments on Pete Hines interview at eToychest

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.0487399101257 seconds