R0J0hound's Recent Forum Activity

  • heal

    I think you should be able to find the collided with tile using the collision point and normal, but I have to think about it. The only issue I can think of is the collision point is on the edge of the tile so you may need to use the normal as well to get a point inside the tile. From there you can find the tile with tilemap's x to tile x expressions. I need to impliment a capx to be sure.

    —

    I haven't looked into it yet, but I probably should.

  • Neat. You successfully captured the same feel as a console game. Nice work!

  • —

    html5 doesn't provide a way to turn it off. From what I've read is a solution is to draw the curve or lines one pixel at a time.

    Here's a capx that does that. If you have the function and canvas objects you should be able to copy the "pixel lines" group over to your capx.

    https://dl.dropboxusercontent.com/u/542 ... ezier.capx

    It isn't completely smooth due a math error I think. I may revisit it later.

    Edit: fixed, it's now smooth.

  • I read the original post a bit wrong, but like blackhornet's example you can do it with blend modes.

    Here's another example to make only part of a sprite transparent:

    https://dl.dropboxusercontent.com/u/542 ... blend.capx

  • I usually handle collisions with other instances of the same object by creating a family with just that object in it and call it "other". Then use events like this:

    For each sprite

    sprite is overlapping other

    for each other

    system compare: other.uid !=sprite.uid

    --- handle collision

  • You can't access dll files from javascript typically. You'd have to make a browser plugin I suppose.

    But if you're wanting to run your c2 projects in your custom engine, it's not a trivial thing to do. Basically you'd be stacking another engine on top of yours which would defeat the purpose. You could pull the level layouts and animations from the xml of the capx files and convert it to something your engine can use, but all the logic would have to be re-written from scratch.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • SpookySkeleton

    Give the tail pieces a private variable called "index".

    Then every time you create a tail piece set their index to -1. Finally to do the ordering use a "for each ordered" loop:

    For each tail ordered by tail.value('index') ascending

    --- tail: set index to loopindex

    That will make the tail piece right behind the player always be 1 counting up to the oldest one. This loop also cleanly handles destroying pieces, so they will be recalculated correctly.

  • In general a behavior is run every tick if it can move the object.

  • "centerx" and "centery" can be replaced with any x and y you want to use as a center.

  • Amusing game! The first thing I did was leap out of the tree... and splatted on the ground. Awesome.

  • Yeah it's based on what was added first. The first three points for the first curve, next three for the second and so on.

    Here's it tweaked to use instance variables for the p sprites instead of using the iid. "group" is used to specify the bezier number, 0 for the first, 1 for the second, and so on. To use more than two you need to change the "repeat 2" condition in events. The other instance variable is "handle" which specifies what control handle the point is.

    dropbox.com/s/l70glhg4ty742vk/bezier_slope2.capx

  • This topic has a few ideas: