Lou Bagel's Forum Posts

  • I wasn't aware of this and am also interested in hearing the answers to your questions, but if you need a simple work-around you can always multiple by -1 or take totalindex-loopindex to count backwards

  • Did the image origin move?

    I believe origins can't be between pixels (only at integer values) so wouldn't affect this

  • Thanks —

    but how do I implement that ?

    Sorry, I didn't look at your capx so not sure what you are doing exactly, but here's an example to explain what I mean and you can apply it to your situation.

    Let's say you want to create 10 sprites starting at coordinates 100, 100 and every 25px moving straight right (increasing X):

    ON whatever triggers

    -For startindex=0 endindex=9

    --create sprite at location x = 100 + 25*loopindex; y = 100

    This will create 10 sprites at x coordinates 100, 125, 150, 175, 200...

  • Ok,i got this but another problem appeared

    Can i compare a letter in textbox.text ?

    It would be the same just replace "ball" with the letter ("r")—not sure I understand what the problem is...

  • For Loop

    base + increment*loopindex

  • ...time corrodes them away...

    I'm pretty sure that depends on the quality of the CD. Yes, the CDs I burned in the 90s don't hold up anymore but the CDs I purchased in the 90s still play fine as long as they aren't scratched.

  • I'm planning on using AJAX events to upload data as the game is played. Not a full solution to beta testing but if you are just looking to test out/track a few aspects or have a really small game it could be useful. Might also put in some prompts at certain points so they can give feedback as they play.

    I haven't done this yet but am planning on trying it out once I get to the point of showing friends even small parts of games.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Are you familiar with arrays?

    They will work perfectly for this, you just have to learn how to manipulate them: https://www.scirra.com/tutorials/307/ar ... -beginners

  • I've used Groups to deal with such:

    Group "BlurIn" (disabled at start)

    -every tick/x seconds -> set blur effect to blur effect plus x

    -If blur effect > 100 disable Group "BlurIn"

    Then when you want it to blur just set the group to be enabled. Can make another group that does the opposite.

  • ...then you've basically reinvented letterbox integer scale mode.

    But without any black borders on unexpected resolutions, no?

    I'm trying to invent an 'integer scale outer' mode. Am I mistaken in my thinking here?

  • Every X seconds or on specific frames should work. You aren't putting them as a sub-event to the collision are you? Collision is a triggered event so only occurs once and won't be repeatedly checked.

    Hard to guess the problem without knowing your events.

  • Not sure what you are doing—I don't see a reason this shouldn't work. What are you doing?

  • When i slam screen of my laptop on that keyboard, hitting both of us to to sleep, then when both wake up in the morning, we are still logged in.

    Must be your cookies, sir.

    Like I said, in gmail and every other browser log-in I stay logged in...

  • Sorry, my comment didn't really make sense—my mind was wrapped up in something else. Though I'm curious to know what the 'is by wall' issues are...

    I understand how the offset works now—are the collision polygons, for both player and solid tiles, rectangular?

    If not, there could be a frame where the lower point of the player collision polygon clips the tile when moved to the right (and up) even though majority is still above the tile.

    Also, is the image the exact spot this happens? and will the player change directions mid-air? I was thinking if maybe on the jump they clip the corner of a 'new' ceiling, as in there is not ceiling above them but above and to the right there is, it could cause the change in direction. But unless it is programmed to not change directions until on the ground you would notice right away.

    ...those probably aren't the issues, but just trying to think out of the box as I don't see any issues in what you posted.

  • Wait X Seconds is a Condition.

    Do you mean 'Every X Seconds'? Not sure 'waiting' as a condition sounds logical...

    But yes, the same logic would apply