Rebind and get the keys in the project (Nodes to get and set keys and get the number of index in each action get arrays of each action and change that)
Change graphics, engine, display settings and others and apply changes (to work in runtime game)
Add, edit, remove vars in the .ini files (at runtime too) (and will be nice if add something to create additional custom .ini files)
All of that need documentation for C++ too because the only example with changes of graphics settings is the Shooter Game, and about examples with .ini or rebind and get keys there isn’t one.
Rebind Keys and settings resource are indispensable, and would be a great help officially exposed as blueprint nodes.
Much better than alternative solutions.
plugin break all Binds if you got Forward Action and use the rebind system then change the 1.0 and -1.0 values to the same keys, about change the inis only can change in one file and you cannot change the settings of the engine, change the screen sizes don’t is change engine settings, you cannot change the blur or aa throw that and save for next run…
Thanks for your great ideas regarding implementing a blueprint system for rebinding keys. I have submitted this feature request to our developers through . If you’d like to refer to this report in the future to check up on the status, please reference: UE-17987
These are things that should be BUILT IN to the engine… not require the use of a 3rd party plugin. As for the .ini files, he reads/writes one INI file… we should be able to define what file we are reading/writing to, just just one specific file that epic gives us access to.
Yeah what I exposed were the rendering scalability settings, resolution/vsync/etc…, and general machinery for working with UGameUserSettings in a BP. In general most games will end up subclassing it and adding their own game-specific settings as well I’d imagine.
I’ll spread the word.