Is there a problem to use the PlayerPrefs every time that the user changes any settings, like I did in the image? or should I use some object to save the settings and only save in the PlayerPrefs after user left the Settings screen to avoid accessing PlayerPrefs everytime?
It’s only a problem if it shows itself as a problem.
If you saved a player pref every update frame I’m sure there would be problems. But if you are putting your audio on hotkey or something and it doesn’t effect the game then hey no problem.
Sorry if you mean in the sense of apply settings. It’s up to you. Id say it’s easier to just slam every setting interaction, and have a restore to defaults button. Though the apply settings button is popular. And comes relevant perhaps when doing resolutions. But usually people have a pop up menu to keep current resolution or change.
The common thing to do is to have the apply button. But I certainly see no difference you can always come back and program it to change it it’s no big deal.
1 Like
My game does not have an apply button because it is a small game and have like 4-5 settings so I prefered not adding it, then I am hitting the PlayerPrefs every toggle button or slider of the volume changes.
I think it works on all major operating systems; phones, but I’m not sure if it works on console. But according to Unity it roots somewhere in all major systems. Implying that it works as a save location on all major systems.
1 Like