oosyrag's Forum Posts

  • I believe the effect he is going for is for the magnifying glass to be positioned at the actual angle the character is from the center of the viewport, but constrained to the border area of the screen.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Put event 3 and 4 in subevents under a For each condition. Also since period is a measure in seconds it doesn't make sense to have it be a negative number... although it seems to work I would change it back to a positive number and use the following

    + System: For each Grump

    ----+ System: Grump.Sine.CyclePosition > 0.25

    -----> Grump: Set Mirrored

    ----+ System: Grump.Sine.CyclePosition > 0.75

    -----> Grump: Set Not mirrored

  • Ray casting finishes within a single frame and the event sheet runs from top to bottom. Separate the ray casting events and ray intersected events to check each ray after they are cast.

  • I haven't tried it myself yet, but I imagine if you used an intermediate data structure like an array to store your base tile upon generating a chunk (instead of setting the tile directly), then setting all the tiles in one go with the bitwise auto tiling function based on that array (compare array values instead of tile values), it should work fine.

  • Being able to click and drag to toggle/lock multiple layers at a time as is common in CAD software would be a nice usability improvement.

  • You do not have permission to view this post

  • Here's an example, I tried to simplify it as much as possible. Sorry the previous reference I linked wasn't in Construct terms - in Construct the "return" parts are handled by conditions, basically if the conditions are not met, then do nothing. dropbox.com/s/6eduutskd8lif24/floodfillexample.c3p

    On clicked object - mark the object for deletion, and check the four adjacent positions to see if it is the same type of object and not already marked, then repeat for each. If it is not the same type or if it is already marked, then nothing happens.

    Afterwards, pick all marked objects. If the total picked is more than two, delete them. Otherwise, clear the marked status.

  • A parabolic arc would consist of a constant horizontal speed, and a vertical acceleration downward (gravity). The exact trajectory will depend on the initial speed and angle as well as the amount of gravity. The platformer behavior has gravity built in, as does the bullet behavior which may also be useful.

    In general though, if you're making a physics game, use physics for all movement. If you aren't, don't use the physics behavior at all, and make your own.

  • Adjacent as in all cardinal directions? Or only in a line, like a match 3(+).

    If it's in all directions, you're going to want a simple flood fill. freecodecamp.org/news/flood-fill-algorithm-explained

    Instead of colors, you're going to set an instance variable, as you have done, to mark for deletion. At the end, you can compare the pickedcount for any objects with matching=true to see if its greater than 2, then delete them. Else, reset all matching to false.

  • Sorry I don't have any sort of a detailed solution for you, but I can tell you at least that you decidedly do not want to mix physics with any other type of motion behavior, including pin.

    No detailed physics simulations were involved in Yoshi mechanics or Levelhead. Was there any particular reason you're using physics? Pin and tween should be sufficient to get that type of grapple, along with the platform behavior.

  • To do something at the end of a tick, use system-wait: 0

  • Iirc viewport size (and left,right,top,bottom) can be changed by layer scale (and parallax), so a layer needs to be specified.

    Canvas size I believe is the same as window size, I'm not sure about this one.

  • The source code behind built in plugins are not available to be modified.

  • It works fine in r254 for me. Current stable is 251.2, and I believe it was not fixed until 253. So you can use the beta or you can wait until next stable release.