dop2000's Forum Posts

  • Use a sprite or TiledBackground object instead of the progress bar. It's very easy - set origin point on the left and update its width, for example:

    Bar Set width to 300*(Player.health/100)

    where 300 is the maximum width, and 100 is the maximum health.

    Here is a demo:

    howtoconstructdemos.com/simple-healthbar

  • You mention the package.json, you can simply edit this in the official launcher to pop the /r218 link directly in?

    Yep. However, I had to use an older version of this file. I guess that launcher does something similar, but the process is automated.

  • I don't know, I'm with Ashley on this one.. I cannot imagine what an enormous task it must be supporting Construct, so forcing people to use the most stable version seems like a solid idea.

    I believe most C3 users are happy with auto-updates. Moreover, many people update to the latest beta the moment it's released.

    OP's problem seems more like a workflow issue, this situation is not common. And there are already a few solutions available - use a launcher, or edit package.json. I tested the second one and it works fine for me, folder saving and everything.

  • I'm not sure I understand the problem, but I still have a few ideas :)

    Before saving, you can generate a new seed string. When loading, set seed to that saved string.

    Or you can probably generate and apply a new seed on every step. So when a game is loaded at step 155, for example, you can tell Advanced Random to use seed "seed_step_155".

    Or maybe you don't need random to be seeded after loading the saved game? In this case, simply disable it.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You can parse CSV with events, or you can use ported CSV addons for C3:

    github.com/erenertugrul/construct-plugins/tree/master/ported_plugins/plugins

  • If you don't need the physics to be very accurate, you can do this: 

    B on collision with A:
 A Apply Impulse 100 at angle angle(B.x, B.y, A.x, A.y)

    Use image point 0 or -1

    To apply rotation, you can get the difference between angle(B.x, B.y, A.x, A.y) and B.angle (or angle of motion). Let's say this difference is 20 degrees, so you apply an angular velocity in the opposite direction, -40 for example.

    Again, this will not be very accurate, but should probably look ok for most collisions.

  • Jim Smith This is correct. All iterations in the loop are executed immediately in one tick. However, actions after "Wait" are scheduled to run later. So if you put "Wait 1 second", all 20 iterations will run after 1 second, but if you put "Wait 0.5*loopindex", they will run with 0.5s intervals.

  • gustavoChico

    I'm not a fan of third party stuff, and I think this is a legitimate issue.

    You can edit the package.json file manually, put "https://editor.construct.net/r218/" there. I don't know if it will still prompt you to update, but it should run r218.

    I don't like auto-updating software either, but I believe in case of C3 it's justified. There are lots of bug fixes in every release, without the auto-update people will continue using old versions and endlessly complain about things that have been fixed a long time ago.

  • This is not possible.

    You can save the updated data to Local Storage. So on start of the game you should check if Local Storage has saved data. If yes - load it from Local Storage, if not - load if from the file with AJAX.

  • In this case you need to put the string in quotes, but they are not part of the string, so you don't need to replace them with RegexReplace. 

    Set clue_url to "https://www.example.com/site#1"
Set clue_url to replace(clue_ulr, "site#1", "somethingelse")

  • Ok, I see the problem. Do this:

  • You can't change opacity for Form Control objects, and they will always be above all other layers.

    Use a sprite or TiledBackground object instead of the progress bar. It's very easy - set origin point on the left and update its width, for example:

    Bar Set width to 300*(Player.health/100)

    where 300 is the maximum width, and 100 is the maximum health.

  • If you need it to repeat only once, use "On touched" event (not "Is touching").