Kyatric's Forum Posts

  • Attach your capx to your post, it will make it easier for us to investigate the current issue with exactly how you've set up your project so far.

  • ayumten: [quote:3qb9sfik]please email from your registered email address + include your username along with your full postal address

  • Please post in English or at least provide a translation with your message.

  • As mentioned, if your game is not made with Construct 2 you're not in the correct website at all.

    Also, "The last guardian" is a PS3/4 title that has been awaited for years now, and this name is copyrighted/reserved by Sony.

    Moreover looking at "The last guardians" on google seems to refer a WOW server in the first search results.

    So will your game be successful ? I doubt it. And if it is, you're facing possible copyright infringement lawsuit.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Well post the current capx you're working with, it will make it easier to edit and add what you want.

  • I think this should answer your question 2.

    I've made modifications mostly in the level layout (that I renamed so that it makes more sense).

    See the attached capx made in r179 (link to r179 at the bottom of the page).

    I hope this helps, otherwise try to explain what you are after in a more detailed way.

  • Use a modulo when "going up".

    Use a check when "going down".

    See the attached capx made in r179, link at the bottom of the page.

  • Also be aware that some of the fullscreen project properties will force an "aspect ration" on your screen, and it will change whether you are previewing it as fullscreen in browser (with or without the url bar/interface for example, in other words when pressing f11 or not).

    Moreover you can make sure to really execute at fullscreen using the "Request fullscreen" action from the Browser object.

    In the end a capx can help, consider attaching one to one of your posts.

  • As ramones said, there doesn't seem to be issue with your control scheme.

    On the other hand though, the "player" will block when reaching the limit of your layout (as it is bound to layout). As you "Scale outer" your project, on a 1920 wide screen it gives the impression that the player won't move into the last right 1/4 of the screen. It's because it's actually out of the "Playzone".

    Is that actually your issue ?

    You can experience it better by delimiting your playzone with a sprite. See the attached capx (made in r179, link at the bottom of the page)

  • cranberrygame: Modified.

  • First, you did not post in the correct forum, so I moved your thread. You'll have better luck getting help in the technical help forum.

    Second, you do not provide a capx. By the look of the two screenshots of the same event sheet, the events should do what you seem to want.

    Third, youtube...

    Use a single event sheet, and in event 3 instead of naming "Go to Level 2" use a global variable to keep the actual level number and use it with the action "System: Go to layout (by name)".

    System: Add 1 to myLevelVariable

    System: Go to layout "Layout " & myLevelVariable

  • JJEvil : [quote:2rxjz4oa]Send an email to with your transaction ID and username and we can issue your badges.

  • MrRuho: Yes, check the manual, there is an official plugin, no need for third-part.

  • So as I mentioned, it possibly would have been a better idea to post your capx (either attach it to your first post or post the public link) since that's what LittleStain was needing to keep helping you.

    I don't know if the layout's size has something to see with the performances, I believe it's more related to the number of colliding physics objects and I don't see what exactly you're trying to have "infinite".

    If you took the time to explain clearly what is your intention, what you experiment and make your capx public, a lot more people could participate in the discussion and possibly help you out.