oosyrag's Recent Forum Activity

  • An example - https://www.dropbox.com/s/dzx2ycubr8wfl ... .capx?dl=0

    Here is a link to the system expressions for reference, in case you don't understand some of the expressions used - https://www.scirra.com/manual/126/system-expressions.

  • With a proper authoritative host set up, the only thing a peer should be sending to the host is their inputs, and the host already has all the data values to begin with.

    But since that isn't the approach you are using, the only things I can suggest is:

    a. Send multiple messages with different tags containing different information.

    b. Send a single message using a token to sperate different information, and on the host side parse it back out with the tokenat() expression. You can use the & operator to combine strings when building your message.

    As for identifying who sent the message, that should have been covered in the multiplayer tutorials. In an event with the "on peer message" condition, you can get the peerid of the originator with the "fromID" expression.

  • The first step is to upload your .capx project file of what you have tried so that you can get a precise answer. There are usually multiple ways to approach any problem, so it helps us give advice without having to guess what your events look like.

    What you describe should have nothing to do with any time based concept at all, depending on what movement system you have implemented.

    The simplest way to do this would be to use the bullet behavior. On bubble created, set speed to initialspeed+score/20*50, assuming you don't need the bubbles to change speed after they have been created.

    If you do, it would just be one additional event to set the triggering condition to whatever you want, with bubble-bullet set speed like above as your action.

  • Set "force own texture" in the layer's properties bar for the effect.

  • Think of it as four less objects you can move every tick (thousands?) or check collisions with normally (hundreds?), in the worst case scenario. Best case you can limit the pool of objects involved in any given collision test (https://www.scirra.com/tutorials/902/li ... raycasting), so it literally does not make a difference at all.

  • You can have a lot of things moving every tick.

    Of course design for your platform, but CPU is rarely the bottleneck. As commonly suggested, don't waste your time. More specifically, keep an eye out for too many physics/collision tests, which are exponential in cpu cost, rather than object position updates.

  • You definitely don't want a huge sprite, as transparent pixels require rendering as well. 4 instances of a 1 px sprite would be the way to go, with negligible performance impact (especially if positioned just outside of the viewport).

  • The first thing that comes to mind would be to utilize 4 invisible helper line objects positioned at each viewport border.

  • Rather than setting the platform vector x, try just setting player position x.

  • From what I understand of your description, it sounds like families might be useful for you. Put all your sprite variations into one family, and have your events refer to the family.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Support for text manipulation is crap in C2. Best to use spritefont object instead.

  • Here is an example. https://www.dropbox.com/s/3yco9jmdthhad ... .capx?dl=0

    There are a ton of ways to go about doing this, you should try to be more specific or upload a capx of your own attempt first.

oosyrag's avatar

oosyrag

Member since 20 Feb, 2013

Twitter
oosyrag has 38 followers

Trophy Case

  • 11-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

21/44
How to earn trophies