Quote from: Kitsune on September 28, 2014, 10:27:23 PM

Quote from: Comet on September 28, 2014, 10:20:28 PM

because it's online only POS game.

i know it's online only, but I still don't get why they take their servers down so often its bull shit.

because its their first online only game, and they dont know how to do shit. also they are trying to fix random error codes for Destiny. im assuming that they use the same servers for the game and their website.

That would be...incredibly stupid, to be honest. There's a link between them, to be sure (like with the other Bungie games), but having the site on the same servers the game is running on is a security risk as well as a dunce move if they want to keep the public updated when the game crashes (as it frequently does).

Quote from: Cheat on September 28, 2014, 10:42:40 PM

Quote from: Comet on September 28, 2014, 10:37:29 PM

Quote from: Kitsune on September 28, 2014, 10:27:23 PM

Quote from: Comet on September 28, 2014, 10:20:28 PM

because it's online only POS game.

i know it's online only, but I still don't get why they take their servers down so often its bull shit.

because its their first online only game, and they dont know how to do shit. also they are trying to fix random error codes for Destiny. im assuming that they use the same servers for the game and their website.

That would be...incredibly stupid, to be honest. There's a link between them, to be sure (like with the other Bungie games), but having the site on the same servers the game is running on is a security risk as well as a dunce move if they want to keep the public updated when the game crashes (as it frequently does).

eh. every time ive tried to check b.net when Destiny crashes (for me) b.net is usually fucked as well. coincidence then i guess.
could be their lolMobile that decides to break and not the desktop...

It could be that the site can't handle the Destiny database not serving it the data it requests and crashes instead of halfway loading. That wouldn't surprise me at all, considering the malfunctions the site's been giving off for months now.

But it could also be that someone decided to host the site on the Destiny servers, yeah. That'd be dumb.

Not the case. Probably because the user profiles, and forum profiles are tied, an issue with the game-related website database, which pulls the data from the game, could have caused a chain of issues. Probably someone deployed new code, or changes applied in the environment of the database. Hardware failure or change is also possible.

Bungie.net pulls the data from PSN, and Xbox Live respectively into small packages, which are then put into Bungie.net's servers and finally rendered as data for the website. That's the same structure they have been using since the days of Halo 2.

But it could also be that someone decided to host the site on the Destiny servers, yeah. That'd be dumb.

The new model probably was made just with Destiny in mind and to improve the connection between platforms and services hosted on Bungie.net (both public and non-public ones) The nameplate system on Halo: Reach was pretty straightforward compared to the whole infrastructure Bungie.net has today.

Too bad that I don't foresee them releasing any kind of document anymore.

Well, yeah; that's what I was hoping it was. Errors with collecting data from a game for use on a site are understandable.

It's not the exact same model that they've used before, though. You're able to poke and prod and move items and weapons around through the app (and probably the site too). It's a bit more complex than the nameplate system they had going for Reach, I'd wager, since you can also edit those weapons in-game.