Ok, for the longest time I have been using a specific setup for my scripts with the way they're wrote and the string rules so I can get my desired affect. Here are some examples:
You collect 3 pieces to one item, a string pops up saying, "You have combined three items blah blah blah" and when it's done typing out all action resumed. Then my script made it so that if you press B or if you leave the screen the string would go away. I had the Messages Freeze All Action and Messages Can Be Sped Up With A checked. So, the action was frozen until the string was shown in it's entirety, but then it remained drawn on the screen until I called a Screen->Message(0); call.
Now, in the newest build it just freezes the action forever. It completely destroys my shop scripts, my item combining scripts, and many others. Now, I don't know if you guys fixed a bug and I was just..."working" with the bug to produce my desired effect. Or, is this new behavior a bug? Also, the strings I am using are under 72 characters.
EDIT: Ok, yeah I'm pretty sure it's just cause I developed the code to work with the 'buggy' Messages Freeze All Action rule before. I've gone and adapted my code to the new way and now it's all cool. Hopefully anyway, I don't feel like changing it all back again. Also, this way cleared up another bug I was having (although I didn't think it was a bug) where my Screen->DrawInteger was disappearing whenever a Screen->Message() was running.