lionz's Recent Forum Activity

  • Great, glad it's working :)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I mean replace low and high with numbers as described in the second line. I don't know what your range of layout numbers is.

  • Go to layout by name : "Layout_"&floor(random(low,high))

    where low= lowest layout number and high = highest layout number+1 (it rounds down)

  • It's not as easy as it sounds but you can accomplish this with some tight function work. You replace every x seconds with the timer behaviour on the zombie object so each has their own timer. Whenever a zombie's state changes you run a function with the zombie UID as a parameter. Then when you call the function you use the condition where zombie.UID=function.param(0), that's how you identify the one zombie object. You can then run things like on zombie.timer ended, run function sending through the zombie UID, and check if you want to make it run a random path and start a new timer on that zombie. If zombie is in proximity of the player you can run a function with the UID to stop it from pathing then change its status to chasing and finding a path to the player.

  • You can assign behaviour to family group then say on enemy A created, set speed to this, then on enemy B created, set speed to this. So you have different speeds but can keep general logic such as 'all enemies(family) path toward player when they have LOS'.

  • In project properties bar, reverse the window size xy. If it's currently 720,1280 then change it to 1280,720.

  • Sorry, I don't really have the time to make this. Try using sprites with bullet behaviour that are created in 2 places and angle toward a cursor object in the centre.

  • It's useful if you are still applying some of the behaviour conditions to all members of the family. For example if you have enemy A, enemy B, enemy C, enemy D all who will move towards the player when they have line of sight of the player, you do not need to say individually enemy A LOS of player, enemy B LOS of player, but you can say enemy family LOS of player. It's up to you to decide if grouping behaviour for all enemies will minimize some code. I can't see anything wrong with applying enemy family behaviours because at least then you do not have to add behaviour to individual objects, they will all adopt the behaviour, then you can set the values separately for each object if you need.

  • Seems fine if the bottom 3 panels are also buttons you tap. I'll have to download and play it rather than just watch the video ^^

  • The sickle looking bits on the table that you move left and right touch, or so it seems. Maybe that's where the player is tapping actually now that I think about it, they might just be arrows where you touch.

  • This looks interesting, what do the 2 end bits on the table do, give you the ability power? Seems fast paced and competitive ^^

  • It's a small bug but not a big problem, just don't use line breaks for redundant 'organising'. The bug is to do with line breaks, not the compare two values condition which the topic suggests.

lionz's avatar

lionz

Member since 5 Aug, 2013

Twitter
lionz has 79 followers

Trophy Case

  • 13-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

26/44
How to earn trophies