Author Topic: onMinigame Events  (Read 1373 times)

I think these would be very helpful with eventing minigames. It would include:

onMinigameStart
onMinigameEnd
onMinigameReset

Mainly, I just want "onMinigameStart".

I think these would be very helpful with eventing minigames. It would include:

onMinigameStart
onMinigameEnd
onMinigameReset

Mainly, I just want "onMinigameStart".

Those are not brick events.  Seriously people, events are for stuff that happens to bricks.

It would be used with bricks. I'm working on a project with zomibes that are behind a wall. This is what I want it to look like:

[5000]     [onMinigameStart]-[ZombieDoor]-[fireRelay]
[10000]   [onRelay]-[ZombieDoor]-[fireRelay]
  •            [onRelay]-ZombieDoor]-[Disappear]-[10]


Something like that. That way, I have constant waves of zombies.

It would be used with bricks. I'm working on a project with zomibes that are behind a wall. This is what I want it to look like:

[5000]     [onMinigameStart]-[ZombieDoor]-[fireRelay]
[10000]   [onRelay]-[ZombieDoor]-[fireRelay]
  •            [onRelay]-ZombieDoor]-[Disappear]-[10]


Something like that. That way, I have constant waves of zombies.

No.  onMinigameStart does not happen to a brick.  That's a bullstuff event.

No.  onMinigameStart does not happen to a brick.  That's a bullstuff event.

forget off. Just because you don't want it doesn't mean everyone doesn't want it. If you think you can make event's start at the start of a minigame, be my guest and tell me how to do it without the old [onActivate] or [onPlayerTouch].

Bad idea.

Too bad we don't use majority rule.

forget off. Just because you don't want it doesn't mean everyone doesn't want it. If you think you can make event's start at the start of a minigame, be my guest and tell me how to do it without the old [onActivate] or [onPlayerTouch].

You're still misunderstanding me.  I'm telling you that onMinigameStart is not a brick event, meaning someone should not make it for use with the brick events system.  It's not a valid event.  Events are only for things that happen to bricks.

Why not just use an old classic button?

You're still misunderstanding me.  I'm telling you that onMinigameStart is not a brick event, meaning someone should not make it for use with the brick events system.  It's not a valid event.  Events are only for things that happen to bricks.

Ok, I'm kinda understanding you now. Sorry for the unkind words. I guess I'll have to think of something else...

Events are only for things that happen to bricks.
Is that why there's "Client" and "Player" sections?
I'd classify events as anything that occurs with a brick, not to it.

I was starting to change my opinion. More details.

For whose minigame does it work?

We certainly don't want offline people to be scoring a lot of points whenever a minigame starts.

Is that why there's "Client" and "Player" sections?
I'd classify events as anything that occurs with a brick, not to it.

Don't argue semantics, idiot.  onMinigameStart is not something that happens with, to, from, inside, outside, on the surface of any brick.  I make a valid point and most of you are still managing to miss it.

Perhaps have an output event called IfMinigameResets? Could that possibly work?

Perhaps have an output event called IfMinigameResets? Could that possibly work?

No, wtf.  Why is this so hard to understand?  Events are not for things that happen with minigames.  Events are for things that happen with bricks.  onDoorOpen is valid because the Door is a type of brick and stuff is happening with it.  onMinigameWhatever, whenMinigameWhatever, ifMinigameWhatever are not valid events because they're about stuff happening with minigames, not bricks.  This is, quite simply, a stupid idea.

How about we get an OnMinigamePlayerTouch/Activate? So these events would only be activated by people in the minigame. What do yal think?