#(zenithsociu) Using flag data in the bungee network

24 messages · Page 1 of 1 (latest)

flat oyster
#

Hi, I just switched from Multiverse to Bungee. Before that, I had flag data of the Ruby coin, used in worlds and also dDiscordbot.

After migrating to Bungee, I thought to save the Ruby data to SQL but after reading the documentation from Denizen this doesn't seem right.

So I want to ask: how to make flag data circulate throughout the server connected to Bungee?
And in Depenizen's config there is mention of Bungee and Clientizen settings, what are those for?

dark perchBOT
#

(zenithsociu) Using flag data in the bungee network

dark perchBOT
#

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>

fossil phoenix
#

!command bungeetag

tall stagBOT
# fossil phoenix !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...

fossil phoenix
#

this command lets you grab a tag from another server

#

!command bungeerun

tall stagBOT
# fossil phoenix !command bungeerun
Required Plugins or Platforms

Depenizen, DepenizenBungee, BungeeCord

Group

Depenizen

Syntax

bungeerun [<server>|...] [<script name>] (def:<definition>|...)

Short Description

Runs a task script on another server.

Description

This command runs a task on another server on the Bungee network. Works similarly to the 'run' command.

fossil phoenix
#

this lets you run scripts on other servers, and you can pass definitions - this is also good for transfering your flags between servers

#

you can use SQL and access the data by reading it every time you need it, but it's typically not recommended unless you have a really good reason to use sql / are actively operating a large server that's experiencing problems with otherwise better options

flat oyster
bronze knot
#

DepenizenBungee on your proxy & Denizen + Depenizen on the server yeah

flat oyster
#
[04:45:30 INFO]: +> [BungeeClient...] Depenizen-Bungee connection ended. If this is unexpected, check your Bungee proxy server logs.

I get a log about every 5 second. What does this mean?
I check the bungee console, nothing happens.
I have enabled Bungee server address: true in config Depenizen

vernal elk
#

true isn't an ip address

#

you probably want 127.0.0.1

flat oyster
#

Ohhhh... Why did I set it to true :(( I must have read it wrong. Sorry

#

I get a connection failed message

05:12:11 [INFO] [DepenizenBungee] Depenizen handshake seen from: /127.0.0.1:53028
05:12:11 [INFO] [/127.0.0.1:53028] <-> InitialHandler has pinged
05:12:11 [INFO] [DepenizenBungee] Connection '/127.0.0.1:53028' now under control of Depenizen.
05:12:12 [INFO] [DepenizenBungee] Connection '/127.0.0.1:53028' failed: Invalid MyInfoPacket (unknown server, gave port '25565')
05:12:12 [INFO] [DepenizenBungee] Connection '/127.0.0.1:53028' ended.

Config Depenizen

# Use "none" to disable Bungee support functionality.
Bungee server address: 127.0.0.1
# Set to the bungee server's primary port (if in use).
Bungee server port: 25577

Port Bungee is 25577

- query_port: 25577
vernal elk
#

that's the query port not the server port

flat oyster
vernal elk
#

post your bungee config

honest questBOT
#
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.)

#

@flat oyster