dop2000's Forum Posts

  • The Tile Movement behavior feels unpolished, I almost never use it.

    C3 has plenty of quirks and oddities. Things like OR-blocks, the Else condition, and Trigger Once could each have a dedicated chapter in the documentation.

    One recent discovery that caught me completely off guard (although mentioned in the manual) - restarting a layout also resets all groups in the entire project to their initial state. I had to go through many of my projects and replace "Restart layout" with "Go to layout". I still don’t understand why "Reset all groups" is not a separate action.

  • Text: replace(currentDialog, "your_tag_here", newline)

    Duration: len(currentDialog)/10

    But if you need to break the text first into blocks and display one block at a time, it's easier to use a local variable.

    The first action extracts one block of text from currentDialog into t variable. The second replaces line breaks in it and typewrites it.

    Or you can do it in one expression if you wish:

    replace(tokenat(currentDialogue, index, "^") , "{line_break}", newline)

  • Meshes are also unavailable in C2.

  • Use Date plugin:

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

    You will probably need to store some data in Local Storage, say, the number of times the object was already displayed this day.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • 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.

  • 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.