Ashley's Recent Forum Activity

  • Well, my policy is "don't use sharp knives because they can hurt you, but if you really need one you can go and get one yourself". There are already lots of excellent JS libraries out there and I don't see why we should reinvent the wheel - you can just go and integrate one yourself, if you're aware of the possible shortcomings of the library for games.

    If your code really is that simple, it should be fine since it appears to avoid allocations. But then if that's all the code is, I'd just use x/y values myself to avoid dependency on a whole library.

    You can use the dependency field, but it can work better just pasting an entire JS library to the top of the runtime.js file. The Physics behavior has the whole Box2D library pasted in to the top.

  • Install Google Chrome, and visit the URL chrome://gpu. It should tell you how well the rendering is supported (e.g. hardware-accelerated WebGL, software-accelerated canvas, etc). It's the same engine as node-webkit so support should match what your game gets.

  • Try using the Rotate or Bullet behaviors for simple rotation and movement without having to create lots of animation frames.

  • Chromium already supports the gamepad API - it should work with XBox 360 controllers - but certain other kinds of controller need special support from Google, I think.

  • Yes, hopefully a future update will have better support for icons. The window size from project properties should already be used.

  • This is an interesting development! Hopefully it will result in more frequent updates to directCanvas. I'm not sure what the exact implications will be for C2 users, but I think that will gradually become clearer over the next week or two.

  • WAV is typically unsuitable for audio since it makes the filesize ridiculously huge. You could easily have a 5mb game with 100mb of audio if you used WAV, versus a 5mb game with 10mb of audio.

    The better solution is for WebOS to add support for OGG, which is a free, high-quality and open-source audio format.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • This is why you should always back up your projects before installing a beta!

  • Construct 2 has no built-in bandwidth limitations. It will use any available bandwidth on your server.

  • Updated OP to include .c2addon, new to r120+.

  • The SDK documentation won't let me post this article right now, so I'm posting it here. Will get Tom to fix the site shortly :) This covers how to make the new .c2addon files supported in r120+.

    -------------

    The .c2addon file format allows plugin, behavior and effect developers to easily package their addon in to a single file. Users can then drag and drop the file in to the Construct 2 window to install it.

    A .c2addon file is actually a zip file with a renamed extension. The zip file always contains *info.xml* in the root, and a subfolder called *files*. What goes in the *files* folder depends on whether you're publishing a plugin, behavior or effect.

    #info.xml#

    The info.xml file specifies metadata about your addon. It states whether the type is a plugin, behavior or effect, and has information like the name, version and author of the addon. It should be straightforward to fill out. Be sure to write documentation and add the link to the documentation to info.xml.

    #Plugin and behavior files#

    When distributing a plugin or behavior, the *files* subfolder needs to contain another subfolder. For example your folder structure in the zip would be:

    info.xml

    files\myplugin\common.js

    files\myplugin\edittime.js

    files\myplugin\PluginIcon.ico

    files\myplugin\runtime.js

    *myplugin* is the name of the plugin or behavior folder, as it should appear in the install directory. Construct 2 will simply copy and paste this entire folder, preserving the folder name.

    #Effect files#

    When distributing an effect, simply place the .fx file and .xml file for the effect in the *files* subfolder in the zip, for example:

    info.xml

    files\myeffect.fx

    files\myeffect.xml

    #Packaging#

    Add all the files to a zip (right-click and 'Send to compressed (zipped) folder' in Windows Explorer). Be sure not to accidentally create a root level subfolder in the zip which itself contains info.xml - that will be rejected by Construct 2. Once zipped, rename the file so the extension is .c2addon rather than .zip. Test it by dragging and dropping the file in to the Construct 2 window. If you can install after the prompt successfully, your file is ready to distribute.

  • Thanks, should be fixed in the next build.

Ashley's avatar

Ashley

Online Now
Early Adopter

Member since 21 May, 2007
Last online 27 Oct, 2026

Twitter
Ashley has 1,834,983 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x6
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs