Quote & Reply- Dump. (Destiny)

by INSANEdrive, ಥ_ಥ | f(ಠ‿↼)z | ᕕ( ᐛ )ᕗ| ¯\_(ツ)_/¯, Tuesday, October 20, 2015, 23:09 (3417 days ago) @ dogcow

Destiny came out on September 9, 2014. Most of the development team was proud of the game, a source told me, and many were shocked to see harsh reviews; although most at Bungie had anticipated that players wouldn’t love the story, the team thought Destiny made up for that deficiency in many other ways. One source says they had internal surveys pegging the Metacritic score at around a 90 average; it turned out to be a 76. (Bungie then missed out on a major bonus, that source confirmed.)

You can give the illusion of randomness, but you want to weight it towards the player… The only point you have to deliver on is that when people leave your game—because they will—when they leave your game, they need to be happy.’”

For more information, read Chapter 13 of my Mega Post.

They also hoped to add a totally new feature called multiple fireteam activities, which a source described like this: “Imagine like you and I are in a fireteam, and we’re fighting down this one path that converges with two other paths and you get three fireteams all fighting together against a boss, or against some sort of mobs.”

This is exactly the kind of thing I was imagining when Destiny was being pitched. Just walking by some random on patrol isn't cool. It's not bad, per say, its just not really anything. At all. Oh look... All these horses and nowhere to gallop.

It’s not uncommon for a game’s scope to reduce during development, but Bungie had a unique problem. People who worked on this project say that one of Bungie’s fundamental issues over the past few years has been the game’s engine, which the studio built from scratch alongside Destiny. Four sources pointed to Destiny’s technology—the tools they use to design levels, render graphics, and create content—as an inhibiting factor in the game’s development.

“Let’s say a designer wants to go in and move a resource node two inches,” said one person familiar with the engine. “They go into the editor. First they have to load their map overnight. It takes eight hours to input their map overnight. They get [into the office] in the morning. If their importer didn’t fail, they open the map. It takes about 20 minutes to open. They go in and they move that node two feet. And then they’d do a 15-20 minute compile. Just to do a half-second change.”

“There was a bet that was, ‘Hey if we did microtransactions, I bet you we could generate enough revenue to make up for the loss of DLCs,’” said a source. “Instead of it going Destiny, DLC1, DLC2, Comet, DLC1, DLC2, they’re actually just gonna go [big] release and then incremental release. So it’ll just be Destiny, Comet, Destiny, Comet every year. It’s basically just switching the game to an annual model.”

This is about, as in actually,... time. It's about allocation. If this pipeline is truly as clogged as reported, (which might I add is absolutely jaw dropping for my green noggin which thought waiting for light maps to bake was a pain!) then it's no freaking wonder we got what we got. It doesn't make up for putting down a ton of cash & trust for a original flawed product, but it helps. Still not buying Taken King. It's not $200 good yet. Might not ever be. Might just have to wait till "Destiny 2".

...no one can reach consensus on how to fix the game in the time that’s allotted, you get a lot of sort of paralysis.

Something something communication is hard or something. Looking outside in with an excerpt, which makes this comment the "best comment", I find my self wondering - isn't that sort of thing the point of a lead? Or am I reading about a "Too many Cooks in the Kitchen" scenario?

All things considered, it’s remarkable that Bungie was able to ship anything in late 2014, let alone build a foundation as solid as vanilla Destiny.

Well... let's be real here, Bungie has experience for desperate situations.