that does not work with branching, for example on master the last sprite id was 10. and from master you create a branch and add a sprite which now has an id of 11, but someone else also created a branch from master there last id is still pointing to 10. (becuase your new changes have not been merged yet) so when they create a new sprite, it now has sprite id 11 (same id across multiple branches). now when its time to merge the code, you will have a conflict because both sprites share he same id. making it random reduces the chance of that happening
before they used auto incrementing numbers, so what would happen is if you were using source control with multiple ppl, you would run into conflict because it would use the same id for different assets. making the id's random reduces the chances of collisions.
that is awesome, this pattern is great for code reuseability.
Agree, future looks very promising
this is a fun game, great work
This is great the API for saving and loading and the script theme changes are awesome thanks
can you reproduce that and send me a minimal c3p file? i can't seem to reproduce what you described.
Thanks for the clarification
How will this work for recurring subscribers so next year when the subscription expire and need to be renewed will it be renewed with the js feature at $99? Or will the price then be $99 + $20 for the year?
Can those streams be uploaded to YouTube for ppl who can't watch at that time. Can watch them later?
Have you thought about type script?
This is pretty awesome, I hope this brings in many new devs to Construct!
The function map feature is really great, thanks for including it.
Hey I will take a look at this this morning. Thanks
I implemented The Detection Of Cellular Automata Groups (works with any map), since this implementation is not part of the rot.js core, I am calling them islands, Let me know if this is what you were looking for? if you need any more actions or expressions? There should be an example project attached.
Member since 26 Apr, 2016