lionz's Forum Posts

  • Well there's not enough info there but it is easy to have problems with picking when you introduce multiple instances.

  • I don't think so, I was using browser log to check. You have a lot of events running every tick though so CPU usage looks fairly high. I think because you have all the events sheets linked it is probably running most events in your game all the time. FYI, no condition is the same as using 'every tick'.

  • Not quite what I described but almost there. You should only have one set bullet angle action, on spawning the bullet with the mouse click event. Delete the rest of them!

  • Yeah the batch waiting for signals every time you receive a signal it runs the next bit 'every tick'. Adding a trigger once fixes it but it doesn't return to phase 1 start. In my opinion better to give up on that structure of wait for signal, go to the actual attacks on animation finished and set the next animation in the sequence there for a better structure.

  • My guess is because your walk animation logic is still true even when sliding? You need to add to your walk 'if slide is false' or something similar.

  • I finally sorted out my subscription and took a look, it is as I said in a previous thread the events are running every tick hundreds of times. Adding a trigger once to what you have will kind of work but then it doesn't reset the attack. You need to find a way of having it trigger once each time and cycle round so try a different structure.

  • I don't understand how anything that simple could cause bugs. In a bigger project, if you approach your coding like this it will turn into a mess of variables spread around event sheet.

    There is also no need to transfer that data between levels (this is what global variables are normally used for) as it is just inputs and if you use getter function you can do it all even better.

    Usually player related things are used globally throughout the game so as a standard I use global variables for anything player related. Whether I'm using global or instance variables it is kind of irrelevant though as the events are the same, it is just a preference.

  • Better use instance variable tho. Bad habit using global variables for everything.

    The variable is used to detect the shooting direction of the player, anything player related I use global variables because it's just easier to avoid bugs. The bullet then takes its angle directly from the player's shooting angle stat.

  • Just do the following :

    Add a global variable

    Under the set bullet to angle degrees actions, add a different action 'set variable to X degrees' where X is the value you have for the bullet angle.

    Delete the set bullet angle actions.

    On the spawn/click event, add an action below spawn bullet : set bullet angle to 'global variable' degrees

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I could make it but you are trivialising the work by saying it is only a battle system, I could not just make it and show you, it would take a while to make, it's a large project. You need to first decide which enemies will spawn and apply all stats. You need to have enemies acting in turn with their own decision making, and all of these attacks need to affect the player. You need to be able to damage and apply statuses to enemies and detect when they die, take them out of the turn based system. You need to then add XP gained, loot and other things that decide the end of the battle. Probably a bunch of bug fixes too along the way. What you are describing that you have already done with the stats sheet, that is the design.

  • I don't see how everything is almost done, looks like none of it is done? To make a turn based battling system it's going to require some work, it's not as easy as saying this is how you make it.

  • You should set the angle of the bullet as it is spawned. Since you already have the key events you could set a variable to a value, and then on spawning the bullet, depending on the value set it will set that direction.

  • Try replacing the bottom events with 'left button is down' and 'right button is down'

  • The conditions at 11, 12 and 13 should be asking whether the global variable is 1, 2 or 3.

  • boss looks good but think about removing that yellow font argh