Hey guys, how have you been? We haven't posted a devblog for a while.. and I'm going to blame discord. We talk to the community there. I hate it. You shouldn't have to lurk in discord to get updates.

So lets start doing this again. Here's our current priorities.

We've had instances where we broke shipped games. We shouldn't ever be doing this now. We should be bending over backwards to avoid it.


We now have a system as part of our build process, where it checks a list of games, and if they don't run it won't let the new build build.

We also added version upgraders for the component system, so if we change a component, we can add code to take older versions to the new version, which should avoid any issues.

If we break a game you shipped then please shout at us so we can fix it before people start relying on the new behaviour and we can't change it back without fixing another game.

The API section was cleaned up, to make it easier to discover APIs you don't know about.

We've got a Developer Documentation site that we've been trying our best to keep up to date. Please shout at us if it's not.

Where possible we've been deleting and reducing to create more clarity. We've merged this site with asset.party, to become this site. One site instead of two.

In the editor we previously let you open a bunch of different projects at once. It was confusing and we got ourselves into a mess. You can now only open one project at a time. This is aligns with expectations and simplifies everything massively.

We added a library system. 

Instead of downloading some compiled assembly from somewhere and not being able to edit it, we opted to download source code into your project folder. 

This has a few advantages. Like you can view the code, so you know how to use it. And you can edit the code if it's not doing what you want. And finally, it's never going to change without you changing it.

We've been getting better, incrementally, every day. The community is doing a fantastic job at finding and reporting any issues that they find. The editor is getting prettier and more stable every week.

As well as Libraries, we've added a bunch of nice things to the editor. From simple things to multi-select editing, to more complex things, like in-scene map creation.

We recently improved the editor with the scene tab system and multiple viewports.

We've converted the sound system to an Audio Mixer system. This system lets you play particular sounds through a particular mixer. This mixer can then have its own volume and other processors.

For example, you could have a mixer called "Weapon" as a child of the "Game" mixer. You could decide that all of your weapons are too quiet, so turn up the volume of your Weapon mixer. But then you might want to add some echoey reverb to all the game sounds in your scene, but not affect music or ui sounds, so you can add a processor to the "Game" mixer.

This system is still a work in progress, but it's infinitely more configurable than what we had previously.

We've been looking at the game itself recently, and trying to find ways to keep people online.

One of the problems is that we're shoving all of these broken, shitty games in people's faces. So we've added a Featured section, which allows us to hand pick a bunch of games to show people.

Another problem is that you think people are playing (because of the player count), and you click the game, and they've already stopped playing. So now we have a new section on the main game's screen, called "Active Servers", which is at most 5 seconds out of date.

We added a party system to the bottom left of the screen. This allow you to create a small group and drag them with you into and out of games.

But generally, everyone playing the game right now are using the editor.. so we still have lots of work to do to get people to keep playing. There's a few things we're going to be trying over the next few weeks.

Our performance isn't terrible. Sometimes it's actually quite good.

We're working on a benchmark system in an attempt to target specific metrics and track how they change over time. We want to make sure that what we do has a positive impact on performance, instead of a negative impact.

The benchmark system will be used to prove performance issues, and then prove their fixes.

One of the things we're going to be doing is getting rid of the invite system. It worked, and it was fun, but it's too much work.

It's time for us to be brave and open up access a bit more. In the new system you will be able to sign into this site and grant access to yourself.

It's still a closed preview, because we can revoke access at any time, but it's an open closed preview. 

I'm going to make more of an effort to post these updates more regularly. We're doing a lot of stuff in the background, enough to fill a devblog every week/month, so there's no excuse other than laziness.