We have created scripts to run through the sequence we require. Every action can be controlled in one menu. 

The Player starts the game with a comic, then immediately the Captain urges the player to land on the planet. We select a location and off we go. 

This system allows us to create popups that portrait certain events, like selecting a  landing zone a.k.a. the first level...

Or the introduction of a new unit...

The event of the popup can be modified according to the needs, in this case, an enemy model gets loaded in idle mode and a text is loaded from the text sheet to provide details about the unit. 

I want to share a brief overview about our inhouse project management organisation and the tools we use. We have a small team and can communicate short ways based on the fact we are most in the same office during the day. But we have team members that work externally, and sometimes home office is in order if the harsh winter messes with the heater.

For a project of this magnitude it is necessary to have good tools for organizing the amount of tasks and content for our game. In general you could say that we established a more or less agile development environment that makes use of some techniques known from Scrum without sticking too much to it. We try to have regular meetings and give decent feedback rounds to features and assets within the team as soon as possible. For inhouse communication we started to use Slack a while ago. https://slack.com/ 

Many of you might be familiar with Slack, but for those who are not,  here comes a small description. Its a free tool for team communication, where you can have multiple chat channels based on separated topics. Even though there is a Pro Version for more specified needs, bigger teams and bigger projects, we are fine with the free version.

So it is easy to organize separate theme related chats, for example one room for art, one for programming, one for game system design. 

You can share pictures and files, have closed discussions, create multiple chat rooms and much more.

Personally, the most positive aspect is that you can find older entries and especially files more easily compared to skype chats.  In the background we use a well known solution called Atlasian Bitbucket.  https://bitbucket.org

Its perfect for our needs. We integrated it within our development structure and our version control of the project (using SourceTree). The dashboard is clean, simple and provides a good overview.

The bugtracking functionality is quite similar to other tools like Mantis, Redmine and follows established QA standards. 

We don’t connect it to JIRA yet, but might do so in the future to have more possibilities.We use it mostly for priority and dependency tracking of bugs and features. One benefit is that you can tag specific branches directly to existing bugs. The seamless integration works great. It supports multiple Teams, repositories and projects. 

The software also offers many other features, like it’s own wiki.

For our daily task management we use a solution called HackNPlan. http://hacknplan.com/

Its a pretty nice tool, still in Beta, but the developers put a lot of effort in it and it offers a great and solid toolkit at this early stage.

It follows the rules of a Kanban board where you can edit or pick single tasks and move them over the board whatever state they are actual in > Planned, InProgress, Testing or Completed. 

Right now we are moving from milestone to milestone based on our project plan.

We keep a growing backlog were we pull tasks for upcoming milestones from and try to keep short sprint periods for bigger development cycles.

Each task can be given several sub-tasks. We are still learning how to reduce task size and break it down more efficiently at the moment.

A single task can contains all the necessary information for proper monitoring like specified due dates, multiple assigners, milestones, estimated time and more.

It helps me monitoring time frames for single tasks to get more efficient in future planning of sprints and the performance of the team.

The offered dashboard for project metrics visualizes every aspect in a clean and easily readable way. You can evaluate performance for each part of the project and have an overview about delays and performance breaks. The possibilities for personal settings are also great.

We are looking forward for future features of this great tool.

We  hope this short excursion provides some insights for you guys.

We are currently working on the level design for our upcoming mobile tower defense game @planetelysiatd. Today we want to show you how we put together a level in Unity.

We set up the waves for the game with Splines inside Unit. All enemies move on predefined lanes that we usually define in triple splines. Then we define a start and an endpoint for the enemies to follow.

.

These are the core layers for the game. Based on a 2,5D world system, the level consist of multiple 2D layers divided into foreground and background layers. The background is prerendered partially in 3D and imported as a single picture to save resources. Animated 2D background elements on sprites can be setup in various layers to give additional depth to the scene.

Background lava shader

Foreground level render

Foreground lava shader

UI Elements layer with the UnityGUI

3D Elements, as in heroes, towers, enemies