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 also think that this scenario you are using to test is not very representative of actual gameplay if this will be a classical RTS.
With 1000 vs 1000 units I would guess that the pathfinding and especially collision avoidance between tanks, when they are actually controlled by a player, will be the much bigger performance challenge and will also cause a lot more delta updates which probably drastically reduces your current bandwidth savings.
Why do you have to update the positions so frequently at all? It's not an action game, shouldn't the units move based on pathfinding? With pathfinding you could only send the mouse click position to the server, calculated the path on the server and send it back to each player. It can then be played almost like an animation, that only gets interrupted through events like getting in range of enemy units or buildings, which could be handled like the projectiles with these network events, which, in addition, could send a full update for that unit.
Though I can see how your method is a more generalized, catch all approach and doesn't need specific planning for each new feature, though I guess we'll have to wait and see about that.
"I have to write custom collision detection code" #MadeInC3 🤡
I'm sorry if this came across as some kind of attack because that's not what I wanted.
English isn't my first language and these were meant as idiom in case that wasn't clear. What I meant with it was people feel betrayed, but that actually sounded more melodramatic to me than the idioms I used.
If you want I can edit my comments and replace the idioms with "betrayal" if that is more appropriate.
Like I said before I didn't expect you to change course, but you said you don't understand why people feel "betrayed" so I wrote it from a users point of view.
And yes these are angry comments, that is because I am angry. It is yet another thing Scirra does that I don't agree with.
I'm sorry that this comment started off with the wrong tone, but It is just very frustrating when again and again you feel like your criticism isn't taken into account at all.
Feels like if the comment isn't angry it is ignored, if it is angry it is inappropriate.
Then you announce that you make a game with your own tool and tell people it is to test the engine, to taste your own dog food.
The expectation is obviously that you will finally experience these issues yourself now and get a better understanding of them.
But then it turns out you skip over all the issues that the vast majority of users struggle with for years by using JS instead of events.
If you like it or not, the message you are sending is, for "real games" you need "real code".
Which is the polar opposite of the dream that you are selling to people for over a decade.
And that is what feels like a stab in the back.
And I genuinely don't understand how you can't see how this is a punch in the guts for a lot of users.
- The majority of people use Construct because of the promise that it advertises, no coding required
- Everyone obviously wants to eventually make their dream game and for a lot of people that is something bigger
- Construct has a bunch of issues when it comes to making bigger games, not only in terms of performance but especially in terms of organization and structure
- We were always told that Construct is capable of these big games and that events are perfectly fine for it (and yes there are bigger games made with it, but most of them moved on to other engines after release and some jump ship even mid development because of these issues)
- People asked for Scirra to make a game with their own engine to see these issues, since they can't fit in a bug report and are hard to communicate. The suggestion page is full of a million guesses how to fix it which creates an even bigger mess
Well that's the problem isn't it. You either can't, or don't want to see it yourself.
(Btw idk if you can see that or not, but just to be clear, I'm not down voting your messages)
This is exactly the way most of your users are reading this.
It doesn't matter what you write, actions speak louder than words.
I complain all the time, but even the people that usually kiss the ground you walk on are voicing their disappointment over this one.
But it's a wasted of time to argue, you already made your choice.
Nice message from the main developer of Construct,
we made little examples with event sheets, but if you want to make a real game the event sheet system isn't enough.
That sounds veeery very different to the messaging we got for years and years from Scirra when we were the ones making games with Construct.
Feels like a total backstab.
I think this is a great idea.
Though using mostly JS isn't Doogfooding your engine IMO, it's mostly dodging the engine and it's shortcomings rather then finding and fixing them.
"No coding required" is literally the #1 feature on the homepage, and "Coding optional" the 2nd.
Excited to see some gamedev from you none the less.
I thought this is what this update was, but it seems like it isn't :(
I tested it with the updated chat example, and if the host disconnects it's just as before, no one can chat anymore. Maybe they forgot to updated chat example?
Yes! Big thank you from me too, best addition.
I don't know how difficult or easy it would be to add the ability to change the sampling modes ( Nearest, Bilinear, Trilinear ) of the Drawing canvas independently of the projects sampling mode?! But if that's something that would reasonably be possible, it would be a really useful addition to the Drawing canvas as well.
I'm already very happy that we can set a fixed resolution now and no longer lose the content of the canvas on rescale though. This opens up C3 to so much more possibilities.
Freaking praise the lord
Member since 29 Apr, 2013