Search results

I will have a new build out today that fixes this problem properly. Sorry for the delay!

Your CreatureId for "VendorNPC" is wrong. That is a GUID (they are different things). Your RepairNPC also has no CreatureId.

Medic's work fine. What exactly is your issue? "It's broken" isn't a valid issue.

Walk up to the Vendor you want to add in-game, and (with the bot running) hit Alt+Shift+D. Information about the current target will be dumped to the bot window, where you can pull the location information (already in XML format).

Are you running ShadowPlay? Or any other video capture software? (Fraps, OBS, XSplit, etc) They are known to break the bot unfortunately. Close them if you are.

Use the "CSIAction" tag. <CSIAction QuestId="-1" QuestObjective="-1" QuestName="Unknown Quest Name" KeypadOrder="1,2,3,4,5" YesNoOrder="Y, N, Y, Y" FailIfNoCSI="false" /> The usual quest-related attributes are there (QuestId, QuestObjective, etc) KeypadOrder is only used for CSI's that are...

I see no problem there? Be more specific please?

No problem! You can do other things while the game is in the background. You just can't minimize it to the tray, because Windows won't send certain events which the bot needs to function properly. I'll add some code to "unminimize" the game if it detects it minimized.

Your logs don't seem to mention anything auth related. However, it does randomly fail to execute properly. (Usually happens because you minimized the game)

I'm not sure what exactly you have bound to "C" and "F". The communicator is the default binding for C. Could you be more specific?

Using the auto-generated tags isn't 100% correct. You may need to actually go and put down a correct hotspot for the collect tags. (The positions generated by the plugin are pulled from the game files, so there may be a tree or something there.)

Use the object browser in VS for your API.

That's a profile issue. Not an issue you'd find in the manual. (Which is literally those 4 steps)

Wildbuddy v1.1 Now requires Microsoft Visual C++ 2013 Redistributable Package (x64)Download link Reporting BugsPlease report confirmed WBcore bugs to THIS thread! When reporting a bug, please include your full log file (found in your bot folder under the "Logs" directory, sort by creation...

I need a lot please! Also, make a new thread in the support section if you could.

Please restart your bot, and test telegraphs again. They should now work! (I have some slight updates to do still, but they should at least be mostly usable now!)

Sounds very strange. Do you have logs for when this happens? I consistently run more than 3 without any issues. (Not that it helps your specific case) We also have users who run 10+ at times without problems.

No. When the Avoid tag runs, it adds the location to the global list of "avoid this spot" basically. Once it runs, it stays there until you tell it to be removed (with the same tag plus 'Remove="true"')

Make sure you are using the BETA build (available in the first post of this thread). You are running the old release build (pre-F2P wildstar)

Thanks for the vote of confidence. Please enjoy your vacation!