I found some weird limitations with the new blueprint parametrisation. The biggest one is the impossibility to have a default value if the value is used anywhere else on the blueprint as a constant.
#Need help with blueprint parametrisation limitations
modest pumice
If I wanted the B signal default value to be 4, I would not be able, since the signal A is using it as a constant.
am I doing it wrong or is just impossible?
stone siren
Doesn't the 4 need to be above the B?
modest pumice
Order does not matter
If I change the 1000 to 4, the game collapses both the four's to a single parameter, which makes me unable to vary B without varying A
stone siren
Oh yeah, if you define B as 4, and use B as a variable in A, then A will use 4 for B. If you need B to be two separate numbers then you need a separate variable
modest pumice
This means that I will need to have a nonsensical value for B, just to avoid collisions right? Also means I can't have a default value.
kinda sucks
stone siren
If you can set a default value to B right now, then you still will be able to later. But if you want A to reference something other than 4 for B, then you have to pass that number through a variable that is not B
modest pumice
If you can set a default value to B right now, then you still will be able to la...
But if you want A to reference something other than 4 for B
I did not understand, wdym with "A referencing 4 for B"
I want A to ALWAYS have the value 4.
I want B to DEFAULT having the value 4, but being able to vary it when placing the blueprint.
My first thought was creating the blueprints with them having different values and only changing it on the parametrisation screen, but it does not works and acts like I build them with the same number.
I found a workaround based on your comment, don't know if that's what you meant:
Set A to 1000
Set B to 4
On parametrisation screen:
Set 4 to be a parameter.
Set 1000 to be a parameter with the formula: 4
This works, B has the default value 4 and A always have the value 4
stone siren
I don't follow, but I'm glad it works!
modest pumice
Still breaks if I want a third parameter to also have a default value of 4 tho
stray glade
Looks like default values weren't really thought about.
Basically, it seems there is no way to associate the number with the signal, all number 4s are considered the same
modest pumice
Yep, people on #friday-facts commented about it, V453000 talked about improving it