Search results

25.

Are you running any screen capture software? This seems like an odd hook trampoline for DirectX.

Remember folks, the profiles are XML. You will have to escape certain characters within attributes and element values. && becomes &amp;&amp; > becomes &gt; < becomes &lt; Etc. Just google for XML escape characters.

Unfortunately, Wildstar is only a 10000th as big as WoW, so there isn't the massive community here, that we have for Honorbuddy. That said, there is little reason to quest in this game, when grinding can get you to 50 in about 1/2 the time. (Proven) When F2P came out, they changed up basically...

Official statement: Cats.

The bot is being update for v1.4.1.12929 0xBA624596 as this post is being written. Please note that from now on, a new .NET version, and new VCRedist is required. (See the first post for download details) We are updating, as Microsoft has called an End of Life to .NET 4.5.1.

Things.

*smells something weird*

Lalala....

The way the bot interacts with the game, will cause things like G-SYNC to die quickly. G-SYNC basically assumes that the game will be running a stable FPS (which it doesn't when the bot is running, since we're hooking some DirectX API). I suggest turning it off for botting. It's not a huge deal...

You'll have to have the item in your inventory (or know some Lua to pull it from the vendor). There is a hotkey (Alt + Shift + I) to dump your inventory to the log file. It is printed under the "debug" level, so it won't show in the UI, but will be in your actual .log file. It includes all sorts...

Use the custom Lua code for the event registration. // Generate quest profile tags RegisterEvent("QuestStateChanged", Events.QuestStateChanged, "function(queQuest, eState, unk) return queQuest:GetId(), eState, unk end"); // Quest pickup/turnin...

Unequip, and re-equip your gadget. Chances are it bugged out when you hit some loading screen. This is a bug in the game itself unfortunately.

I'm pushing yet another beta build, that should resolve the issue (hopefully) fully. It will let the auth fail a maximum of 3 times before kicking you off. The load balancing we use is causing the issues. This will at least fix it on the client side while we work on the server side.

To the best of my knowledge, nobody has been banned from Wildbuddy directly. Obviously if you're botting 24/7 or botting in high population areas, risks go through the roof. Wildbuddy is currently not detected, but that doesn't make it undetectable. I'd suggest not using any 3rd party stuff...

I know this is frustrating, but please grab the latest beta, and send me a log from when this happens again. I can't reproduce it on my end, so extra logging has been added to help.

Automatic restarts will happen when I figure out what exactly is causing the crashes. Until then, it's manual.

Folks, it was 3AM for me. Like most humans, I need sleep as well. The server is back up.

The timeout is to avoid staying too long at a hotspot. Not forcing it to stay. If there is nothing to kill, it will move to the next hotspot (since it assumes the area is cleared, and waiting around is pointless)

I need a full log of your error when it logs you out. A 2 line snippet doesn't help at all.