zzz
-
Posts
27 -
Joined
-
Last visited
Content Type
Forums
Articles
Bug Tracker
Downloads
Store
Everything posted by zzz
-
Any idea if your VPN's detected by maxminds high-risk/fraud/anonymizer detection? Try with residential IP if you can acquire one.
-
Reason: Automatic Anti-Cheat Ban. - Silver hand
zzz replied to Andoido's topic in Quester assistance
Been trying to get banned on LH for some time now (with some success ?), I can safely say that on Lights hope is not detected by warden, or the -bphook works. I haven't renamed my .exe for this round of bans, was going to try it when I actually get banned next time. I am at this point, pretty confident that these bans are on LH are based on reports, GM's being more active or they have figured out some pattern that they can scan from their DB. I'm strictly questing, and from that perspective, my character looks pretty legit, no extra mob grinding - just the questing part. I've been keeping the thread below updated on my findings and good guesses. -
Updating this - 3 weeks mark will be reached 2 days, account still not banned for some reason.. Can we have a bit more information: What product did you use if not questing profile/grinding, automation? Or did you turn on the bot just at the character selection screen? Anything you could think of why players would report you?
-
This was what happened to me on LH on the very first ban as well, but not on the second.
-
Just updating the status of this experiment, 2 weeks of 24/7 botting, still no ban on LH.
-
I don't think it's detected either, or the -bphook flag works. One week of nearly 24/7 botting again ( ~22h/day is my realistic estimate ) - and I am pretty sure I was reported for being stuck in OG for hours. (Wrobot can't path to the building that this npc is at https://vanilla-twinhead.twinstar.cz/?npc=9317 @Droidz) Will keep you guys posted, I don't expect this account to last much longer, but we'll see.
-
Not sure if that would help, I think they would get wise pretty fast. Started new account, this time -bphook from the very beginning. I'll report back in a week!
-
Sadly, I was too distracted to catch what the name was, or what class he was on, just the level. ?
-
Well just banned again after a good solid week of botting ?. I saw a level 13 character run past me just as I got banned in a higher level area where he shouldn't be, so I'm pretty certain this was a manual ban. Botted 3 characters (tauren, undead and a troll) with 100% questing only, bot was up almost 24h/day ( ~i'd say averaging at 23h). Time to roll on ally and see how it goes there!
-
the -bphook causes some random crashes to the wow client, not very frequently. Logs don't have any indication on why this happens, wrobot seems to crash before the wow.exe, or it at least throws the crash error before wow's crash dump pops up.
-
Got banned 2 days ago on lightshope and re-created new account, been botting on that new account northdale for almost 48h now, just turned on that no edit memory, How fast do these bans normally come on lightshope-northdale guys? - Edit: Also, could you guys post what area you had been botting/what kind of bots (grinding, gathering, questing?) on before the ban happened?
-
Does the pathing for some reason prioritze walkable coordinates based on Z coordinate being relatively-extremely high or low compared to most of the path? This path has only very slight detour (not really even a problem or something I would complain about), but it for some reason really wanted to go up that little mountain. Most (if not all?) of the detouring paths I have seen have had one thing common: either relatively-extreme drop or increase in Z coordinates. Droidz, could this be it? relatively-extreme change in Z coordinates compared to other waypoints on the wrobot generated paths?
-
I'll just throw these in here. Ignore the mess, there just was a lot of mobs hotspotted in this quester, the random detour through the sea just shouldn't exist, no hotspots are there, yet it still wants to go there. More detours that shouldn't exist
-
I am sorry if I seem rude, that is not my intention. this pathing problem is just frustrating to everyone. thank you for the thousand needles fix, that solves the specific issue. Good work! But, it is non satisfactory solution in general related to this issue. Or am I not understanding this offmesh thing? I understood that all these offmeshed are hand crafted, is this something automated? if it is manual thing, it is not a solution.
-
I'm hoping other people would pitch in on this issue, otherwise this will stagnate on me trying to convince you that the pathing is broken and that making offmeshes is not the solution. Its great that you made that for the specific 1k needles case, but why is it not already part of the meshes, the clipheight is static number afterall and recast/detours supports this (maxclimbheight). ^ This could also work if you loaded the fence doodads in recast and applied the clipheight to those! But that would be just a nice-to-have-feature, the unstuck can handle fences right now just OK, so not saying more about that! The creator of recast/detour has also helped other people fix the stupid detours that wrobot is facing: https://groups.google.com/d/msg/recastnavigation/vDrxqlUl1B4/zIY72aHxXK8J (this looks exactly like some of the paths wrobot does, wrobot just takes much longer detours) How can we help you make the paths actually not do stupid things Droidz? Is this a math problem? Triangle extraction problem? Please, we all just want the pathing to work, share the problem, we will help.
-
It's all in this bugreport, but this is just one specific case, there are thousands of these problems all across the world.
-
I'll just post some screenshots, bot is ignoring Z coordinate completly. Edit these are part of the problem, but these are what I can 100% replicate every time.
-
Please read my edit on the post, I improved my reply on there.
-
I do understand that its not perfect - I'm not looking for perfect pathing, but 100% of the zones have bugs like this - every single zone -. Can't you at least take look, spend day or two improving the pathing? Making offmeshing better does not help at all. EDIT: I am going to mention, this isn't installation problem / addon problem / plugin problem / profile problem / or because of angry kittens. I am not the only one having these problems, everyone is. Everyone agrees that the pathing is bad and it should be at least at the level where you can safely AFK from your bot. And not come it being stuck in some random place unable to generate path up stairs, navigate around a cliff, not take 3000 yard detour for 200 yard path, getting stuck in the only water puddle in a zone, whatever the case might be.
-
No, no - you don't understand! We should not be responsible for fixing the paths. I have Profiles that will walk everywhere in the current world, why should I (or any other user for that matter, I am not speaking for only myself here) spend hundreds, or even thousands of hours on MANUALLY making meshes to the world? The pathing is BROKEN do you not understand this? Do you use your own product? It's generating these horrible paths everywhere very often, and its not right.
-
Yeah, I know. Improving offmesh does not help this issue, the issue is the fucking horrible pathing that seems to be getting worse and worse constantly. "strange" (read this as: idiotic bottish) paths (see the first post) static paths (mailbox -> auctioneer) changing (see the first post) bot taking huge detours (see the first post)
-
I know. adding improvements to the offmesh does not help with the pathing being horrible and constantly degrading on quality.
-
I was told that I should give you links to fix things faster. I was told that all this pathing poop is broken meshes, I'm leaning towards some wrong optimization on your end (as the paths have been better in the past). But people insisted that its just broken mesh generation, so here goes: stock go-to guide for everyone who intends to work with meshing recast detour: https://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/wow-memory-editing/317944-path-generator-recast-detour-wowmapper-step.html Unfinished project from a friend of mine to generate meshes, end goal was to generate meshes for sharpnav (c# recast/detour clone): https://github.com/miceiken/WoWMap Older project to generate meshes, should be relatively easy to port for different expansions if you have original MPQ's (not the pserver modified ones) : https://github.com/stschake/meshReader -- Need more help or resources? Give a shout on discord, we have people who will happily assist you to fix this pathing problem.
-
So, the pathfinder has recently gotten much much much worse and its not funny anymore. Droidz, you cannot just shrug it off anymore. Not going to beat around the bush, the pathing sucks, it absolutely sucks right now, its unusable for AFK botting, anyone who dares to leave their character unwatched with the pathing right now will absolutely not survive players watching the bot. Just look at this path for example, this is fucking ridiculous: (Picture provided by <not-to-be-named-person> in Schaka's discord) No one can call that pathing - especially when the bot cannot swim. An example of your average day with the pathing: Yesterday, my bot suddenly started taking huge detours in thunderbluff (this is AFTER the pathfinder crashed..) This is what the paths looked like before: OK, it looks bottish since it already doesn't take the most direct path.. but fine, its not too long detour and it doesn't walk too often. [N] 22:27:05 - [Path-Finding] FindPath from -1213,678 ; 93,96169 ; 133,7028 ; "None" to -1263,31 ; 44,5454 ; 127,545 ; "Flying" (Kalimdor) [N] 22:27:05 - [Path-Finding] Path Count: 7 (77,99333y, 0ms) But then this happened: [N] 00:12:20 - [Path-Finding] FindPath from -1209,873 ; 98,67814 ; 134,6978 ; "None" to -1263,31 ; 44,5454 ; 127,545 ; "Flying" (Kalimdor) [N] 00:12:20 - [Path-Finding] Path Count: 10 (120,5144y, 0ms) Extra 43 yard detour, yeah.. It started walking trough the fucking only puddle in thunderbluff and getting stuck in it, I was lucky to catch it happening, it would have been guaranteed ban if not. (^ this is from a bot that is running as a AH bot, so only walks between the mailbox and auctioneer, the paths never change. Or at least they shouldn't change.) This is just beginning, let me post few links from the front page of this bugtracker (disclaimer one of them was mine, it's ignored - but I assume this is because you're fixing all the other wrobot related bugs..) But yeah, all those posts from just the front page?! And more coming constantly, the different wrobot-related discords are getting multiple complaints about the pathing daily, this is not a long term business plan. Would you please recognize this as a problem? People are really unhappy with the pathing, especially anyone trying to work with questers. "Create offmesh path" seems to be the de-facto answer for these issues, but in all honesty - the pathing should be fixed. I'm not going to get into the remote pathing server at all, I hate all DRM's but its your decision to keep us out of it. We have multiple (cloud)system specialists in discord if you need help making it HA, we'll give you a hand. But I do pray that you would show us some love, the pathing is horrible, and it needs to be fixed. -Z
-
thousand needles bad meshes - tries to walk up huge cliffs (ignoring Z coordinate?)
zzz commented on zzz's bug report in Bug Tracker
adding more details - bot seems to be unable to path to any of these three gears in this picture (quest is grimtotem spying) specific coordinates ( try to navigate these from anywhere outside of these three big rocks/mountains, the problem will occur) <Vector3 X="-4922.240" Y="-1831.890" Z="80.820"/> <Vector3 X="-5139.710" Y="-1918.910" Z="89.188"/> <Vector3 X="-5184.790" Y="-2164.450" Z="94.634"/>
