StarCrawlers - Moving to Unity 5

The StarCrawler team announced on Steam that they are moving from Unity 4.6 to Unity 5.

Unity 5 Update Inbound!
15 October - Thunderflux
Updating to Unity 5

During test builds of the next update we started to encounter issues with Unity 4.6's ability to compile the project (there's a lot in there, and Unity 4.6 can only address 3 gigs of memory to build - then it crashes). One solution would be to reduce the quality of or remove assets to allow the project to compile, and while that worked early on, it's become increasingly problematic and undesirable - we want to add MORE!

Originally the benefits of moving to Unity 5 were outweighed by the benefits of sticking with 4.6, but that has now reached the tipping point:

=>Unity 5 supports offers Auto API update (switches a lot of code from 4.6 to 5 automatically)
=>Unity 5 can address as much memory as it needs to build, ending the build issue for us.
=>Unity 5 offers features that will improve how StarCrawlers plays, looks and feels.
=>Unity is ending support for 4.6.

The biggest hurdle with switching to Unity 5 was supposed to be converting our entire codebase (StarCrawlers currently has over 223,500 lines of code) but I'm extremely happy to announce that part is DONE - we were able to update and fix the entirety of the code in less than a day!

There are some minor animation, graphic, UI, and general transition wonkiness that needs to be resolved, but given how quickly the code was addressed, we're optimistic about committing to the full transition to Unity 5.

What this means :
A brief delay before the next update while we complete the transition to Unity 5 and ensure the game is smooth and stable on all platforms- then we'll be back with even more to show. In the meantime, these guys are on their way...

Here's the TLDR version:
We're moving to Unity 5! There will be a brief delay while we update the project, but it means more good stuff for the future.

Thank you everyone for your support!!!