Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
I think somehow scoping variables is a must, unless I'm missing a way to do that.
Having all variables global will lead to many confusing bugs once people start using each other's logic contraptions as "black boxes". Any variable changers can potentially affect variables anywhere. Especially since the slow text input don't encourage long, descriptive variable names, I think we'll see a lot of e.g. "value" or "result" variables. Just using a variable changer in a microchip and then cloning the chip can make both clones broken (this happened to me, and it took me while to figure out what was going on).
Any particular reason it's not possible (AFAIK) to directly wire a changer to variables, instead of using the name? I think that would solve most of the issues.
I suppose it's possible to avoid using variables most of the time, but since they're there, they will be (ab)used :)