The handling for ACS_ExecuteAlways was changed recently.

[randi]

The handling for ACS_ExecuteAlways was changed recently.

Details, please. When? Sounds like a bug to me.

[Graf Zahl]

I split this off to Bugs so that it isn't forgotten.

[Slasher]

The handling for ACS_ExecuteAlways was changed recently.

What do they mean by the handling was changed? I've been using ACS_ExecuteAlways a lot lately and I haven't seen any strangeness with it. It appears to work exactly as it should be. I'm using r858.

(Wow, this wasn't a very helpful post at all, was it?)

[bagheadspidey]

AFAIK Nash noticed the bug first here. I can confirm the behavior.

[Slasher]

Oh that. Having to pass all arguments vs. not having to. Yeah I've noticed that change also, but I don't know when I first noticed the change. I didn't think it was a bug though, I just kinda accepted it as necessary and I've been passing zeros for the empty arguments ever since. Doesn't bother me that much...

[Project Shadowcat]

I thought that was a good change for consistency if you ask me.

[Graf Zahl]

Ugh...

Anything that breaks old data is a bug (unless expressly stated otherwise.)

[Graf Zahl]

Fixed. The DECORATE parser's previous arg count information was inconsistent with ACS's and when I rewrote that code I used ACS as a template which requires at least 2 args. It's back to 1 now.