newt's Forum Posts

    • Post link icon

    How about?

    Enterprise edition= 99 a year, full access, unlimited exports.

    Single project= pay per event, billed at the end of each month for additional events, exports cost extra.

    -If you decide to stop paying for extra events, it reverts to a free type version where you can only have the amount of events you have paid for.

    • Post link icon

    > Wed Feb 01, 2017 2:17 pm

    > Most people here who use & enjoy C2 are hobbyist, myself included. I will not pay a subscription fee for C3.

    >

    Your sentence holds a lot of truth. More so than what most supporters of the new subscription model appear to realize.

    I guess the question would be, what would they loose without the hobbyists?

    If the money was enough, then we wouldn't be having this conversation.

    What will they do without all the wonderful things the users do?

    Surely someone who likes to tinker with badges should know the answer to that.

  • Try a different frame, bigger texture.

  • Yes, like I said though it's not implicitly picked by the condition, the creation event is expected to pick just the new ones.

    That may not be all that's happening.

    Objects referenced in actions and that are not picked by conditions default to the first instance.

    It's possible that the first instance is also being picked.

    But that's probably just a byproduct of a bug with containers and arrays.

    Note to Ashley.

    It doesn't seem to affect dictionaries.

  • Don't forget you have a container that exists at the start of layout.

    That array is not implicitly picked by any condition, but neither are the ones just created.

    No idea where that 4th array is coming from.

  • Use something like to get the distance.

    Use some trig to place the dots at the distance divided by segment size.

    Aiming would just be the angle() between touch, and the emitter.

  • I would suggest just going to the hundreds, or thousands decimal place.

    mid(), left()

    Then int(), back to numbers.

  • On start of layout, text set text to uppercase(someone can explain me what is the difference between)

  • Set cursor from sprite

  • tokenat("text", index, separator)

    text="1,5,6"

    int(tokenat("text", 0, ",")&tokenat("text", 1, ",")&tokenat("text", 2, ","))

    • Post link icon

    Well you have to look at the math.

    Even with the decimation from the loss of "hobbyist" users they will still have a viable business even with a subscriber base of just a few thousand.

    Of course that means they will have to try to retain those users by offering a better product.

    It also means they can try to retain those users by locking them out of the ability to edit their own content if they were to unsubscribe.

    You should probably stop asking for for that. It's just not going to happen.

    No company would ever give up that kind of control.

    Sadly, more professional, feels a lot less friendly.

  • Alright, I guess I got it backwards.

    The x component for the first loop would be 0.

    That's not a row.

    Thanks to all that took a look.

  • I expect

    for x= 0 to 3

    ->for y= 0 to 3, create object at x component= loopindex(" x"), y component= loopindex("y")

    To give me:

    0,1,2,3

    4,5,6,7

    8,9,10,11

    12,13,14,15

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I've updated the capx to illustrate the difference with some text.

  • I just haddn't linked the sheet for the first save.

    Sorry, it should be correct now, otherwise just link 1 to 1, 2 to 2.

    Still sure something's changed with loops however.