he most crucial part of my game in mind is the cut scenes.

Somehow, I think that a great game needs a great mechanics + nice some nice audio/visuals can help (But, as "Thomas was alone" (non-C2 game) shows, you can make an incredible game with just grayscale boxes ;-) )

I'm not sure if great cutscenes alone can make a great game, but I wish you success, and I hope to see one :-)

Anyway, have a look at "Arcade" - there are quite a number of games with downloadable source.

You can also take a look e.g. at gamedevelopment.tutsplus.com for more C2 tutorials.

Merry Christmas!

G.

Hi zipman,

You need to detect when is the time to go to the next level - you can do it e.g. picking all instances of bricks, and checking if count of picked objects equals zero.

(But you might have already resolved this, so onto your main question).

Once you want to go to another layout, in the event sheet add an action system-> goto layout , or (which I would choose) system -> goto layout (by name) - as you can simply name your levels/layouts "L1", "L2" etc, and then just jump from one to another, by using a global variable that keeps track of which level you are currently on.

Hope it helps,

G.

Hi majikk

Having a 50MB project might cause issues while downloading your game - users might have to wait quite a bit of time, before they can play.

Several workarounds here:

1) If you are creating a multimedia-heavy game, consider releasing it as an executable with NodeWebkit/Cocoon etc.

2) Create a smart loader with a mini-game, that will keep the player busy until the main part downloads

3) For audio, use lower bitrates to keep file sizes smaller.

Your node-webkit solution will be *smaller* than the web-export, if you use a lot of sounds - as Node-Webkit only needs an OGG format, while regular web-export will have to keep wider compatibility and use multiple sound formats.

Cheers,

G.

—

True :-)

So, thinking about how I'd approach the "enemy drops an item" problem, I would try to:

1) Create an "Item" sprite, with separate animations for each item type (e.g. coin, dagger, bomb), and naming the animations appropriately

2) put the item type as an instance variable in an enemy

3) upon killing the enemy, spawn "Item" object, then set the animation to whatever I need - e.g. "coin".

Then, if your "Item"s have different functionalities, you can easily code these by checking what animation your "Item" is playing.

This allows easy adding new item types, just by adding new animations.

Cheers,

G.

Another solution, from the manual:

====

Create object

Create a new instance of an object type on a layer at a given position. If a Family is chosen, a random object type from the family is picked, and an instance created for that.

====

So, add all your enemies to a family, and then spawn a new family member ;-)

G.

Hi majikk

From your description I suspect that you are asking the projectile to respawn itself ;-) - and so it can only work if the projectile exists somewhere in the current scene.

You can get any other object to spawn the projectile for you - e.g. catapult -> Spawn another object, or use sytem->create object as suggested above.

Cheers,

Greg

Thanks so much, Ashley !

I have a crazy time this week, so I'll probably do it during the weekend.

All the best,

Greg

Hello,

I came up with an issue about paths in NodeWebkit infterface, but I'm not sure if this can be considered a bug, or maybe I'm just doing something wrong?

When you query NodeWebkit plugin about the User Folder / Home Directory path, on Windows, your'e getting something like:

(Win8 output)

\Users\UserName

The problem is, it does not contain drive name! So, when I run the application *with unpacked resources* (= with package.nw unpacked and deleted), this is the only case when the app actually runs from within the folder where I call it from. Now, when I call it fro D drive (or any non-sytem drive), any calls to user folder end up referencing the local drive!

This effect is invisible in preview, it is invisible when running the app right after export, but it persists if you use unpacked resources (as I do, having 300Mb+ of audio/graphics). In a "typical" case the NodeWebkit will first unpack package.nw to a temp directory on a system drive, so the problem will not be visible either.

Any suggestions on how to deal with it? The only idea I came up with is checking if 2nd character in path is ":", and if not, add "C:", but that would be hard coding, which is a bad idea anyway :-(

Thanks for all suggestions,

Greg

Hi,

I think you might want to use some shuffling or helper storage, to avoid getting into the same room twice. Two ways (there are certainly more):

1) create array of size 250

2) fill it with consecutive integers

3) shuffle random pairs of a hundred or more times

4) make the player go from room to room, according to the (shuffled) order of elements in your array.

Way #2:

1- draw random integer as in examples you've seen above

2- if integer is already in the helper container (#3 below), repeat drawing

3- store the number in a helper array/string etc

4- proceed to the selected layout

Hope it helps,

Greg

ays I need to buy a license. I am guessing there is no way around that?

Node Webkit is free to use, independent of C2 - you can grab it and manually package any HTML5 app into a NW package - Construct2 simply does automatically for you all the tedious setup work ;-)

Considering the ratio of incredibely useful features to a very reasonable price, I'd say it's better to buy a license for C2 than to waste time with manual export to NW ;-)

Cheers,

Greg

Hi,

One difference might be that the preview does not use compressed data.

Have you tried checking the speed with uncompressed data in the exported package? Just unzip your .nw file (and delete the .nw), and see if it makes any change.

Greg

Hi randy70,

For me, rexrainbow's CSV plugin works *like a charm* - I've been using it for over a year to load the kind of data you've mentioned, and I'm not gonna look anywhere else ;-). [Thank you, @rexrainbow !]

This + ajax gives me a huge flexibility - all configuration in external data files, whether over the web or in nodewebkit.

Take a look at the examples that you can find on rexrainbow's pages - this should give you a headstart.

Good luck,

Greg