Black Angel
Arcane
Seven Dwarfs, Aliens, Alpha Protocol, Stormlands. Remember when people were excited that Obsidian would finally be able to make a traditional RPG instead of console popamole lcd trash? The truth is that they're a garbage company run by garbage people, the rot starts at the top and permeates down.Dungeon Siege 3 would like a word with you.
DS3's narrative was sabotaged by Feargus Urquhart.Dungeon Siege 3 was an egregious example of bland garbage (and showed how an entire company can phone it in when it suits them... even good writers like Ziets and Gonzalez).
Roguey
I usually consider myself well-versed in industry gossip (especially pertaining to CRPG companies), but I've never heard of Feargus sabotaging D3 in any way. Not saying you're wrong, but do you have something to back it up?George Ziets said:Kevin Saunders said:I've got one for you George: when I departed DS III in June 2009, the creative foundation you were laying was awesome. I expected another story masterpiece. But the final game (10/2011) didn't excite most critics with its story. What the heck happened? =)
Good question, Kevin. The DS3 story went through so many rewrites that I don’t remember exactly where it was when you left the company, but I’m sure it was early in the process – probably right after I finished the Ehb sourcebook.
My early drafts of the story were truer to my usual narrative tendencies. They were more personal - focused on the player – and they depicted a “grayer” version of the Legion. One of the storylines – possibly the one you remember – also included a lot more supernatural elements.
However, it was decided (above my pay grade) that we should keep the story focused on a threat that affected the nation or the world. Also, there was a desire to ensure that the Legion was clearly Good. I think the underlying impulse was to avoid a lot of narrative complexity, which makes sense in a franchise like Dungeon Siege.
So at that point, I started a long cycle of story revisions. Normally, the iteration process is where your story gets progressively stronger. But in this case, I remember feeling that we’d ended up with a weaker, more watered-down story than some of the earlier versions.
https://rpgcodex.net/forums/index.p...eciation-station.101693/page-190#post-5548080
The only time I recall him getting heavily involved in story at all was Dungeon Siege 3.
https://rpgcodex.net/forums/index.p...archies-and-more.121588/page-125#post-5599622
(Feargus' story iterations ranged from a wide variety of crap ideas, where you had to dig deep and wide to find the good in them - his craptastic story skills also caused a lot of problems on Dungeon Siege 3).
https://rpgcodex.net/forums/index.p...archies-and-more.121588/page-138#post-5600643
After DS3, I did get asked to take on a Project Director role (for a potential sequel) not by Feargus - but because of Feargus.
The reason I was asked, however, was because of how Feargus was treating the team – for all the control he tried in DS3, it had upped in DS4, and the team came to me and asked if I would come on to be a buffer between them and Feargus, since they were finding a hard time getting approvals and getting work done. It ended up being a lesson that made me very hesitant to report to Feargus (even though I did in the last year at Obsidian).
Feargus, it turned out, sometimes had a tactic where if he disapproves of someone or is angry at someone, he micromanages them to an excruciating degree, calls out everything he objects to (not something that’s necessarily wrong, just something he objects to), and makes it very difficult to move forward on anything. I had seen hints of this indirectly, but never experienced it – it sometimes was employed as a way to get someone to resign without actually firing them. It mostly seemed like an extended form of punishment with no positive goal except to punish the person for some perceived failing.
So I agreed to take on the role, because the ones asking me genuinely seemed to need help, and I also foolishly thought that surely this couldn’t be the case. The project also seemed like it might be fun.
Within 2 weeks of the role, I realized the team was absolutely right, and the problem wasn’t limited to what was brought up to me – it was worse.
While being a buffer helped (slightly), the issue started coming up that Feargus would do sudden pivots on elements he had approved and the team had spent a lot of time on. He would also forget he approved them and would assume he hadn't when he saw a decision he (now) didn't like had been made.
I’m not sure I even classify these events as lies when they occurred because it involves memory and the old classic managerial “gut instinct,” but what I discovered is that elements I would fight for and the team wanted (starting with the story, which was being savaged just like DS3) would be given approval by Feargus when I asked, then he would forget he gave approval, and within a few days of me relaying the good news to the team, he would backpedal and say, “Why this story and not mine? I never approved that.” When confronted on the fact he had approved the change, it would then become, “well, it’s not how I feel today.”
When this occurred, I felt as if I had lied to the team and let them down – and the situation had been out of my control despite my best intentions.
Realizing I couldn’t manage if I didn’t get reliable approvals (it undermined anything I said or did), I stepped down.
Truly, hell hath no fury like a