Labels

• already exists

  Feature requests that are already possible using existing features
• construct game services

  Feature requests relating to the Construct Game Services
• declined

  Feature requests that will not be acted upon
• documentation

  Feature requests relating to documentation
• duplicate

  Same feature request as an existing submission
• expired

  Feature requests automatically closed after 1 year (see the feature request guidelines).
• in development

  A feature request that is actively under development
• infeasible

  Feature requests that are judged to be impossible due to technical or workload limits
• major project

  Feature requests that are deemed to likely require significant time investment/high complexity.
• missing required information

  Feature requests which cannot be adequately reviewed or implemented due to missing key information
• need info

  Pending a response from the author
• pending release

  Feature requests that have been implemented and are awaiting shipping
• planned

  The team intends to implement this feature request (but please note this is not a guarantee)
• scripting

  Feature requests relating to JavaScript or TypeScript coding.
• sdk

  Feature requests relating to the addon SDK.
• sdk-v2-porting

  Feature requests relating to porting SDK v1 addons to SDK v2.
• shipped

  Feature requests that have been successfully implemented and shipped in a public Construct release
• usability

  Feature requests relating to improving the user interface usability.
• website

  Feature requests relating to the general website