OK, I updated to the latest revision last night (after the merge of the branch back into the trunk), and here is a bug report from my Dev, Kayen:
Quote:
I am experiencing some pretty funky bugs with combat state
First it wasn't switching it correctly. Now I can't even get it to define a combat state. All I am doing is running a timer with $combat_state and it comes back undefined, and sub event combat state does nothing.
Tried this on a few scripts seems its broken
|
So far that is the only thing that needs quick attention that we have seen so far. I will keep an eye out for more issues, but we will probably have to revert back until this issue is resolved.