UPDATE:

Made some changes to the topic to reflect the content added with our last patch.

Level Editor, new level & more have been added!

UPDATE:

We updated the entire topic to reflect the game in its actual state, also we'll be releasing on Steam Early Access on March 24th!

Feel free to spread the news and share it to your friends and families!

InsaneHawk yep it's all good. it's great you have that many testers! I hope they have been giving you good data.

has there been tons of work since all the feedback? I haven't officially went through that step yet so I'm just wondering how it is. I'm sure you are in feedback overload. I hear also you have to read between the lines to figure out what is actually being said since the player (or non devs) don't know how it was made, they are only seeing the end result therefore the feedback is sometimes strange.

I'm very thankful to have such a nice and positive community for now, and even if most of them don't know precisely how game making is working, their input as a player is very important, because there's such a large variety of players, that from one to another, the experience might be completely different, so every feedback is important.

A lot of their feedback has been implemented since the alpha, and we'll keep going as they're going to play the game in the end, so it's our job to make sure they enjoy every single part of it as much as possible!

looks great, are you still looking for testers?

Yes we're still accepting applications, you'll find all information on Discord!

UPDATE: New patch recently kicked him, which result in the second chapter to make its entrance!

Here's a preview of what's in this patch, took this opportunity to update the topic at the same time!

> kinda of like the journey of the function plugin, it was a separate plugin for a long time until it became a first class citizen of then engine.

I'd really want to avoid going through that again. Replacing a major feature with a different and not entirely compatible one is a painful transition to go through for both us and many users. It also leaves us supporting both indefinitely, as there are always too many remaining projects using the old feature to justify removing it. It's much better to get it right first time wherever possible. The only reason we didn't with functions was it was designed in a hurry in the early years of C2 with many shortcuts deliberately taken, and the replacement was so much better (and so many people were asking for improvements) that it justified all the pain and awkwardness of going through a replacement.

We all know this proposal about the global sprite with instance vars acting as an enum (by all I mean, people working with Construct for quite some time now) but as you mentioned it is a workaround. It works very fine, and sometimes is enough, but how about new user experience? This isn't something new users can get that easily, and when I first started Rhythmy over two years ago now (as an example) I had no idea this could be done and just assumed that enums/lists just weren't a thing (and in some way, they're not as this is a workaround

if the work around is the preferred choice, it should be its own object type (not associated with sprite, which has has rendering/world properties etc)

If my proposal would require too much work, maybe this could be a solution, because it makes no sense to make an empty global "sprite" to make a static enum? (and for new user experience, even less)

But maybe looking forward to an official solution like this, that won't require a massive rewrite of the engine as you mentioned, because that definitely won't be possible with the current ressources you guys have, maybe this can be a solution that won't require an insane amount of work, and improve overall workflow.

And that way, you won't be "erasing" or forcing replacement for people that were using the old workaround, because as it's a workaround, it would still be possible, but you're giving the opportunity to have it supported more "officially"