Apoc
Well-Known Member
- Joined
- Jan 16, 2010
- Messages
- 2,790
- Reaction score
- 94
Hi Apoc,
Thanks for the last reply. You're right, it only supports hotspots in subprofiles and not the top level profile.
As others have mentioned, it does look like the tool mixes up MinLeval and MaxLevel only on the top level profile, and also switches TargetMinLevel and TargetMaxLevel in subprofiles.
You mentioned earlier in the thread that you have another tool that parses the X's and Y's and finds the Z's - since you can't package it, can you at least hint at a name so perhaps us DIYers can find it and try it?
HB currently spits this out with Z="findhighest"
Code:[2:48:24 PM:811] Value "findhighest" in "Z" attribute is not supported! Expected floating type. - From: Honorbuddy [2:48:24 PM:934] Attribute Z of floating type was missing in "Hotspot" tag. - From: Honorbuddy
I'd like to be able to confirm those bugs, but I can't. I can't reproduce them at all.
As for "findhighest" it seems someone broke it in the newest release of HB.
Edit; "findhighest" works fine for me. It's only valid on hotspots, so could you confirm that it's being used in other elements?
Last edited: