What next for Construct 2?

Technical improvement only really help the upstream developers which is a smaller group of people. Where as community features help the whole.

I'm pretty sure a lot of people find the event system daunting at first. By having a debugger, Scirra can make a short vid under the 'Events system' on the front page that shows the debugger go through the events one at a time, and this would be HUGE in helping people realize how easy it is to use it.

I voted for a debugger. Yes, if I only want to trace variables I use textBox or Chrome console, but the real benefit of using a debugger is to step through events one by one and see the state of the SOL and variables at a specific moment in time.

I really don't like the way search function works in C2. I want to see all the events, not filter them, instead I want my keyword highlighted.

Also a good option will be to highlight all the instances of the object or variable on which i clicked.

I had almost give up on C2 only 1 month after purchase for the lack of a debugger, but now I see that Scirra team is working real hard to satisfy most of us.

I actually do it using textbox, where is the difficult? And I think the most part of the users from this community never did more complex games than me, using simple textbox.

Please, don't throw so far the textbox if you're unable to extract the best of this feature.

Per happen, will be nice to have this feature alive someday, to help the newer users.

By the way is Modularity include passing a variable into a function like...

fucntion Awesome(A, B){

A + 10;

B *1000;

}

I would go with Modularity features.

The second would be debugger. I hate the fact I need to create many variables to find bugs.

> Also the debugger can be built using text box or something, if you can't built a debugger yourself than Construct 2 is to advance for you or you have a hard time figuring out problems even with a debugger. The debugger won't tell you logical errors or stuff that you cannot realize yourself. I'm not discouraging building a debugger, but I don't think it will help Construct2 that much.

>

Yes, for simple games, that will suffice.

Perhaps you should try making more complex games. Then you might see the need for an actual debugger.

Well, depends on how good the debugger is. If he was to built a really good debugger, than it would take a lot of time than that would also be equivalent to him building the multiplayer capabilities. Chances are the debugger won't be that advance in the beginning to help you a lot in debugging advance games. I think a simple debugger can be made fairly quickly , this is base on my opinion. But I won't dwell on this so much because I think modular seems to be winning the vote now.

Well, depends on how good the debugger is. If he was to built a really good debugger, than it would take a lot of time than that would also be equivalent to him building the multiplayer capabilities. Chances are the debugger won't be that advance in the beginning to help you a lot in debugging advance games. I think a simple debugger can be made fairly quickly , this is base on my opinion. But I won't dwell on this so much because I think modular seems to be winning the vote now.

Ashley described what he had in mind for the debugger in the first post in this thread. Please read that to understand what the debugger is intended to do.

Can we have a show of hands, for the "find references" voter? <img src="smileys/smiley36.gif" border="0" align="middle" />

I would like to see a better image editor. Or at least some sort of back button. I don't know how many times I have accidentally made a dot or line and I cant undo it.

You can undo in the image editor. Control+Z

Excal (at least for me) for some reason it only works when you're outside of the editor so it gets a little annoying ;)

You can undo with the image editor window open (multiple times) by pressing the back arrow, in the main editor...I only recently discovered that too!

pixel perfick I'm the guy who voted for the reference search

I've never used a development environment with a "debugger" before, but this sounds like the laziest approach possible to me...

If you structured your events correctly, without mixing stuff all over the place, you should have an idea of the things you have to change if a bug happens, and that's where a better control over references is very important, as you can concentrate on making changes related to specific points.

And that also works when your project has to evolve...

lemo Find references would be a great feature, and I'm hoping they will be added via the regular update process.

This is a light hearted vote and nothing is at stake here, but I don't see how using a debugger is lazy practice, it has many uses, fine tuning positions of objects, timing of sounds and events, to name a few.

Anything that makes the editor and ultimately any project made in construct 2 more robust has to be a good thing.

i second Kyatrics opinion: Modularity features!

it's better to have features which help us out today and are technically interesting today rather than having yet another feature that will (probably) work in a year or so.. if at all.

Part 1

I know that some Ideas that I've wrote down here can be in some way designed in event sheet or already have in some kind community plugin/behavior. But my intention its to facilitate some users transforming this ideas to Oficial Plugins/Behaviors instead of Community Plugins/Behaviors which in many cases its bad or hard to use.

Suggestions:

• Add Patrolling into Pathfinder Behavior - Via pre-made path, linear path,circle path and patrol in area walking randomly.

• Explosion with Angle? of Force - With the possibillity to set the force, direction cone angle and time of explosion radius expansion(fade-out explosion time).

• Add Avoid into the Pathfinder Behavior. With the possibility to set with Objects to Avoid(flee).

• Real FullScreen without black margins in .EXE mode independently of the monitor size.

• Easy Animation Movements like iTween of Unity3D -

  itween.pixelplacement.com/index.php[/li]

• Several Transition types between Layouts. (Fade-in,Fade-out and etc)

• Dynamic Shadows and Lightining.

• InGame Payment System Integration. (Google Wallet, PayPal,PagSeguro). Including some mobile payment systems would be Great.

• In-IDE/Editor download system to get functional Event Sheets, User-Made plugins/Behaviors.

• Community Sprites/Sounds/Tilesets/Backgrounds/CharSets and other stuff database system that integrated with In-IDE/Editor download system allows users to share and easy get stuff to apply on projects. (Nice for Dumb designers Like me <img src="smileys/smiley1.gif" border="0" align="middle" /> )(Possibly sell stuff to like ShutterStock)