dop2000's Forum Posts

  • You can use 3D objects in a 2D game. See the official Gravity Portal example.

  • Arrays are often overrated.

    To pick two non-repeating random values you need the AdvancedRandom plugin:

    You can also do this with object instances. Say, if you want to give the player 2 random keys out of 10, you can place all 10 key sprites on the layout (somewhere off-screen). Then on start of the layout pick two random key instances and destroy the remaining ones.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The sprite should be destroyed if it's selected in Tween options, doesn't matter which property you are changing.

    Do you also have Fade behavior on the button? Maybe it interferes with the tween.

  • Afaik this method still works:

    construct.net/en/tutorials/sending-data-construct-23-1447

    If there's an error in preview, you can try the fix for cross-domain requests from the manual:

    construct.net/en/make-games/manuals/construct-3/plugin-reference/ajax

  • Not sure what it has to do with reducing lag, but you can probably do this: 

    Enemy On collision with EnemyFamily

. Enemy health>EnemyFamily.health : 
.........Enemy add EnemyFamily.health to health, destroy EnemyFamily
. Else
.........EnemyFamily add Enemy.health to health, destroy Enemy

  • See the response from the developer:

    construct.net/en/comments/57765

  • Which error? Did you restart the editor after installing the addon?

  • Ashley The current system is inherently unfair to users who submit their ideas later in the year. These suggestions often don’t get enough exposure before the annual reset, meaning excellent ideas risk disappearing unnoticed. Meanwhile, mediocre suggestions are repeatedly reposted at the start of every year, cluttering the list.

    A 12-month expiry period for all suggestions would ensure equal treatment, as every idea gets the same amount of time to gather votes and attention. At the end of the 12 months, the number of votes would accurately reflect the suggestion's usefulness and popularity. You could then decide the next steps for most popular suggestions — whether approve them for development or decline and archive.

    This approach could also help reduce the number of reposted suggestions, which aligns with your goal of keeping the list short and relevant. If users see that their idea hasn’t gained many votes in 12 months, they’ll be less likely to repost it, as it no longer provides the advantage of being at the top of a freshly reset list.

  • Oh! I thought that only those requests that get few votes over time were being eliminated.

    Nope. Everything is purged, and then there’s a rush of users reposting their old suggestions, hoping they’ll stand out and get a few votes while the list is fresh. Then others start reposting suggestions they liked from the previous year. Then the original authors return to find their ideas already re-posted — sometimes in a less detailed or lower-quality form.

    We've seen this cycle repeating every year. It’s clear that this system has significant flaws.

    Implementing a 12-month expiry period for posts and automatically removing those that haven’t received, say, 20 votes within that time frame could be a simple and effective solution.

  • Hi Ashley,

    First, I’d like to thank you and the team for all the hard work you put into making Construct 3 better year after year.

    However, I believe the annual purge of feature requests might need a rethink. It doesn’t make sense to delete great ideas from November or December just because of a calendar reset. To use an analogy, this is like tossing out ALL the food in your fridge every month to avoid spoiling.

    A more balanced approach might be to set a rolling cutoff period — remove feature requests that are over 12 months old and have not received a significant number of votes. This way, older ideas naturally phase out, but newer suggestions still get a fair chance. It would also cut down on people reposting the same ideas, which inevitably happens at the start of every cycle.

  • on the website construct.net/en/make-games/addons/290/faceapi

    There are two example projects, have you tried them?

  • Well, I was already using global variables, and they still reset.

    They should not reset, unless you have an event that resets them.

  • Just to clarify, can I use the Dictionary object to store item details like name, quantity, and price all in one entry for each item?

    No, you'll need to use multiple keys.

    In your case an array would be a better option.

    But the best option (in my opinion) is JSON - it will allow to store any data in any format you like.

  • It's hard to tell what's happening without seeing the entire project. The function on your screenshot should definitely create "score" key. If you previously parsed another data with "score_table", then the JSON should contain both keys:

    {"score_table":{"id":1,"position_x":"0","position_y":"0","boss_counter":"0"}, "score":{"id":1,"position_x":"0","position_y":"0","boss_counter":"0"}}

    If this doesn't happen, maybe the function doesn't work? Or another AJAX request immediately overwrites JSON with the old data from the server? I can only guess.

    Learn to use the debugger tool (Shift+F4). Temporarily disable the loading function and test that the saving function works - check the contents of JSON in the debugger.

  • lightning_ I respond when I know the answer and when I have time. If you need help fast, try Discord or VK group.