Since my first blog I've been putting together the overall architecture of the game. You can see some of the initial work in the commit log on GitHub. This can...
Ran out of room. I'm sorry to be long-winded but I feel like it's important.
"I think the coding part of Construct is under-utilized and is strongly competitive with other more coding-focused tools".
I'm sure that is true but the biggest sell of the engine is the event blocks for a crowd that doesn't want to stare at walls of text while building a game. For this, there is really no competition out there. You guys do it the best.
As far as traditional coding goes... Unity is a fantastic option for those who are happy to go down that road (without the need for a subscription).
At the end of the day C3 is still my engine of choice. It is powerful enough for my vision and I still love the event blocks. I do think the blog itself is fairly off-putting though. The part about *maybe* using events for the menu's is particularly on the nose for me.
Again, sorry for the negativity. I only say this for the passion I have for your product.
I think I'm just repeating myself here, but the goal of the project is to show Construct can be used for coding, as well as event sheets. I guess it might not be for everyone, but I've set out the goals and gone in to detail about why I've gone in this direction.
Thank you for the response. I did read what you wrote Ashley. I'll be honest in that a lot of it goes over my head, but that is why I am here in the first place.
Over the years I have seen people dismiss construct, refer to it as a toy. When you of all people avoid using events it only pushes that stigma further imo.
Could you not overcome some of the shortcomings by making some new plugins specifically designed for RTS's? It may not be pushing the limits but it might get the job done and would certainly help the majority of users a lot more.
I only say this because I want you guys to continue to succeed. When I read things like "we would expect the most advanced users to shift from event sheets to coding" it makes me question my long-term investment in construct 3.
If people like me decide to code, then you have just jeapordised your next sub by putting yourself in direct competition with Unity. I don't know why you would want to do that.
I mention in this blog post how, for this architecture, it's actually impossible to use event sheets fully, because it's going to use multithreading.
There are already loads of big and impressive games made almost entirely using events in Construct, so I don't really feel we still need to prove that point.
I don't know why someone deciding to code would jeapordise anything. The fact Construct lets you do coding too means if you make that decision you can keep using Construct. If we had no coding support at all, then someone in that position has to move to a different tool and so we definitely lose their subscription. And it's not all about Unity - there are other coding tools Construct is strongly competitive with.
IMO, It jeapordises many subscriptions because most I assume are here to use events and you guys are the best for that. If I start feeling the need to code then all of a sudden you have plenty of competition.
I wasn't aware that there were no mainly scripted large games made with construct, that does change the situation a bit. I could be biased and say that supports my claim made above but who am I?
I'm not suggesting to remove the ability to code entirely. And I definitely don't blame you for making your game whichever way you see fit. Maybe I read into this too much and I truly apologise if that is the case mate.
I just hope that you don't move forward with the mentality that advanced users switch to coding because I can't imagine how that wont translate into less time spent on improving further your main selling point and the reason why most of us are here.
It's not like we're taking away anything from event sheets. Everyone can choose whichever usage suits them! We're just providing extra options: event blocks, code, or a mix of both.
Very, very, very few "big" games use Construct. Out of those, even fewer use the C3 runtime due to its limitations. This is a willful misrepresentation.
I meant there are already lots of examples of larger Construct games made just using events. I wasn't trying to claim that we have a big percentage of the gaming market or anything. I don't think there are any large Construct games made mainly using scripting, and I'd like to provide an example of one with this project!