Lou Bagel's Forum Posts

  • No, it still picks from what's currently picked. I've used both extensively and they work as expected.

    Ah, yes. I think I was thinking of the pick all

  • Should be easy, you can set their angle to the player's angle

    So just add to that 'every tick' event the action for the movement keys 'set Angle' to 'Player.angle' (I think there may be the action set angle to another objects angle, but either way)

  • If we don't know what you are doing then we don't know what you are doing wrong...

  • [incorrect comment removed so I don't mislead people ]

    ...haven't used it much but that's my understanding from what I've read

  • I don't see the issue with the events you posted, but you said that those aren't the events that were causing the problem, so that doesn't help much.

    Anyway, I've had similar issue, the problem was if you spawn a bullet then change the direction you are fine, but if the bullet gets destroyed before the the angle is set then it picks all the bullets. LOS may be going in and out quickly? not sure, so maybe this doesn't apply.

    Anyway, first thing I would try is 'On Bullet Created' -> set angle to: boss.direction = "right" ? 0 : 180

    (if you don't know the ?: I recommend learning, very useful)

  • So active this commuity :/

    haha, it was only 1 hour 10 minutes between posts

    ...and usually more people help if you attempt to create it and ask for help when you have issues.

    Wall slide - decrease max fall speed while wall sliding and change animation

    Wall jump - when in contact (wall left/right) with wall and input detected then bump Y vector

    Also, these feature are quite commonplace and if you search you can probably find lots of tutorials and forum posts on these topics. So instead of mocking "the community" help yourself first and others will help.

  • 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 have time to dive into this at the moment but one thing stuck out to me, probably isn't causing the 'hitch' but:

    Both of those 'for each' will occur every tick that the player is overlapping an active spawnTrigger. Even if you disable the spawnTrigger in a subsequent event I would still test that out to see how many times it runs. Maybe a 'trigger only once' would take care of it but would definitely test that out.

  • Can you post screen shots of the events you are referring to?

    I still have a feeling something is more CPU intensive than it has to be

  • Creating a lot of objects at once is intensive. I think you should be able to create around 20 without getting a 'hitch' though. Is 'the hitch' on everything, so lower FPS? Or are you only noticing it affect the new objects?

    One thing I would try is make a txt box (or use console.log) and append text on every part of event ("loop started" "variable checked" "instance created", etc etc, whatever descriptors you need to identify). Then you can see if certain events are running more than necessary. For example, if you used 'on created' -> 'for each' then if you create 20 enemies at a time you are running that loop 20 times when you only need to run it once. If you have 100 spawnSpots to check that is 2000 checks when it should only be 100. That could cause a 'hitch'

  • First question would be how many are you usually creating at once?

    Second question would be are you using a 'for each'?

    Side note answer: anything on a different layout should have no affect on current layout

  • Overload Test

    Now that I'm moving along in the art area I need to focus on evolving the gameplay.

    The zombies walk animation I created only looks okay if moving really slow. So I wanted to see how many of these zombies the player could take coming from one direction:

    See for yourself here

    This doesn't factor in reloading time and only one direction instead of four, but lets just say I will probably have to make some faster moving zombies or other challenges...

  • Yeah, in short, I don't think destroying it is the smart choice if you want to retain that much information about it

  • In my game i have 4 different enemies. When the player kills an enemy they spawn a key that opens a chest.

    I'd like to be able to have a different enemy spawn that key. EXAMPLE: player kills enemy 2, they spawn the key. If the player quits the game and restarts or passes that level on the next level(s) enemy 4 will spawn the key.

    Thanks for any help.

    My first thought is to have an instance variable that is a boolean (hasKey - default to no). Then set an event to randomize it

    On Layout Start - > pick random instance --> set boolean to yes

    Or could do:

    On instance destroyed

    If instance count > 1

    If random(0,1) > 0.75 then spawn key

    Else (if instance count is 1) then spawn key

  • I d'nt Know Use this ;(

    Pick closest to:

    Player.X

    Player.Y

    I have confidence that you can get it to work

  • I assume that when an instance is destroyed there is no information kept on it's last location and such. But you have several options I can think of of the top of my head:

    Instead of destroying the instance move it off screen or turn it invisible

    Respawn an instance of the object

    If the instance won't always be in the same location then you could use the 'on instance destroyed' to store location or other information in global variables or array.

    If all objects need to get restored you can simply use 'restart layout'

    In short I don't believe there is any event that you can set this up in one step but you have plenty of tools at your disposal to achieve what you desire.