Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Heppell08 last won the day on September 5 2014

Heppell08 had the most liked content!

About Heppell08

  • Rank
    Advanced Member

Contact Methods

  • Twitter

Recent Profile Visitors

2866 profile views
  1. So i used to frequent these boards a while back but had to take a break from writing games and coding because of family life and children etc. I've decided to now come back to the coding scene and was just wondering what's new here? Spent alot of hours browsing these boards in the past and loved seeing this community flourish and help one another. Thanks for taking your time to read this and I look forward to speaking again sometime very soon! Also thanks Photon Storm you are one dedicated dude to this framework and i think alot of people would be very stuck or even lost withou
  2. RT @gustojunk: There is bad design, and then there’s shared touchscreen inside a public bathroom design. https://t.co/BqnhxtROHr

  3. This is something that requires you to destroy all the game elements and upon restarting that state again you create the game again. There are a few ways to achieve this with proper destruction and creation. Some elements may not need destroyed at all depending on what your game is and does etc but you do need to destroy then recreate on loading the state again.
  4. I would have used a for iteration loop with that group and moved them like that with some parameters in place for distance/alive etc. Even a forEach may have done the trick here too.
  5. You wouldn't need to ask the user if they are desktop or mobile to show the onscreen touch keys you would be adding because phaser has device code in there. If you're using states like boot and menu etc then you can decide if touchscreen is on or not via the boot with a simple if(). if(this.game.device.desktop === true) { return; } else { // load touch buttons here } I'm on mobile at the minute so that is psuedo code but look up device code in phaser. It is like the code above that can sit in the boot and either load or not load them buttons for you. The main change would really be to add a b
  6. Have you got a for iteration loop doing the checks and lifespan on the group of sprites to be killed at the alotted period you set? Have you any code examples or snippets on what you are doing? I don't personally use lifespan but to achieve the same result you require would be simple in the terms of creating a custom sprite timer but that is just overlooking what lifespan does for you in phaser.
  7. Yeah I use codevinsky's yeoman generator. Has watchify, server, minify and all the other cool stuff required. Don't see the use for more generators when Codevinsky's already does the job required. Suppose each to their own though.
  8. Destroy the layer the recreate the map as normal.
  9. i personally used this for my game to have the onscreen touch joypad. You can choose different looks and styles etc with it and its pretty responsive too. My code for it is: if (this.game.device.desktop) { return; } else GameController.init({ left: { type: 'joystick', joystick: { touchMove: function (details) { if (details.dx < -5) { left = true; } else if (details.dx > 5) {
  10. Maybe set them to out of bounds kill so when they go off screen they are killed that way?
  11. Hmm, well if even making it global doesn't help them maybe trying to user a getAt() in a loop and cycling them. I would have thought a forEach would do the job or a getFirstDead() cycling the group would do the work for you.
  12. Place coin as global and not anon in your create function.
  13. function coinKill(coin) { if(coin.x < 0) {coin.destroy();} } Its how I kill coins but its similar to collide coding the coins. You shouldn't need to reference the actual group itself because you can reference the children (coin) instead.
  • Create New...