Not sure what you're doing here :D but I will say every tick is probably not a great idea for the timer because it will alter the number of miliseconds on different framerates so some players will be faster or slower than others that are actually taking the same amount of time, look into dt and framerate independence in the manual.
> I think for detailed games it's better to use an array, you store data in there. You can then present it whenever you want, when you open the inventory you create the items. U mean to destroy the items when inventory close and re-create all items when inventory open?? Is that better?? ^_^
> I think for detailed games it's better to use an array, you store data in there. You can then present it whenever you want, when you open the inventory you create the items.
U mean to destroy the items when inventory close and re-create all items when inventory open?? Is that better?? ^_^
Yep
I think for detailed games it's better to use an array, you store data in there. You can then present it whenever you want, when you open the inventory you create the items.
Yes there is a behaviour called Move To built in to C3
It works alright but it is tedious, and I would like to have has better control over the selection so I could adjust the selection during a fx. 'For Each" runtime. Would make a 'drunken man' map generation much more interesting I believe.
Sorry I don't know what any of that means :D
Seems fine? As long as it's a reusable function and you don't keep pasting those actions everywhere.
Right click - apply to whole animation
Family > pick by UID, then you can pull data from that instance
Develop games in your browser. Powerful, performant & highly capable.
Probably an issue with that photon event you are using, I don't know about that.
Depends what you want to do. You can select family > is dragging condition, that will be the one currently being dragged.
Touch x,y is where the cursor touches the screen, the x,y of tiles is its position on screen, they won't be the same unless you touched exactly at the x,y position of the tile when you started the drag/drop which is unlikely.
Ok so the touched objects x,y co-ordinates are unlikely to be the touch x,y. You can check for these values yourself and decide.
You've trapped yourself by having a game where any click does something but also clicking a pause button counts as any click. You can get around this by having conditions like 'on any click and cursor is not over pause button' but I see your point.
I don't really know photon but the picking seems fine, maybe it's just not true for any instance. You can debug it by doing simpler actions and checking in the debug preview to see if the variables are matching with the position of the object.
Also the outcome is kind of thin because I'm not sure how you can get into too much trouble if an 'on any click' triggers in the same tick but earlier than 'on clicked on an object'.