This might not be a bug...
When using an action list that has the same variable as a parameter as a variable passed to an included project via the "include Project" Action List, the "Set Variables Before Loading" modifies the variable in the Action List's variable space rather than the project's variable space.
From what I understand this might be just a consequence of the variable precedence rules, it is some what unexpected since setting the Action List's local variable value isn't propagated to the included project.
This might be just a caveat that I missed, but I've attached two files that demonstrate the behavior via the logging the value of the Variable "Variable".
Thanks
test12a.fbz6 (2.009 KB)test12b.fbz6 (1.411 KB)