Firstly, a great cheat for Windows OS users...

If like me, the Pro version of Unity is a bit off-limits at this early stage in the game dev journey.

This means I'm using the Personal Edition of Unity 5 and sadly, it is not skinned in the easy-on-the-eyes black but a rather light shade of grey.

This may seem ok at first but after a few hours in the Unity editor it can start to take its toll on the eyes so here's how to be kind to your eyes.

(These 2 cheats also help for general computer use!)

1) Get F.Lux (google search justgetflux) as it removes the blue light from your screen after sunset so that it is less eye straining to work on a screen at night and also getting rid of the blue light that naturally prevents you from being ready for sleep for up to 1hr.

The good thing about F.Lux is that you can disable it for an hour (for colour work) and also you can activate movie mode which puts back slight blue light for video watching (without blasting you with the full amount of blue light)


2) Set up the built-in windows magnifier in Windows XP/Vista/7/8/10 so that it is 100% but tick the colour inversion option.

The good thing about this is that it makes Unity editor darker like the Pro version!
The great thing about this is that anything white it inverts to black and the black text inverts to white - perfect for coding, working in white websites/notepad etc etc (you get the idea)
In Unity case monotype is white screen black text so it inverts perfectly to make it easy on your eyes.

I do appreciate for colour work you will have to compromise but if you can handle most of the time not needing to know exact accurate colours duing your workflow then flux and windows magnifier colour inversion are a huge help!

One of the most common mistakes in Unity is making changes while running your game and then stopping the game and not realising you have lost the changes as they dont persist if made while running the game.

To avoid this happening often you can do the following:

1) Just don't make changes while the game is running!
(While I know this is hard and may seem more restrictive to the point of actually hindering workflow, this is the mindset to get into so you don't end up with the habit of changing things often while running your game as eventually you will lose changes and not even notice until the next time you run your game to test)

2) There is an option in the Unity editor to disable making changes while in game running mode. This works well and takes the risk away completely

I have chosen to opt for number 2 myself.

You can add one change in running mode. Before stopping test, you can copy parameters of some component and paste this in this component after :)