, computers.
You create a constant combinator with an L signal of value 1.
Elsewhere in your blueprint however, you have an arithmetic combinator serving some other purpose and its taking a signal and adding 1 to it.
You might face an issue, where those two values become bundled parameters, and if the player says "I want my train limit to be 5", suddenly your arithmetic combinator is adding 5, instead of 1, breaking some circuit somewhere.
This is a problem I have faced, but have found a work-around!
For values that you need to stay absolutely static no matter what, give them a unique number such as 1001, then in their parameter Formula tell them to actually be set to 1.
You are then free to set the value parameter you are querying the player with to the default of 1, and when the blueprint compiles, no matter what value the player has set their query to, the static values will remain static.
I hope this image makes it a bit more clear.
- 10-28-2024, 21-26-21.png (1.82 MiB) Viewed 1576 times