FYI will not scan nodes currently. It will scan mobs. Scan for nodes is currently not working correctly and was causing the delay. We will be working on a fix but for now it should still work very well. Combat is fast again and etc as far as I can tell.
Walter removing a lot of our "fixes" now that BW core has them integrated. So if you have last nights build and you are noticing delays, update to the current test build. Smoothest I've ever seen it. Way to go Aevitas!
Hi walter, I thought I'd try out your latest test build (137), since mine is a few weeks old, but I can't start it without the following errors: DefaultCombat was the only folder I had in Routines, and I did try restarting everything. It was tested on a character with a Vanguard/Assault build. And yes, I have a sneaking feeling that I've missed something painfully obvious, but my brain is too tired to work the problem today. EDIT Corrected my test character's build.
Dev, I updated today during lunch on one of my bots and was able to use my Gunnery commando with no problems. Everything runs much smoother Walter, thanks. Near as I could tell before I had to leave again, nodes appear to be working fine. Thanks!
Thanks Jests. It looks like the kind of error you get when you mix folders or have an extra folder in Routines, but neither is the case here, so I'm still stumped. I'll try this out on my Jedi Knight and see if the errors still occur. EDIT The same issue exists for my Guardian/Vigilance, on a different machine. I simply moved the old folder and dropped the new folder in, but the same errors occurred upon starting the bot. @Jests = was the build you tested at R137?
Weird... have you tried just completely reinstalling the routine just to see if something weird happened last time you put the folder in there? That happened to me once.
Problem solved, and as expected, it was all me. I had created a few extra MercHelper files to test various rotations after I last updated a few weeks ago, and they were both left there after I updated this time, right next to the latest MercHelper file. Deleted, and issue resolved. I knew is was something related to my foggy brain today... EDIT On another note, it seems that Aevitas has been hard at work, because yet another version is BW is now available. Cheers!
New issue regarding Guardian/Vigilance: The latest test build (137) now starts correctly, but my character won't move after starting the routine. The log just stops here: I've gone back to using an older working revision for now until we can get to the bottom of this. Cheers, -D
I had that problem once with a previous build and when I restarted my computer it was fixed... you tried that?
I haven't tried restarting, but I think the issue might relate to moving more than one hop with the latest (1006.399) BW build (just uploaded). So far, on the new and old Walt builds, when using this latest BW update, my character pauses, with no extra log lines, when mobs are more than one hop away. I applied the previous BW update again (1004.397), and multiple hops are again working as expected. Is anyone else seeing this behavior?
I was having that problem (it was REALLY bad) until I got the newest version of walter's. I didn't watch it for long before I had to leave again, though.
Per the other (Pindleskin) thread, I think this is a R399 bug. The bot only moves whenever baddies are within one hop, so that might be why it appeared to be okay. Reverting back to 397 should fix the issue until Aevitas releases a new version.
Yea I talked to fearless leader my self and tested update 400 for last 30 mins for him. Let me know if you have anymore issues. Vendor also works very very nice now! PS I should be posting my update will all class support and major fixes later. I was just trying to get to the bottom of other issues that came up since loot targeting provider blah blah blah.
Let me know if you are having death bugs. My guy died and didn't respawn but who knows. I change so much shit at times lol.
