oosyrag's Recent Forum Activity

  • Assuming you have a maxhp or monsterlevel GLOBAL variable for each monster (you don't want an instance variable, because that gets lost when the instance is destroyed). It starts at 0.

    Trigger Monster on Death - Increase monsterlevel by one

    On monster created - Set hp to 100*(2^monsterlevel)

    Or

    Trigger Monster on Death - Set maxhp to maxhp*2

    On monster created - Set hp to maxhp

  • In the sprite editor, the right side is 0 degrees, or "forward", not the top.

  • angle() is an expression that gives you the angle between two points, in this case from the sprite to your mouse.

    So every tick, set angle to angle(sprite.x,sprite.y,mouse.x,mouse.y)

  • Try Set angle TO angle(sprite.x,sprite.y,mouse.x,mouse.y)

  • That is really a personal best judgment type of question... But I'd say 1080 would be more than enough.

    Don't underestimate memory requirements though, remember there is a difference graphics memory and system memory.

  • What recording softwares have you tried?

  • It's a simple stat calculator with 88 events and 3 small images o.o

    It's not a game by any means I just can't really see how 3 Images with 88 events = 101MB :/

    Your program - 1 MB, NW.js wrapper executable (Chromium browser engine) - 100MB. (Not exact, just for example)

    Basically, most people already have a browser installed so you don't need to bundle the browser engine. Just export as HTML 5 and it will run in whatever people already have installed.

    The main purpose of NW.js is to create an executable file for windows on a controlled platform. So for you, you don't really need NW.js and thus your original statement is correct in a way. Doesn't mean it is worthless for others who find it useful though.

  • Hello there.

    Generally speaking, you don't have to worry about performance/speed when talking about image size. What you do need to worry about though, is available memory. See https://www.scirra.com/blog/112/remembe ... our-memory for more information.

    Basically it depends on the memory limitations of the platform you are developing for, and how many assets you have in your game. It is a trade off between fewer high resolution images or many lower resolution images.

    Ideally if you are not nearing your limits, you want to design for the highest resolution considered, then downscale.

    On the other hand, I haven't had many issues with blurry edges and upscaling. There are some things to try such as pixel rounding and sampling type in your project properties.

  • Use the angle value between the center/origin of your OSC and your touch coordinate, then separate out 8 conditions for each angle range you want.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Try angle(car.x,car.y,object.x,object.y) to get the angle between the car and object, and apply the impulse at the same angle.

  • Yes, basically if your player x position is within the Thwomps width (assuming the origin point is in the middle of both).

    Then you'll need to tweak it as you see fit. Does the player need to be completely under the thwomp? What happens on a partial squish? Or if they player moves into the side of it while it is falling? ect.

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