RealUI beta
 

In order to prepare RealUI for its release, I need your help!! Specifically, I need to know what changes need to be made for your class/spec. I don't play all the classes so I don't know what changes will be necessary for things like the AuraTraker.

Known Issues:
Unit Frames: These are being re-writen and are currently in a rough state.
Skada: Division by zero

Bug Reports

• Check for errors. If you have any, there will be a red bag icon with the minimap buttons just below the minimap. Post them here in [code] tags.
• Be as detailed as possible. Include where you were, what you were doing, any other addons you may be using, or anything else that might be relevant to the issue.

The Debuff from a glyphed Avengers Shield is lingering on top of the minimap when it should be above the target frame. (see attached image)

Information:
Class: Protection Paladin with Glyph of Dazing Shield
Addons: just Blizzardsstuff and those that came with RealUI Beta

Some Error From Bugsack I got while fighting mobs in the southern half of Gorgorond:
And 2 minor change requests:
a) put the Garison minimap button with the other minimap buttons please, maybe make it visible for a short while when/if it would flash, if that is possible
b) bartenders cooldown overlay is a bit to bright at least for my tastes and its cooldown doesn't seem to be that reliable, but that prolly is just the lagging server

Edit 1: After playing in an area that was a little more crowded I think its all debuffs that end up in the upper left corner, additionally they cover each other as if they are all anchored to the top left most point of uiparent. (seen Frostbolt, Frozen Orb, Censure (Judgement from Seal of Truth) and Execution Sentence up there so far.

Edit 2: The descriptive Texts in the rewards section of both the quest accept and quest hand in frames are too dark. (see lower half of the 2nd image)

Edit 3: And another error, might be related to Edit 2 or to this:
Noticed that the highlighting for the selected questreward is not showing up, selecting itself and then finishing the quest still works fine though. Quests I noticed this on were 2 of the Wanted: ... Quests in Talador on the alliance side (the bird and the riverbeast one, forgot the names sorry)
anyway this is what bugsack caught:
And one more for Bartender:
The Cooldown overlay ignores the visible state of the bar, only noticed that during combat not sure if it shows up out of combat (see image 3)

Thanks for the reports. I have an update in the works that will fix most of these.

The Garrison button is a tough one, and i'm not really satisfied with where it's at. That said, I don't think putting it with the other minimap buttons would be a good solution considering the impact it will have in WoD. I have tried to have it hidden by default, but the pulse animation is somehow preventing it from being shown again.

The Skada error is a result of tighter asserts in the code for beta, and will not be present on live. Due to this, it is unlikely to be fixed.

The quest stuff is being worked on :)

My chat keeps getting spammed with Map: WORLD_MAP_UPDATE


edit:
I see you posted something about skins and I figure this falls under that category, but I figured I'd mention anyway.

Oops, forgot to remove some debug prints. I've re-uploaded beta2, just copy over !Aurora and nibRealUI.

Please see the OP about bug reports. What you have here is not much to go on, especially since I'm not getting them.

Server: Beta Leveling Realm 02
Class/Spec: Paladin/Ret Level 98
Location: Everywhere
Other addons: Monomyth, DBM
Turning off the !Aurora addon made the chat spam stop immediately.
The spam occurs more often when I open the world map or turn in/accept quests. It happens out in the world as well as in instances regardless of what I'm doing.

Another Aurora error pertaining to the minimap but it could be related.

Beta3 is up and has fixes for these issues.

Note: !Aurora is being renamed to !Aurora_RealUI to remove ambiguity with Aurora. Please be sure to delete and copy over the correct addons.

It looks like a bunch of spells got officially removed in the latest build. Due to this, there are a number of errors resulting from looking for a non-existent spell. Once I track down these changes I'll post an update.

Thanks for getting this going for beta. I just got in today and I will be doing some testing later this week. I haven't posted anything previously as RealUI has just worked out of the box for me, but I see that some work will need to be done to get it working well for WoD.

All that said, I'd probably have a rough time playing this game without RealUI. Not to say that I would quit altogether, but this is just such an awesome solution. Blizzard should take a note out of your design if they ever decide to redo their UI. Either that or hire you. :)

Edit: https://github.com/NibelheimInt/RealUI-80/tree/Beta Is this the correct spot for most up to date (beta 3) download?

Hah! That would be Nibelheim if anyone, i'm just here to keep it running. :p She's the one that made the design.

While you can get it there (check the releases link), the prefered location is here on WoWI (image link in OP).

RealUI beta 4
 

Hi

I have some spam in chat with "GetauraInfo"

If i disable nibRealUI, it's disappear.

Thanks

Yup, I saw that last night and re-uploaded that version. Download it again and copy over the nibRealUI addon.

I've noticed that if I have quest items and try to use them from the on screen quest tracker that I get an aurora pop up as such. In order to use the item, I have to open my bag and find the item.

Next time you see this, please also post the error message you get. It can be found by clicking the bag icon below the minimap.

That function is not used *anywhere* in RealUI or any of the addons it includes. Make sure you're using the most recent version, and disable any other addons you're using.

just got the same error moodib posted using just beta4 and the 'usual' blizzard addons
I wouldn't be surprised if that error comes from their addon code, wouldn't be the first time

"X tried to call the protected function Y" errors are not meant to be taken literally. (Well, maybe Blizzard intended for them to be taken literally, but if so they royally botched the implementation, because it just doesn't work that way.) It almost never means that X actually tried to call Y directly. It just means that X touched something that touched something that touched something that touched something that touched something that's somehow involved somewhere in the chain of Blizzard code that calls Y, rendering the whole chain of execution tainted.

Look for any places in your code where you overwrite functions or variables that are originally defined in Blizzard code, or if it's not obvious, you can enable taint logging to get a full report of everything you're tainting. Find the ACTION_FORBIDDEN error in the taint log, figure out which variable it says is tainted, and then trace that variable back through the log to see where it was first tainted.

Well some how I'm not getting this error, and you guys are. I even rolled back my local version to beta4 just to be sure, no dice.

So Ordrosh and Moodib, do this:
Get to an area where you can get this error, then start logging by entering into chat. Do whatever it is you're doing to get the error, then type to stop logging.

Then go to World of Warcraft Beta\Logs, upload the taint.log file to your favorite file sharing site, and PM me the link.

here you go:
got that 4 times for clicking on the questitem button 4 times (quest in nagrand at the ancestral grounds (Lighting the Darkness)
Edit: something I noticed: it appears to only show up after picking up a quest with a button in the questtracker, after a reload of the UI the button works just fine while before the reload the taint popup shows

Is that the entire taint log? Try that again, but with

will get back to you once i get across another quest with that particular feature

edit there you go, I hope it helps but I doubt it

That is from my file...

This was very helpful, thank you. Beta5 should fix this.

What exactly caused this? I'm trying to iron out taint in my UI as well and I get the problem with the objective tracker too sometimes.

I can't say for sure since I never got the error, but the log pointed out a leaked global. Seeing this, I went and grabbed the WoW Global Finder to track down others. Quite a few typos >_<

Blizzard has "stringHeight" accidentally declared as a global. Silly Blizz. :p

During the "The Thunderlord Clan Approaches" scenario in the Garrison, there are a lot of NPCs which have icons on the minimap which I think are flagged as rare, making the rare alert spam its brains out. There are three different icons that I noticed: an X, a green circle, and a red circle. When you hover over the red circle it says "invader" in the tooltip and "follower" for the green circle. The X is for the Legionnaire dude. Any time a new icon shows up on the minimap the rare alert starts losing it's marbles. The game crashes a lot during this scenario for me so I don't have much more information.



edit: I'm using v5 and no other addons aside from the WoW defaults and Monomyth.

Looks like Blizz has added more triggers for the VIGNETTE_ADDED event. Hopefully one of the return args will allow discernment between types of minimap icons.

Yeah blizz is using the Vignettes a lot more in Draenor. I'll probably end up making a session cache for vignettes you've seen or a throttle, maybe both.

Upon logging in on a level 100 feral druid, I received this bug:

When entering and leaving combat (feral), I am also getting the following in chat:
After Savage Roar falls off the player, it counts in negative numbers. I see a default set up in the auras panel, but it doesn't look like the other player buff auras. Setting it up manually is difficult because when clicking on buttons or radio boxes or using sliders, no change is seen until you close the auras panel and reopen it. I may have also configured my new "Savage Roar" aura incorrectly, because the white time in the upper right hand corner of the aura (that shows how long it will last if you cast it with your current combo points) did not appear.


(I moved the chat box in order to select the "copy chat" option. It goes below the bottom of the screen.)

A default Aura for level 100 Talent, "Bloodtalons" would be a great help too.

Also, it would be nice, in my opinion, to have combo points moved over to the left side next to the player health bar and show without a target. In WoD, they are tied to the player, not the target, and they degrade slowly over time (out of combat).

Sorry for the super long post, and for any additional walls of text that I post in the future. Thanks so much for maintaining this UI!

The custom auras don't have the ability to display pre-calculated time-remaining for abilities such as these (requires calculations based on talents/set bonuses/cp/etc), which is why a specific Savage Roar module was made. Gethe is quick so you'll get a working SR aura again soon :)

Interesting. Us Rogues have only been asking about that one since Classic :cool: Hopefully they don't revert it :eek:

Celestalon "Yes, Combo Points are 'on the Rogue' now. Could revert based on feedback, but trying."

In WoD, combo points are still primarily for use against the current target, Recuperate being a secondary use. In this reguard, not much has changed other than showing available combo points on loss of target if that is possible.

On aquiring a new target in WoD, they get the available/unused points (the only real difference).

Moving Combo points to display on the player would be a mistake IMHO, moving them there on loss of target (if possible) is just an eyball dance)

Aye, good point.

It's a tough one. Generally the Player side for buffs and stacks/points for effects which affect the player (i.e Soul Shards) and the opposite for the Target side.

Some things kind of fall in the middle, such as Holy Power. Stacks on the player and can affect a range of abilities that work on both player and target. So Holy Power is displayed in the center of the HuD instead of on one side or the other.

Combo Points could become similar, but it's still going to affect abilities used, in the majority of cases, on the target. Perhaps moving it to the center would be the right move.

Couldn't the same be said for any secondary resource? All of them are on the player frame, and they are all very much used primarly offensively. The only difference, until now, is that combo points were attached to targets. I don't think it makes sense to keep them on the target frame any longer.

WoD Target/Combo point swapping is instentaneous. I don't have to wait for a "resource" cooldown/proc/whatever.
Combo points "fade" over time out-of-combat not increase/rejuvinate. ie. they are the reverse of most secondary resources as they are reliant on having a target aquired (and in combat if you start out with none).

I can see the argument that combo points are now a class bar rather than a target bar.

from what I've read here it seems to me that combopoints behave just like holypower, with the exception that paladins spent starting with 3 for full effect, so treating them similarly would be my thought (for example putting the cp display in the same area where the hp display is).

In this sense they behave just like Chi for Monks, which is currently located next to the player. How it happens mechanically is irrelevant imo, what matters is how it feels and how it can be used. I've tested this out, and you can totally spent combo points even if you don't have a target.

Combo points have spent the last 10 years anchored to the target and they're still there on the default UI. Make of that what you will.

A lot of really good points have been made here. I can definitely see both sides of the argument, but combo points have also spent the past 10 years being attached to the target instead of the player. (Mechanics-wise)

Seeing as how the way combo points behave is changing, I would argue for a change to how they are displayed on this custom UI.

A good middle ground might be to have a setting allowing the player to pick which side to put them on.

Since the last update the info bar with friends,gold etc is no longer showing. No error in regards to it is being thrown in game though.

getting a few errors with the todays build
Number 1:
Number 2:
Number 3:
Number 4:
Number 3 and 4 look like they are related to number 2
Number 3 is also the reason why the infoline doesn't showup

Yeah I saw that. Blizz changed the function GetAddOnInfo. You used to be able to use an addon name, but now you can only use the list number.

Eww, you're still using Tablet-2.0 and Ace2?! Upgrade to QTip already... :(

It's on my list

Ace2 has been officially deprecated and unsupported for over 4 years now. I'm actually amazed to find any part of still being used in an actively developed addon... it's like meeting someone who owns a smartphone and does all their shopping online but still commutes to the office by horsedrawn carriage. :o

Well that portion of the UI was probably originally written close to 4 years ago, but since then Tablet has been working fine so there hasn't been any real reason to upgrade. In fact, this is the first time i've actually had to do any kind of maintenance for it.

Regardless it is one of my TODOs, but right now rewriting the unit frames is more pressing.

I just made an account to say, that I LOVE the look of this UI and it's overall vibe/feel.
Please continue the development once WoD hits live (:

This error occurs when i fight agianst a Lumbering Ancient, and get a Chattext warning :
Including this taint/loop LUA error:

Since this affects more than just RealUI, I posted a link in this thread with an updated version.

Bartender Config Problem
 

Hey,
first off, amazing work, LOVE your UI and I usually Hate packaged UIs
that said, the only thing missing in my life now is conditional bar swapping. Bartender does this, however whenever I uncheck to RealUi Control and press the Advanced Settings Button, or type in /bt, bug sack catches the error listed below
I also wanted to know if this was a RealUi issue, or a Bartender issue and it seems to be bartender, as when I disable all addons and only run BT and type /BT, the error comes up again

Oh an tho I'm guessing it would be practically impossible as you are combining many addons you don't have control over, I would love to see a Global Profiles deal so that I don't have to spend hours reconfiguring my UI from toon to toon

Thank you again for all that you do

51x ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0-58.lua:1803: 66AceConfigRegistry-3.0-15:ValidateOptionsTable(): Bartender4.args.bars.args.1.args.state.args.stances.args.berserker.name: expected a string or funcref, got 'nil'
[C]: ?
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:50: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:45>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:187: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:182>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:221: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:231: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:231: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:231: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:231: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:231: in function <...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0.lua:196>
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:259: in function `ValidateOptionsTable'
...-3.0\AceConfigRegistry-3.0\AceConfigRegistry-3.0-15.lua:312: in function `app'
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0-58.lua:1803: in function `Open'
...acenibRealUI\Config\ConfigBar\ActionBars.lua:300: in function `func'
nibRealUI\Config\ConfigBar\GUI.lua:447: in function <nibRealUI\Config\ConfigBar\GUI.lua:447>

Locals:
msg = ": expected a string or funcref, got 'nil'"
errlvl = 9
t = <table> {
1 = "Bartender4"
2 = "args"
3 = "bars"
4 = "args"
5 = "1"
6 = "args"
7 = "state"
8 = "args"
9 = "stances"
10 = "args"
11 = "berserker"
12 = "name"
}
select = <function> defined =[C]:-1
tinsert = <function> defined =[C]:-1
error = <function> defined =[C]:-1
MAJOR = "AceConfigRegistry-3.0"
tconcat = <function> defined =[C]:-1

Downloaded and Thanks:)

@Gardorian:
If you don't have it already, go to WoWAce.com and download and install the latest Ace3 (A: r1112). Install it as a stand-alone. You won't have to do anything (except unzip the file 8^)), just download and install it. See if that cures your problem.

Unfortunately, that did not solve it :(

Wow, that is a lot of nested tables.

Berserker Stance is removed in WoD, so any addons that depend on its existence (eg. the stance configuration in BT4) will need to be updated.

Edit: There's a version of Bartender4 updated for WoD available on the WowAce project page:
http://www.wowace.com/addons/bartender4/

Welcome to Ace options tables. :p

Yeah,
according to the Bartender4 curse comments, it's specific to warriors (which makes sense with the berserker stance thing)
I did a workaround by going into another toon, copy the realUI profile so that toon can have it's own setup, then switch it back to the realUi profile, configure it how I like it on my warrior, then switch back to the one I had copied for my alt (lock in this case)
Since the profile will stay as the realUi profile, which is the one that my warrior is stuck on, it will still reflect like that when I log onto him

I am now in the beta ,, now Testing this ui:banana::banana:

Been playing around with the UI in the beta and there's a few things that pops up so far:

- doesnt work in the garrison building ui.. altho garrisons hardly work as-is.
- when clicking on quest items in quest log on the right side the UI taints.

I like the way it handles in game so far and I just installed the UI for my live install also ;)