In September I started part-time development of a real-time strategy (RTS) game in Construct using Javascript coding. I've been posting regular updates on it on...
Thank you for explicitly starting with reaffirming Scirras commitment to event sheets to address the concerns of many C3 users.
It might be a bit early for it but would you be willing to port the same game over to event sheets after you are done with the JS version (or a different game of similar complexity)?
Obviously a port to events sheets could not support as many units and such, but would still create the opportunity for even more C3 improvements, but this time more focused on the visual scripting workflow.
I think a port to event system by Ashley isn't feasible, since it's only a part-time project to show "JS" capabilities of Construct 3.
However, this game is open-source and the community doesn't have to wait for Scirra's permission to get involved with a port. I personally would volunteer to do a small portion of it and with a dozen more people, it will be possible.
You are missing the point, no one cares about the end product, it is about Ashley working with the engine, on a complex project, in the same way the majority of his customers do. With event sheets.
Optimally he would actually run into every single possible problem users have experienced, so that he can find a way to fix, or improve them.
Also, "no one cares about the end product" is too much of an exaggeration. When did any of us got selected as the representative of everyone?
Ashley is creating a complex project using the end product to refine the end product itself. So how is it unrelated?
"No one cares" as in "who cares" as in "it is not the point of the exercise", not what people are looking for.
But I do see how that could be read the wrong way.
While I obviously can't speak for everyone, I certainly communicate with a lot of C3 users who feel the same way, which the amount of thumbs up on my initial comment supports.
I think you're the one missing the point here. He is running a business and a business has to grow while it is trying to survive among the competition. The majority that you're talking about, including me, are often hobbyists who barely breakeven by publishing a game. But when professional studios seriously consider Construct, it will get more resources, more marketshare and more pro features. Game studios will likely use Events for the prototyping stage. What comes next is a proper coding language and a deeper access to the engine itself.
Scirra is pushing for recognition of Construct 3 as a battletested game engine and a key player in the industry. I personally haven't found a flaw in the event system itself. Its decade-old architecture, yes. But the system itself works as it was marketed. So it would be helpful if you could elaborate further on the kind of problems that you experienced when the event system was the main cause of the problem.
So you are a hobbyist like the majority of C3 users... that's literally what I'm saying, most C3 users are hobbyists, or small single person indie devs who use Event Sheets, not JS, to make their games.
So that is what Scirra should try to improve.
I do agree that there should be better tools for pros. But I also think that I should be allowed to ask for at least the same treatment and care for event sheets without you coming along and declaring on behalf of Ashley that that isn't feasible for some reason, and then getting agitated when I point out that you clearly missed the point I was making with my comment.
Your solution, to your made up infeasibility of my proposal, is to let the community port the game.
Which isn't the point. It's not about the finished game, it is about Ashley using his own product the way most of his users do, so he can improve Construct with that knowledge/experience.
And congrats that you never ever had any issues with C3 I guess.