C3 - I'm not getting it.

>

> >

> >

> > See you there bud. Bring your copy of Construct with you, we will all be fascinated. You could do a demo - wear one of those headset/mic thingies.

> >

>

> I'm totally serious, actually. Shoot me which talks you're going to via PM and we can talk the realities of game development face to face. My company is having us share passes, so I won't be there every day, but I'm sure we can make it work. I'm generally interested in the design track stuff since that's my day job, but whatever, the place isn't that big.

>

Well, look at you. A "serious" game designer, with all the bells and whistles, and using Construct - what are the chances? As much as I'd love to chat "shop" with a total stranger, 'face to face', from a forum, I will decline your offer.

And before you suggest it, you're right - I'm declining your invite because I've never worked at any major software company and have never written a line of code. You win my friend!

Frankly your snarky attitude and manner of speaking makes it obvious that you aren't really a professional, despite your mockery of people who consider themselves developers but don't share your opinions on tools. Real developers don't speak to one another the way you're speaking to all of us. We generally support and respect each other. We keep things civil even when we disagree. We don't mock people trying to get started in making games no matter what tools they choose. Making games is difficult enough without this kind of petty, childish sniping, and if you bring this kind of attitude to a job in this industry, you won't last long.

I don't use Construct in my day job - I use it for smaller side projects. But that doesn't make "worse" than what I do use on the job (which is Unreal Engine 4 - I've also used Unity and various proprietary engines in my career). Construct is simply a different tool for a different job. It's better suited to smaller, 2D games. "Smaller" doesn't preclude the possibility of a game being very fun or very successful. Construct is much easier to learn than Unreal or Unity, and certainly FAR easier than rolling your own solutions with code, from scratch. Construct is also a helluva lot of fun to use. A person can absolutely be a serious developer and use Construct. It has some technical and workflow issues (just like every engine I've ever used) but fewer than many of them. For example, Unreal crashes for me more often than Construct does. There are no silver bullets out there, "dev level" or otherwise.

So, if you're serious about being a "real dev" yourself, the first thing I'd suggest is to stop assuming you somehow know everything despite having never done any serious work in this field. Stop assuming people who disagree with you are fools. Stop wasting your time picking fights in forums. It might make you feel good to lash out and insult people, but you're not doing yourself any favors. Spend your time mastering a tool of your choosing - pick one and stick with it even when you encounter frustrating problems (which you will, usually in no time flat). Use it every single day anyway. Ask for feedback on your work and consider it carefully, and be respectful towards the people kind enough to give it to you even when you don't like what you're hearing. Read up on your craft (Gamasutra and the GDC vault are great resources). And don't give up. This stuff is difficult, and even with some of the great engines we now have access to, it takes a long, long time to get good at it or to finish anything worth finishing.

Good luck.

Frankly your snarky attitude and manner of speaking makes it obvious that you aren't really a professional,.......

So, if you're serious about being a "real dev" yourself, the first thing I'd suggest is to stop assuming you somehow know everything despite having never done any serious work in this field. Stop assuming people who disagree with you are fools. Stop wasting your time picking fights in forums. It might make you feel good to lash out and insult people, but you're not doing yourself any favors. Spend your time mastering a tool of your choosing - pick one and stick with it even when you encounter frustrating problems (which you will, usually in no time flat). Use it every single day anyway. Ask for feedback on your work and consider it carefully, and be respectful towards the people kind enough to give it to you even when you don't like what you're hearing. Read up on your craft (Gamasutra and the GDC vault are great resources). And don't give up. This stuff is difficult, and even with some of the great engines we now have access to, it takes a long, long time to get good at it or to finish anything worth finishing.

Good luck.

You seem like a young 'un. This is a tough industry son. I'd drop the Construct and focus on true code, and don't mention Construct during an interview process. Trust me on that one.

But thank you for your insight into my lack of experience. I had no idea how inexperienced I actually was.

>

>

> Frankly your snarky attitude and manner of speaking makes it obvious that you aren't really a professional,.......

>

> So, if you're serious about being a "real dev" yourself, the first thing I'd suggest is to stop assuming you somehow know everything despite having never done any serious work in this field. Stop assuming people who disagree with you are fools. Stop wasting your time picking fights in forums. It might make you feel good to lash out and insult people, but you're not doing yourself any favors. Spend your time mastering a tool of your choosing - pick one and stick with it even when you encounter frustrating problems (which you will, usually in no time flat). Use it every single day anyway. Ask for feedback on your work and consider it carefully, and be respectful towards the people kind enough to give it to you even when you don't like what you're hearing. Read up on your craft (Gamasutra and the GDC vault are great resources). And don't give up. This stuff is difficult, and even with some of the great engines we now have access to, it takes a long, long time to get good at it or to finish anything worth finishing.

>

> Good luck.

>

You seem like a young 'un. This is a tough industry son. I'd drop the Construct and focus on true code, and don't mention Construct during an interview process. Trust me on that one.

But thank you for your insight into my lack of experience. I had no idea how inexperienced I actually was.

Haha, young I am not, sadly. Not really. I wish that it were so. Not totally old yet either, though.

Anyway, I'm happy to talk over PM and we can have the battle of the resumes there. I'm not looking to trade insults. Now you have me genuinely curious as to your background. I just can't imagine any of the people I've worked with in games hopping onto a forum like this to berate beginners for their choice of tools.

As for mentioning Construct during interviews, what sorts of interviews do you mean? Programming? Design? As I said, I'm a designer, so I'm not greeted with any particular elitism with regards to which game engines I've used. Maybe programmers are more judgmental about such things, although I can't see why mentioning it would HURT, assuming you can otherwise show that you know what you're doing and would be a good fit for the team. Using Construct admittedly doesn't prepare one to be a programmer, although many of the basic concepts are similar.

For everyone else, if you're going to interview for a game design position, don't be afraid to mention things you've done using Construct. Things like that don't count against you - why should they, unless that's your only experience and the job requires engine-specific knowledge? In game design it's more about what did you actually MAKE, not necessarily the tools you used. When I've interviewed candidates, I'm always favorably impressed when they built games on their own initiative. We hired one kid based on his positive attitude and a simple game he'd built using an engine very similar to Construct. Another junior designer I know was hired partly because of his experience making maps for Left 4 Dead. Passion and determination counts for quite a bit.

Please ensure posts are polite and on topic or I will lock the thread.

Some posts are skirting 'being personal' and borderline abusive, which will not be tolerated.

Thanks

If you have no interest in monetization, and you just want to pay $99 PER YEAR to show Granny you're a 'dev' and made a game of Pong, knock yourself out.

lamar? Is that you??

mOOnpunk , Agree, lots of bugs.

"...and we'll get right to it! Meanwhile time on your license is running. 'ts all good!"

A minor hiccup in Admobs, but I've got it working flawlessly

Sounds good in comparison so C2's which doesn't work eh?

Android exporting is BRILLIANT in C3. Super quick and easy!

TBH this is really the only thing tempting me to "Upgrade" to C3

...snarky attitude and manner of speaking

Ugh. Reminds me of Tigsource Day 1. This is why I left that community. Might not be that many but the snarky ones are the most vocal.

lamar? Is that you?? <img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";)" title="Wink">

I doubt it's lamar since lamar himself was a grampa

Lamar's Youtube channel:

Seems like a nice person to be honest. Except for the part he went apeshit on here.

I have read many C2 docs over the years and they were in general at an amateur level. My suggestion is that if you are charging "big boy" per annum prices, that you hire a trained tech writer

I wrote the manual. I also wrote all of C2. Are you suggesting we get someone who didn't write the code, and doesn't know the inner workings, to write the manual instead? That hardly seems like a way to improve the quality of the manual.

Also if you want to build APKs, you can always sign up to PhoneGap Build - the paid plan is also a subscription, and costs more than Construct 3, which provides a full game development IDE and a build system, at a cheaper price.

Still, if you don't want to use Construct, you don't have to. If you think a different tool will better suit your needs you are welcome to go and use that instead.

Anyways this thread is already too close to a totally unnecessary flamewar, so closing.