Ashley's Recent Forum Activity

  • When an update comes out, just tell your team to all update.

  • The solution is for everyone on your team to update at the same time. That's all you need to do.

  • What you're describing is essentially the same as saving a project in r225, and then opening it in r218. That's never been supported. Of course you can't use mesh distortion in r218 - the feature does not exist in that release.

  • Updating Construct does not affect the use of GitHub or any other source control tools. I need to understand exactly what has happened to be able to comment further or provide any help.

    For example, if you're seeing conflicts on source control, updating Construct does not cause that. Those are actually caused by submitting contradictory changes. That's a different type of problem. Even if Construct completely changed the project file format, that in itself does not cause a conflict on source control. You just need to submit an update which makes the necessary changes, and make sure it doesn't conflict with anyone else's changes. But in this case, Construct has not changed the project file format at all. So even that is not a problem here.

  • Correct, there is an issue for those that are using C3 Desktop. And it's a big one.

    And what is the problem exactly? I still don't know what the specific problem is that you're talking about.

    FYI there were also stable releases in late April, June, August, September, and now November.

  • We work hard to ensure a very high degree of backwards compatibility. Updates should never break projects. In fact you can open up projects made years ago, even with Construct 2 in 2012, and open them fine in Construct 3. If anything breaks, please file an issue following all the guidelines. As far as I'm aware, such breakages are very rare, and are usually corrected quickly.

  • In your original post you stated there was "a huge issue" in "c3 Desktop", and asked that "that this will be eventually looked into". It sounded like you were saying there was a big problem in C3 and asking for help, so I tried to find out more.

    As far as I can tell, all that's happened has been a routine stable release exactly as we've been doing for years and years. I don't think there's anything more I can add.

  • It sounds to me like this isn't actually anything to do with Construct. Of course software updates happen all the time no matter what software you're using. When using source control, it's up to you to manage updates with your team so you stay in sync - that's not specific to Construct. Also, I'm not aware of any problematic changes we made to the file format, it should be virtually the same and not cause any unnecessary conflicts on source control. Also there were no breaking changes I'm aware of so I don't know why your custom plugins would have broken, but it's up to you to maintain those anyway. I don't think it's fair to come here and tell us we shouldn't be making routine improvements to Construct, as we've been doing for about 10 years now without these types of problems seeming to happen to anyone else.

  • Construct doesn't have a plugin named "Text box" - there's the "Text input" form control, which doesn't support BBcode, and the "Text" object, which does (and I presume you mean that).

    As ever it's all documented in the manual page for the Text object.

  • Thanks for the feedback! We've worked hard to make C3 even better, as well as maintaining a high degree of backwards compatibility.

  • gustavoChico - I'm afraid I'm still mystified as to what the actual problem in r225 is that you're talking about. It still supports everything you've mentioned, including folder-based projects for use with source control like GitHub.

    That feature is still there, and so you can update to r225 just fine.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Construct picks an arbitrary existing instance to copy the properties from.

    If you have two instances with different properties, and create a new instance at runtime, which should it pick to copy properties from? There's currently no way to tell Construct which one to use as a reference, so it guesses one. It could use either.

    The main idea behind this is that if all your instances use the same properties, new instances get the same properties like you'd expect. If your instances use different properties, you can use actions after creating the instance to set the properties that matter.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,768,542 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
  • x5
    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
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs