lionz's Forum Posts

  • Create a 'starting point object'. On start of layout, set the position of the starting point object to the object you are shooting(setposition). Then when you press/touch the object to return, set the shooting object to the position of the 'starting point object'.

  • I think you want Dictionaries (check the manual). I guess create textboxes for text entry and whenever text has been entered and confirmed, add it to a list of string variables stored in Dictionary form. Then when you select the button to spit out a random name, choose one of the stored strings or choose a random number which is assigned to a random string via Dictionaries.

  • It's one of the template levels if you go to New > Template: Auto Runner.

  • Beaverlicious lol

  • ?

  • russpuppy

    nice, thanks!

  • All ideas welcome. I want to finish a gameeeeee.

    Or perhaps just a thread for listing small game ideas that are not Candy Crush : D

  • Look at web storage for cash data. If you're talking about storing actual cash funds, ermm you'll probably need a license from the gambling commission first..

  • Haha looking cool, I want to play it.

  • I agree. Start each layout with touch inputs disabled for a second. It'll stop the constant touch detection and flicking between layouts.

  • If player is overlapping ladder

    AND key UP is pressed          > simulate control up

    you may have to do this every tick or every x seconds and you'll need some logic in to end the movement

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • The purple bar is a timer for the enemy. When it fills, the enemy will attack. I've added MP now and a Cure ability.

  • Something I'm working on. Reaaaaally basic. Might make an RPG.

    Play me

    SPACE BAR - confirm

    ARROW KEYS - move (only one Attack option though)

  • Does it not make sense to have a layer with the same name in every layout that always exists as the top layer?

  • Start off with a low number of conditions for the main animations, so running right = running anim, running left = running anim+mirrored, not running = idle. You are bound to come across logic that conflicts with other logic when playing certain anims, bugs are expected but they can be easily fixed if you keep the logic simple and not too convoluted. I'm not sure something like 'is on ground' is needed unless you're triggering different anims for different types of ground. If you're coming across any specific problems then detail them here and someone will help simplify the logic.