To be completely honest, I had a childish fantasy when looking for Game Making Engines that don't code but events that I would eventually find one that was exactly like Construct 2 but its code was in C++ or C# or perhaps Python (this was before I ever found out about Construct 2) and that I could simply make my games like a real developer without getting my hands stuck in the Matrix that is code.
And when my game was done I could simply click export like in Photoshop or Premiere Pro or After Effects and it would ask me which platform to export to and some other stuff and I could get my PC game.
The closest I got to that was Construct 2, but it's in HTML5 which is reliant on browsers so I can't just poop out a .exe out of the engine without worrying if Node-Webkit or something else was buggily designed. I meant what if development for Node-Webkit stopped all of a sudden. We'd be struck with a wall all of a sudden.
I read something in a manga called "Tower of God", a character in it says something about people that I think applies a lot to game engines, not just Construct 2.
[quote:3298cbiv]God is quite cruel
When he first shows you this world
It makes us feel that we could do anything in this vast world...
However, with a sudden appearance - He tells you, 'Thats your limit'.
Even though there are so many things that we want still unfulfilled.
I really think that extends to game engines, when I first got Construct 2 I was literally exploding with development, I was making features left and right, then I hit a little fence and stopped for a couple months, then I kept making features like before, then another bug but this time it was only one month, now I'm here after fixing it and doing more in-depth research into the features that my game will require.
When we first get a new game engine, or just start for the first time developing a game. We're filled with all these exciting emotions that we're finally going to make our own game! We're no longer going to be just gamers, we're going to be game-makers as well!!
Just soon after, or often immediately, much like game characters themselves, we get smacked in the face by an invisible wall.
We do not see how to bypass this wall as it's invisible. That wall is very much game engines, when we use an engine that relies on other companies to make features or exports, we become that helpless little game character that is stuck waiting until the invisible wall either gets remove or we give up and walk away. There's always the option of hacking the game and making mods, but who has time or knowledge to create engine extensions and exporters? Not everybody is a knowledgeable coder and programmer.
Most of if not all of the people using Construct 2 came here because they didn't have use code to create games, but like everything there are limits, some have more than others.
I understand and know that HTML5 is great, I have no problem with it or it being the language which Construct 2 uses to code games, I just solely wish we had the ability to create native desktop apps. I played a Construct Classic game, Minitroid and it plays a lot better than Node-Webkit. There's no micro-stuttering or anything else (even now, with Node-Webkit updated to newest release, when my character jumps he kind of sways left to right by around 1-2 pixels).
newt said [quote:3298cbiv]Think more new editor, less new engine.
If Construct 3 is just going to be a really big major update of Construct 2, I'd rather it be released as "Rxxx" rather than Construct 3.
I'm probably sounding super naive in saying this, but I had dreams that Construct 3 would be a lot different than Construct 2 the same way Construct 2 is a lot different to Construct Classic. The programming language changed from DirectX to HTML5, the UI is a lot better and looks a lot smoother.
The least I'd personally expect from Construct 3 is at least a programming language change, I know that HTML5 is great and all but if there's going to be two Construct engines that use HTML5, with the newer version just being a big update a revamp of the same engine of the current then I don't personally see any point in making it Construct 3. I'd rather it be Construct 2 RXXX or at least Construct 2.5.
Especially if you're still going to continue developing builds for Construct 2.
I purchased Construct 2 less than a year ago and already it's going to be kind of (if not mostly) obsolete when Construct 3 comes out, which is turning out to be Construct 2+. It gives me the feel of Construct = iPhone (in the sense that there are newer versions made regularly with small differences), but I know that is not the case and not even close.
Basically, Construct 2 and 3 is going to be kind of like those smartphones that are totally the same, but have slightly different hardware specs, e.g. 4/8 cores and 8/16GB.
But that's just me and my delusional expectations. Take from it what you guys will, that's my two cents.
Before I first got C2, I imaged finding an event-based engine that was basically Construct 2 expect it used C# or C++.
Then I got C2 which is needy and wants browsers to run so we always have to worry about NWK, which other engines don't, so if someone stopped developing NWK we'd be stuck with old versions.
When I first got C2, I had child's delight and was developing my game really fast, then rage quit for 2-3 months due to a bug, then fixed it and rage quit for another month because of another bug which I now fixed and here I am now.
When we first get into game development we got "Omfg yuss!" and then get smacked in the face with reality.
Personally, CC's .exe >>>> C2's NWK in terms of performance, I played Minitroid which was made with CC.
I find it kind of bs that C3 is going to be C2 v2.0 instead of a real C3, since C2 was a major game changer (literally!) from CC, with a different programming language and entirely new and better UI. From C3 I'd expect it to do to C2 what C2 did to CC.
Currently we'd get C3 from Ashley while he also develops builds for C2, so development would slow on both.
Right now I feel like Scirra is pulling an Apple by making Construct 3/IphoneX+1 when it's really kind of an firmware update instead of a whole phone. Even though we know that Scirra is a lot better than Apple and doesn't do that.
But that's just me.