I just tested Local Storage on iOS 10.2.1 and it worked fine.
Are you sure it isn't just a mistake in your events? This is why in bug reports we ask for a minimal .capx demonstrating the issue.
Construct 2 already has a savegame system, which uses browser storage. If you want your savegames to be synced to other devices, it doesn't seem like a good idea to pick platform-restricted services - presumably you'd want to cover all platforms. The API in the original post looks limited to Android only.
At least at first, there won't be. There are lots of non-obvious problems, such as you can't currently pass Z positions to the renderer, because there's no need for them - everything is 2D right now.
Having it in Construct 3 other than a plugin made by some hobbyist (and by NO means do I intend any disrespect to the developer of the Greenworks plugin...he is a lifesaver where Construct 2 could not do this)
If you mean the Construct 2 plugin, we do develop that officially ourselves already.
Both Construct 2 and Construct 3 already use 3D contexts and just render 2D content in to them. There is far more technical work to do to enable 3D rendering though, and right now that's not a goal of the product.
Develop games in your browser. Powerful, performant & highly capable.
Nintendo won't tell us anything, not even if it will be possible for us to support or not. So... if Nintendo tell us anything, we'll pass it along.
Yes, we will be working on an Xbox Live plugin shortly, and this will make it possible to publish to Xbox One.
There seems to have been some conflicting information in the past, but this is definitely happening.
Yes, we'll have an Xbox Live plugin out soon.
It's hard to know what to do about it without any specific suggestions. Could you show some mock-ups to demonstrate what you think a better alternative would be?
We've had other people comment that they like the simplicity of the interface, BTW.
It's linked to in layout properties so you can generally easily access it from a layout view. However we could always try to make it more visible. Where else do you think it could be exposed?
BTW this is a good example of something that a CSS theme cannot change - it needs logic added to the application itself.
Also remember Facebook is just one avenue, and subject to what Facebook's algorithms think is interesting - we have Twitter, thousands of people on mailing lists we're keeping up to date, etc.
BTW, I don't see Scirra in that list of possibly affected domains.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.