hey its andres wrote:The only real use for dead angling is to finish someone off, which has more effective methods as well.
I've have yet to hear anything substantial about the mule epidemic, and the problems its caused. That's an example of a game breaking glitch for sure.
Jansports wrote:I lieu of certain posts I would say dead Angling is an intended exploit. I still can't ignore the fact it was carried over from Demons to Dark.
TheMeInTeam wrote:........High level play and success is not mechanic knowledge, but rather one's approach and frame of mind....
SWEET!!!! 
FexDS wrote:Since this discussion keeps coming up, I should add so people can differentiate and the argument can hopefully stop.
A glitch is a completely unintended, random, unforeseen occurrence that game developers didn't see coming and have little idea of how it's happening. Bugs are forms of glitches that persist and can be easily recreated. Glitches and bugs are always the top priority of patching. An example of a glitch is getting stuck on the landscape. An example of a bug is the bottomless box share.
An exploit is the player's cunning use of an in game mechanic to create unintended results and give themselves an advantage. As exploits are player generated, and by large dependent on core game mechanics, they are seldom patched unless they are game breaking.
Balancing is when developers look at the practical application of intended mechanics/items/skills and how the playerbase is acting with it and decide to intervene to prevent unintended overpowered combinations. This is what happened to the fog ring, etc.
Dead angling is, from the above, an exploit, and it is very unlikely to be removed because the effects of it are not gamebreaking and the developer has bigger issues to consider and would have to rework the mechanic completely.
TheMeInTeam wrote:High level play and success is not mechanic knowledge, but rather one's approach and frame of mind. A souls veteran will be MUCH more likely to do well quickly in DS II.
reim0027 wrote:Same goes for toggle escape. Maybe it was unintentional at first, but it certainly added positively to the gameplay, IMO.
Rynn wrote:FexDS wrote:Since this discussion keeps coming up, I should add so people can differentiate and the argument can hopefully stop.
A glitch is a completely unintended, random, unforeseen occurrence that game developers didn't see coming and have little idea of how it's happening. Bugs are forms of glitches that persist and can be easily recreated. Glitches and bugs are always the top priority of patching. An example of a glitch is getting stuck on the landscape. An example of a bug is the bottomless box share.
An exploit is the player's cunning use of an in game mechanic to create unintended results and give themselves an advantage. As exploits are player generated, and by large dependent on core game mechanics, they are seldom patched unless they are game breaking.
Balancing is when developers look at the practical application of intended mechanics/items/skills and how the playerbase is acting with it and decide to intervene to prevent unintended overpowered combinations. This is what happened to the fog ring, etc.
Dead angling is, from the above, an exploit, and it is very unlikely to be removed because the effects of it are not gamebreaking and the developer has bigger issues to consider and would have to rework the mechanic completely.
And That also makes all exploits, by that reasoning, a glitch or bug too.
As I said a moment ago, it's a limitation of the coding, and it's a problem that persists in a lot of games i've played. It's directly based off limitations in the code.
AnCapaillMor wrote:reim0027 wrote:Same goes for toggle escape. Maybe it was unintentional at first, but it certainly added positively to the gameplay, IMO.
I used to love toggle escape, it saved my butt from zwei\greatsword stun locks so many times, but my latest build is kind of a strength build and i absolutely hate toggle escape. You fight a few who don't know it then come up against someone who knows it and you get parried or bs'd to hell.
FexDS wrote:Rynn wrote:FexDS wrote:Since this discussion keeps coming up, I should add so people can differentiate and the argument can hopefully stop.
A glitch is a completely unintended, random, unforeseen occurrence that game developers didn't see coming and have little idea of how it's happening. Bugs are forms of glitches that persist and can be easily recreated. Glitches and bugs are always the top priority of patching. An example of a glitch is getting stuck on the landscape. An example of a bug is the bottomless box share.
An exploit is the player's cunning use of an in game mechanic to create unintended results and give themselves an advantage. As exploits are player generated, and by large dependent on core game mechanics, they are seldom patched unless they are game breaking.
Balancing is when developers look at the practical application of intended mechanics/items/skills and how the playerbase is acting with it and decide to intervene to prevent unintended overpowered combinations. This is what happened to the fog ring, etc.
Dead angling is, from the above, an exploit, and it is very unlikely to be removed because the effects of it are not gamebreaking and the developer has bigger issues to consider and would have to rework the mechanic completely.
And That also makes all exploits, by that reasoning, a glitch or bug too.
As I said a moment ago, it's a limitation of the coding, and it's a problem that persists in a lot of games i've played. It's directly based off limitations in the code.
No. There's a very specific difference between "no idea how you're getting stuck on a rock" "we know why this boss becomes unresponsive after x attack let's fix it" and "oh look the players are using mechanic x to trigger reaction y which we did not intend... and we can't fix it without remaking core mechanics"
Please don't try to muddle a very clear distinction.
undefined wrote: There may be a clear difference from a development standpoint, but this doesn't suddenly make the occurance not a glitch or programming quirk. By this logic one could say that in the first iterations of Call of Duty, that quickscoping wasn't a programming quirck (before they, after trying to get rid of it for 4 games, simply made it a feature).
But I digress, it's a pointless argument since we're both essentially saying the same thing, and disagreeing on one small detail.
FexDS wrote:undefined wrote: There may be a clear difference from a development standpoint, but this doesn't suddenly make the occurance not a glitch or programming quirk. By this logic one could say that in the first iterations of Call of Duty, that quickscoping wasn't a programming quirck (before they, after trying to get rid of it for 4 games, simply made it a feature).
But I digress, it's a pointless argument since we're both essentially saying the same thing, and disagreeing on one small detail.
You are incorrect. Vocabulary exists for a reason and "glitch" and "exploit" are not the same thing and exploits are not glitches. Saying that everything is a programing quirk is as saying they are all 1s and 0s... a pointless aggregation resulting in the logical fallacy: Men have legs, Chairs have legs, therefore Chairs can run marathons.
The very fact that exploits often get incorporated into the game as a proper feature in later iterations of games sets them appart from "glitches" which are core mechanics *not* working as intended. Exploit is a core mechanic working as intended and being manipulated by the playerbase to do what it shouldn't. This distinction is important beccause people in this thread had been asking 1) Why did it carry over games then (because its a core mechanic working as intended being misused) and 2) Why hasn't it been fixed then (because it's player generated and not gamebreaking)
I am not trying to pointlessly argue with you. This difference is relevant to the ongoing conversation.
TooLeet wrote:
I think this has made the most sense out of everything posted in this thread. It makes 100% complete sense and there's no way to argue with that logic.
/thread.
|
|
|
by Leet Mon Jul 08, 2013 7:31 pm
