Punishing afk/ bots in pvp and event arenas
MercenaryKnight
We all have seen them, either characters who stay still, hit c space or a more likely follow bots in arenas. We report them for leeching maybe once in a while and get the whole team to do so. Yet the bots keep on gaining points.
My suggestion is that if you have dishonor and try to enter mission while dishonored, it adds time say 10 minutes for each click you do while under dishonor. Then when a bot gets reported the first time for leeching, it'll go back to town and continue to click enter mission and wrack up more and more dishonor/ hours of being unable to play.
No real person would sit there and keep clicking and so it will not affect anyone except the noobs who don't know what dishonor is or whatever.
I think this would be an almost perfect way of making bots less used in pvp/ events like costume brawls. Seeing as, if they get reported once, they would effectively stop the bot from working for easily several or more hours.
ADDED
Warning will send a message in chat or some other function that will state the first time you click enter mission while dishonored. It will say something along the lines of "You have been dishonored, you can not join until the effect is gone. Repeated attempts at joining will cause more dishonored points and more time needing to wait until you can rejoin.
Something like that, but it will only show up the first time when you get your newly dishonor. Repeated clicking after that will give no warning.
My suggestion is that if you have dishonor and try to enter mission while dishonored, it adds time say 10 minutes for each click you do while under dishonor. Then when a bot gets reported the first time for leeching, it'll go back to town and continue to click enter mission and wrack up more and more dishonor/ hours of being unable to play.
No real person would sit there and keep clicking and so it will not affect anyone except the noobs who don't know what dishonor is or whatever.
I think this would be an almost perfect way of making bots less used in pvp/ events like costume brawls. Seeing as, if they get reported once, they would effectively stop the bot from working for easily several or more hours.
ADDED
Warning will send a message in chat or some other function that will state the first time you click enter mission while dishonored. It will say something along the lines of "You have been dishonored, you can not join until the effect is gone. Repeated attempts at joining will cause more dishonored points and more time needing to wait until you can rejoin.
Something like that, but it will only show up the first time when you get your newly dishonor. Repeated clicking after that will give no warning.
Kerwyn Nasilan
Maybe 1 min so if ou accidently hit enter after getting dishoner you dont have o wait double time.
Maybe if they get reported enough they will just get banned, I guess /signed.
Maybe if they get reported enough they will just get banned, I guess /signed.
Shayne Hawke
I definitely like where you're going with this, but I feel like it's missing something to prevent someone innocently clicking Enter Mission without realizing that they're dishonored of getting more dishonor.
t3dw4rd0
Make it if you click it more than twice while under dishonor, so stupid people don't get more than they deserve. Also put a message in chat saying "You cannot enter because you are under dishonor" or something for the first two times, then "10 Minutes has been added to your dishonor for attempting to enter again" or something like that.
MisterT69
mayb have like a purple haze effect as if your drunk so u know you're dishonored? idk, but the idea seems like it would work on paper, it's just the nub problem that needs to be addressed.
wind fire and ice
/signed
Just have a short warning first time you get dishonor so noobs dont get confused and run up 3hour dishonors.
Just have a short warning first time you get dishonor so noobs dont get confused and run up 3hour dishonors.
zelgadissan
100% /signed, especially with the addition of a first time "warning". If new players can't lrn2read, then by all means let them get hours of dishonor. They'll never forget again.
dilan155
add your idea and misters idea and make the massage like that of when you try to enter an area with a bigger party than it can handle so it has a big noise and a flashy way to warn people.
Rak Orgon of Beowulf
/signed this idea is one of the better ones. as long as the warning message appears the first time...first time i got dishonor (d/c'd twice in a row) i clicked a few times like WTF?
again /sign... bot hate is ftw
again /sign... bot hate is ftw
Chronos the Defiler
Anyone with Post-Process effects disabled will not be able to see the effect...and it would be ultimately useless...otherwise it would work fine :P
Shasgaliel
Very nice idea. I would add that if the dishonor gets till 3 or more hours it is almost sure that it is a bot and should get a ban. It will make tracing bots much easier. On the other hand I can imagine some frustrated player just clicking enter mission 20 times per second. But in this case a ban would be nice to calm him down.
MercenaryKnight
I figured that having a warning that will pop up in the dialogue box or message will be enough to make the person refrain from repeatedly hitting enter mission.
The warning can happen the first time you get dishonor/ get sent back to the arena. Then it could be coded to do that every time you first get sent back to town with dishonor. So no one would complain they didn't know.
I am hoping that regina will see this and that they will hopefully be able to implement this in the near future.
The warning can happen the first time you get dishonor/ get sent back to the arena. Then it could be coded to do that every time you first get sent back to town with dishonor. So no one would complain they didn't know.
I am hoping that regina will see this and that they will hopefully be able to implement this in the near future.
Sage Tylos
Umm, I'm quite ignorant about how bots function, but, aren't they programmed to some extent by the person using them? What's to stop the person from setting up the bot to be able to realise it has 'dishonorable' and to just wait until the timer expires?
MercenaryKnight
A bot that sophisticated would need a real program. And it would need pixel detection to realize the square of dishonor on the screen.
Most bots are made through scripts. Repeatedly clicking on the enter mission spot then when in game hitting skills and c spacing over and over again.
Thus, for about 99% of the bots it'd screw them up, and I don't think their is even 1% using a real program bot that would be capable of pixel detection and integrate itself into gws to know it was dishonored.
Most bots are made through scripts. Repeatedly clicking on the enter mission spot then when in game hitting skills and c spacing over and over again.
Thus, for about 99% of the bots it'd screw them up, and I don't think their is even 1% using a real program bot that would be capable of pixel detection and integrate itself into gws to know it was dishonored.
MercenaryKnight
Bump this up due to another post being made about similar problem.
JASON626
/signed decent idea.
This would get rid of most novice macro bots made by people.
This would get rid of most novice macro bots made by people.
Eragon Zarroc
yeah, i think that anyone capable in the field of botting would be able to navigate around the dishonor buff. but /signed. it will rid us of very noob botters and doesn't affect anyone elses' play experience negatively unless they just accidentaly hit enter (in which case is just oh well, pay more attention next time)
Dookie Dookz
/signed
If dishonored, upon pressing the Enter button, a confirmation box should appear to confirm "Yes" or "No" and telling you the consequences of each action. Maybe even go a step ahead and physically type in "Yes" or "No" similar to what you would do before completing the deletion of your character. Only happens when dishonored.
If dishonored, upon pressing the Enter button, a confirmation box should appear to confirm "Yes" or "No" and telling you the consequences of each action. Maybe even go a step ahead and physically type in "Yes" or "No" similar to what you would do before completing the deletion of your character. Only happens when dishonored.
Copenhagen Master
I sign, but they should also DEDUCT!! factions from there leeching gains say each time you get dishonorable you lose the factions that were gained or something to that effect
StormX
/SIGNED
go red engine 12 chars
go red engine 12 chars
AngelWJedi
/SIGNED
yes i hope this stops bots. because it seems a few people rather report those that lag or dc'd in pvp areas then the bots. their have been times i had bots in my group but i couldnt leave their but with out getting reported myself.
yes i hope this stops bots. because it seems a few people rather report those that lag or dc'd in pvp areas then the bots. their have been times i had bots in my group but i couldnt leave their but with out getting reported myself.
Cyric The Liar
/signed
Good idea, but I'm not holding my breath.
Good idea, but I'm not holding my breath.
newbie_of_doom
Something like this idea would be good, as long as you avoid clicks by accident from being punished. + Bots should just be banned anyway
Reverend Dr
Horrible idea. It is not that difficult to adapt the bot code. It would work for a day or two, that's all. If the change does not address the reason why botting is used (effort vs reward) it is going to have a stronger effect on the people that aren't botting.
I KNOW HOW ABOUT WE PUT IN A CAPTCHA THAT IS REQUIRED TO ENTER ANY ARENA!!!!!111
I KNOW HOW ABOUT WE PUT IN A CAPTCHA THAT IS REQUIRED TO ENTER ANY ARENA!!!!!111
Tullzinski
/signed
perhaps you could have a random time setting between 10min-99 min clearly displayed such as:
"Due to dishonor you are unable to enter ANY Arena for XX minutes any attempt to reenter before this time expires will result in additional 2 hour penalty per attempt"
This would keep the botter from just reprogaming the bot to click enter mission at the end of the set time expiration of 10 minutes. A longer possible maximum cool down time would make it much less profitable for the bot to sit idle(1 1/2 hours for example) waiting to reenter.
Death to bots!!!
perhaps you could have a random time setting between 10min-99 min clearly displayed such as:
"Due to dishonor you are unable to enter ANY Arena for XX minutes any attempt to reenter before this time expires will result in additional 2 hour penalty per attempt"
This would keep the botter from just reprogaming the bot to click enter mission at the end of the set time expiration of 10 minutes. A longer possible maximum cool down time would make it much less profitable for the bot to sit idle(1 1/2 hours for example) waiting to reenter.
Death to bots!!!
Nodair
This will not stop people from setting a timer that they could use once they get out of the map. It wouldn't be hard you would just have to have it check for ip changes, then tell it to wait 10-20 mins after each map just in case so it will not stop all of them but it would stop the follow bots.
assassin shaun
/signed
this is a great idea, and if noobs keep clicking enter mission then they deserve a longer dis honor, then they wont do it again
hopefully it should stop bots / make them easier to catch
this is a great idea, and if noobs keep clicking enter mission then they deserve a longer dis honor, then they wont do it again
hopefully it should stop bots / make them easier to catch
Owik Gall
Bot haters is never a problem because everyone is ok with that except the bot users, who anyways are breaking the agreements and enemies of anet the second they start using a bot. Bot hating is always welcome.
/sign
/sign
Balky
Signed !!!!!!!!! Don`t limit it to only give them the dishonour tag and warn them about trying to re-enter......fine them the equivalent of 5 wins of faction gain for whichever arena they`re in, IE:-
JQ 5 x 3500
FA 5 x 2500
AB 5 x 1500 ( as an average )
plus wipe every bit of Balth faction they have.
That will soon make them take notice
JQ 5 x 3500
FA 5 x 2500
AB 5 x 1500 ( as an average )
plus wipe every bit of Balth faction they have.
That will soon make them take notice
Liam016
/signed
This is by far the best method i've heard to tacle leeching.
This is by far the best method i've heard to tacle leeching.
Hailey Anne
/Signed.
To those saying that they will just write new code to wait 10 minutes..atleast thats 10 minutes without that bot.
To those saying that they will just write new code to wait 10 minutes..atleast thats 10 minutes without that bot.
Reptile
/signed
I like the way this though is going. Might need some fleshing out with practical application. The introduction of this would not be 'an empty, fruitless solution', as even if the bots waited 10 min by default, would it not do that *every time*? Not just when it was dishonored? That would make botting less effective too...
Just my thinking on the matter...
I like the way this though is going. Might need some fleshing out with practical application. The introduction of this would not be 'an empty, fruitless solution', as even if the bots waited 10 min by default, would it not do that *every time*? Not just when it was dishonored? That would make botting less effective too...
Just my thinking on the matter...
Giga_Gaia
There probably aren't many who can write a program to counter something like that like the OP has said. And even if there are, those people would probably be programmers IRL and I would imagine have better things to do with their time?
Anyways, this is probably the best idea proposed so far, so it gets my vote.
Anyways, this is probably the best idea proposed so far, so it gets my vote.
Reverend Dr
This will be a waste of developer time. After a couple of days the bots will adapt, not too hard to put in a pixel check and won't click enter mission of dishonorable is up. This kind of check is incredibly easy to do, it doesn't even take a real programmer to create this a script kiddy can do it.
Actually I wouldn't be surprised if most bots already have this. A history of constant clicking of 'enter mission' while under a dishonorable hex is a giant indication that it is a bot script.
Half the bots right now it won't even phase, the other half will have adapted in a week. After that, the situation will be exactly the same as it is now, only with developers have wasting time to implement a wortheless 'countermeasure.'
Actually I wouldn't be surprised if most bots already have this. A history of constant clicking of 'enter mission' while under a dishonorable hex is a giant indication that it is a bot script.
Half the bots right now it won't even phase, the other half will have adapted in a week. After that, the situation will be exactly the same as it is now, only with developers have wasting time to implement a wortheless 'countermeasure.'
frikkus
/signed.
I'm not holding my breath though. I love Aspenwood, but there are leechers and bots there I know by name that have been leeching and botting since before I even started Factions.
I started playing on the Kurzick side out of frustration, and now we have Verata's Gaze twits, on top of the usual bots, sucking the fun out of that side. I understand staff are probably busy with GW2, but after the management, (or distinct lack thereof), of leeches and bots I doubt very much I'll be bothering with GW2.
I have a fantastic screenshot from a few weeks ago where 7 out of the 8 luxon team were leechers.
http://s481.photobucket.com/albums/r...rent=gw135.jpg
I'm not holding my breath though. I love Aspenwood, but there are leechers and bots there I know by name that have been leeching and botting since before I even started Factions.
I started playing on the Kurzick side out of frustration, and now we have Verata's Gaze twits, on top of the usual bots, sucking the fun out of that side. I understand staff are probably busy with GW2, but after the management, (or distinct lack thereof), of leeches and bots I doubt very much I'll be bothering with GW2.
I have a fantastic screenshot from a few weeks ago where 7 out of the 8 luxon team were leechers.
http://s481.photobucket.com/albums/r...rent=gw135.jpg