Editing PlayerPrefs directly in plist

What that's it? I thought there was some kind of mystery here...

$$anonymous$$inda sucks to have to exit each time, but thanks!

Sweeeeet! That did the trick. Thanks much Eric!
For anyone using the PropertyListEditor (PLE) on Mac OS X, here are some things i've figured out that might help, or at least save you some pain:
- You can use booleans in the plist, if you read them using PlayerPrefs.GetInt()
- Using the wrong Unity function for the data type in the plist usually results in 0 being returned. E.g. using GetInt() to read 3.543
- If you enter a number in your plist as 2.0 (because you intend to read it as a float), the PLE removes the decimal value, leaving you with 2!! PlayerPrefs.GetInt() will read that, but PlayerPrefs.GetFloat() will return 0. Sucks if you need that value to be a float. I might end up setting up all my number values as strings in the plist and just parse them via float.Parse() or int.Parse() as needed. $$anonymous$$ind of annoying to have to do that, tho...
- Good idea to save a backup of your plist if you've manually created it, just in case you forget to close Unity while editing the pList and end up wiping out all your manually entered keys!
Thanks again!

I still have the problem with Unity 4.2.2f1 . The file is always overwritten. Quit and restart the application don't work.