a property for every button option?
Put it all in a zone that doesn’t allow for people to drop stuff, and surround the zone with walls.
Bump. I recently came back to this problem to take another shot at it.
Some further intel.
So each team has their own button. When another team presses it, it becomes under their control, incrementing the counter. From there, the other three teams can once again attempt to claim it by pressing the button. When pressing it, their team’s counter goes up, and the team that it previously belonged to decrements.
EDIT: I just closed the game so the code is now obsolete.
1 Like
Wow, looks nice so far!
I think I have a way to do this. Place down your buttons, and place down properties equal to the number of teams in your game. Wire each button to a trigger. Go into each of the triggers blocks, and make them check for the triggering players team number, then make it update a property by 1 for whichever team pressed the button, then make it check if one property is equal to the number of buttons and all of the others equal 0.
1 Like
is this still unresolved? i thought my solution was pretty good.
It’s been almost 7 months. It’s probably not going to get marked.
4 Likes
Please don’t necropost on old topics to mark a solution. It creates a lot of clutter and is honestly kind of annoying.
3 Likes
uhh you kinda just did
1 Like
9 days later is not really necroposting
It is better than 4 months later
1 Like
ok
No, I was explaining to a newer user why they should avoid that.
2 Likes
ok
Ok, so what is the problem here, are u trying to make it so that there are 4 buttons?
9 days later is more of a BUMPPP, while necroposting is like, 5 years later, or 4 mounths later
5 years? The forums aren’t one year old yet…
if you ask me it isn’t about time
I see necroposting as replying to something old that doesn’t need to be seen
1 Like