Got a question?

Frequently Asked Questions

• ⚠️ PLEASE READ THIS ‧ I downloaded the asset and it's not the latest version / it's not working / I don't have all the files
  First, start by making sure you're running the latest current version of Unity. Then try downloading the asset again. Each version of the engine requires a specific Unity version, and if your version doesn't match, you'll get an old version. That's normal, that's how the Asset Store works. You can check what the requirements for each engine's version are on the Releases page.
• Is there a tutorial or something ?
  Yes there is, have a look at it over at YouTube. Furthermore, the asset includes a complete documentation of all the classes of the Corgi Engine. Plus, the code is heavily commented, so understanding it shouldn't be too hard.
• When will you release the update X or feature Y ?
  When it's done. I don't give ETAs. Things get released when they've been properly implemented and tested. I don't believe in releasing half done work, and prefer focusing on quality. By definition it's hard to predict that kind of stuff, so don't buy the asset for what may or may not come, but for what's already in it.
• When is the next release coming?
  When it's done. I don't give ETAs. Things get released when they've been properly implemented and tested. I don't believe in releasing half done work, and prefer focusing on quality. By definition it's hard to predict that kind of stuff, so don't buy the asset for what may or may not come, but for what's already in it.
• What's the best way to update from an old version of the engine?
  Whatever you do, make sure you have a commit / backup to rollback to if a problem happens. Then, remove the old CorgiEngine folder, and import the new one. If you don't, due to the way the Asset Store importer works, some scripts may be duplicated, not removed, etc. Depending on what version you're updating from, and what version you're updating to, you may have some light refactoring to do. Make sure you check the release notes to see what changed and what may have an impact on your own code.
• Can you develop that feature that I really need ?
  I'm always open to suggestions, and I'll be happy to add yours to the list. Don't hesitate to use the contact form to suggest new features. Please note that requesting a feature doesn't mean it'll get instantly done. My goal is to create a strong yet generic basis for a platformer game. If your request is very specific (like a grappling hook or a portal gun - although I reckon that'd be pretty fun), it probably won't make it. The engine is for everyone, not just one user, and what you need is very valid but may not be what most people need :)
• How easy is it to do this thing I want to do ?
  I don't know. How easy something would be to implement depends on your skills, not mine. I can't answer that for you. Usually if you're asking the question, that means you have no idea how to do that task, so I'd say "relatively hard". Break your problem into smaller problems and see how you could address them. And maybe look at the documentation and list of features to see what the engine can do for you regarding these specific problems.
• What's the awesome music I can hear in the demo levels ?
  That would be The Victory of Buckets and Doors and There is no Way, by Uniform Motion, which is probably the best band ever, check them out.
• What are the minimum prefabs I need to start a level from scratch ?
  I get that one a lot actually, so I've included a "minimal demo" scene in the assets. It contains, as the name implies, the only assets you need to get started.
• The asset is not working with my gamepad!
  Controls have been set up for keyboard and xbox pc gamepad. Obviously including support for every gamepad/configuration would be impossible, so I just went with the most common conf. Luckily for you, this has nothing to do with the Corgi Engine, and is really a general Unity matter. You should be able to find the right conf by googling it or on the Unity forums. Key binding is set up in the engine like in any other Unity project, via Edit > Project Settings > Input.
• The asset is crashing on my device!
  My guess is it's a performance issue.
  - does it work in the editor ? If it works in the editor, your device may not be powerful enough to run it.
  - does the MinimalLevel scene alone work on your tablet ? If it works, your device may not be powerful enough to run larger levels.
  This is a general Unity performance problem, nothing really specific to the engine I'm afraid. If you absolutely want to run it on that device, aim for smaller assets, less enemies, stuff like that. Mesa1 level for example does include some very large assets (4096x4096 backgrounds for example), clearly not fit for slow devices.
• Where can I change the input settings ? I don't like pressing A to jump!
  Like in any good Unity project, the settings are defined in the Input Manager. You can access it via Edit > Project Settings > Input.
• How can I add my own mobile controls, or the ones from that asset I bought ?
  If you look at the current mobile controls, you'll see that each button has its various events (button pressed, released, etc...) bound to methods in the InputManager class. As you'll see, this class is full of simple methods like Jump(), RunStart(), etc... It acts like a remote for your character. If you want to replace the mobile controls included in the asset with your own, you just have to remove these, and bind your new buttons/controls to these InputManager methods.
• What programming language is the asset written in?
  C#
• I'm completely new to Unity/C#, can I buy this and make a game?
  The short answer is no, it's likely not a good idea at this point in your journey. Like any other tool, it's best to learn the basics of Unity before adding more stuff to learn on top of it. Without any knowledge of Unity, you'll probably bang your head on simple problems, simply because the extra learning curve will make things too hard for you. Without any C# knowledge, you'll be limited to the features already present in the engine. And while there are many of them, it's of course best if you can build on top of it to make your game unique and interesting. So if you can and want to, take some time to learn Unity's basics, set achievable goals for yourself (recreate Pong, then Pacman, for example), take baby steps and soon you'll be able to have a look at bigger frameworks like the Corgi Engine or others. A good way to know if you're ready for it or not is to look at its documentation. If you understand most of it, go for it.
• Can I add this to an existing Unity project?
  The Corgi Engine is what Unity considers a "Complete Project", that means it ships with its own project settings (input, layers, tags, physics settings, mostly). That allows it to work out of the box. The project is meant to be a foundation you build your game on, so usually you'll want to add stuff on top of it, instead of adding it to an existing project. If you decide to still do so, the easiest way to do it is to create a separate project, import the engine there. Now you'll need to merge settings. You can either just copy and override files from the new project to yours, or you can edit them and only bring the parts you want. And if you're using version control, the best way is to merge them using your VCS tool and cherry pick what you want. You'll want to make sure you bring over InputManager.asset, Physics2DSettings.asset, TagManager.asset and DynamicsManager.asset, the rest isn't too critical. Whatever you do, make sure you backup your own project settings first, in case something goes wrong!
• Can I mix this with the Infinite Runner Engine, Highroad Engine or the TopDown Engine into just one project?
  All of these assets are what Unity considers "Complete Projects". That means that they come with their own dependencies, and their own project settings (input, most importantly, but also layers, tags, etc). All of these assets were designed to be foundations on their own, not to be used together. It's of course possible to do so, but you'll have to do some refactoring, and this is not officially supported (it'd be impossible to maintain compatibility across all assets at all times). If you decide to do so, I'd recommend unifying MMTools and input first, the rest should be pretty straightforward.
• Are there any legal things I need to know about? Can I use this asset commercially?
  You can absolutely use this asset commercially. What you can't do is redistribute the asset (or parts of it), but you can of course use it to compile a game and sell that game. Apart from that, the only copyrighted things are the asset's name, and the placeholder music tracks, that you can't use.
• Do I need to display some form of credit?
  No, you don't have to. If you want to it's fine though, in which case you can put a "Made with the Corgi Engine" mention somewhere.
• Am I allowed to use the code in more than one project ? Can I modify the source code or the visual assets ?
  Once you've bought the asset you can do anything you want with the source code, you're just not allowed to redistribute it (offer it for free, sell it anywhere, etc). You can of course use that code to create commercial games and sell these, just don't redistribute the contents of the asset. And yes you can modify it, use it in more than one project. It's yours now!
• Can I just compile the asset and upload it without changing anything to Google Play, Steam or the Apple Store ?
  Well no you can't. Although this sounds like a genius masterplan, I'm afraid it's not legal. Be imaginative, create your own game. Of course you can use the asset as a basis, that's what it's for.
• I really love the asset, is there any way I can help ?
  Of course, you could put a nice note or review on the asset on the Asset Store.
• What is the Corgi Engine? Why did you create it and how? Will you stop soon?
  I've been making games for a long time (professionally since 2003). It was mostly Flash games back in that day. Then I took a break from games to focus on mobile apps and UX for a while, then came back to it in 2014, mostly due to my obsession at the time with Rogue Legacy.
  
  I started reading Unity's documentation, watching tutorials like this one, this one, or Sebastian's ones. I ended up with a platformer game, but back then I didn't have time to actually focus on it and finish it, balance it, create levels, etc. All I had were base bricks, and a growing love for building them. I put what I had on the store, not sure anyone would be interested. My reasoning at the time was that if a few people bought it, I would be able to buy a game or two on Steam.
  
  It turned out to be pretty popular. The first few months saw a lot of full rewrites, as the first versions weren't that great, using the wrong patterns, and generally packed with early days mistakes and performance issue. After v3.0, things started stabilizing and the engine has kept growing ever since. A massive community built itself around it, and now plenty of amazing games have been released using the engine.
  
  I now work again in the games industry as a gameplay director, and Rogue Legacy 2 is using the engine. There are absolutely no plans to stop updating it, and keeping all updates free.
• Who are you? What is More Mountains?
  My name is Renaud Forestié, I'm a French game designer based in Montreal, Canada. I also do illustration work and I'm available as a freelance. I founded More Mountains, my creative studio, in 2015, after 15 years spent as a freelance art director and game designer.
• Got another question ?
  Are you sure it's not answered above ? Then you can join the discussion on the Unity Forum thread, or send me a message using the support email on the asset's page. Or you can use the form above. It's up to you :)