#(Grocer) List all players on bungee network

1 messages · Page 1 of 1 (latest)

desert cargo
#

Is it possible to get a list of names of all players connected to bungee network?

tidal ferryBOT
#

(Grocer) List all players on bungee network

#

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.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

deft garden
#

maybe try look at
"bungee player joins network"
"bungee player leaves network"
or the "BungeeTag"

last kindleBOT
hushed dawnBOT
# boreal talon !command bungeetag
Required Plugins or Platforms

Depenizen, DepenizenBungee, BungeeCord

Group

Depenizen

Syntax

bungeetag [server:<server>] [<tags>]

Short Description

Parses tags on another server on a Bungee network and returns the results for this server to process.

Description

This command parses tags on another server on a Bungee network and returns the results for this server to process.

As a more technical explanation: All commands in Denizen parse tags in any input arguments prior to processing them further.
This command skips that step, and sends the raw tags out to the specified server to then have that server perform the actual tag processing,
when then gets sent back and allows the command to complete.

Tags will be parsed on the remote server, but definition...

boreal talon
#

optimally though, you should track when users join the network and when they leave and save a flag on the servers, then you don't have to bungeetag

#

like dingel mentioned;

#

!event bungee player join

hushed dawnBOT
# boreal talon !event bungee player join
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.

boreal talon
#

!event bungee player q

hushed dawnBOT
#
Possible Confusion

Did you mean to search for bungee player switches to server?

boreal talon
#

!e bungee

hushed dawnBOT
# boreal talon !e bungee
Cannot Specify Searched Event

Multiple possible events: bungee server connects, bungee server disconnects, bungee player joins network, bungee player leaves network, bungee player switches to server.

boreal talon
#

!e bungee player leaves

hushed dawnBOT
# boreal talon !e bungee player leaves
Required Plugins or Platforms

Depenizen, DepenizenBungee, BungeeCord

Group

Depenizen

Event Lines

bungee player leaves network

Triggers

when a player leaves the Bungee network.

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 leaving player's name.
<context.uuid> returns the leaving player's UUID.
<context.ip> returns the leaving player's IP address.

boreal talon
#

those two

desert cargo
#

I think I will use bungeetag as events may be unreliable in case of server being offline

#

It is just strange that there is no <bungee.list_players> or smth as it can be easily obtained via bungee plugin messaging channel

#

And no need to parse tag on all the servers

cinder gale
#

if bungee provided that information denizen would offer an api for it

#

it's going to be quite inefficient for you to constantly parse tags tho

#

you should be tracking server online/offline status if that's a real concern

desert cargo
prisma timber
#

Besides, that isn't much different then what was already suggested above - it's sending a network request for the player count

#

If you still need help with anything else feel free to ask, otherwise:

clear martenBOT
#
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.)

#

@desert cargo

desert cargo
#

Yeah, I forgot about online player requirement thing

#

Makes sense