Original project link unavailable so closing.
> It seems like it doesn't account at all for multiple fade behaviors—it triggers stuff based purely on the object instance the Fade behavior belongs to
>
You're right, this sounds like it would explain it from the description, and it's an architectural oversight more than a bug. The proper fix would involve re-architecting all behavior triggers which would be quite a lot of work, and possibly cause compatibility problems with third-party behaviors. So I think it would be easiest to fix this in the upcoming C3 runtime which is being rewritten anyway.
I'm not sure why you'd want to use two of the same behavior anyway - why not just adjust the settings of one?
Ehhmm, so C2 fade behavior will still bugged?