Thank you for replying, I eventually figured a slightly longer way to do it, but it works well enough.

Instead of having one event including the button family (e.g. On any "Button_Family" pressed, do XYZ), I created 18 events, 1 for each button, essentially getting rid of one dimension.

On Button pressed

For each "Sprite_Family" -> Set opacity to (Global variable counting total jobs for that time frame / the correct variable on the sprite, which I can now name in the event itself instead of trying to have the logic pick it for me

Absolutely not efficient, probably going to make people retch, but its for a personal project, not sharing it, not selling it, so thats good enough for me!

Thanks for you reply again dop2000, surely this will help someone else one day

Hi Braus !

How about this :

(system)Every second :

(system)Pick random "MyInstance" object => Set invisible.

How would that work for you ?

My bad then

Thank you !

hi yolkgames ,

Your images are quite difficult to read, since your event sheet is full of variables names and other stuff we can't figure out until we know what they are.

Here is my take on it :

I think I understand your "box" object has 2 frames : One frame when it's closed, and 1 frame when it's opened.

Dragging the key will make it disappear and open the box, making the frame number change.

On your event sheet, event number 30, you tell your game to set your box frame to 1, then make its animation play, and then make it stop immediately after. That looks weird to me. If you want it to play, let it play, but if you do not want it to play, then make it stop straight away ?

Also, if you are having trouble with having animation frames, you could isolate each frame in a separate animation, and simply change the animations (containing a single frame only) when you need them. This would suppress the problem you could have with animation stopping/playing, which could be your problem since you are saying your box is "opened and then closed".

Hope this helps.

Hi Unconnected ,

further responding to duditon 's answer, you could also try and set your containers elements origin points to position your containers elements on spawn.

For example, if you have object A and B in a container, and you want object B to be 100 pixels south of object A, then simply put object B's origin point 100 pixels above its center, and the object will spawn 100 pixels south of where it "should" have spawned.

This can help you a lot positioning everything in one go, without having to have any events positioning stuff for you, and also retains every object's position, even on object destruction. The problem is that it's tedious to set up properly if you have lots of objects in your container.

________________

Another solution could be the one I use in my game in progress, which have about half a dozen menus stacked on top of each other : Put every menu in it's own layer (1 layer per menu), set them up how you want them to be set up, and make them appear/disappear by making the layer appear/disappear.

The only problem with this is that every clickable object will still be clickable , even when invisible. You will only need to make these objects unclickable by using a boolean , off when the layer is invisible, and on when the layer is visible. Pretty simple stuff.

Hope this helped !

Hi sebrosen ,

I'm not very familiar to particle objects, but this really looks like a particle object with some properties edited to it to make it bouncy.

I've tried to make the same, and I was able to recreate everything done in your video, apart from the bounce, only using the particle properties, and 0 events, apart from the event that creates the particle effect on mouse click.

Maybe the bounce is just an advanced part of it, but this should help you a lot already !

Small bump, I updated my last post with an image, should be useful I hope.

I don't get where the "function" usefulness comes from ? Instead of using a function trigger to start your event, just use the "on object created" trigger, what do you think ?

In order to have a function triggered event to run, you need to have something trigger this function in the first place. I'm almost certain you know that and probably have another event somewhere that calls your "SpawnDot" function, but it seems over complicated to me, as seen.

Also, in order for your object to move, you need to have another event that goes like this :

Dot => on path found => move along path

at the moment, your object calculates the path to point A to point B, but is not told to move along it properly.

Hi kellehk ,

This is probably over simplified, but what about the pathfinding behavior ?

On Dot spawned, make it pathfind to wherever you need to (even if thats a random cell, as you do have "cell" objects)

On path found, move along path

and that's it ?

Hi OP,

As dop2000 said, every single clickable in your game is actually enabled at all times. I am doing a game with multiples menus stacked on top of each other on something like half a dozen layers, and when I discovered I was clicking on half of them at the same time on one click, I wasn't really happy.

I used groups activation/deactivation to manage this problem efficiently with a minimum of events. All you have to do is program your buttons on your layer, put all these events in a group, and ass a single event saying "is layer X visible" => activate "group", and of course, its opposite, "is layer X invisible" => deactivate "group".

Really easy !

Enjoy your game !

Hi Semoreh,

I was just passing by, reading your post and I thought of a potential solution :

How about adding a global variable that stores inputs and triggers what your button should be triggering by using an event ?

For example :

on "A" (any button) pressed => store "whatever "A" should do" in your general variable

compare general variable value : if "value" = "A" => trigger action X

Or maybe even better, you could associate every button on your pad with a boolean variable that triggers when the button is pressed, and associate your events with the booleans and not with the actual buttons ?

Not sure that would work in practice, but what do you think about that ?

Edit : You could even use events like "on variable A and variable B boolean = true" to trigger events while 2 or more specific buttons are pressed (simultaneously, how you want it to be)