Any time someone exploits mechanics with self rez it completely negates the accomplishment, to me at least.
[spoiler]I find it hilarious that most of you have no idea what an exploit is lmao[/spoiler]
The amount of salt being thrown at me right now is reaching critical levels. I'm sorry you all can't handle simple terminology.
English
-
My 4 cents, Yes, it is an exploit. Yes, it is fn amazing. Very few players will be able to do this, before being over light level. These guys are the trouts, lebrons, and brady's of our game. They are exceptional players.
-
An exploit yes, considering it circumvents the mechanics of the fight. Now obviously a solo would not be possible without exploiting the 30 second bomb lockout. However this does not take anything away from the achievement. Go ahead and Solo Aksis for me using this "exploit". You wouldn't stand a chance..... scrub. (nor would I). This is still highly impressive.
-
작성자: tiptronic22 10/26/2016 8:22:22 PMTo be fair you may or may not be a scrub. You are definitely a troll though. Anyone that gets 200+ responses, mostly salt with 0 up votes is trolling hard. You are trying to take away from others achievements because you don't like the way it was accomplished. We only have video evidence of this being completed twice. If you are the PvE all star you say, prove me wrong and be the third to get it done.
-
There is a big portion of this thread is based on [b]Brick perfected's argument[/b] but as a lot would agree here is why his argument does not hold up. The players are just utilizing the games mechanics to the best of their ability which by definition [i]would[/i] be an exploit but not in the context you're (brick perfected) using it. He is exploiting the self Rez I.E. Using it to the best of its ability. It's only a cheat in the context of gaming if he somehow circumvented a safeguard or preventative measure within the games programming in order to finish the encounter. There is no safeguard against this, nor is he glitching the game. Just because a developer didn't think about doing one specific think a certain way (its intent) doesn't make it a cheat if a player does it. You're (Brick perfected) using a definition of the word exploit that says itself to be [b]debatable[/b] and not a clear proven fact. So you argument really has no proof whatsoever. Just a debatable idea. (Don't get your argumentative points from Wikipedia I guess) As well, by your logic, a blade dancer using the swing of the arcblade to cross a gap or distance that would otherwise be uncrossable is cheating. This would mean that going into pvp and blade-dancing and killing someone from a very far away distance is cheating. Which it clearly is not. It's a super. Supers enable you to do things that are normally not possible in your characters' neutral state to give yourself an advantage. That's what makes them [b][i][u]Super[/u][/i][/b]. It just so happens that one advantage of selfres is that it revives whenever you want. Dying in the first place removes the debuff you had previous to dying. That removal of the debuff is clearly in the programming of destiny and most other games with "debuffs". So that anyone when they are revived are not revived at a disadvantage I.E. with a debuff [u]That is not cheating[/u] as the game is programmed that way. Brick Perfected's argument is flawed in that he provides no evidence of the the player circumventing or glitching the game's programming in anyway. It's all just his (frankly limited) understanding of the term exploit, and his opinion of using self Rez as "cheap."
-
Cheating? Who said cheating? The devs obviously did not design this encounter with the intent of same person who uses the cannons throwing the charges. Thus, OP negating the "Charge Lock Out" mechanic is an exploit. It is much more cut and dry than you're making it out to be.
-
[quote][quote]In video games, an exploit is the use of a bug or glitches, game system, rates, hit boxes, or speed, etc. by a player to their advantage in a manner not intended by the game's designers.[1] Exploits have been classified as a form of cheating; however, the precise determination of what is or is not considered an exploit can be controversial. This debate stems from a number of factors but typically involves the argument that the issues are part of the game and require no changes or external programs to take advantage of them.[2][/quote] That idea above that you posted is the way in which you're using exploit. That description literally claims exploits are a form of cheating. So by choosing that claim you're agreeing with it. Meaning you think the actions of the OP are cheating. If it wasn't cheating, what else would your problem with the actions of OP be?
-
I'll argue a counterpoint, since this is actually a good argument. Forgive me for the annoying formatting, but I think it will help. In terms of 'exploitation' of game mechanics, it is a matter of "working as [u]designed[/u], but not working as [b]intended[/b]". Computer code can often do weird things that were never intended to happen, such as bugs or crashes. A great example of this in a game is the Atheon/Templar pushing strategy: enemies are [u]designed[/u] to move out of AoE grenades, but these big bosses were never [b]intended[/b] to be push out of bounds. The Templar was never [b]intended[/b] to even move other than by teleportation. I would argue that this can be considered an exploit, but [i]only[/i] in terms of the raid mechanics/debuffs and [i]not[/i] self-rez mechanics. The 'Charge Lockout' debuff is intended to last 30 seconds and prevent players who use the cannons from throwing SIVA charges. The[u] design[/u] (or mechanics if you will) of debuffs means they are lost upon death; dying in a Raid means you are usually dead for at least 30 seconds anyways and the lockout still happens, just through death and not the debuff. The issue is that this mechanic[i] does not factor in[/i] the useage of Self-Rez. This ability is [u]designed[/u] to remove the penalty of death and respawn timers. It performs this intended role just fine, and this mechanic does nothing more than that. The problem comes by the fact that debuffs are [u]designed to lead to death[/u] as their punishment. You don't actually 'cleanse' the debuff as much as you negate the consequences it brings. This can be considered exploitation of the debuff mechanics. They were [u]designed[/u] with the idea that death was a consequence, something to be avoided. When we can nullify that consequence that is supposed to drive the gameplay (removing debuff/forced to work around it), then debuffs are not working as [b]intended[/b]. It's mainly a problem of the engine Destiny runs on and how debuffs are coded. It is also an issue of the Raid not being [u]designed[/u] with this exploit in mind. Self-rez is working as [b]intended[/b], which is to remove the state of death. The ability to resurrect yourself is just the tool used in order to exploit other mechanics, namely the removal of debuff upon death.
-
Agree to disagree. Here's the thing about coding. If at the end of a code line is "not true" then there's a path written to execute another action. However, in a case that there is no "true" result, such as it does not exist therefore "not true" is not in the equation then the code would stop in theory. Since the written code has stopped the game should have crashed since an anolomy has interfered with proposed actions. With revive, I believe Bungie has already determined that the scenario would eventually happen. It was coded to offset the Darkness Zone deaths, Heroic Raid deaths, and Trails death. It's ment to used just like how 2 Ward of Dawn are ment to be used to stop an Oversoul.
-
This is very impressiv by you both. God Job and you both amazie me with your plays. Bungie must send both of you guys a reward. Wish that other would not be so bad and say bad stuff about it. You guys dont deserve it. Ceep up the impressiv gameplay. It would be very nice to see bungie make a raid with insane difficulty level and see you guys in action.