oosyrag's Forum Posts

  • Your peer version's event should be using Multiplayer.MyID

  • My approach would be to push the results into an array, only if that category doesn't already exist in the array (you can check by using array.indexof(category). If it does exist then add one to that index instead.

    Alternatively, you can check if only the last entry was the same, by comparing either the front or back of the array (whichever one you push to), to your current input. If it is the same, increment, and if it is different, push a new cell.

  • At a glance, it looks like LTI is handled by https on the application layer. You should be able to do everything you need with the iframe object, or alternatively with the url actions in the browser object.

  • What's Never Allowed?

    ✗

    Pornographic/overly sexualised games

    ✗

    Racist, sexist, homophobic or any other abusive content

    ✗

    Politically motivated games

    ✗

    Any assets or content you do not own the full distribution rights to

  • Use an instance variable(s) to keep track of the pinned object, and check it on start of layout.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You can also use the PickedCount expression if you want more control over what happens when there are x objects overlapping.

  • After selecting the object, some options include shift+arrow keys to move them faster, or just type in the coordinates in the properties.

  • I misread, I meant it in terms of you shouldn't need a loop to check overlaps, but you need it to generate your objects so I edited it out.

  • To check instances of the same object overlapping, put it in a family and check "is family overlapping object".

  • I'd say yes. Even Mode7... I vaguely recall R0J0 having a working example somewhere.

    But I mean, even the oldest published games on those systems were not exactly "indie" efforts... so just because it CAN probably remake any game from the 8 bit era it doesn't mean it would be easy to.

  • Sorry I don't know the answer to the question, but maybe I can phrase it more clearly.

    In the event of a delayed IAP approval or denial for a consumable product that the store does not keep track of, what happens if the game is closed before triggering on purchase success/failed?

    I assume the purchase would simply be lost. Although I was under the impression that credit card processing happens entirely in the store overlay, with success or failure determined before even returning to your game. I imagine play store would have it's own timeout protections, but I don't have any experience with that.

    But that's what those tests are for, so you can try it and see what happens to decide how you want to handle it.

  • Hmm I'm not sure about the memory loading.

    I do know all sprite objects used to be required to be on a layout previously, and that was no longer the case with c3 at some point.

    Putting the sprites on an unused layout was a way to get around it, without deleting everything at start of layout. They didn't need to be global.

    Someone more familiar with this than I can probably give a more definitive answer.

  • Put them on an unused layout, set your default parameters there. Same effect as destroying them on start of layout.

    As far as performance goes, I believe all sprites used in a given layout are loaded into memory before the layout starts, regardless if there is actually an instance of it there to begin with.

  • > If the object's origin is in the top right, set it's position to x=ViewportRight("0"), y=ViewportTop("0")

    That's the theory. But in my case the ViewportRight(0) is 1080 in a viewport of 1000 width. This can not be...

    Also th layer has parallax x = 0% and y = 0%. So, what I'm doing wrong?

    ~edit:

    Sorry, that's my fault. Now I'm using ViewportRight(0), not ViewportRight("Layer") and it seems it works. I will make a few more tests. ;)

    It is correct, because your viewport can change at runtime because of your fullscreen mode. Due to different aspect ratios, the viewable area on each device can be different.