lionz's Forum Posts

  • The way I do it is to give the 2 objects instance variables, like an ID, and then they are the same number so they relate to each other. Will that work?

  • Again you can say if a symbol is overlapping it then it is true. You can do this by other methods though, on touching the object you can set an instance variable to true to note that you touched it and created a symbol.

  • Time to revert back to the basic events you had then :) no need for function. I think also if you are calling the function every tick then there isn't a need for it.

  • This is all about picking and relating the symbol to the object. In simplest way you can say 'on touch object' pick symbol that is overlapping object, destroy it. And for the second part, pick in the same way and change it. There are other ways to relate symbol to object but this is a basic way.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Did you use spawn or create? I think if you use spawn sprite 2 from sprite 1 then it should pick correctly and relate the sprite 2 to the sprite 1. So you say for each sprite 1, spawn sprite 2 at image point 1 should work for each, try that.

  • I know this but you didn't change anything? The guy above mentioned how to fix it. This appears to be the same screenshot from the first post so what did you try?

  • I am correct guys! luckyrawatlucky what's the problem? share a screenshot of the new events and where the issue is, thanks

  • not curx. if you are going to use slot IDs then you need to relate the slot ID to array X. so slot ID 1 is 1 in the array also. Then when you select the slot object which is ID 1, you take the slot_Id and then compare array x where array.x = slot.ID, then delete the contents. You should also get rid of item ID that's not needed. Think of the inventory more as the array and not the visual side.

  • You should be making use of slot_ID to relate to the array X. This makes things easier. When you select the item you look at the slot_ID and delete the item from the array X that is the same.

  • When you use actions the object instance to apply the actions to is already picked by the conditions, when you use functions the actions inside don't automatically pick the instance of the object from the previous conditions.

  • Nice! I like this game, glad it's on Steam now.

  • Not sure I understand, your old logic was fine I just said replace that line

  • You do not have permission to view this post

  • > It's create object array.at("random_chibi"). remember "random_chibi" is just a number.

    yeah a number linked to link it with the array since the frames of my sprite are 10 from 0 to 9 so array value = 0 is set to a frame as i mention above.

    sadly its not creating a sprite T_T

    Did you replace the logic as I mentioned?

  • It's create object array.at("random_chibi"). remember "random_chibi" is just a number.