Bounty Hunter Archive
Thread: THE DUEL EXPLOIT
So you'll be OK if the cycle continues and the fix for this hoses the Jedi?
Or will it be as if a million Jedi whined in terror and were suddenly silenced?
Shaan'ti Hokai (Kauri) 
TashunkaSapa wrote:
huttu wrote:
I want to be on terms, i am full templ
bh's are fun to kill
So instead of doing the /duel; /endduel BS, why not just go to Kaadara or Dearic and actually DUEL Bounty Hunters?
Save yourself the time and us the aggravation of dealing with cowards.
no-DB fights are boring, I dont db in duels...
what does these /duel /endduel exploits and offer ride exploits do to a user? No one has ever done it to me...just wondering..
It would make jedi more paranoid especially if it had a range of like 300m (out of range of map). Just bring a bunch of friends along to enter the jedis range from all sides and let the fun begin!
And anyone can cause a disturbance in the force except tailors...cause they are broken
snipaho wrote:An exploit is when you take advantage of a bug. The /duel/endduel thing is not a bug, it's how they designed it. They programmed it with the intent of giving the /duel'er a message that they cannot duel because the other person can attack them.Working as intended.
By this Jedi's mentality credit duping and resource duping was just an ingenious way to conduct business and not exploiting anything.
He obviously loves to do this and wants no harm to come to a bug created by the Devs when they fixed the previous /duel bug when BH were exploiting the /duel, dueling and not allowing their mark to attack back. He justifies his or her ignorance by stating it is intended design. HMMMM I was under the impression that /duel was to begin fighting with a player that you do not have TEF on. Never do I recall it being intended to check for a sys message stating you can not duel targeted player. Thereby as I understand it, it would be a unintended game design and to "exploit" it to gain undue advantage, is against EULA, community standards rule 12. I have stated on the Jedi Forums that this will come back and bite them in their arse, as the next fix may really screw with them, but to no avail some if not many continue to abuse game design, so that they may receive an unintended sys message generated by mission holding BH, because they are to inept at detecting BH, to Paranoid of BH, and to slow to act if attacked, thus needing this BUG. One would hate to receive from the moment they logged on until they logged off these messages, I wonder how long it will be until we have a day of protest and we find everyone running these macros on everyone else. I am not looking forward to that. My only wish is that they stealth fix it with removal of the /endduel command and the users of this are locked into dueling until they die. I guarantee they would think twice after coming out of the cloner of trying it again.
Eskie wrote:
snipaho wrote:
An exploit is when you take advantage of a bug. The /duel /endduel thing is not a bug, it's how they designed it. They programmed it with the intent of giving the /duel'er a message that they cannot duel because the other person can attack them.
Working as intended.
Yes, and this fix was done because BHs exploited /duel to override the BH TEF and keep a Jedi from fighting back unless he also /dueled the BH.
But they forgot to take into account that a Jedi should not know if a BH has his mission unless the BH reveals himself. In the Jedi / BH case it shouldnt be a message like the current one but a behaviour as if the BH declined the duel after 5 seconds, for example.
As far as I am concerned a Jedi being able to tell a BH has his mission before the BH himself chooses to make it known by attacking or some other means is violating the design of the BH / Jedi system in which a BH is supposed to have the first strike surprise attack. Therefore it cannot be intended and is a bug. And using a bug to gain an advantage over somebody else is exploiting.
Lets not forget that the /duel fix was not only in response to the old BH /duel bug, but they also had to take care of the groups that would hold open /duels on the jedi in the group, and if anyone came to close or started attacking a jedi, they would help incap and take the db, since now you don't take any XP Loss except to a BH.
So this goes both ways. Don't blame just the BH on this one.
So, the Jedi use /duel because the BH exploited /duel in the past? What was their excuse for the /trade exploit? BH exploiting /trade as well?
Anybody who rationalizes using a broken mechanic as "working as intended" needs to grow up and learn some ethics. If you have to rationalizean act in a video game, it is wrong.
Raikir wrote:
So, the Jedi use /duel because the BH exploited /duel in the past? What was their excuse for the /trade exploit? BH exploiting /trade as well?
Anybody who rationalizes using a broken mechanic as "working as intended" needs to grow up and learn some ethics. If you have to rationalizean act in a video game, it is wrong.
QFE You said it so much better than I did.
ocili wrote:
Eskie wrote:
snipaho wrote:
An exploit is when you take advantage of a bug. The /duel /endduel thing is not a bug, it's how they designed it. They programmed it with the intent of giving the /duel'er a message that they cannot duel because the other person can attack them.Working as intended.
Yes, and this fix was done because BHs exploited /duel to override the BH TEF and keep a Jedi from fighting back unless he also /dueled the BH.
But they forgot to take into account that a Jedi should not know if a BH has his mission unless the BH reveals himself. In the Jedi / BH case it shouldnt be a message like the current one but a behaviour as if the BH declined the duel after 5 seconds, for example.
As far as I am concerned a Jedi being able to tell a BH has his mission before the BH himself chooses to make it known by attacking or some other means is violating the design of the BH / Jedi system in which a BH is supposed to have the first strike surprise attack. Therefore it cannot be intended and is a bug. And using a bug to gain an advantage over somebody else is exploiting.
Lets not forget that the /duel fix was not only in response to the old BH /duel bug, but they also had to take care of the groups that would hold open /duels on the jedi in the group, and if anyone came to close or started attacking a jedi, they would help incap and take the db, since now you don't take any XP Loss except to a BH.So this goes both ways. Don't blame just the BH on this one.
I thought this is still possible? Since when does a BH TEF prevent accepting duels? In fact, you can be attacked by a BH in a duel and you still will be in the duel after the BH attacked you.
If Jedi A gets a BH TEF from BH B, Jedi C can still /duel Jedi A since A cannot attack C currently. Or did I miss a patch note?