What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

<MoveTo Nav="Fly" Why doesn't code work in profile?

Ruinit

Member
Joined
Nov 1, 2010
Messages
992
Reaction score
4
Code:
<QuestOrder>
    <MoveTo Nav="Fly" X="957.8577" Y="353.651" Z="451.7675" />
	<PickUp QuestName="Meet the Scout" QuestId="32246" GiverId="64610" GiverName="Lyalia" />	
  </QuestOrder>

Will run ground mount and run to spot but not fly? Yes I have flying mount, yes I can fly , yes in correct zone, yes current hb release.

Thanks
 
Try <CustomBehavior File="FlyTo" DestName="xxxxx" X="xxxxxxx" Y="yyyyyyyy" Z="zzzzzzzzz />
 
Code:
<PickUp [FONT=Verdana]Nav="Fly" [/FONT][FONT=Verdana]QuestName="Meet the Scout" QuestId="32246" GiverId="64610" GiverName="Lyalia" [/FONT][FONT=Verdana]X="957.8577" Y="353.651" Z="451.7675" />
[/FONT]
 
Try <CustomBehavior File="FlyTo" DestName="xxxxx" X="xxxxxxx" Y="yyyyyyyy" Z="zzzzzzzzz />
Why use custombehavior when hb has build in Nav="Fly" built in now?

Hi, all,

Seems the Nav="Fly" attribute got supported in almost every profile element, except the most important one?MoveTo.

We have no clue how an oversight like this occurred, but it did. The issue is captured as bug report HB-126 ("MoveTo does not support Nav="Fly" "), and is still in progress. No ETA.

The work-around for now is the suggested FlyTo Quest Behavior. Sorry for the inconvenience.

cheers,
chinajade
 
Hi, all,

Seems the Nav="Fly" attribute got supported in almost every profile element, except the most important one?MoveTo.

We have no clue how an oversight like this occurred, but it did. The issue is captured as bug report HB-126 ("MoveTo does not support Nav="Fly" "), and is still in progress. No ETA.

The work-around for now is the suggested FlyTo Quest Behavior. Sorry for the inconvenience.

cheers,
chinajade

Thanks for the info CJ! Thought it was me doing something wrong again ... lol
 
Hi, all,

Seems the Nav="Fly" attribute got supported in almost every profile element, except the most important one?MoveTo.

We have no clue how an oversight like this occurred, but it did. The issue is captured as bug report HB-126 ("MoveTo does not support Nav="Fly" "), and is still in progress. No ETA.

The work-around for now is the suggested FlyTo Quest Behavior. Sorry for the inconvenience.

cheers,
chinajade

Is there a way to check the status of bugs online?

Also, Nav=Fly also does not appear to work with the <Objective> tag, is this part of the same bug?
 
Last edited:
AFAIK there is no way to check the report current status but you can check http://updates.buddyauth.com/GetNewestChangelog?filter=HonorbuddyBETA constantly to see the beta change log against your issue to see weather its fixed or not.

I've also posted on the feedback forum a suggestion so we can have similar feature of a online change log were we could potentially track bugs and other stuff or at least what we report to them over here:
https://www.thebuddyforum.com/honor...ck-honorbuddy-improvements-3.html#post1568986
 
The bug reports are internal only, although you could suggest a read-only version but for security reasons I'm not sure it would be allowed.
 
The bug reports are internal only, although you could suggest a read-only version but for security reasons I'm not sure it would be allowed.
Nevertheless they do list the beta change log and the rest is probably there somewhere on the archive as well so rather then placing it like that making an actual changelog page would be a lot better to track everything.

And they could place it internally on the buddyauth page so only people with key have access to check it or something
 
Back
Top