How many of you guys HATE using C2?

Discussion and feedback on Construct 2

Post » Wed Dec 31, 2014 1:23 pm

Now, the tittle sounds bad, in reality, i LOVE contruct 2, so, what do i mean when i say that i hate using C2?

well, c2 is the greates software ever, this software gives me the opportunity of making a great game, but there is something that i cant get out of my head.
Have you guys who dont know how to program ever felt like noobs? i kinda know programing, but its on a very useless language, Visual Basic i was quite adept at it, and im starting to learn C++ right now, but for now im using C2, and everytime i come across a bug, problem, limitation, i feel like a noob, many times i say to myself something like this for example:

"-God, this sucks, i dont know how to make this sprite move like i want it to do, i bet that a real programmer would do this without a problem"

or

"-UUUGH! this bug is driving me nuts! i have tried everything i know and no one in the forums could help me, im going to have to remove this feature from my game, since its causing this bug, becuase i can't fix it, im forced to remove it, i know that a programmer would know how to make it perfect without problems for sure"

do you guys get what i feel? i feel noob and sometimes my self-confidence goes down, why im triying to compete in a professional field against professionals? even when my game looks great, still, what happens if a bug happens thats out of my hands? and im forced to tell my costumers:

"-Sorry! but i dont know how to fix the problem, i dont know how to program" :(

i feel sometimes, like a simple peasant compared to the gods that are the programmers, C2 has nothing to do with this, the engine it self its gold, but i cant help to feel this way, especially when i see people doing extremely complex math, who else gets this feeling too? please share :)

-Luna
B
23
S
6
G
3
Posts: 316
Reputation: 3,461

Post » Wed Dec 31, 2014 1:37 pm

Nobody really ever knows what they are doing, they just do their best to get along.
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,699

Post » Wed Dec 31, 2014 2:01 pm

Logic + Problem Solving + Trial & Error + Experience is all you need... the tool doesn't much matter.
B
21
S
5
Posts: 196
Reputation: 1,984

Post » Wed Dec 31, 2014 2:02 pm

that comes with experience, but some sort of rules can get you pretty much out of most troubles.

-When does the issue happen/under which circumstances? (can help identifying the event or behavior).
-what is the problem, and what is meant to happen normally? (very important, if you just don't know what you are doing and go sorta like "well, that feels kind of good, we will keep it", change how you work)
-what could cause the problem? (kind of hard to inspect, but rememeber that in case you cannot identify it, there is an entire community here that may be able to awnser your question, to be fair, if you present your issue in a way similar to a bug report (aka. simplified capx to show the issue, explaining what you want to have, with some screenshots to be precise), I do not see how anyone would have a hard time awnsering you.)
-clean is love, clean is life: do not get messy with your events, you have to be able to read everything you have done without too much trouble (for very complex or repetitive parts, isolations into functions can help).

I recommand having a really clear idea of what you want to achieve before implementing it, sometimes I have discussions that go like that:

"what is the problem?
My object does not shoot like it should.
how should it shoot?
Idk. how you would make it shoot?
That is not my game, I can make suggestions, but I cannot help you doing what you want if you do not know already"

mostly planning ahead, good use of the tools (which are described in the fabulous manual), organisation.

that was the part to help, now the real part.

It happens to me, and not to me, you have this "why it does not work, did I made something wrong??" feeling sometimes, when that happens and you cannot identify the problem, stop, take a breath, do soemthing else, come back, and analyse later, if you still cannot figure it, try to get some help, but I understand this frustration that can come from a lack of organisation or working too much. Find a good rythm, it might be better to work just 5 hours efficiently than forcing you to work 8 hours with the brain that goes on strike, sometimes even then that does not work, rethinking the design can be of help (not do something else completely, but do the thing you wanted without thinking the same way), those are frustrations that even a programmer can fell, because doing a game is an hard work => it is translating the concepts, ideas, mechanics, into a way the computer can understand, that part cannot be understated, and is coming with every tool out there.
Game design is all about decomposing the core of your game so it becomes simple instructions.
B
53
S
22
G
18
Posts: 2,122
Reputation: 17,123

Post » Wed Dec 31, 2014 2:16 pm

That's why instead of long events I break them in to smaller parts, put them in to separate event sheets and chain them with functions most of the time. Much easier to find an issue if there is one.

But what pisses me off about construct is that I just can not do certain things with events. Like the infamous solid behavior limitations.
Last edited by megatronx on Wed Dec 31, 2014 3:08 pm, edited 1 time in total.
My professional Royalty Free Music at Scirra Assets Store
--------------------------------
Specs: i5 2500, 16gb of ram, gtx 770, win 7, Focusrite Scarlett 8i6, Mackie mr8mk2, Alesis 320, browsing the net on chrome.
B
91
S
30
G
22
Posts: 1,985
Reputation: 20,149

Post » Wed Dec 31, 2014 2:43 pm

Far as I'm concerned, the behaviors and all the built in stuff are to blame. Most other engines have you make your own platform engines and such, as well as level editors, data tools, etc. With C2 you don't really learn much of anything...so if you start with C2 you'll likely always be a "noob". Not to say I don't appreciate behaviors and all, but ultimately we'd be better off with more features to make our own exactly how we want..
Image
B
243
S
30
G
13
Posts: 1,787
Reputation: 18,770

Post » Wed Dec 31, 2014 2:58 pm

Tokinsom wrote:Far as I'm concerned, the behaviors and all the built in stuff are to blame. Most other engines have you make your own platform engines and such, as well as level editors, data tools, etc. With C2 you don't really learn much of anything...so if you start with C2 you'll likely always be a "noob". Not to say I don't appreciate behaviors and all, but ultimately we'd be better off with more features to make our own exactly how we want..


well. one (more than one actually) can argue easily that when using C2, you do not really want to learn those aspects first anyway, and it does not prevent from understanding them or even recreate them (it is possible to do a game without using any behaviors nor system maths expressions, not worth the time however, but that is not the point), while most engines Forces you into doing this, while C2 actually makes you learn at your own pace while being organised, and more into a game designer way than a programmer way. Of course nothing will force people to learn, but my point: if someone wants to not stay a noob, he can do so, but if peopel do not want, well, there is no forcing them.
Game design is all about decomposing the core of your game so it becomes simple instructions.
B
53
S
22
G
18
Posts: 2,122
Reputation: 17,123

Post » Wed Dec 31, 2014 3:06 pm

Weird thread... in my experience Construct2 works perfectly and flawlessly. Try to avoid blaming the tool for your own shortcomings, instead learn how to use the tool properly. That's what I believe is the way to behave when you're in this business. Always be ready to learn and adapt.

If you feel you'd be doing better with actual programming, then go learn that, it will always be a great thing to learn a new tool. But I really don't think the tool even matter that much; Construct2, just like any other tool, allows you to do pretty much the same thing in the end (as long as it's 2D =P). And just like you would need to invest a great deal of time learning C++, Javascript, C#, or any language really, you could just the same learn how to use Construct2 =)

But bad news, if you think C2 is hard and unforgiving, I don't even want to imagine how you'll feel learning actual programming xP
B
43
S
12
G
6
Posts: 446
Reputation: 6,807

Post » Wed Dec 31, 2014 3:37 pm

Tokinsom wrote:Far as I'm concerned, the behaviors and all the built in stuff are to blame. Most other engines have you make your own platform engines and such, as well as level editors, data tools, etc. With C2 you don't really learn much of anything...so if you start with C2 you'll likely always be a "noob". Not to say I don't appreciate behaviors and all, but ultimately we'd be better off with more features to make our own exactly how we want..


Can't say I quite agree with you on this one. Overly relying on behaviors will indeed leave you in the dark on how certain things actually work. But the way the C2 event system works will teach you a lot about programming in general. Because it is just that: programming. Without having to care about syntax.

Regarding many things you can apply the same logic to jump into Javascript (for example)relatively quickly. And that will enable you to do your own plugins. Which then enables you to do even more things exactly how you want. :mrgreen:

So I do believe you can start out with C2 and it isn't a given that you'll always stay a "noob".

Anyway, from the OP I rather got the idea this was a casual thread about things that can be annoying in development and hard to figure out, especially if you're not a rather math savvy coder type. Which would be a far greater issue if it wasn't for C2 of course. Many if not the majority of users wouldn't be developing games if it wasn't for Construct.

That being said, I also do know the feeling very well not being able to figure something out that seemed trivial when you were planning it in your head. It's easy to feel stupid and overthink stuff in an endeavor as complex as game development. And I do bet it also happens to people with a real coding background from time to time. ;)
B
23
S
6
G
11
Posts: 1,045
Reputation: 8,061

Post » Wed Dec 31, 2014 4:07 pm

Sure C2 can teach some very high level programming concepts. I meant you don't learn how to do a lot of things yourself which in turn make you a better programmer and more confident in your abilities. Like...probably half of the feature requests I see are for things you can already do with events, but people don't even realize it because they rely so heavily on behaviors and never learned the code. The solid exception feature megatronx just brought up is a great example. People using other engines have already made that feature themselves decades ago with no trouble whatsoever...meanwhile we've been begging for Ashley to add it to the behaviors for 2 years now.

And sure you can still make your own behaviors with events but I bet you half this community doesn't know how because no one posts that sort of thing...they too just use the behaviors. Thus they are forever stuck in that "noob" phase and limited to the behaviors feature sets.
Image
B
243
S
30
G
13
Posts: 1,787
Reputation: 18,770

Next

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 12 guests