Look at what you have in the action already, X=1, Y=1. Change Y to loopindex, keep X as 1. Change the value field to array.at(0, loopindex) instead of array.at(0, loopindex-1). When I write set at xy (1, loopindex) I mean x is 1 and y is loopindex.
Ya but what about my example? Yours is set at xy (1,1) to array.at(0, loopindex-1). Instead use what I mentioned above set at xy (1, loopindex) to array.at(0, loopindex)
I understood the video, just sayin it could be your events (more likely) and not a bug with Construct. Solid is related to line of sight obstacles and we can't see every event.
It's just a for loop, and the action is using the array object set at XY
for array1.height - array2 set at X,Y (row, loopindex), value array1.at(row,loopindex)
Develop games in your browser. Powerful, performant & highly capable.
That should be a problem with your events, better to share the project. Also you posted this in the wrong place it's for issues with the website.
Do you mean in random position/direction or that you have a list of items to randomly choose from? There is choose() expression, maybe this will work. I'm imagining you mean something like a loot box but I could be wrong.
Seems to be as designed that if you load a game that involves transitioning to another layout, it runs through events after the game load. Some are skipped though like 'on start of layout' events. I wouldn't expect anything different because loading the game in a sense is going to or loading the layout unless you are already in it.
Yes that is how Construct works, you pick with conditions and apply actions to picked instances.
Yeah you add to the condition something to pick the target object. If it also has an instance variable for name then you can use this.
This sounds very overcomplicated, what do you mean by 'named instances' ?
You do not have permission to view this post
Member since 5 Aug, 2013