Loot UI 2.0

[kyle2143]

- I'm fairly sure that your updateLootUI proc is unnecessary. You're basically re-implementing one of the key features of chui, which is displaying the same page to all subscribed clients to that window. Might have to ask Somepotato to be sure.

How would a chui window trigger an update on external actions?
For example a player unequips their hat.
How does the window know to update the UI?

It wouldn't. I meant the part of how it tries to keep the screen snyched for all people viewing the html page. You have a for loop of viewers of the mob in question. Chui has a list of clients that view the window and updates them all. With the chui subscribe/unsubscribe procs you can do what it looks like you're trying to do(updating the page for all users). It's just that that's handled for you with the chui stuff.

But also, I guess I'm not sure why those calls are added in the action_controllers and whatnot when they weren't there before too. Unless, is that supposed to be a new feature? Even so, you're remaking the entire html file on any update and sending the whole thing to the client, instead of just sending what information has been changed.