In reality the most effective botter is the guy who voke bots and then comes onto QCDN and denouces voke botting so that his opponents will decide never to use them, making himself the only one with the advantage.
Hmkiroko said:How about everyone in the Aery does a <t> prior to the window opening so everyone is on the same playing field? The claim bots target the mob in memory, so if a botter types <t>, it will come up with the mobs name instead of a basic <t>.
This might be effective due to the "guilty until proven innocent" methodology that everyone seems to adapt. Why not do it if you are innocent? Only the problem people would be reluctant to par-take in such practices.
Instead of everyone deviating to the norm of "botting" just because it is the equilibrium in the game, why dont we introduce measures (like the one I just mentioned) to increase the "stigma" value of botting. Since the simple <t> check is easy to do, and if caught in real time, in front of everyone, will have real reprecussions (at least hopefully) within our bot fearing server.
Image is everything, and by doing this, I believe people will save face and claim legitly as opposed to dragging their name through the mud if proven that they are not legitimate.
Unfortunately there are ways around this, so it's not a perfect solution, but I think it's a start.
Firestreak said:Anttaru I'm sure the best bots out there are flawless in design and compensate exactly for when the mob becomes vokable,
Firestreak said:the reason legit people get claims is either no one is botting, the bot is not built right(either it was always shitty or it was thrown off by an update) or the commands issued from the bot is delayed to the server by an unpredictable lag spike. If we were all playing directly connected to a LAN then voke botters would win every time 100%.
Mattaru said:Ant, the issue I have always found with /targetnpc is that if you are relying on a quick claim a mob could be closer than you than the NM and it will automatically target that pet or regular npc mob. I find that one macro reading:
/stnpc
/wait 0.5 (can assume that you will hit lag to delay, but I have used Charm on an NM before "target is already claimed" but not getting the claim with a 0.3)
/ja Charm/Provoke/ChiBlast etc
This relies on you spamming tab and being able to catch the mob name before it is fully popped. A good bot throws all that out of the window because it doesn't rely on a sense of the user.
EDIT: Raes the slippery-slope argument isn't appilcable because any other manner of cheating is detectable, so there is no slope to slide down.
Firestreak said:Not so sure that the <t> command thing would actually work, and even if it did people wouldn't want to alert the world exactly when a pop window was going to start even if they thought they all knew the exact window.
Anttaru said:Gah ! Very simular to what i wrote indeed. except <t> should be /targetnpc spammed before the actual catch macro is released.
Anttaru said:Remember. If we exacute the macro too soon, we reecieve a penality, so it's more of a timing thing than a speed thing, plus the lag issues not even the bot can correct. We can go against the bot. Remember. It's possible to claim NM and HNM before it even appears. Many of us have forgotten this. The later generation would have no idea of this. The bots true advantage, is that we wait for visual confirmation where as the bot already targeted the mob and is already processing the 2nd macro for the catch.
Mattaru said:Those players can continue playing if their image is tarnished by NA experience with those players unimpeded. Thus the one defecter still makes a logical decision making calculus lean to botting.
Hmkiroko said:I'm trying to discuss not how we can beat the bots using conventional means, but to try and discourage it's use even though Mattaru states that in equilibrium, everyone will bot.
Let's try and stay on topic.
Mattaru said:I just don't see why if I rely on a macro line which represents coding for an action that will adjust for the timing before an NM popping (red dot, name only in target window) can not be duplicated in a bot.
Link, self explanatory: http://www.youtube.com/watch?v=un2kC-AVLCs
Anttaru said:The Bot itself is a macro, and the difference between us and the bot is milliseconds. Sometimes the bot will win sometimes it won't due to lag.
Making the macro line that represents the fine tuned time code, is only usefull when used to end of a spam of the first macro.
exampe: "spam macro 1" = Hold ALT and rapidly press 1111111111111111
Upon the first glimpse of touchdown press ALT 2 (wherever the macro is set)
This would challenge the bot alot better than waiting for visual confirmation as in many cases we can target the mob before we see it.