lionz's Forum Posts

  • Share the project file of what you tried and I can take a look

    Every 2 minutes would be annoying, 2 hours is a long time. Also the pop up could be useful to remind you to save.

  • You are spawning them outside the layout (Y=-70) and the object is set up to be destroyed outside layout.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I don't think you can do it by name you'll need to pick the object. What's the problem you are having where you can't just pick enemy1 for example?

  • Look at the conditions under player with the platform behaviour. If player is overlapping spike, or on collision with spike can also work. Then the action on the right would be to destroy player or subtract some hp.

  • You can add another condition to 'on start of layout', I think system compare two values LayoutName = "Layout 1" should work well.

  • Load them in the current layout

  • Well what I'm thinking is if you are on a remote preview and they are testing an exported game then the variables could be different. You can be playing two different versions of the game and in the preview you could be starting from a different point of the game.

  • Where are you playing the game from and how are you sharing it?

  • Layout view doesn't have the same rules when you're adding container objects and sometimes doesn't treat a container as such. I found it is better to create them during runtime. These bugs about moving parts of a container are kind of trivial because the point of a container is to pick everything together in one event, so on your event sheet you would set the layer of one of the objects and all other objects would follow, no real need to start doing all this in the layout view.

  • The main issue I see now it is because on the vectorX actions you've used self.x needs to be self.platform.vectorx.

    Probably you will have an issue if you add more than one enemy, this is the picking I mentioned earlier. I would just use the collision box X and not the enemy as I've edited it here.

    dropbox.com/s/nhuxbhvvvnudbmm/castle_raider%20%281%29.c3p

  • Yeah I can see that, the problem is that the box doesn't relate to the enemy. You can use the box instead of the enemy though (probably). Or a container. Share the c3p I will edit it.

  • You can use the green object X instead of the enemy x, will that work in your game? Not comparing vector X, compare X the position it's a different condition.

  • Since it's already picked, can you use the green objects X instead to compare?

  • In the sub event with system conditions try replacing them with the enemy object condition pick compare X against the player collision box and see what happens.

    The problem is even if that fixes it, you will come across a bug when you add more than one enemy. If the green object is in a 'container' with an enemy then it could relate well. The problem you have is green object colliding with player doesn't relate to any enemy.