Author Topic: Database Team Doors help?  (Read 2634 times)

Since the events in JVS were changed it is now incredibly painful to accept team members in a fort wars. Now I have to input a players ID in every door I restrict so my base is secure.

I was wondering if I could use a button and database so when a player clicks it, it sends their ID to all the doors databases at once and will they will be able to open the door. I am new to variables so sorry if its something simple and stupid. Just looking for a more efficient way to let team members use my base. A list of all the events needed would be awesome thanks!

I know that a new expression events mod is being made. (Variables)
It lets you evaluate, add onto strings, etc. It should be broad enough (once it's done) for this to be possible with enough mathematical thinking. There was some AddToDatabase event, but i think that was brick specific and my server encountered frequent crashes with it enabled.

ouch don't want any of that. Guess Ill do it the long way till that new event is out

slayer has events that are team based
so you could do onActivate(Team 1) > Self > Door >Open or whatever

You could have your button modify a variable on the client, like make your own up (ie "Asaiya") then on your doors just check for that variable and your ID. That variable will only work for those who push your button, if someone else decides to event using the same variable it wont work for them.

Are you using JVS or default doors?

JVS but remember the Content start / stop events no longer exist.

Um, no?

You just remove the legacy doors add-on, or just not enable it.

Or perhaps you have a broken version.  If you like, I can give you the updated one.

OR you can use the simple VCE system I suggested.

OR you can use the simple VCE system I suggested.
That would work, but if they betray you, you have to have them trigger an event to disable that item.

I suggest use with command events so you can at any moment say /ec "BL_ID" "terminate"

Or make it player-based instead of client-based, so if they die they need to hit the button again.