brushfe's Recent Forum Activity

  • Like any game, this type of game is just a combination of objects, actions, and reactions. So if you break down your game into those components, you'll find it a lot easier to build, find tutorials, etc.

    Monopoly, for example:

    Objects: game board, game pieces, dice, cards, money.

    Actions: dice rolls, buying/selling property, paying money to other players or the bank.

    Reactions: roll results, player movement, landing on a game board square, earning/trading/losing property, adding/removing motels and hotels, drawing/viewing cards, earning/spending money, etc.

    Once it's broken up like this, it's a lot easier to imagine how to design each component individually than a whole game (e.g. If people are gaining/trading/losing property, we need an array to keep track of who owns what, and we need a function to modify that array).

  • Hey! Is the problem that the character is sitting too low on the platform?

    If so, check the collision box on your sprite, and make sure it's aligned with the bottom of your sprite.

    Double-click on the sprite object, and press the collision box tool (red arrow in the image below). Then drag the box handles so that your collision area at your character's feet (blue arrow).

    Hope that helps!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It would be much easier to help if you could share your code (the screencast video player is really slow!)

    But in the meantime, I'd suggest using Families for this kinda thing. It's a lot easier to use one block of code that governs multiple objects.

    I've put a quick example together here, see if it's helpful!

    drive.google.com/file/d/1i8sKF7b0PxsrmsBy3Whi1I_3bHFSsCUq/view

  • winkr7 has a lot of great points!

    Getting comfortable with arrays opens a lot of doors. It'll be really useful for a large scale project, but really any project benefits from keeping your variables centralized and easy to balance. The new template feature and the built-in array editor make it super easy to implement.

    And save a new copy your project with each Construct release, especially if you use betas.

    I use timer behaviors constantly. I find them really useful in later development, when the pacing of things matters (menus appearing, rewards being given, moving to the next level). It's a lot easier to fine tune the experience when actions are tied to timers.

    Don't forget to check if you need a "for each" condition when picking.

  • If you're comfortable sharing your project, it would help someone here find out what's wrong. It's usually impossible to do with a video showing only parts of your code.

    If not, you'll have to keep digging into why collisions work in one layout but not another.

  • Understood, thanks!

  • I thought I'd check before assuming it was a bug report—

    In the Animation Editor, when the Rotate Image buttons are pressed, the image points rotate with the image.

    But when the Flip horizontal/vertical buttons are pressed, the image points stay where they are.

  • Haha that 'feeling dumb' is the best! I'm a card-carrying member of that club... I tell myself it means we're learning :)

    The playground experiments are a good habit! It's a good way to get a handle on a behaviour, and really helpful if you do in fact catch a bug and need to report it.

    I'm looking forward to your project - keep at it!

  • Hey there!

    So are you saying that in your project, re-enabling the object's Platform behaviour also restores its previous vector x/y?

    With these kinda things, it can be helpful to make a project from scratch, with just the minimum objects you need to isolate your problem. A single sprite with Platform behaviour, a key to enable/disable that behaviour, and a text object displaying its Platform vector x/y should show you the answer.

    Or, if you're asking if that's a bug, the same minimal project will help folks here assess that.

    In either case, these quick focused tests are great exercises to find out whether its the behaviour's intention or something else in your code that's causing the output.

    Hope that helps!

  • Amazing, thank you! I really appreciate it—I'll try it out tonight! Thanks!

  • A few years back, R0J0hound, you saved the day with some code that launched a 2D baseball into 3D space.

    Would you (or anyone else) know if it's possible to use this code to drop a ball onto its shadow from above?

    Specifically, I'm reusing this code for characters in a Beat 'em Up. It works great for jumping and knockback, but when they respawn, I'd like to start the sprite 100px above the shadow, and have them drop straight down to the floor.

    Is it possible to change the variables in this formula? Or is it something different entirely (i.e. should I just use MoveTo)

    Thank you again and as always!

  • Thanks for the feedback, and I'll create a new suggestion.

    In this case, though, the Admin Response didn't really address the suggestion. (It's the one about rounded collision co-ordinates). The example use case (pasting floating-point collision points) isn't solved by the Admin's response. And there's another issue raised with the their proposed solution, which I've put in the follow-up comment - but I imagine the discussion is over, as the "already exists" tag is the same as "case closed"?

    All to say I'm not sure how I'd clarify these points with the Admin, when the response is through a tag, rather than a comment. The bug tracker provides the opportunity for clarification and brief discussion, which I'd vote for here, as it's a far more efficient process than reposting suggestions until they're resolved.

    Food for thought anyway! Thanks again, I'll repost the suggestion and address the grid system.

brushfe's avatar

brushfe

Member since 21 Jul, 2013

Twitter
brushfe has 2 followers

Trophy Case

  • 11-Year Club
  • Forum Contributor Made 100 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
  • RTFM Read the fabulous manual
  • x10
    Quick Draw First 5 people to up-vote a new Construct 3 release
  • x3
    Lightning Draw First person to up-vote a new Construct 3 release
  • x2
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

21/44
How to earn trophies