You can create a simple actor class that you drop in the level and have the GM, GS, GI etc reference. I’ve done this in the past for Levels that have different values for settings. Now I use Data Tables.
above suggestions are good. my fav is data tables.
another option are data assets.
alternatively you can also mark attributes as config file available, and then they can be set on the .ini files after packaging. but for this i suggest using a base class.
you can also have a DeveloperSettings class, so that you can set them on the settings, and obtain during runtime.
The most convenient way I’ve found to do this in just blueprint is to simply create a function library with pure functions that return the values. They’re easy to access from anywhere that way, without needing any additional nodes.