#(ewolina) Bungeejoin leave with permission/spam check

1 messages · Page 1 of 1 (latest)

green void
#

hi, at the moment i'm working on this bungeejoin/leave thing, and i need littlebit help

https://paste.denizenscript.com/View/116895
found snippets from searching but how to handle the leave permission check, on some servers the user didnt get the group list
is the idea right on the join thing? i'm checking for online just on the server, and then i do the groupcheck, to annoucne it to the other servers...

elder portalBOT
#

(ewolina) Bungeejoin leave with permission/spam check

elder portalBOT
#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

radiant vortex
#

hello, this script will error when the player joins the server for the first time

#

!e bungee player joins network

sacred portalBOT
# radiant vortex !e bungee player joins network
Required Plugins or Platforms

Depenizen, DepenizenBungee, BungeeCord

Group

Depenizen

Event Lines

bungee player joins network

Triggers

when a player joins the Bungee network (but has not yet entered a server).

Has Player

when the player has been on this specific server before. - this adds switches flagged:<flag name> + permission:<node>, in addition to the <player> link.

Context

<context.name> returns the connecting player's name.
<context.uuid> returns the connecting player's UUID.
<context.ip> returns the connecting player's IP address.
<context.hostname> returns the virtual hostname that the player is connecting to.

radiant vortex
#

it should have check whether the player is truthy

green void
#

how you would do that?

radiant vortex
#

!t objecttag.exists

sacred portalBOT
# radiant vortex !t objecttag.exists

Returns true if the object exists (is non-null). Returns false if the object doesn't exist, is null, or the tag errored.
This functions as a fallback - meaning, if the tag up to this point errors, that error will be hidden.

Returns

ElementTag(Boolean)

radiant vortex
#

aand other thing iss, if youre announcing it to each server, couldnt you just announce it via bungee itself?

onyx heath
radiant vortex
#

oh one is with announce to_ops didnt notice that, ye

onyx heath
#
>         # block join for idiots
> - if <[player].groups.contains[permanentguest]> || <[player].groups.contains[gebannt]>:
>   - foreach <[servers]> as:server:
>     - bungee <[server]>:
>       - announce to_ops "<&7>[<&8>+<&7>] <[playername]>"
>   - stop
> ```
like drjoenh said, this would be invalid on the server this script is ran from if the player enters another server before this first one;
eg: take for example if:
- you have two "hubs"
- a player joins "hub 1" instead of "hub 2"
- script is saved on "hub 1" (you would not want this same script concept on every server without checking with the network first)
"hub 1" will work properly but "hub 2" will not because <player[<uuid>]> is only valid where the player has physically been seen first
#

but the actual question doesn't make sense

green void
#

so the joining of new players is not a problem, i just wait in the script for the player to be joined on the server

#

need to be improved for the leave thing, because i can't check for the group

#

maybe someone has improvement ideas

somber zodiac
#

I'm sorry, what's the actual issue?

#

Or thing you want to do?

green void
#

i filter the banned players on join, but on leave i get the [-] in chat, because there is no option to check for .group
or my brain is not ready to handle this xD

somber zodiac
#

and you don't want to send a leave message when the player gets banned?

#

and you cant check because the player does not exist yet?

green void
#

when the player is unknown for the server, or when the player didnt joined -
groups only get refreshed from luckperms when the player was online - but for banned players, they didnt come online to get that refresh so the quit message is harder to stop

green void
#

need help 😦

ashen pagoda
turbid prawn
#

Feel free to ask if you need any more help, otherwise -

cosmic obsidianBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@green void