Friday, July 15, 2022

Dreadout 2!

A third-person horror adventure that draws inspiration from Indonesian folklore and urban legend! Use your camera to frighten off evil spirits, and when that doesn't work bludgeon them instead.  Explore creepy environments as you search for answers, redemption, and acceptance towards your role in stopping mankind's greatest threats.

Dreadout 2 uses the Unreal engine, and we helped bring it to Xbox One, Xbox Series X, PS4, and PS5.

Thursday, June 2, 2022

Unexplored 2!

A unique and beautiful roguelike with more adventure and less combat, Unexplored 2 tasks you with destroying the Staff of Yendor in persistent randomly generated world.  Play different characters within the same world and see things change over time!  Hear rumors of distant places, and go loot them!  Unlock secrets and get attacked by bat creatures!

We worked with Ludomotion to make Unexplored 2 available on Xbox One and Xbox Series X, and on Steam!  Look for a PlayStation version in a few weeks!

Friday, December 3, 2021


Archvale takes you on an exciting quest through a bullet-hell RPG world.  Do you wish Zelda was more like Enter the Gungeon?  Today is your day!

We worked with idoz & phops and Humble to bring Archvale to Xbox One and Windows Store!  Also available on Switch and Steam, Archvale is a great title with a ton of roguelike dungeon-crawling fun!

Friday, November 5, 2021

First Class Trouble!

 A sneaky social deduction game set on a futuristic space cruise, First Class Trouble challenges a pair of robotic Personoids to avoid detection while wiping out the remaining humans.  Built in Unreal Engine 4, we helped bring the game to PS4 and PS5!

If you're a Playstation Plus member it's available for play right now!

Wednesday, September 15, 2021

Flynn: Son of Crimson!

A charming and beautiful platform game built on GameMaker, Flynn is now available on Switch, PS4, Xbox, and Steam!  We worked with Humble and Studio Thunderhorse to bring the title to all three console platforms.  Explore Rosantica with your trusty dog, Dex, by your side.  Push back the scourge and discover the truth behind what threatens your home!

Friday, September 3, 2021

Fixing Invalid Frameworks Folder in iOS App Store Upload

Upon moving a couple of recent projects to 2020.4, we learned that recent versions of Unity apparently have problems when exporting iOS applications.  They’ll run and test fine, but upon uploading to the App Store, you’ll get an error.  This reads:

Invalid Bundle. The bundle at '' contains disallowed file 'Frameworks'.

We spent a long while trying suggestions on forum threads and reviewing the build behavior before we came up with a solution that works for us.  This also handles a further error we got after submitting the iOS app, which reads:

Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.

You can use the solution we created by saving the below code out to a file called UpdateXcodeBuildSystemPostProcessor.cs and putting it in your project’s assets/editor folder.

using System.IO;

using UnityEngine;

using UnityEditor;

using UnityEditor.Callbacks;

using UnityEditor.iOS.Xcode;


// Create specific aliases for iOS.Xcode imports.

// Unity Editor on macOS can report a conflict with other plugins

using PlistDocument = UnityEditor.iOS.Xcode.PlistDocument;

using PlistElementDict = UnityEditor.iOS.Xcode.PlistElementDict;


public class UpdateXcodeBuildSystemPostProcessor : MonoBehaviour



    public static void OnPostProcessBuild(BuildTarget buildTarget, string path)


        if (buildTarget == BuildTarget.iOS || buildTarget == BuildTarget.tvOS)





    private static void UpdateXcodeBuildSystem(string projectPath)


        string workspaceSettingsPath = Path.Combine(projectPath,

            "Unity-iPhone.xcodeproj/project.xcworkspace/xcshareddata/" +


        if (File.Exists(workspaceSettingsPath))


            // Read the plist document, and find the root element

            PlistDocument workspaceSettings = new PlistDocument();


            PlistElementDict root = workspaceSettings.root;

            // Modify the document as necessary.

            bool workspaceSettingsChanged = false;

            // Remove the BuildSystemType entry because it specifies the

            // legacy Xcode build system, which is deprecated

            if (root.values.ContainsKey("BuildSystemType"))



                workspaceSettingsChanged = true;


            // If actual changes to the document occurred, write the result

            // back to disk.

            if (workspaceSettingsChanged)


                Debug.Log("UpdateXcodeBuildSystem: Writing updated " +

                    "workspace settings to disk.");





                catch (System.Exception e)


                    Debug.LogError(string.Format("UpdateXcodeBuildSystem: " +

                        "Exception occurred writing workspace settings to " +

                        "disk: \n{0}",







                Debug.Log("UpdateXcodeBuildSystem: workspace settings did " +

                    "not require modifications.");





            Debug.LogWarningFormat("UpdateXcodeBuildSystem: could not find " +

                "workspace settings files [{0}]",



        // Get the path to the Xcode project

        string pbxProjectPath = PBXProject.GetPBXProjectPath(projectPath);

        var pbxProject = new PBXProject();

        // Open the Xcode project


        // Get the UnityFramework target GUID

        string unityFrameworkTargetGuid =


        // Modify the Swift version in the UnityFramework target to a

        // compatible string


            "SWIFT_VERSION", "5.0");

        // Write out the Xcode project


        Debug.Log("UpdateXcodeBuildSystem: update Swift version in Xcode " +




We do two things here:

  1. Unity writes out the Xcode project using Xcode’s “Legacy Build System”, which is currently deprecated in Xcode 12.5.1 where this was tested.  We remove the “BuildSystemType” key from the Xcode workspace settings so that Xcode uses the default build system.
  2. Once Xcode is using the default build system, it no longer recognizes the format of the Swift version that Unity writes out in the Xcode project.  Unity writes something like “5 0 5 1”, but Xcode expects “5.0”.  So we forcibly set the Swift version to a value Xcode currently understands.
You could do this manually.  After making a Unity build for iOS, you would open the Xcode project, go to the File menu, select Project Settings, and change the Build System in the drop-down menu there.  Changing this through Xcode will automatically fix the Swift version value.

Thanks to everyone on the various Unity forum threads who have been wrestling with this problem.

Thanks also to user uannoymejo on this forum thread for bringing up the Xcode build system.