oosyrag's Forum Posts

  • I tried this a bit, and there are a few things that make it significantly more complicated. For starters, you can't use the object.count expression anymore, because that will get you the total count of all necks. object.pickedcount doesn't work either since we're running a loop per neck so there's only 1 neck picked at any given time. We also won't be able to use object.IID to keep our necks in order either, since set 1 will have IIDs from 0-5 and set 2 will have IIDs from 6-10 for example (it's not 0-5 for each one). I'll see if I can think of a more flexible solution later today.

    Edit: Dynamically creating a set at runtime should be easier, it's just a matter of setting all the right variables and creating the associated parts whenever you create the body. However, you'll need to know all the data you need for the neck part to work properly first. It's best to work on one thing at a time.

  • You can make a parachute like behavior by lowering the gravity amount, or applying a small (less than gravity) upward force every tick.

    If you change the gravitational force, you're changing the angle of motion.

  • The layout coordinate of the tile or the tile index can both be plugged into the advanced random function for usable results.

    To get the layout coordinate, you use the tile to position expression with the tile index to get your value.

    Or you can use the tile index directly in the advanced random expression as well.

  • You'll need to identify and associate the sets of parts. A simple solution would be to assign a common instance variable to each set, so that you can use it to pick the relevant parts in your events.

    You can absolutely spawn parts at runtime. Just on start of layouts or whenever, for each body, spawn parts. Containers I think would not be as suitable since you need multiple instances of just one part. Hierarchies might be more applicable, but I'm not familiar with them.

  • You can use either the absolute tile position or the tile index, either will work.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Yes. The 2d advanced random noise functions/expressions will give you a value between 0 and 1 for every x,y input you enter. In your case, the x and y would be the tilemap coordinates.

    It is up to you to define what you want the returned value between 0 and 1 to mean.

  • dropbox.com/s/48rdqokyr566kmd/stretchyneckexample.c3p

    Constructsaur goes rawr.

    Note that you can calculate the difference in x and difference in y from the head to the body and store it in an instance variable like in the tutorial if you want to, but I just put it directly in the expression.

    Edit: Also added a second event sheet, doing the exact same thing with the lerp expression, which is how I would probably approach this. The way on event sheet 1 is more like how the tutorial does it though. The end result is exactly the same either way.

  • Move the object and the drawing canvas somewhere clean to take the snapshot then move it back. Or spawn a helper background sprite to cover everything else and then delete it. Or make everything else invisible and take the snapshot and make them visible again. You can do this by utilizing a dedicated layer for screenshots if you want, and hide/unhide all the other layers.

    I believe these can all be done within 1 tick so the user doesn't actually see anything.

  • Works fine for me, even on two different computers, on your host (where the project is hosted generally doesn't matter by the way, it's a peer to peer connection).

    Some connections can have issues without a TURN server, which is not utilized by default, but there is nothing stopping you from adding one.

  • You should definitely be using tiles, for the floor at least. You can draw that outline in your tile as well.

  • dropbox.com/s/p5k02teeayy74sk/offsetcameraexample.c3p

    You could also use the system scroll to position action every tick to target an invisible sprite or imagepoint on your main sprite instead of the scroll to behavior. You could also use the pin behavior instead of setting position every tick.