Bounty Hunter Archive
Thread: Curious: How long did it take the devs to fix the duel exploit when it hurt jedi?
After reading the replies to my post I must say I am disapointed with the jedi replies.
I have read only "staw-man" replies that hold no validity. Thats where you key in onaspects of an agument that are not critical to the point .. then make them seem of huge importance... only so you can dismantle them.
If there is another valid agument that can tell me why exploits should not be fixed... please post
Message Edited by Anarchicgorilla on 09-13-2005 05:04 PM
Anarchicgorilla wrote:
After reading the replies to my post I must say I am disapointed with the jedi replies.
I have read only "staw-man" replies that hold no validity. Thats where you key in onaspects of an agument that are not critical to the point .. then make them seem of huge importance... only so you can dismantle them.
The point is this:
The duel end duel used by jedi is an exploint... this has been admitted by devs. seen in replies here and in countless tickets i have recieved.
The point is there is a exploit that is being used and nothing is being done about it.
To the jedi replies
1) It does not matter what you say about "it only effects dumb BH who can be dueled"
A: straw man ... does not matter if BH is an idiot ... It is still an exploit and should be fixed.
2) BH used exploits
A: staw man ... does not matter who did what first ... It is still an exploit and should be fixed.
3) Stop crying you "must" be 9-years-old
A: staw man ... it does not matter if i am a 2-year-old . It is still an exploit and should be fixed.
4) This, that, and the other jedi replies thus far
a: staw man...
Possible valid agument agaist this post are these:
1) We want exploits (valid to reply... but not a acceptable solution)
2) This is not an explot (it is, and has been confimed)
3) (which i hope is the case) The devs have been tring to fix this but cannot figure out how to do so... Not from lack of effort but from not understanding their own program. They are trying to hire people who understand how the game functions and are trying to fix this, at thisvery second.
If there is another valid agument that can tell me why exploits should not be fixed... please post
Message Edited by Anarchicgorilla on 09-13-2005 05:04 PM
KammaRocca wrote:
blademaster30 wrote:
please show a post from someone that matters that this is a exploit
From the rules and policies page on the starwarsgalaxies.com homepage:
http://starwarsgalaxies.station.sony.com/content.jsp?page=Policies%20Community%20Standards
"Exploitable bugs include, but are not limited to bugs that grant the user unnatural or unintended benefits in-game."
Just ask yourself: Is the /duel command intended to show a Jedi if a BH has his mission or is it to *gasp* challenge someone to a duel? If you don't actually intend to fight the person you challenge, that would make it an exploit.
Oh really? I guess you wont mind then when I have my macro make sure I hit once a second by using the non exploit of reducing cooltimers
AvataroftheSith wrote:
Anarchicgorilla wrote:
The duel exploit used by jedi has been reported and posted time and time again for atleast 2 months now (maybe more)
I am curious how many months could the bh duel an jedi and kill him without jedi being able to attack back before it was fixed?
It's not an explot unless a dev says so.
Anarchicgorilla wrote:
After reading the replies to my post I must say I am disapointed with the jedi replies.
I have read only "staw-man" replies that hold no validity. Thats where you key in onaspects of an agument that are not critical to the point .. then make them seem of huge importance... only so you can dismantle them.
The point is this:
The duel end duel used by jedi is an exploint... this has been admitted by devs. seen in replies here and in countless tickets i have recieved.
The point is there is a exploit that is being used and nothing is being done about it.
To the jedi replies
1) It does not matter what you say about "it only effects dumb BH who can be dueled"
A: straw man ... does not matter if BH is an idiot ... It is still an exploit and should be fixed.
2) BH used exploits
A: staw man ... does not matter who did what first ... It is still an exploit and should be fixed.
3) Stop crying you "must" be 9-years-old
A: staw man ... it does not matter if i am a 2-year-old . It is still an exploit and should be fixed.
4) This, that, and the other jedi replies thus far
a: staw man...
Possible valid agument agaist this post are these:
1) We want exploits (valid to reply... but not a acceptable solution)
2) This is not an explot (it is, and has been confimed)
3) (which i hope is the case) The devs have been tring to fix this but cannot figure out how to do so... Not from lack of effort but from not understanding their own program. They are trying to hire people who understand how the game functions and are trying to fix this, at thisvery second.
If there is another valid agument that can tell me why exploits should not be fixed... please post
Message Edited by Anarchicgorilla on 09-13-2005 05:04 PM
Well here's a Jedi that's going to give you a decent reply. First off, there's no reason it shouldn't be fixed. Its an exploit exactly like you said and it needs to be gotten rid of. HOWEVER, your post is unnecessarily inciteful as it makes a comparison between this duel exploit and the previous one and suggests that because this one hasnt been fixed as quickly, then Jedi must be the favored dev class.
This is a flawed argument and probably the reason you're not getting any real valid responses. Under the old duel exploit the BH could attack the Jedi and the Jedi could do nothing in self-defense. In essence, it created a one-way tef that rendered it impossible for the BH to lose and guarenteed that a Jedi who didn't know to /duel back would suffer xp loss.
The current duel exploit merely informs a Jedi when a BH has his mission. While it does remove the element of surprise from a BH's attacks, it in no way completely dictates the winner of the battle. The BH is capable of counterattacking as is the Jedi and if the BH feels the element of surprise is lost and is necessary for his success the BH still has the ability to simply not attack. Furthermore, should the BH lose, there is no penalty applied to him. For these reasons the current /duel exploit is of significantly less severity than the previous one, and as such falls lower on the developer "to fix list" than its predecessor.
Well here's a Jedi that's going to give you a decent reply. First off, there's no reason it shouldn't be fixed. Its an exploit exactly like you said and it needs to be gotten rid of. HOWEVER, your post is unnecessarily inciteful as it makes a comparison between this duel exploit and the previous one and suggests that because this one hasnt been fixed as quickly, then Jedi must be the favored dev class.
This is a flawed argument and probably the reason you're not getting any real valid responses. Under the old duel exploit the BH could attack the Jedi and the Jedi could do nothing in self-defense. In essence, it created a one-way tef that rendered it impossible for the BH to lose and guarenteed that a Jedi who didn't know to /duel back would suffer xp loss.
The current duel exploit merely informs a Jedi when a BH has his mission. While it does remove the element of surprise from a BH's attacks, it in no way completely dictates the winner of the battle. The BH is capable of counterattacking as is the Jedi and if the BH feels the element of surprise is lost and is necessary for his success the BH still has the ability to simply not attack. Furthermore, should the BH lose, there is no penalty applied to him. For these reasons the current /duel exploit is of significantly less severity than the previous one, and as such falls lower on the developer "to fix list" than its predecessor.
Your absolutely right, its would be an incredibly easy fix (hell, just get rid of the special sys message would do it), but you know how lazy the devs are and the reason its not being fixed right away is because of that laziness and the fact that it just isnt a severe bug,not any preference for Jedi over BH. Hell, Jedi have been waiting since the CU hit to get their cooldown timers to work properly and their speed mods to work and thats still not fixed where BH have had correctly working timersand speed mods since the start, does that mean the Devs love BH more? Of course not. It just means they're incompetent.
Anarchicgorilla wrote:
Well here's a Jedi that's going to give you a decent reply. First off, there's no reason it shouldn't be fixed. Its an exploit exactly like you said and it needs to be gotten rid of. HOWEVER, your post is unnecessarily inciteful as it makes a comparison between this duel exploit and the previous one and suggests that because this one hasnt been fixed as quickly, then Jedi must be the favored dev class.
This is a flawed argument and probably the reason you're not getting any real valid responses. Under the old duel exploit the BH could attack the Jedi and the Jedi could do nothing in self-defense. In essence, it created a one-way tef that rendered it impossible for the BH to lose and guarenteed that a Jedi who didn't know to /duel back would suffer xp loss.
The current duel exploit merely informs a Jedi when a BH has his mission. While it does remove the element of surprise from a BH's attacks, it in no way completely dictates the winner of the battle. The BH is capable of counterattacking as is the Jedi and if the BH feels the element of surprise is lost and is necessary for his success the BH still has the ability to simply not attack. Furthermore, should the BH lose, there is no penalty applied to him. For these reasons the current /duel exploit is of significantly less severity than the previous one, and as such falls lower on the developer "to fix list" than its predecessor.
I agree with what you said about the first exploit was of a more "severe" nature.
However, the current exploitcould be a very simple to fix. Thats were I am upset... it would not take much at all to fix it
1)Give jedi no messege, instead give messege to BH...you have been challeged to a duel by a player you can target...thenBH only get the option to deny duel attheir convience (ie BH can close the window like you can on other duel requests and give no response). BH would still not be able to challege a jedi they have mission for.
Having an open duel (even though only answer is no) would in no way interfer with other aspects... jedi should know this with the "accept duel froma freind" so friend can DB.
2)Make it is so the the request come back with the same response you get when someone does not accept the duel... but put this on a random 5 second to 5 minute timer.
Nothing changes here either.
3) Just make it so BH cannot challege Jedi... let a jedi challege a BH as normal (from what I read the exploit only worked if BH challeged jedi.. not the other way around... correct me if wrong)
These are Just 3 simple fixes that would all work.... i could easily list more
Anarchicgorilla wrote:
Darkknight109 wrote:
What's funny is the reason the current duel exploit exists is it was a fix to BH who used the old duel exploit. Ironic, eh?
Just one question...
Lets say the devs say screw it and just go back to the old way... where bh can duel and kill jedi without them being able to attack....
Would all you jedi say "what irony"we screwed ourselves by using an exploit....or would the posts be flooded with "bh exploit devs fix?"
Doubtless it would be the second option. But how is that any different from what is happening right now?
mindspat wrote:
This is sad "boo hoo, jedi /duel me. now they no i have there mish. Waaaahhhhh!!!"
Truth be told, it's not impacting you. If you are actually playing the game and not trolling let me ask you this:
Why do you show up with "Master Bountyhunter" tag above your toons head and loiter around them when there's no one else around? Chances are if you're getting a /duel it's becasue you've spoiled your chances to surprise them.
*in all fairness, there needs to be a fix to remove any system msg which prevents a give away on the BH. There also needs to be a cool down of at least 10 seconds when issuing the /duel option. Players should not be able to spam /duel;/endduel at will.
.....