Author Topic: Event System: Ideas and Suggestions!  (Read 1172 times)

There's plenty of stuff that can be done with the event system, but surprisingly, it could be made capable of much more than it already is. This is a thread for everyone to post ideas and requests for modding events. Let's get things started:

Event Limitation: This is a must. Basically, a seperate GUI that Super Admins can use to toggle what events players can and cannot use, or put a limit on the options of certain outputs (ie make it so they can't spawn a bajillion gravity missiles in a fraction of a second). Very, very useful.

Inputs:

- Specific Projectile Hit: Activates event based on a projectile specified from a drop box hitting the brick. Example: Shooting a log with a gun will do nothing, but shooting it with a flamethrower causes it to toggle an event that makes the log burn.

- Marked Player Touch/Activate: Activates event based on specifically marked players. See "Mark Player" output below.

Targets:

- Specific Player: Affects any player on the server chosen from a drop box. Admin only for obvious reasons. (Voodoo, anyone?)

- Marked Player: Affects players with a specific mark. See "Mark Player" output below. Admin Only.

Outputs:

- (un)Cloak Player: Makes player invisible or makes invisible players re-appear.

- Teleport Player: Obvious. Teleports player to specified brick.

- Mark Player: Puts a mark on the player, specified by a text input. Example: A jail spawn puts the mark "PRISONER" on players who touch it. If the marked players attempt to escape and step on a certain brick, an event could be toggled to set off an alarm, but if a non-marked player steps on it, nothing happens.

I'll think of some more later. If you have any ideas, don't hesitate to post them!

These are all great. We really need a teleporting output.


Event Limitation: yes
- Specific Projectile Hit: yes
- Marked Player Touch/Activate: yes
- Specific Player: yes
- Marked Player: yes
- (un)Cloak Player: no, abuse
- Teleport Player: done already
- Mark Player: yes

I could make an output that checks if the player is marked, and if they are, it enables events on the brick, and if they aren't it disables them.

But I cant make the specific inputs.



If that would be sufficient enough I can work on it immediately.


these are for when tdm (or rtb2) gets released:

input:
(team) is in area
(team member) has activated

just a brick capture system (NOTE: this only lets certain teams use features of a brick. this dosent transfer build rights)

input

(team) owns this brick
(team) has captured this brick

output

let (team) capture this brick
lock team owner of this brick
unlock team owner of this brick

- Marked Player Touch/Activate: Activates event based on specifically marked players. See "Mark Player" output below.

I did something like that, there was an output event with a textbox, in which you put a list of IDs.  If the player who triggered the input was on the list, it would send a relay to the brick (thus, you could do ID-only doors, by doing onRelay disappear).

The "mark" system could also come with a small GUI that admins can use to manually assign marks.

Dont hurt me here, but i would like to see some IF and THEN gates, er, events.

Could come in handy. Maybe a toggle system thats a tad more clear. But eh.

Ok, i'll be working on Cloaking and Marking.
Nah, wont do cloaking.
« Last Edit: August 13, 2008, 06:34:51 PM by Amiret »

Ok, i'll be working on Cloaking and Marking.

You should probably wait until someone makes Event Limitation. Both of those could cause nasty things in the hands of non-admins.

Well, i can't even seem to see how to make an event admin-only anyways.

I think a camera event would be kool. like you step or click a brick and you see what the other one sees

We need an event that lets you check what prints on a print brick.
Would come in handy for keypad doors, different functions for different prints, etc.

EDIT: Prefferably an input "onprintnumber" then a small box to select the number?