brushfe's Forum Posts

  • I think that's your answer then! It doesn't look like the "On created" trigger occurs with objects already placed in the layout.

    If you already have the Obj_Object on the layout, you could change your "On Obj_Object created" trigger to "Trigger Once while True". This should fire the spawn of Obj_ObjectAbove.

  • I've tried out the first "Doesn't Work" code in your screenshot, and it seems to work fine. There might be another part of your code interfering.

    Here's the C3P

    drive.google.com/file/d/1mjCUbwdunQRdHaSdxoz7dWnTdfhJIANg/view

  • Almost. The condition is a string and it's an OR.

    Global string = Text

    YourVariable = "Five"

    OR YourVariable = "Eight"

    That said, if I drop the OR block and only compare for the "Five", it still doesn't work.

    If I change the YourVariable from a string to a number and check if it equals 5, it does work. But I need to check a string, and I don't understand why checking for a string would break it if checking for a number works fine.

    I see — I don't think you can put OR blocks and Triggers in the same block, but I might be wrong.

    I've always separated them like this. This approach also stops the code from checking "YourVariable" every loop, which can slow things down, and just check whenever a Sprite object is created.

    But ROJOHound is right, it'd easier to see what your code looks like.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Is this what you're trying to do? Both of these work for me:

  • It's a good point; I really love the new style, but it certainly feels built more for new users, or maybe no users and just an "overview of Construct".

    I think the page functionality could certainly be brought more toward the advanced users (e.g. Adobe CC went through the same journey). The fact that it takes two clicks to open a file is a good example of that. Your suggestion about having more Recent File slots as well. Giving more real estate to advanced user flows, rather than things like social media, the more balanced it'll be.

    Just for fun - a starter thought on how it could go:

  • It won't be possible to help you by looking at a screenshot - the problem is in your code, not your layout.

    You should consider posting your project or a screenshot of your code instead, and explaining the problem in more detail.

  • Even with a short tab name like "Layout 1", there is a much bigger area to click on the tab to select it than to close it. The X is pretty small and so should actually be difficult to click - like the famously tiny small X button on ads that people complain about being hard to close. How is it possible to repeatedly accidentally click a small button? I don't understand this at all, can someone explain?

    I'd absolutely vote for an option to remove the X and using right-click menu instead. In my view, there's a few additional things to consider:

    • In larger projects, with multiple sheets open and organized, the downsides to accidentally clicking the X are way higher than the upside of having it there.
    • As in any customer experience, the more often a pain point like this occurs, the stronger the negative response to it becomes. At this point, after making this small mistake over a hundred times, it's grown into a large frustration.
    • For tablet users, the cursor isn't nearly as precise as a mouse/trackpad. And you can make a lot accidental clicks.
    • Different Construct themes have different sizes of X and different padding around it (see below).

    We know that our individual experiences don't equate to the average or aggregate experience. As a product grows, as users become more advanced, the need for personalization grows in step.

  • Yeah it's super strange - it seems to happen in all kinds of arrangements between the start/end object. It's also not targeting the precise X/Y of the end object; it's finding a path a little down/right of the origin point.

    Sorry I can't be much help! It feels like a bug but hopefully someone with more experience can see the issue.

  • Does the result differ when you change the cell size?

    construct.net/en/construct-2/manuals/construct-2/behavior-reference/pathfinding

  • These may be dumb questions, but does your Hotdog object have an animation named "Walking Left"? Is the spelling correct? Is the speed of the animation greater than zero?

  • You can also add "Object -> On frame changed" so that the action runs every time Frame 2 is drawn (Trigger Once will only run the action once)

  • Without any conditions, all objects are picked. So when you say "sprite -> subtract 1 health", it's saying "subtract 1 health from them all".

    But once a condition is added to an action, it starts looking for an individual instance. So when you say "Sprite health ≤ 0", it's asking "if you find one Sprite with health ≤ 0, do [this action]". It'll pick out one random instance of Sprite, and apply the action to it.

    So "For each Sprite" means you want all the instances that meet your conditions, not just one random one.

  • Great question! I'd love to know if there is (or could be) a quick erase feature or something for tilemaps.

    What I've been doing isn't great, but in case it helps: after creating the tilemap full of unwanted tiles, I select all the tiles in the tilemap window (the place where you pick tiles to draw) so there's a big selection of tiles, like 10x10 or more. Selecting the eraser in the tilemap window turns that selection into really big eraser, so you can quickly erase huge areas of the tilemap object at once, and clear it out quickly.

    Not perfect by any means (and likely quite obvious), but it helps. Hopefully there's a better answer!

  • Ah, ok! That makes sense! Thanks for the update. Also, this folder import feature is a fantastic addition. Really saves a huge amount of time!

  • I love the option of removing the Xs and right clicking to close!

    I'm not sure what the state of the suggestions platform is, but it'd be a great idea to add there.