I’ve noticed that when I open a console variable collection file to edit it all the console commands in the list get applied in the engine as soon as I double click the file to start editing. So basically editing the list equals executing it.
It’s hard for me to imagine any scenario where I would want this to be the default scenario. Is this by design? If not can you please change it. Maybe add an “Apply” button at the top or something so you can just look at different collections without automatically setting every commmand in every list you view.
Digging into this a bit more, I see that you can uncheck the console commands. So you could save a preset with all of them unchecked and then when you open it to edit it they wouldn’t automatically execute but that’s still not quite the behavior I would want.
The one nice thing is I can buid a widget and/or a blueprint that can take in a collection and then I can script the behavior I want, so that will be ok.
Nevertheless I think it’s really not ideal, especially for something as opaque as console commands to have them be automatically executed. I bet a lot of people using these console variable collections open 4 or 5 of them and without even knowing it have changed 100+ console commands and then move on. Just because I want to view a few different lists that maybe other people have made definitely doesn’t mean I want to execute all of them.