Manage your Game Settings
Configure what settings your game has directly from the Unity Editor. No need to write any code to manage user configurable settings, simply go to Project Settings and set them up. We'll take care of the rest.
Create Reactive Menus
Quickly build in-game settings menus without writing a single line of code. Just use the provided components to configure two way bindings between your UI inputs and your settings.
Using custom inputs? Write your own extensions to configure two way binding with anything you like! Less than a couple of minutes is all it should take to integrate a new input, whether you got it from the asset store or made it yourself.
Tell me about it
The Loris Settings Manager is a Unity3D extension for configuring and accessing game settings. It is intended to facilitate the setup of all of the settings that might be user configurable, provide a code interface for accessing their values, as well as providing a simple way to build the in-game menus to modify them.
It should allow you to very easily keep track of and manage what Game Settings you have in your project in much the same way as the Unity Input Manager allows you to manage your controls. Equally, you should be able to build a working settings menu in just a few minutes, or even hand it off to UI designer with no coding knowledge. You can ditch the Unity launcher window and add a bit of polish to your game with very little time investment!
Why did you make this?
A little while ago I was working on a personal project, and I started building an in-game settings menu. Often Unity games ship with only the default launcher window; but if you want your game to have custom settings or to be able to change resolution without restarting, then you need to build your own. I spent a while on this, and I realised that Unity doesn't provide much out of the box. It gives you the PlayerPrefs class to save these custom key values to the disk, and not much else.
I thought it would be useful to have more functionality available directly in the editor for this, so I started with the intention of making a wrapper around EditorPrefs that allows the developer to configure their settings from the editor. From there I started streamlining the process of building UI's by creating functionality to support event driven two way bindings with the settings values, as well as built in validity tracking, and several other things like that. I have tried to build it with two philosophies in mind: allowing settings to be configured and menus built that control them by someone with no coding knowledge, and making it very simple to code two way bindings with any custom inputs.'