Somebody's Forum Posts

  • Step 1 - Anti-spam bots

    Step 2 - ????

    Step 3 - SKYNET!

  • Somebody - if you have time.

    I hope this solution will work and not that it will eff up depending on which browser/system you use.

    That cracked me up given all the cuteness in this project

    Seems to work perfectly. It shouldn't be affected by browsers or anything, since the scrolling logic is entirely up to C2. As long as the numbers are correct it should be as well.

  • I had observed this previously as well, but in a complex project - couldn't replicate in a separate small capx. Glad to see you managed.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Try Tiled?

  • Somebody , WOW ! Just WOW ! O.o

    Thank you so much for sharing!

    Well, just sitting on them wouldn't do anyone any good

    Glad someone finds them useful or at least neat™

    Still hoping to see some usage examples/ideas/improvements, though.

    And, of course, more to come.

  • Basically array separated by the given character.

  • Well looks like the teaser site actually cares for mobile browsing, so perhaps the new main site will also be improved, fingers crossed.

  • That's really cool! Neat idea, well executed.

    How do you do the -^- part scrolling into the | line - masking or just layered sprites?

  • Well, you gotta remember

    In general depending on how complex your waves are a decent approach seems to use groups inside the event sheet and enable/disable those as necessary. So you basically plan out what the next wave should look like, place all the spawn/setup events into a group, make it disabled and enable it when the time comes.

    If your waves are super-complex it can get as far as making a system that, for example, takes something you have placed into a layout and stores all the important things into an array - then you save the array and use an opposite function to load the settings and create a new wave.

    It's all going to take some work, either way.

  • Uh...

    Oh, I realize that might be too subtle - look on the bottom of that screenshot.

  • I believe the suggestion is to mostly stay within sensible sizes, i.e. don't make your art 513x513 pixels as then it will need a 1024x1024 texture. As you crop your images the system will find the best way to arrange them on a spritesheet while adding a single pixel of transparency on each side to avoid artifacts when scaling. So if your initial art is within a power of 2 minus 2px rectangle you should be just fine.

  • I'm not exactly sure, but I think safari doesn't really do WebGL right? What does the debug say?

  • You yourself mention having a "For each enemy" - this shouldn't be needed as on collision they are already picked. Also I'd use random(1,10) for the imagepoint choice.

  • Well, I did put "nearly daily" in the title so here we go - Cinematic:

    Might be neat for a modern fps style GUI or just making things breathe. Accepts positive and negative values.

    Added to repo and first post.