Jump to content

maylu

Members
  • Posts

    92
  • Joined

  • Last visited

Posts posted by maylu

  1. 21 hours ago, LukeJudd said:

    People are still missing the issue here. They 100% have some way to connect the botting accounts together. I accidentally logged an account in from my native IP while 6 other bots were running properly through proxies. 10 min later the revealed account and all bots that had been running at the time were DCD and banned at the same time. 

    Are the accounts being created on separate IPs as well? IP is logged into their database when the account is created. Depending on their GM policies any IP that account is attached to will be banned.

     

    On 7/16/2018 at 2:21 AM, Bambo said:

    I use proxycap. Still got mass banned many times.

    Also it is not 95% reports. All accounts gone in the same Minute and Multibot ban as reason. That is not because of reports.

    Hopefully you're tunneling with puTTy and proxycap, and that the program will only accept a connection from an assigned IP through proxycap, which I'm going to assume you have done. If not, I would look into doing this. 

    Depending on the investigation and procedures of the private server, they may log all bans at once. You see this happen on servers such as Paymane (Warmane). The reason behind this is to prevent botters and hackers from trying to save the account or log out and change the IP the account connects with. I can tell you without a doubt that almost all bot bans are caused by player reports or flags generated by their anti-cheat (or manual server queries for previously banned IPs) that require manual review from previously banned IPs.

     

    7 hours ago, milkme said:

    I believe one banwave was caused by proxycap actually crashing and me not noticing as at some point I think it wasn't on, maybe I even fucked something up myself, but that was before the banwaves so my memory on that isn't so clear. As long as proxycap is running the proxies can go down no problem, it won't let you log in because the proxycap rule still tries to send you through the proxy, but if proxycap itself is down then there are no rules active unless you somehow block the respective wow.exe's through other means.

    There are many ways to block your wow.exe from connecting with your IP using puTTy/proxycap. Some quick Google searches will answer this.

  2. Greetings,

    So I'm new to the vanilla botting scene (usually bot on tbc) and was wondering what is causing this issue:

    I enabled CTM (click to move) and it doesn't respond to the movements when in windowed/windowed maximized mode. It stops short of the distance it is told to travel.

    I've messed with a combination of the settings below and it still doesn't work

    -VSync
    -60hz (in-game and monitor is set to this)
    -Hardware cursor

    Any ideas?

  3. My bot will die after 'x' amount of times (sometimes even just once) and then it  will refuse to move from graveyard. It will spam "You are dead" in-game as if it's trying to do something. When I stop the bot and restart it, it will start to run to corpse, but pause and spam "You are dead" yet again.

    Here is log at the time it begins to act weird.

     

    Quote

    00:25:45 - [Resurrect] Player dead
    00:25:45 - iWarlock Pro initialized.
    00:25:45 - iWarlock Loaded
    00:25:45 - [MoveDuringCombat] Loading.
    00:25:45 - [MoveDuringCombat] Loadded.
    00:25:45 - [Quester] Started
    [D] 00:25:47 - [Resurrect] Blacklist corpse position -3366.588 ; -3127.544 ; 25.67173 ; "None" - Radius: 30
    00:25:47 - AvoidIt loaded.
    [N] 00:25:50 - [Path-Finding] FindPath from -3291.665 ; -2439.178 ; 18.59659 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:25:50 - [Path-Finding] Path Count: 14 (745.0087y)
    00:25:52 - [Resurrect] Player dead
    [N] 00:25:57 - [Path-Finding] FindPath from -3291.597 ; -2452.335 ; 18.61082 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:25:57 - [Path-Finding] Path Count: 13 (731.7216y)
    00:26:03 - [Resurrect] Player dead
    [N] 00:26:08 - [Path-Finding] FindPath from -3305.087 ; -2505.738 ; 20.37889 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:26:08 - [Path-Finding] Path Count: 13 (676.9248y)
    00:26:15 - [Resurrect] Player dead
    [N] 00:26:20 - [Path-Finding] FindPath from -3318.237 ; -2557.797 ; 16.86694 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:26:20 - [Path-Finding] Path Count: 13 (623.1782y)
    00:26:26 - [Resurrect] Player dead
    [N] 00:26:31 - [Path-Finding] FindPath from -3331.363 ; -2609.761 ; 9.440998 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:26:31 - [Path-Finding] Path Count: 12 (569.1287y)
    00:26:37 - [Resurrect] Player dead
    [N] 00:26:42 - [Path-Finding] FindPath from -3331.576 ; -2662.568 ; 10.60813 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:26:42 - [Path-Finding] Path Count: 11 (515.3978y)
    00:26:46 - [Logging]20 Jun 2017 23H04.log.html copied on your desktop.
    00:26:49 - [Resurrect] Player dead
    [N] 00:26:54 - [Path-Finding] FindPath from -3328.632 ; -2715.922 ; 22.79119 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:26:54 - [Path-Finding] Path Count: 11 (462.715y)
    00:27:00 - [Resurrect] Player dead
    [N] 00:27:05 - [Path-Finding] FindPath from -3325.68 ; -2769.437 ; 17.5921 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:27:05 - [Path-Finding] Path Count: 11 (408.9409y)
    00:27:11 - [Resurrect] Player dead
    [N] 00:27:16 - [Path-Finding] FindPath from -3331.966 ; -2820.081 ; 11.85611 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:27:16 - [Path-Finding] Path Count: 9 (354.5317y)
    00:27:23 - [Resurrect] Player dead
    [N] 00:27:28 - [Path-Finding] FindPath from -3366.099 ; -2861.753 ; 12.77089 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:27:28 - [Path-Finding] Path Count: 9 (300.6766y)
    00:27:34 - [Resurrect] Player dead
    [N] 00:27:39 - [Path-Finding] FindPath from -3391.683 ; -2908.315 ; 12.12286 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:27:39 - [Path-Finding] Path Count: 7 (246.5999y)
    00:27:45 - [Resurrect] Player dead
    [N] 00:27:50 - [Path-Finding] FindPath from -3403.56 ; -2960.475 ; 24.19615 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:27:50 - [Path-Finding] Path Count: 7 (192.7272y)
    00:27:57 - [Resurrect] Player dead
    [N] 00:28:02 - [Path-Finding] FindPath from -3415.529 ; -3013.045 ; 24.88643 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:28:02 - [Path-Finding] Path Count: 7 (138.8732y)
    00:28:08 - [Resurrect] Player dead
    [N] 00:28:13 - [Path-Finding] FindPath from -3421.45 ; -3065.526 ; 23.14082 ; "None" to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth)
    [N] 00:28:13 - [Path-Finding] Path Count: 4 (84.83084y)
    [D] 00:28:18 - AvoidIt Mark spot: -3355.839 ; -3072.996 ; 22.33091 ; "None"
    [D] 00:28:19 - AvoidIt Generate new path to: -3366.588 ; -3127.544 ; 25.67173 ; "None"
    [N] 00:28:19 - [Path-Finding] Partial result: -3392.621 ; -3105.457 ; 22.80346 ; "None" (Azeroth_37.82273_38.36116) to -3366.588 ; -3127.544 ; 25.67173 ; "None" (Azeroth_37.86415_38.31236)
    00:28:20 - [Resurrect] Player retrieve corpse
    00:28:20 - [Fight] Player Attacked by Crimson Whelp (lvl 25)
    [D] 00:28:22 - AvoidIt Mark spot: -3492.313 ; -3013.1 ; 18.60295 ; "None"



     

  4. Greetings WRobot community and @Droidz

    Does anyone else have issues with WRobot using an extremely high amount of CPU? It's impossible to run more than 4 bots on my system (and this is on an i7 5k cpu)

    It takes on average 3 to 7 times more CPU power than the WoW.exe to run the connected bot.

    Does anyone else have this issue? (and no, it doesn't matter which fightclass, profiles, or product I'm using)

  5. I'm getting issues when Warmane's server goes down. The bot will reach the Server Selection screen and get stuck on Authenticating. Is there anyway to fix this? The server is definitely up, but isn't receiving an update from the server. 

    edit: This is a pretty big issue because it ultimately stops all bots. Can I place a manual delay on the relogger, say, 10 minutes?

    edit 2: Just to clarify, I'm speaking of the bot's relogger feature, not the separate program.

    edit 3: Found the issue on the bugtracker: 


    but I'm still curious to know if I can add a manual delay

×
×
  • Create New...