Since patch 1.3.5 you can no longer create your own model frames. Now it will display the following error: Model are marked as Blizzard Only and cannot be created by users. This has screwed up my UI, because now you can't duplicate/resize/move the models from the console panel.
Yes, this actually made me pretty angry. It seems most of the frames in the InfoPanel cannot be overridden either. Since it is one solid chuck containing everything from weapons, armor, the unit wire frames, and most importantly to me, the behaviors, I can no longer create my own specific UI to show buffs and debuffs. I'd have to build a UI AROUND the standard layout, which kind of defeats the purpose of a custom UI to begin with.
Could you post the script you used for moving the Weapon and Armor icons as an example? I know I can move the entire InfoPanel, but as of 1.3.5, any attempts to use the frame type "BehaviorBar" or "UnitWireframe" returns an error saying it is a Blizzard only frame and can't be used.
Thanks Helral. I don't know how you keep all this stuff straight in your head. I'm having a hell of a time =P
So to clarify, as of 1.3.5, Blizzard has disallowed the ability for users to create additional frames of certain types, but you can still modify the existing ones.
I am so ridiculously annoyed by that fact. By being able to create frames, you could use anchoring as it was intended to, and not just make a bizarre amount of offsets that would breat at any moment. The custom UI I made was a pain to do my just moving around items, and it was so painless and seamless to do so with user created items. Why mark them as blizzar only, that seems rather draconian.
Since patch 1.3.5 you can no longer create your own model frames. Now it will display the following error: Model are marked as Blizzard Only and cannot be created by users. This has screwed up my UI, because now you can't duplicate/resize/move the models from the console panel.
damn that sucks :S
Would using images instead of models work for your usage?
What about making it with triggers? Is there some way to attach a model to the screen? I think it can be achieved using portraits.
Yes, this actually made me pretty angry. It seems most of the frames in the InfoPanel cannot be overridden either. Since it is one solid chuck containing everything from weapons, armor, the unit wire frames, and most importantly to me, the behaviors, I can no longer create my own specific UI to show buffs and debuffs. I'd have to build a UI AROUND the standard layout, which kind of defeats the purpose of a custom UI to begin with.
@BloodLX99: Go
you should still be able to move the default Behaviorbar/Wireframe/Experience Bar/etc. around.
Hmmmm will look into it just to be certain.
See attached image. Changes in it:
@Helral: Go
Could you post the script you used for moving the Weapon and Armor icons as an example? I know I can move the entire InfoPanel, but as of 1.3.5, any attempts to use the frame type "BehaviorBar" or "UnitWireframe" returns an error saying it is a Blizzard only frame and can't be used.
@BloodLX99: Go
you probably made a mistake with the naming then. cause that would cause that error to appear.
Attaching all the UI files used by my map atm. Have not the time to figure out which one it was exactly.
@Helral: Go
Thanks Helral. I don't know how you keep all this stuff straight in your head. I'm having a hell of a time =P
So to clarify, as of 1.3.5, Blizzard has disallowed the ability for users to create additional frames of certain types, but you can still modify the existing ones.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI am so ridiculously annoyed by that fact. By being able to create frames, you could use anchoring as it was intended to, and not just make a bizarre amount of offsets that would breat at any moment. The custom UI I made was a pain to do my just moving around items, and it was so painless and seamless to do so with user created items. Why mark them as blizzar only, that seems rather draconian.
Go play Antioch Chronicles Remastered!
Also, coming soon, Antioch Episode 3: Thoughts in Chaos!
Dont like mapster's ugly white? Try Mapster's Classic Skin!