I changed it because I wanted to do it differently in first place. But by doing that I recognized that I needed a second set of event handlers to handle all the unit events. I tried using oUF to handle the events for me which worked out amazingly well. With the new system you have the freedom to build any nameplate possible. With the old system I could just change some of the Blizzard code here and there.

If you want the old stuff you can always go a step back in Github and use the old code.

Yes, I was just wondering if the change was due to the api changing, but it's due to design so it's fine, thanks.

I changed it because I wanted to do it differently in first place. But by doing that I recognized that I needed a second set of event handlers to handle all the unit events. I tried using oUF to handle the events for me which worked out amazingly well. With the new system you have the freedom to build any nameplate possible. With the old system I could just change some of the Blizzard code here and there.

If you want the old stuff you can always go a step back in Github and use the old code.

I was working on my new oUF unit layout and nameplates over the weekend and while doing that it occured to me that oUF might by able to handle the nameplate spawn too. That is because since Legion nameplate units are valid unit ids.

This saves a lot of trouble since you do not need to implement a second unit framework for your nameplates.

Quite possible because rNamePlates changes the nameplate parenting. Reason for this is the fps drop issue. See info page. This can cause errors with other addon that rely on the default nameplate frame parenting.