Bounty Hunter Archive
Thread: Duel exploit...
lol please all, feel free to angle it anyway you want....it's an exploit. now for the my point...WHO CARES! ?? there are tons of exploits...and i for one am stuck on whether i should count them as part of the game or not. so many times i fight fair and then go back to the combat log to find that while i was not exploiting my opponent was. it's funny, about half way through the fight, right around the point wher the jedi realizes he might not win this one...his attack speed all of a sudden becomes totally uber...and sure enough when i check the logs my suspisions are confirmed. idon't blame them, and that's my cue to do the same from now on. i think at this point maybe we have to accept that exploits are part of the game. i hate that this is the way it is....but that's life in the wacky world of online gaming. oh and devs....FIX THE D A M GAME
pagoa
JeddoJogger wrote:
Until a Dev clearly states their intentions on any game mechanic no one should be accusing anyone of exploiting. No one knowsthe Dev's intentions or thoughts except the Devs themselves. I have read the EULA, and it all comes down to the developer's viewpoint. The Devs need to post their intentions in writing, then the accusations and suspensionscan be brought fourth and enforced.
We won't see any public announcements about any exploit until the developers realize that there is an issue at hand and have a fix in place. That requires post trolling and in-game testing. I'm sure they have done both for this /duel issue.
The issue at stake IS NOT BH vs Jedi /duel requests. The real issue is the TEF system, and that it will infact allow a /duel request to be "pushed" back, so to speak to a Jedi who /duel's a BH who has his mission. If you are overt, and the target is opposing faction overt, and you /duel them. You get the same message. The problem in this case is that the system programming makes no difference in the BH TEF and the factional PvP TEF. It's the same TEF to the /duel request string. In nano seconds the sytem does the following check:
Player 1 duel requested Player 2
Can player 2 attack player 1? No? Proceed to A, Yes? Proceed to B
A. Allow Player 1 to /duel Player 2
B. Dissallow Player 1 to /duel Player 2 - Result: "You cannot duel so-and-so because....."
So that being said... the developers know what the problem is, and have isolated what it COULD be. Then they say "what is the least impactful way to fix this? (read easiest programming way) They have 2 options that I can tell. They can change the entire TEF /duel system to just allow duel requests regardless of either player's ability to attack the other.... OR they can create a new system entirely from the ground up, which accomplishes the same results.
RoundWallKing wrote:
bmill wrote:
Map the following to a hot key on your keyboard
/duel
/underhandshot
/end
/spit
/say Silly Jedi, Exploits are for kids!
When you get the duel request, quick target them, and hit this key. I mapped mine to the \ key. Works WONDERS on annoying them!
Wont work if I have a macro that goes,
/duel
/endduel
Also, who are you to call it an exploit. No dev has ever said this is a sploit and the issue has been known for awail. As a matter of fact how do you know its not working as intended? Oh ya...you dont.
Message Edited by RoundWallKing on 09-27-2005 04:42 PM
Sorry to bring this all back up but try going to
actually pre-cu the devs DID state it was an exploit.
if it was then, and the same problems are still happening from it's use, then guess what..... IT'S STILL AN EXPLOIT.
shadowdragon2k wrote:
RoundWallKing wrote:
bmill wrote:
Map the following to a hot key on your keyboard/duel/underhandshot/end/spit/say Silly Jedi, Exploits are for kids!When you get the duel request, quick target them, and hit this key. I mapped mine to the \ key. Works WONDERS on annoying them!
Wont work if I have a macro that goes,
/duel
/endduel
Also, who are you to call it an exploit. No dev has ever said this is a sploit and the issue has been known for awail. As a matter of fact how do you know its not working as intended? Oh ya...you dont.Message Edited by RoundWallKing on 09-27-2005 04:42 PM
Sorry to bring this all back up but try going to
http://forums.station.sony.com/swg/board/message?board.id=bounty_hunter&message.id=395257seeing tanks said and i quote " Jedi keep spamming /duel, /endduel to determine if a BH has a mission on them. Devs have acknowledged that as an issue. "i believe it is pretty safe to say that this is ovbiously an exploit due to the fact that the devs have acknowledged its an issue. its ovbiously not working as intended. or wouldnt need fixing and use of this tactic would be considured an exploitthank you have a nice day...move along
That says nothing, What does "we know its an issue" mean? They said the same about primium pearls not dropping and then we came to find out it was intended.
Message Edited by RoundWallKing on 09-28-2005 09:58 PM
Again, I have seen zero proof positive to support your claims the /duel /end is being used "as intended" and not an exploit. Whereas many have shone multiple examples of why this is an exploit. Where is your proof?
RoundWallKing wrote:
That says nothing, What does "we know its an issue" mean? They said the same about primium pearls not dropping and then we came to find out it was intended.
Message Edited by RoundWallKing on 09-28-2005 09:58 PM
RoundWallKing wrote:
shadowdragon2k wrote:
RoundWallKing wrote:
bmill wrote:
Map the following to a hot key on your keyboard
/duel
/underhandshot
/end
/spit
/say Silly Jedi, Exploits are for kids!
When you get the duel request, quick target them, and hit this key. I mapped mine to the \ key. Works WONDERS on annoying them!
Wont work if I have a macro that goes,
/duel
/endduel
Also, who are you to call it an exploit. No dev has ever said this is a sploit and the issue has been known for awail. As a matter of fact how do you know its not working as intended? Oh ya...you dont.
Message Edited by RoundWallKing on 09-27-2005 04:42 PM
Sorry to bring this all back up but try going to
http://forums.station.sony.com/swg/board/message?board.id=bounty_hunter&message.id=395257
seeing tanks said and i quote " Jedi keep spamming /duel, /endduel to determine if a BH has a mission on them. Devs have acknowledged that as an issue. "
i believe it is pretty safe to say that this is ovbiously an exploit due to the fact that the devs have acknowledged its an issue. its ovbiously not working as intended. or wouldnt need fixing and use of this tactic would be considured an exploit
thank you have a nice day...move along
That says nothing, What does "we know its an issue" mean? They said the same about primium pearls not dropping and then we came to find out it was intended.
Message Edited by RoundWallKing on 09-28-2005 09:58 PM
you sir, are in what is commonly know as "denial"
To people saying "bla bla, if he dueled you had blown your cover already".
Not intireley. Sometimes when I load into a city just for some shopping I get dozens of duel requests. When I was trying to grind MCM and had to join a group, most of the jedi in that group would /duel me.
And also sometimes when I was really out there hunting I got to a jedi in a npc city and tried to blend in. He /dueled me, my guildmates that were in me and almost everyone in the vincinity that could be a bounty hunter.
So your argument is an invalid argument.
Hehe, I find it funny that the people that say "this is not an exploit" will not respond to my posts. Possibly because I have shone beyond reasonable doubt that it IS in fact an exploit? Or perhaps they just have supporting evidence to support their claims, while I have shown ample evidence to support mine?
Ah well... it's time for this post to "die" anyway. Not as if we are going to change anything by debating it here. The argument is for all intentions, over.
bmill wrote:Hehe, I find it funny that the people that say "this is not an exploit" will not respond to my posts. Possibly because I have shone beyond reasonable doubt that it IS in fact an exploit? Or perhaps they just have supporting evidence to support their claims, while I have shown ample evidence to support mine?
Ah well... it's time for this post to "die" anyway. Not as if we are going to change anything by debating it here. The argument is for all intentions, over.
Yup I noticed that too...
The point is clear... it is an exploit... if it wasnt the devs would have said 'working as intended...'
Not 'its an issue'