lionz's Forum Posts

  • You can do anything you want. You can pick by UID or IID. You can give it an instance variable to identify it. How many unique identifiers do you need?

  • One option I suppose is to not use the platform behaviour to move the block, you can try sine or just events to increase its Y, will that have the desired effect?

  • Only controlled by the device itself, you should change the design so it's not based on being idle.

  • Hard to guess let's see the events/code

  • Does pin behaviour with pin at image point on top of the block do anything? Too lazy to set up a test.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Nice, your method seems fine too for a simple spawning. If you want to keep the spawners around you could set an instance bool hasItem to true so it's not picked again rather than destroy. There are many approaches for this kind of thing :)

  • Using an instance variable on the spawner object, something along the lines of :

    Pick a random instance of spawner, where instance variable is not set to 0 (default/empty), set var to 1.

    Repeat this for 2, 3 and 4. You can use a for loop for 1 to 4 and use loopindex as the variable which will be 1,2,3,4 or just add 4 events top to bottom and they would run in sequence.

    Then you have 4 spawners each randomly set to 1, 2, 3, 4.

    Add logic to make 1 relate to a particular item, 2 is another item etc

    Or if the item names are known and its easier with text, set the instance variable to a string and say where instance variable is blank/"", pick a random instance of spawner and set to item1name etc and repeat 3 more times.

  • You can use set mirrored/not mirrored actions together with the simulate actions in the same event.

  • Dunno, cannot see the code :D should be a simulate left/right and if it collides with the invisible sprite then simulate the opposite direction

  • The object has properties bar and near the bottom there is 'initially visible' which is usually ticked, you can untick this to make it invisible by default.

  • That's how it works in the one I made

  • I don't think localstorage and dictionary are interchangeable, what you've done is swapped out variables for dictionary? You didn't mention how you did it originally but dictionary would be saved as json format in localstorage as well.

  • Something like this : dropbox.com/s/aenxu10o766mgza/levers.c3p

  • There's no need to set true/false variable for each instance of the variable, surely just landing on any button and setting it to true/false is fine. I see what you've done with the button checks though and it might not work. My approach would be to have any button linked to that moving platform with the same variable number. Then you can pick all buttons that have the same number (and are set to false) as the moving platform, and compare pickedcount, if its 0 that means all buttons are true and it can move. If you are always going to use 2 buttons with a platform you can of course compare if the buttons are true and that the pickedcount is 2, but the false way adds flexibility if it is more than 2 buttons.

  • Explain the problem you had with ads on C3? My experience was fine, it was really easy.