lionz's Forum Posts

  • Yes this approach will not work. If just one blue unit cannot see a particular red unit then it will be set to unseen. The fix for this could be something like always set red_unit to unseen, and keep the event for if blue unit has line of sight then set to seen.

  • You do not have permission to view this post

  • A sprite can perform the function of a button, on touched or on clicked.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You first add the instance variable to the object so a string 'name' then use a condition in the event sheet using the object compare instance variable.

  • Hello!

    For movement it is the 8-direction behaviour which allows a kind of top down movement and by default with the arrow keys.

    To create at a random position would be to use sytem > create object and the position would be the same Y but with a random X, it would be something like random(0,500) for example which chooses something in that range.

  • It's a strange approach I guess, you shouldn't have to bring in gameplay assets from another layout and set them invisible, but if you are doing that then I don't see how the player colliding them while invisible is a problem? Anyway the approach is not great as you start bringing in unnecessary art assets and increasing memory usage. They are invisible, serve no real purpose. You should process the overlap checks when you enter the layout that contains the crops.

  • Seems kinda counter intuitive to make them global then hide them on other layouts, why are they global? What purpose do they serve?

  • There's no real need to check this every tick and my guess is it's not running for each soldier so it just applies to the first one. I would set everything in position when the enemy is created and pin it then you just do it once. All of the actions from that every tick can probably be moved above to the enemy on created block and that's all you need. You would know it is picking the enemy correctly, the one created.

  • Yes that's right

  • You can also disable collision on the objects

  • What do you mean exactly by cutting off at the end?

  • The instance variable shouldn't change unless you set it to another value, are you setting it back to its default value somewhere and if so why ?

  • Not really understanding the question because your logic is not to follow by UID but to find path on the enemy that is clicked? Clicking the enemy picks it so you can find a path. To find by UID would be something like condition enemy.UID=num, find path to enemy but with a trigger once added.

  • You worked on it for 3 years and don't have any spare capx or projects?