Hello everyone!

The first order of buisness, we now have a public Discord. Feel free to stop by and say hello, ask questions, or show your support.

It's been a while since the internal playtest. Feedback was good. The holidays came and went. We've taken this time to iron out where we want to go and what the road-map for the future is.

Public Demo is the big milestone we're aiming for. Internal playtests were favorable, and we really want to get the game into as many hands as possible while moving ahead. To support a wide release however, we're looking at restructuring some of the behind the scenes how matchmaking and server code works. Currently the engine takes every and any two connections it receives, and pairs them up with each other. For internal multiplayer testing, this works fine, but for a wide audience, some kind of server browsing will be necessary to see who is playing and be able to pair up with the people you want to pair against.

If the public demo goes over favorably, we have a few irons in the fire we are considering, mainly facing the realities of developing a full game, which means bringing on more people, considering sources of funding such as crowdfunding campaigns, and boosting our signal to get more notice by the public at large.

Looking For A New Programmer on that topic, getting out the public demo in any amount of time will be an undertaking in itself, so in that regard we've opened up our doors and are extending out feelers looking to bring another programmer on board in a permanent position. The team has agreed we're looking for someone who is experienced with Phaser already, who can slot into the process and hopefully stay with us until launch, do work on various aspects of the game from odds and ends, to helping with things like pathfinding and AI.

If you're interested, we have a post on the HTML5Gamedev forums with more information, or you can contact us at our email, on twitter, or on the new public discord.

Playtest Results

The first wave of playtests has ended now, to promising feedback. Our initial playtest protocol was refined across the many playtests until we reached a smooth streamlined process, complete with local recording of matches for later review, a lengthy questionnaire covering various aspects of the game, and free-form comments from the playtesters.

Major points of feedback:

• The Unit Watcher was not well understood. Pictured right, the watcher shows the same basic 'selected unit' info as any other conventional RTS, albeit in a more compressed format. Unit name, picture, health bar, defense, and attack damage against all other unit armor types is listed out vertically. The small blue dot indicates what type of armor this unit itself possesses. Sadly we are taxed for HUD space and cannot display this data anywhere else or in an expanded format without nearly a complete HUD overhaul, but I agree there is room for improvement.
• Terrain defense and speed bonuses were also not well understood. Another problem area for playtesters was the effects and benefits of terrain on their units. Unique to SCS' gameplay, the type of terrain a unique is moving over widely affects its speed and defense. Continuing the Starcraft comparisons, a Stalker will always move the same speed anywhere on the map, and always deal the same damage any target it shoots. In SCS, moving through trees and mountains will buff up your defense with the cover they provide, while greatly diminishing their move speed. Inversely, roads make units move faster than they would otherwise, while providing them next to no defense against unexpected attacks.
  These two areas struck us as problem places that require attention, because these speed and defense buffs are integral to the core gameplay design, not something we are about to just toss out because playtesters didn't understand them. They need to be represented in such a way that its obvious and natural that a marine moves faster than a tank would in Woods or that a Tank cannot pass over Mountains the way a soldier can.
• Some units were God Units. Part of playtesting is always the balancing, and while our initial balance was good, nothing shows its flaws like outside players given a chance to try to exploit it. Very rapidly we were shown which units were 'god units', capable of beating nearly any other or being too cost effective. Sidecar Scout Bikes rapidly proved themselves to be the single most powerful unit in almost all matchups, in large numbers even overpowering tanks meant to be their counter. Healing units such as Medics and Engineers also rated highly due to their ability to keep said Bikes and other units alive a bit too effectively, able to out-heal most incoming damage with ease. A quote from one of the playtesters:
  "Rush bikes, I win if my bike comes up before he can defend against it, I lose if he counters it."
•  Without CO powers, it was easy to build game-winning momentum. In the current tested build, the key element meant to counteract steamrolling momentum is not yet finished so wasn't implemented, and as the players become more skillful with their unit composition, it showed. Rapidly capturing half the map/s points proved the income difference was usually enough to guarantee a win depending on player skill, as there were still some dramatic turnarounds when players out-positioned their opponents.
• Improved unit control was the most requested feature by far, as basic commands such as Hold Position were barely implemented, and others such as Patrol completely nonexistent. Better player information also was highly rated, tooltips being second most requested as without previous knowledge of the game, there is very little to tell you what that an Attack Dog can't attack tanks, or what the tank with the long barrel is a Tank Destroyer.

Major planned changes consist of:

• Locking the mouse cursor to the game screen. A common problem almost all the playtesters had was with the fact that the game doesn't lock your cursor into its own window. It runs in a browser but we as devs had become so used to using arrow keys to pan the camera that we didn't realize how much people relied on edge panning.
• Tweaks to Attack-Move behaviour. Another oversight of ours was how ingrained the RTS standardized controls are to RTS players. For example, in Starcraft, you press 'A' to order an attack, then left click the location or target you wish to attack. in SCS, A is held down and then right click is used to issue the order, like any other targeted action. This confused several of our playtesters who were used to Starcraft's style, and while both have merits, it might be easier to follow their conventions.
• Better Visual Feedback. Given that none of the playtesters in this circuit had experience with the game before, we found it very common for them to miss things that we thought were 'obvious' after having played the game for 1,000+ hours ourselves. Your headquarters being captured was the most prominent, as its loss spells your defeat. Playtesters wouldn't notice it being captured because the only 'announcement' of this was just a sinking bar next to the structure indicating capture progress.
• Unit-building Structures beyond the HQ were universally ignored. This one is a bit tougher to rectify. In most matches, even when facing an opponent attempting to play a teaching match, playtesters wouldn't realize that structures other than their initial HQ could be selected and produce units, even when watching units appear from no where atop those structures for the enemy side. Even the experienced players in times of stress would default to only building at their HQ, instead of the multitude of Factories across maps.
• Mousewheel to Zoom. This one is a bit tentative as it has to be done right or else the pixel art graphic style will get all blown up from mis-scaled pixels. We've squashed dozens of strange pixel glitching and artifacting in the past that scaling for a zoom is a can of worms to open up again.

Thanks to our rigorous quality controls, bugs were few and far between. High lag occurred when a match was run overseas from Canada to the UK, but beyond that there were next to no desynchronization issues. Occasional graphical glitches such as sprites overlapping that shouldn't popped up, but were easy rendering order fixes to be squashed,

As for moving ahead, the waters are still murky as we plan out when/how public releases will be done, the development schedule of features new and old, and evaluating this feedback and its benefits to further development.

The Command Card

Big design block on how the command card is going to work, as well as what kind of actions you can order your units to take. All the usual actions you can expect from an RTS are there, from Moving and Attacking to Patroling and Holding Position. 

Devblog 2.0

I'm proud to declare the retrofit of this devblog complete.

It took just under a month from start to finish. I realized that the blog's original look was aging badly and holding us back as production on the game ramped up, and that it was time to give it a new coat of paint to better represent the game.

The old look was grey and drab, as shown here.

So I took it upon myself to draw a new design. This is the design sketch I mocked up in Photoshop on April 24 as my vision of the new look.

As you can see, as it was implemented certain design aspects evolved into new shapes. Tapered edges turned out to be more trouble than they were worth. The Twitter widget was broken for a long period of time, finally fixed by disabling "Exclude Replies" as for whatever reason, this was excluding all our tweets.

I didn't do this all myself however as CSS and HTML are not my primary skillset by any means. A friend of mine Esther put in a few hours guiding me in the proper ways to margin, border, background, and generally improve the website as a whole, so they deserve 50% to 99% of the credit.

Along with updating the look, I'm also proud to announce our official Subreddit (now linked under the Forum button) as well also took the time to go over the Media and About tabs that had been long since neglected. They now contain more up to date screenshots, the pre-alpha trailer, and a blurb about the game and our team.

State Of The Game 2016

Hello everyone, it's been a long time.

Where have we been? For a while, the game went on hiatus, but we are back now. We've brought a project manager on board and expanded the role of game designer. As of roughly three months ago, the game has resumed active development. A new programmer was brought in and with his help we have started to set up sprints and meet daily goals.

Trello, our team's management platform showcasing the active cards.

What has been done? Extensive bug fixing to make multiplayer stable and implemented tons of missing features to make game play closer to the vision, the map format has been overhauled to support a more user friendly format. The terrain atlas has been restructured and expanded from 512x512 to 1024x1024. The HUD was tossed out in favor of a new style. Collision maps have been added for the multitude of terrain types. We expanded and clarified the roles of game designer and project manager; who developed a more disciplined development methodology based on sprint and agile techniques.

Where are we going? The current goals are:

• Internal Alpha - Internally we've been working hard to make sure the game runs smoothly and patching anything that prevents this such as multiplayer desynchonization issues.

• Closed Alpha - Once the game runs cleanly internally, testing with a broader audience will begin initially only open to close friends to gather feedback.

• Open Alpha - With the changes brought on by external feedback in place, we plan to release a demo version that, while far from feature complete, should have all existing systems fully functional including online matchmaking. 

Most recent screenshot of the game running, featuring an entirely new UI.