There is tons of plugins seeming to be getting made. However there is no section for the development of them specifically nor is there a section for completed ones.

Could we get these forum sections made so it will be easier to find completed and plugins and plugins under development?

Looks good but there is a couple of issues I think "Exlorer" is typoed I believe, and for Construct I think you may have the Run All and Run layout reversed.

Also one thing I cannot seem to find is a very simple and useful tool I used in MMF2 Dev which was the Duplicate command on a sprite or object, I could tell it how many rows, spacing, and how many to put in what rows. I cannot seem to find a similar feature in Construct.

Array paste looks like it could or would be the feature, but I am unsure how to use it if it is. It confuses me badly.

> I disagree. There is no disadvantages of being able to export source code only advantages. I understand it may not be human readable, but even so saying the code as an export would not be useful or have any advantage is a bit extreme and over the top. Code at its very core is better then events, yes I understand events work really really REALLY well in construct, but if the program has a bug or they wish to expand on it with extreme custom code and actions that they could not do within the editor then it would be best to be able to see that code.

>

> I know it will never happen because of how advanced and great the event system is but saying exporting code would not have any advantage is not true in any part of the context. Not trying to call you on anything but facts are facts.

>

> I know the event system can do 99% of what anyone would possibly want with python possibly picking up the slack, but exporting code would be the ultimate in debugging and advanced mechanics.

>

So what are these advantages? From what I can gather from your post, you state code is better than events even when not human readable. Why is that? Isn't it better to write custom code in plugins which Construct already supports? I'm not saying events are always superior to code - they're not - but the options are put your code in a plugin, or ponder what to do with tens of thousands of lines of unreadable code. This isn't about code vs. events, it's about Construct generating tonnes of useless source vs. giving you the finished thing. That's not a feature, it's a waste of time to develop, from my point of view!

Don't think this is a personal attack or anything, it's just that this idea about Construct generating source code comes up from time to time. I can't really see any point to it at all, so I'm trying to establish what people think it will enable. Such as:

> he wants to create the source code itself ... so he can take it over to another program, like you would a jpeg or a text file.

>

Remember this is a big ball of mud code which doesn't make sense. What are you actually going to then do in another program with this unintuitive source code? I'm yet to hear any convincing real-world scenarios yet.

I never said unreadable code would be better, or even needed. I simply said the advantage is having access to that in case something comes up that cannot be fixed or added with events because of the scope needed, which in itself probably will not ever happen but the possibility is always there. I would never use it if it was added for several reasons I am just saying because it is unreadable and a mess does not make exporting source code as you put it "only disadvantages" as that is one single disadvantage among its so many, possibly useless uses. Those uses can still have advantages in extremely rare cases to some people. Not sure why but that cannot be dismissed.

> "export" the source code back out

>

What do you mean by importing source code to XNA then exporting it out again? That doesn't make any sense. Source code is source code.

As for exporting to source code, I really don't see the point. You would never be able to modify the source code to make changes. The insides of the event engine are very complex, and because there are no languages that support event style picking as language features, the generated sourcecode would not be human readable, it'd just be a massive mess, like a really complicated function copied and pasted a thousand times. And what kind of changes would you make? What would the advantages be? There are no advantages to exporting source code. Only disadvantages.

I disagree. There is no disadvantages of being able to export source code only advantages. I understand it may not be human readable, but even so saying the code as an export would not be useful or have any advantage is a bit extreme and over the top. Code at its very core is better then events, yes I understand events work really really REALLY well in construct, but if the program has a bug or they wish to expand on it with extreme custom code and actions that they could not do within the editor then it would be best to be able to see that code.

I know it will never happen because of how advanced and great the event system is but saying exporting code would not have any advantage is not true in any part of the context. Not trying to call you on anything but facts are facts.

I know the event system can do 99% of what anyone would possibly want with python possibly picking up the slack, but exporting code would be the ultimate in debugging and advanced mechanics.

What advantage does exporting source code rather than built EXEs have? What does that have to do with this thread?

Well it depends on what language the source exported in. If it went to a C or C++ or even C# it could be useful to build a base game using construct and the rest or expand on it in one of the languages mentioned.

Onto what that has to do with this thread? Nothing.

Construct is not fully translatable, so I would wait until better translation support is implemented.

While support may be limited, if the source is open why is it that translation is not fully possible?

Just started learning Construct, I know the power and advantage of having Python in Construct, I don't currently use it but if I need too in the future I would learn it and use it then. There was no option for that but I wanted to let it be known this is a great feature and should remain intact or improved upon, never removed. More power is always better!