Author Topic: Event: OnMinigameReset (Read 786 times)

Scorpion1855 · February 28, 2009, 02:59:30 PM

Basically an event that would have Named Brick and Minigame as targets, for resetting objective-based zombie games that have respawning off, and other challenges.

Ad Bot · Advertisement

Chrono · February 28, 2009, 03:01:45 PM

However, minigames can't have input events. :(
Also you cannot get rid of named brick targets.

Space Guy · February 28, 2009, 05:14:14 PM

This could cause lag if it ends up triggering for every brick in the server or something like that.

It'd be cool if we could directly create events for Minigame objects themselves - have an extra GUI and have things like onClientScore, onMinigameReset, etc.

Chrono · February 28, 2009, 05:17:34 PM

That would be a great idea. I was planning on making AiPlayer events aswell, just not anytime soon.

Edit:
Instead of onClientScore, how about onClientScoreUp and onClientScoreDown?

Space Guy · February 28, 2009, 05:18:58 PM

AIPlayer events?

AIPlayers currently use the Player events. Since the Target for the onBotTouch events type is "Player" (for the Bot), your events wouldn't show up there. That would be useless.

Chrono · February 28, 2009, 05:20:14 PM

No, I mean like input events you put on a bot, not a brick.
Like onRespawn, onSightPlayer, onDamage and more.

Space Guy · February 28, 2009, 05:21:47 PM

Ah, I see. It might need changes to the Events GUI to get it to work, though. (for both the minigame one and AIPlayer one)

Chrono · February 28, 2009, 05:23:08 PM

Yeah I heard someone talking about something similar. They said all the brick inputs were mixed with the other object inputs.
This was quite awhile ago, and I have bad memory. So I'm not sure.

Chrono · March 01, 2009, 11:46:23 PM

Update on events research:

Although it is possible to register input events for different classes on both the server, and the client, the event gui cannot change object classes it assigns and reads inputs for. It seems to only use the fxDtsBrick class, and is unchangable from as far as I can see. I checked $ vars, dynamic fields on the events gui, and tried messing around with clientCmds, and nothing worked so far.