There's Interaction Problems between TimerX Event and Hide proxy.

[yun9221]

hidebugged.txt

https://youtu.be/gR2k-S7JENQ

ok here is the PAC file.

and this is the problem situation.
As you can see, if use TimerX as a Parent part of the Hide Proxy when use to Hide or Unhide, the Hide Proxies ignore that TimerX events.

I don't use this workflow, but the reason I use this logic was that if I use it to Hide or Unhide parts, it operates on the server side, not on the client side, so there's no personal delay. (it mean, well working also in the trash computer player.)

This bugs reported from my friend, and I recreated the bug.

[pingu7867]

Hide proxy doesn't directly apply Hide the checkbox but instead sets an "event hidden" state. This is not like other properties.

Also, when the proxy is hidden, it removes these flags thus reverting the hide back to unhidden, unlike other properties which are written in "irreversibly".

hidebugged_alternative.txt

hidebugged_alternative2.txt

An alternative method is to use the "property" function to apply changes that were written in by another proxy normally on an unused property like DrawOrder, and use a separate proxy to read that "fake variable" value. Instead of having two Hide proxies that compete, one proxy can set the value somewhere else and another will use it. This is the closest non-networked alternative you have to pac_proxy and pac_event commands.

In a future update (it's already on dev branch but it'll be on main soon) the property function will be able to read any part's value so there'll be less trouble for structuring but for now you gotta have the variable holder be the parent of the final Hide setter, because "property" takes from the parent part (or 'target entity'). The value setter can be anywhere though.

Let me know if that's helpful, though it's not perfect.