Sounds like fun, but with 2 kids and job hunting I don't really have the time :( Plus my strength is programming. Since that's covered well enough my extra help won't be as much. Maybe another time when I have more available time.

Though it does sound like a lot of fun :)

Also to websockets you can check out

github.com/rexrainbow/C2_plugins/tree/master/plugins

RexRainbow provided a server techonology and plugin.

Here are my last comments on multiplayer.

1. The MP needs to server is LIE.

Servers offer community based features and opportunity for server side cheat checks. However Scirra is going to use P2P, Google Play is P2P. it's not uncommon and still used regularly. Get over it.

2. REXRAIBOW ALREADY CREATED A SERVER AND PLUGIN github.com/rexrainbow/C2_plugins/tree/master/plugins

But it's NOT used because of a lack convient access. Stop the that. Drop it. MP doesn't need to be bumped in priority :D

Ashley right on the effort part. modularity would be architecture changes. This is pretty heafty and can end up causing some serious changes. Even so. I suspect it's the big one that needs to be tackled.

I suspect the reason why Modularity was voted lower was for this reason. People's behaviour are based on our subject views desires. Tilemaps and multiplayer are voted higher due to the fact of immidiate rewards. Modules offer the greater long term reward, but not in regards to an immidiate fix.

As a simple example of the difference

1. Multiplayer P2P comes out.

2. everyone fragmented works on MP stuff on there own.

3. people offer suggestions and help

4. go to 2

Where as in modularity is first(with asset store)

1. Modularity comes out

2. people share

3. modules improve

4. people make games from modules

5. release new feature(MP)

6. go to 2

this results that the cycle means a consistent improvement overall and modules that make everyones lives easier :)

anyways at this point I've expressed my view point from different factets. At this point I don't think I can share anymore :)

But it's been a great thread :) you all have been very insightful :)

That's mostly the point of the CAPX section. It's for people to reverse engineer or to use to build up from. It's not meant to be a robust learning tutorial.

This is a good idea to get all those "tutorials" where they are not tutorials at all. Also it let's people just find CAPX when wanted. However after looking. I think this should be it's own section rather than under the Tutorials.

Instead should be CAPX repository. That way this can sorted into there own groups like tutorials are.

Hey thanks. I think this is a great start of a repository :) I don't feel it's a 100% finish goal. But it's a great server side start :). It's a good idea as personally tutorials should be a learning environment where as CAPX repo's only need a description :)

kudo's on the step :)

edit:

as a suggestion. Only CAPX that are targeted at stable releases should be allowed. As the Manuals only update the new features on stable release. The capx should target the stable releases.

Modulairty before Mulitplayer. Even once MP comes out it's going to be simple P2P. Much of the advanced stuff is still going to be on the developer heads. Think of the Web Audio Api that C2 uses.

Modulairty will allow better community shared developement where as of this moment now. It's going to be the same problems. Everyone needs to start from near ground zero and build up on there own. And when some one does share it's going to be forgotten or lost.

Asset store + Modularity is the key for growth.

Also on a note. There is no reason that MP can't be done now. As the prior poster noted he is doing so NOW. I wrote a Photon Plugin in one day and ran a very servicible top down shooter. I can run my server now and we can play NOW. there is no need to wait for later when the tools are around NOW. It's just no one will use them for various reasons.

Don't get me wrong. i will see peoples capx and help them out and they will be filled with plugins. But then I have to have spend the time installing these plugins manually :( or the helpee needs to remove them :(.. where as an integrated module asset store could allow a download of such plugins(if allowed) and this becomes less inconvient.

Modulairty should have highest priority.

edit:

I agree with Datawolfpad. Websockets are fine for real time games. That lie needs to end. TCP isn't good for real-time competative shooters and Stree Fighter like games. Everything else can get away with it. Heck most RTS online games still run TCP.

edit again:

Here is the thread I started last month for the call

scirra.com/forum/suggestion-a-call-for-modularity_topic79249.html

I still stand by this :D

Arima

As for collision. C2 just needs to use a Quadtree system like

mikechambers.com/blog/2011/03/21/javascript-quadtree-implementation

C2 uses a brute force. so when a check type is used C2 checks ALL of them. Where as a good quadtree is more effecient :) but i'm sure some day :)

mepis

I disagree with the target level and the price. I think it's a great target and price. I think though the potential is not leveraged enough. An asset store for free and cost items would do wonders for Scirra team.

Also some one tried to make a repository before. But unfortuantly it's not adopted enough. Mainly due to Excal's point. Dev/users just don't use much outside of the IDE. The access isn't convient enough or there is a mental block to using them. the asset store needs to be integrated to the IDE. but it's awefully nice of you to consider.

Maybe offer a code build that can be integrated into C2.

to set multiple return values

Function.setReturnValue( value & "," &value2 )

to get return value

var = tokenate(Function.returnValue, index, ",")

C2 doesn't support multiple natural return values. I know some lanuages do. it's a nice feature. But C2 isn't one of them much like C/Java....

Excal

I was saying the same thing. Then lost my post with an access denied :|

Anyways. Good luck with Unity :) it's a nice tool kit :) I've been thinking of moving to GMS until Modularity and Mobile has been resolved. but probably won't :D

Tobye

I've used SVN, Github, Putty to a linux and a few others over the years. For me it's not he trouble. It's the situation that the hurdle exists that holds back. Though I thought the tutorial would be pretty good.

The easiest way for this hurdle to be handled; is for C2 to have a Group Project IP/address. Where then only the IP needs to be put in with the information of the project name and such.

It all comes down to the one rule "Convenience is King" and using an external program, planning and diligent practice is not convenient. this will result in a reduced use.

Excal

I fall into your categories :\ I'm very guilty. I totally agree. The lack of an integrated system and modularity is hurting C2's growth.

However The tutorial sections are fantastic. There are a lot of excellent tutorials. Some people are happy with detailed docs. I've seen others who couldn't care and only want the capx file. And finally there are people who NEVER look at the tutorials and even know they exist :(.

CAPX are the best way to share. It's not drop in and some times it's a pain to import a CAPX feature. But it's possible. It is however inconvient. Also lack of a good integrated repository hold other methods back. Rex holds a repo, which get's some use. But I bet if there was an integrated way to access Rex repo the use of Rex plugins would likely sky rocket.

I understand Ashley's situation. As I understand he is the sole C2 programmer with Tom on the web/server side stuff. So He has to weigh in what features need to be added.

maybe what Ashley should offer next prior to modularity is a true C2 Plugin system. Not by way of plugins for created games. But instead Plugins that assist in making games by the way of new interface options? new gui boxes? This could allow Lucid to work on a Spriter importer directly or some one else could have created a TileMap system already.

Unity seems to allow developer enhancements to Unity. I think this could let other people develope areas that C2 is missing. Some could develop a modularity system.

overall I agree. Modularity and Community based easy access features are missing for such a fantastic tool. There seems to be a lot of old C++ design paradigm for IDE use and sharing. In a time where integrated social features are the norm. C2 is running behind :(

Excal

I was expecting the same old. eh it ****** But nope. You have a lot of valid points. I have made comments that C2 needs the modularity for growth, that the modules should be on an Asset store that is integrated into C2 IDE.

And while the plugins is a great system. It's a hurdle for most developers. Where as Unity modules are still in C#/JS. That language is the primary programming language. Here the primary language is C2 Event Language. Which does very well dropping the barriers to allow non traditional coder writers to program easily. but the SDK level is and will often be for most be out of reach.

I totally feel where you coming from. Growth of the community developement can't go farther. it's just not the nature of such a low barrier and no integrated support. c2Addon was a good start. But it's not enough.

However a few points I want to make out.

Unity sat in the same boat as C2. No one took the toolset seriously until a handful of top design games came out. However this happened well after the asset/modularity system was in place.

Game Maker Studio is indeed making the transition from "toy" to serious game kit. Miami Hotline, Risk of Rain and Another Perspective are becoming more noticed and helping GMS.

So I agree. While C2 did a great job of lowering the barrier the execution still needs work. I feel the are three key factors for C2 to hit main stream.

1. C2 Event Language modularity

already covered

2. More Open Asset store integrated into the IDE

Asking developers to do stuff in the the files/folders is a barrier. This is to remove that barrier. Personally for me it's not hard. But this is still an inconvenience.

3. IDE team work synchronization.

SVN is ok, but this still requires active diligence on the part of the developers. However with a lower barrier entry that entire idea requires more support in the tool. This really can't be expected that the entry users will quickly scale up to elite programmers.

Don't get me wrong. I'm looking forward to the Multiplayer features. But these are the key elements needed to shift everything to mainstream.

Anyways have fun with Unity :)