Hi fellow constructors,

Just a question regarding the Windows8 object:

according to the manual: On successful purchase - fires after a successful purchase of the App or a Product (in-app purchase) On failed purchase - fires after cancelling a purchase (or failed attempt) of the App or a Product

Question - Do these triggers work only when the app is actually published to the Windows Store or should they also work in test mode?

Thanks in advance...

Unfortunately the true answer is Scirra developed export options (I know this has been discussed in other topics)

It is bad enough having to rely on browsers, with their never ending inconsistencies and app breaking bugs, which is of course something we can't avoid in a product that is well HTML 5, and therefore browser reliant. But exporting to anything that is not going to run in a browser should be just as reliable as the product that we use to make the app in the first place.

Construct2 is a very, very cool product - hands down!

But all the export options are prone to bugs and\or never-fixed nuances - and this has the often reported problem of breaking C2 apps. In this post the problem is NW. In another post (sticky) the problem is chrome - resulting in a need to re-publish older games. Well I might be alone here but if a game runs fine at the time of release, you should only have to re-publish it to remove bugs in the game itself or because you added new features - not because a third party dependency breaks it!

Time for Scirra to write their own export wrappers, be it for desktop or mobile devices.

Yes it means inventing the wheel again to some degree. Yes it means taking time from adding more features to C2. Yes it won't be a small task. BUT it will definitely mean well written and robust export options that work best for Construct2. That is the confidence I believe we all have in Scirra.

Whenever you are in a chain, you're only as good as the weakest link.

C2's weakest link has always been and still is the export options. Relying on third party developers to deliver the most important part of your game-development cycle. Lets face it Construct2 is a fantastic tool to use for development. Well that is great for the developer, but if you want all that development to be enjoyed by others - then they have to be able to play it. Now if those third parties are breaking your very cool product - then surely it is better not to have to rely on them at all.

At the moment history could well be written something like:

Construct2 was a brilliant product that became nothing more than a prototype tool for developers, due to its reliance on third party tools that never produced reliable export options. After many years of waiting/hoping for real solutions, even C2's most dedicated adherents finally had to jump ship. Que sera sera....

We would like history to be written something like this:

After many years of dissapointing results due to reliance on third party tools, Scirra decided that the answer was in-house. Developing their own export options has resulted in their flagship product - Construct2 - being one of the most robust HTML 5 game development tools around today.

Personally, I'd love to see global variables get their own window, outside of the event sheets entirely, with additional support for sorting them into trees and branches. I usually end up putting all my global variables into a separate event sheet anyway, so they're out of the way (since they can't be put into groups), but then having to switch back and forth between that sheet becomes a bit of a chore. If we could have a window that can always be open, and easily arranged, that would save a whole lot of time.

Yeah, I do the same thing. This is definately a great suggestion. +100

Hi, Kiozuky Naji,

here's an example capx, very basic but gives you something to go on...

[attachment=0:2bfrl0kf][/attachment:2bfrl0kf]

Happy constructing.....

Hi,

you need to add the WebStorage object to your project, e.g. the same way that you add a sprite....

Yeah, difficult one I think.

I for one hate adds in any form on any media - with a passion.

To me, a fairly good game free of adds, is way more professional than an excellent game with adds.

Actually I refuse to put adds in my games - and it would be a fantastic thing if every dev - large or small, pro or indie - would do the same thing.

But to the concluding question of your post:

Paid up front:

Likely lead to less downloads. (It seams these days people don't even want to spend .99!) At least until you get a name for good products.

Implement Adds:

Most annoying thing on the planet. Only do it if the paid version removes the wretched things completely. (hmm nah, what am I saying, dont' do it at all..!!!)

Other options:

First level free:

Up grade to unlock all levels.

Completely free:

In-app purchases for more powers, weapons, vehicles etc. But be careful, don't make it seem like a money pit, and make the purchase really special.

Just my 2 cents worth, I am sure others will see things differently....

katzin, hi...

If the global variable (GV) is resetting to the default value between layouts, then you must be telling it to do so somewhere in your code.

GV's are accessible at any time from any layout. So if GV is set to 1 in layout1, it will still be 1 when you go to layout2. Make sure you are not resetting it when the layout starts.

Can you provide simple capx...

—, great review from indiegamemag!!

Reinstalled, but still same result: the never ending luidi splash, and the the app crashes.

I find android to be pretty pathetic at times, when I get time I will give the pc version a spin....

— Awesome, will check it out after work.

Haha, codah replied while I was replying...

Hi,

name your layouts, for example: level0 level1, level2 etc.

Create a random number when wanting to go to your random layout, Then use:

System: gotolayout(byname) > 'level' & randomnumber.

happy constructing.

Maybe something like:

Touch is touching sprite>set sprite.x to touch.x.

happy constructing.