#nextcontposx or whatever the command was
Have you ever looked at what the current container is while things are changing on the screen ingame? I mean, even the numbers that float up when damage is being taken are shown as containers. (Damage is even in the name of the container
)
So, nextCPos has never been worth much considering how often the client sees stuff as a container, since at any given moment the next container can (and more often than not, does) change...
What continues to confuse me is how event macro 50 3 can be responsible for opening a healthbar (container), and yet - when you use #contpos the moment after you invoke event macro 50 3 - it will
virtually always ignore that container {healthbar}
if it was already open and moves on to whatever last container had the focus. But
if it's not open prior to invoking 50 3, it
always treats it as
the last open container...
And I just don't see how that works...
*** Edit *** I'm now wondering if event macro 50 3 (
in addition to popping open the healthbar)
also sets it as the last container open -
but it doesn't do this if it is already open??? Could this be the case?
