I don't think this game is gory enough, I'm going to make a petition...
You're psychotic if you don't think this is gory enough. None of the Diablo games have been this gory. IT'S AWESOME!
Rollback Post to RevisionRollBack
Blizzard is not responsible for the death and loss of your hardcore characters for any reason including Internet lag, bugs, Acts of God, your little sister, or any other reason whatsoever. Consult the End User License Agreement for more details. Blizzard will not, and does not have the capability to restore any deceased Hardcore characters. Don't even ask. La-la-la-la-la, we can't hear you..,
This scene really does show that D3 isn't as 'cartoony' as everyone making it out to be, ableit I do agree some of the textures/models could be more 'realstic', I don't think there needs to be a major overhaul as some people make out.
Remember, the mini-bosses, or random bosses in D2 looked the same, but simply had different colors to stand out from all the other monsters. I do hope they put randomly placed minibosses in this!
The "Siege breaker Assault beast" "living siege engine of hell" seems to be an enlarged, robotically augmented version of the furry brown beasts that were being fought earlier on in the video.
Question is:: is the beast meant for breaking a siege? or for carrying out a siege on fortifications?
Maybe both?
Maybe what happens in the game is, the player character heroes are about to assault a stronghold of evil, and the siege breaker beast is summoned to "break their siege" on the stronghold
I betcha this beast is the equivalent of theoretical boss in Diablo 2 who guards the entrance to the Monastery in Act 1. (i dont recall there being a boss guarding the monastery entrance)
For me, it's not the fact of the blood splatters being produced, and then disappear that makes a scene gory. To me, the Butcher's room was gory. That had entrails and body parts as part of the background, and made it seem all that much more evil. When you killed critters in Diablo and 2 they had death cries, and also their body stayed on the ground to use or just to look at. What I see in D3 as an example is a lot "cleaner" of a game. Sure, the boss battle has a few gore spots and there are giblets everywhere in the regular fighting, but the giblets and bodies tend to disappear rapidly rather then sticking around and messing up the nice scenery. That's what helped to make the originals far more graphic.
It was so much easier back then to set the mood, with less tools, you didnt have much room to choose.
Ever notice when you read a good book, then you go see the movie how much worse it is? D3 seems like the movie of D1 and D2. Not saying D3 is worse, just .. it looks awesome and all but.. doesnt seem the same.. yet!
You're psychotic if you don't think this is gory enough. None of the Diablo games have been this gory. IT'S AWESOME!
Eh, what? Have you not played D1 or D2? Butcher much? Corpse explosion much? Very literally dead bodies everywhere, both which you or other things have created? Maybe your definition of gory consists of simply what you do to creatures (or what they do to you), but that's such a small portion of gory that it defies logic to just ignore the fact that we could cause corpses to explode into gibby little bits in D2.
Remember, the mini-bosses, or random bosses in D2 looked the same, but simply had different colors to stand out from all the other monsters. I do hope they put randomly placed minibosses in this!
The "Siege breaker Assault beast" "living siege engine of hell" seems to be an enlarged, robotically augmented version of the furry brown beasts that were being fought earlier on in the video.
Question is:: is the beast meant for breaking a siege? or for carrying out a siege on fortifications?
Maybe both?
Maybe what happens in the game is, the player character heroes are about to assault a stronghold of evil, and the siege breaker beast is summoned to "break their siege" on the stronghold
I betcha this beast is the equivalent of theoretical boss in Diablo 2 who guards the entrance to the Monastery in Act 1. (i dont recall there being a boss guarding the monastery entrance)
He is one of those "Random Unique" Boss guys.
Or that other dude was, when they were still in the dungeon.
Actually, both. And the guy is used as a living siege machine against bastions standing against Hell.
Quote from "Credge" »
Eh, what? Have you not played D1 or D2? Butcher much? Corpse explosion much? Very literally dead bodies everywhere, both which you or other things have created? Maybe your definition of gory consists of simply what you do to creatures (or what they do to you), but that's such a small portion of gory that it defies logic to just ignore the fact that we could cause corpses to explode into gibby little bits in D2.
Um, okay, watch the video? The small fries explode in clouds of blood, the time-bomb cultists fall apart into big yummy chunks of flayed flesh and the bosses explode in heaps of bone, marrow and gore!
Did you see the locusts take out the zombies? The blood went down the hillside with the damn skeletons, man! That's awesome!
1) Corpses disappear because no "raise killed enemies" skills or characters with said skills have been introduced so why would they bother in the demo?
2) It'll diminish lag, so stop bitching.
And I'm sure there will be GORY areas, like if we go back into Hell? Just awfully gory!
But this was just a dusty library dungeon and the outside of it, jeeze, calm the fuck down about the color and gore.
Rollback Post to RevisionRollBack
Blizzard is not responsible for the death and loss of your hardcore characters for any reason including Internet lag, bugs, Acts of God, your little sister, or any other reason whatsoever. Consult the End User License Agreement for more details. Blizzard will not, and does not have the capability to restore any deceased Hardcore characters. Don't even ask. La-la-la-la-la, we can't hear you..,
Or that other dude was, when they were still in the dungeon.
Actually, both. And the guy is used as a living siege machine against bastions standing against Hell.
I don't know how random those encounters were, to be honest. It seemed completely triggered, that is to say, once the player walks up to the area that the creature will come out. It has a very TQ feel to it.
Obviously they were already set for the demo, like the chest was, but they've explained through numerous videos that each time you log in there will be unique quests, side-bosses, and the area wont be the same. Yadda-yadda.
Rollback Post to RevisionRollBack
Blizzard is not responsible for the death and loss of your hardcore characters for any reason including Internet lag, bugs, Acts of God, your little sister, or any other reason whatsoever. Consult the End User License Agreement for more details. Blizzard will not, and does not have the capability to restore any deceased Hardcore characters. Don't even ask. La-la-la-la-la, we can't hear you..,
I don't think there is a specific place to fight the siege beast. They're Unique monsters, I think, not exactly bosses. I think they'll be scattered (lightly or maybe not) depending on where you are currently in D3.
Rollback Post to RevisionRollBack
Blizzard is not responsible for the death and loss of your hardcore characters for any reason including Internet lag, bugs, Acts of God, your little sister, or any other reason whatsoever. Consult the End User License Agreement for more details. Blizzard will not, and does not have the capability to restore any deceased Hardcore characters. Don't even ask. La-la-la-la-la, we can't hear you..,
Um, okay, watch the video? The small fries explode in clouds of blood, the time-bomb cultists fall apart into big yummy chunks of flayed flesh and the bosses explode in heaps of bone, marrow and gore!
Did you see the locusts take out the zombies? The blood went down the hillside with the damn skeletons, man! That's awesome!
1) Corpses disappear because no "raise killed enemies" skills or characters with said skills have been introduced so why would they bother in the demo?
2) It'll diminish lag, so stop bitching.
And I'm sure there will be GORY areas, like if we go back into Hell? Just awfully gory!
But this was just a dusty library dungeon and the outside of it, jeeze, calm the fuck down about the color and gore.
:rolleyes:
It's obvious you didn't know what I was talking about by piles of corpses, probably because you've never played Diablo 2, and if you have, never up to Act 4. I never mentioned the corpses the enemies left behind, but that's a good point you bring up. They shouldn't be disappearing. Lag is a poor reason for it, especially since the game is clearly not going to be computer heavy.
Clouds of blood is pretty... bleh. Considering the destructible environments, we should be chopping off limbs and the like as well. "BUT OH IT WILL CAUSE LAG!" Read above. Cultists barely did much of anything besides have a particle effect. No remains means that the dungeon I just cleared thousands of monsters in will be just as pretty and brand-new-looking as when I entered it.
The locusts on the zombies, again, was pretty tame. Oh boy, a green mask over our enemies that, when they reach 0 health, the skeleton appears. They could very easily make it much more gruesome, but they won't. Why? Because they can't do gore, and won't.
But that still isn't even what I was talking about. Not even in the slightest.
Piles of corpses. The enemies came from the same cathedral that the butcher, diablo, mephisto, and all the other demons came out of. There is no reason why there shouldn't be 2 or 3 bodies in the scenery in 20 minutes. You should be seeing, at the least 20 bodies... at least.
A pile of burning books would be nice as well. Although it isn't gory, it would make it seem less like we're playing in a place that no demons have ever ventured.
You can easily make the most simple of programmes lag up your computer, just because the graphics don't require a computer as big as the Siege Breaker Assault Beast doesn't mean they can do anything without causing lag... Diablo II still manages to lag up my computer in some cases, even though I don't own a petium II...
Removing lag is not a 'poor reason'...
Diablo 2 lags everyones computer regardless of how powerful it is in Act 5 when you kill the guy that triggers the plethora of artillery stuffs to fire. It's a poor engine that causes this.
And you can make the most complex of programs be completely lag free on the slowest computers. The argument that corpses cause lag is pretty bunk considering what we are talking about. The majority of enemies we saw in the video did not respond to physics. They simply had a death animation and sat there. Those enemies that did respond to corpses didn't exactly do much of anything after they stopped moving. Even further, they didn't respond to each other as was demonstrated by the Locust Swarm example.
Most enemies had death animations (ghouls, cultists, the dogs for example) and simply sat there. No real reason for those corpses to not stick around, especially since the number of enemies we saw in the demo was rather small, including the beginning bit.
It should be an option like all games with mass killing (MMO's are an example of this).
Number of corpses?
NONE
FEW
SOME
MANY
TONS
ALL
Fairly simple, to be honest.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
You're psychotic if you don't think this is gory enough. None of the Diablo games have been this gory. IT'S AWESOME!
Besdies that would delay out precious D3...
Props for sharing the video.
The "Siege breaker Assault beast" "living siege engine of hell" seems to be an enlarged, robotically augmented version of the furry brown beasts that were being fought earlier on in the video.
Question is:: is the beast meant for breaking a siege? or for carrying out a siege on fortifications?
Maybe both?
Maybe what happens in the game is, the player character heroes are about to assault a stronghold of evil, and the siege breaker beast is summoned to "break their siege" on the stronghold
I betcha this beast is the equivalent of theoretical boss in Diablo 2 who guards the entrance to the Monastery in Act 1. (i dont recall there being a boss guarding the monastery entrance)
http://www.diablofans.com/topic/34229-diablo-iii-beta-impressions/page__view__findpost__p__743763
Ever notice when you read a good book, then you go see the movie how much worse it is? D3 seems like the movie of D1 and D2. Not saying D3 is worse, just .. it looks awesome and all but.. doesnt seem the same.. yet!
Eh, what? Have you not played D1 or D2? Butcher much? Corpse explosion much? Very literally dead bodies everywhere, both which you or other things have created? Maybe your definition of gory consists of simply what you do to creatures (or what they do to you), but that's such a small portion of gory that it defies logic to just ignore the fact that we could cause corpses to explode into gibby little bits in D2.
He is one of those "Random Unique" Boss guys.
Or that other dude was, when they were still in the dungeon.
Actually, both. And the guy is used as a living siege machine against bastions standing against Hell.
Um, okay, watch the video? The small fries explode in clouds of blood, the time-bomb cultists fall apart into big yummy chunks of flayed flesh and the bosses explode in heaps of bone, marrow and gore!
Did you see the locusts take out the zombies? The blood went down the hillside with the damn skeletons, man! That's awesome!
1) Corpses disappear because no "raise killed enemies" skills or characters with said skills have been introduced so why would they bother in the demo?
2) It'll diminish lag, so stop bitching.
And I'm sure there will be GORY areas, like if we go back into Hell? Just awfully gory!
But this was just a dusty library dungeon and the outside of it, jeeze, calm the fuck down about the color and gore.
I don't know how random those encounters were, to be honest. It seemed completely triggered, that is to say, once the player walks up to the area that the creature will come out. It has a very TQ feel to it.
:rolleyes:
It's obvious you didn't know what I was talking about by piles of corpses, probably because you've never played Diablo 2, and if you have, never up to Act 4. I never mentioned the corpses the enemies left behind, but that's a good point you bring up. They shouldn't be disappearing. Lag is a poor reason for it, especially since the game is clearly not going to be computer heavy.
Clouds of blood is pretty... bleh. Considering the destructible environments, we should be chopping off limbs and the like as well. "BUT OH IT WILL CAUSE LAG!" Read above. Cultists barely did much of anything besides have a particle effect. No remains means that the dungeon I just cleared thousands of monsters in will be just as pretty and brand-new-looking as when I entered it.
The locusts on the zombies, again, was pretty tame. Oh boy, a green mask over our enemies that, when they reach 0 health, the skeleton appears. They could very easily make it much more gruesome, but they won't. Why? Because they can't do gore, and won't.
But that still isn't even what I was talking about. Not even in the slightest.
Piles of corpses. The enemies came from the same cathedral that the butcher, diablo, mephisto, and all the other demons came out of. There is no reason why there shouldn't be 2 or 3 bodies in the scenery in 20 minutes. You should be seeing, at the least 20 bodies... at least.
A pile of burning books would be nice as well. Although it isn't gory, it would make it seem less like we're playing in a place that no demons have ever ventured.
Diablo 2 lags everyones computer regardless of how powerful it is in Act 5 when you kill the guy that triggers the plethora of artillery stuffs to fire. It's a poor engine that causes this.
And you can make the most complex of programs be completely lag free on the slowest computers. The argument that corpses cause lag is pretty bunk considering what we are talking about. The majority of enemies we saw in the video did not respond to physics. They simply had a death animation and sat there. Those enemies that did respond to corpses didn't exactly do much of anything after they stopped moving. Even further, they didn't respond to each other as was demonstrated by the Locust Swarm example.
Most enemies had death animations (ghouls, cultists, the dogs for example) and simply sat there. No real reason for those corpses to not stick around, especially since the number of enemies we saw in the demo was rather small, including the beginning bit.
It should be an option like all games with mass killing (MMO's are an example of this).
Number of corpses?
NONE
FEW
SOME
MANY
TONS
ALL
Fairly simple, to be honest.