Every profile I've looked at has invalid XML Incorrect: Code: <HotSpots> <Hotspots XYZ="...."> </HotSpots> ===== Correct Code: <HotSpots> <Hotspot XYZ="...."> </HotSpots> or Code: <HotSpots> <HotSpot XYZ="...."> </HotSpots> I have absolutely no idea how these profiles could have ever worked in the past, but to try and make this work now without breaking anything would be more effort then profile creators updating to valid xml.
From what I've seen yes and I can't understand how it worked at all because internally they are two different objects which is why they are named differently. (Hotspots are a list of individual hotspot)
Version 344 Code: Quest Behaviors have been extracted from the core and are now compiled at run time so that users may examine and modify them. Qb's are compiled at start up one time, reloading them without restarting the bot is not currently planned. A lot of the older qb's don't have the best coding standards that the newer ones do (Synthesize is a much better example to look at then huntbehavior) Api: CraftingManager.SetQuality has been added, look at Synthesize.cs for context Bug fixes: Bot will now default to orderbot on startup for the first time.
any way to get quest behaviors loaded before plugins? I had a few tags in plugins that extended behaviors that have stopped working.
<HotSpots> <HotSpot XYZ="...."> </HotSpots> is causing it to return as 0,0,0 for me in GrindAreas. For the correct values, I need to use: <Hotspots> <HotSpot XYZ="...."> </Hotspots>
3.1 changed a ton of things under the hood and updating the bot to be compatible is going to be a lot of work. Can't give any etas but don't expect anything today.
Was hoping for a staged release of some kind, but all in good time. Hope you're stocked up on coffee and snacks =)
Don't hurry Better a complete view into that stuff as something fast released. Ofc I miss my FateBot, but I can sure wait a bit longer =)
Everything is a little donked and a few important things are majorly donked so doing a staged release doesn't make much sense.
Rofl, it's fine, I just had this dream while the servers were down that I'd be able to get through the new combat content by being lazy soonish after launch, but no worries man XD
Version 347 Code: Initial release for 3.1 Version of final fantasy Everything except queuing for dungeons should be working, please report any issues in the support forum with a full log file attached. Api Gameobject.Status is now deprecated, they totally reworked how this functions.
the exact momment you posted this i get an email sayingdont expect rb to be working today....soooo this is odd
