Describe the bug
When you run the command, the server stops, but does not crash.
To reproduce
command /zulfbungeetest:
trigger:
broadcast "&aPrinting all players on the bungeecord network..."
broadcast "&b%all bungeecord players%"
broadcast "&aPrinting the name of this client:"
broadcast this server's name
broadcast "&aSending all players on the network a message through iteration..."
loop all of the bungeecord players:
proxy message loop-proxyplayer the message "&b&oWhy hello there! I am a message!"
broadcast "&aPrinting all the servers connected to the proxy..."
set {_servers::*} to all of the online servers
broadcast "&b%{_servers::*}%"
broadcast "&aSending all servers a message (this is used for inter-server communication)..."
loop {_servers::*}:
proxy message loop-value the message "Sample Text" called "Sample Title"
broadcast "&aSetting a network variable..."
set network variable {zulfbungee::test::*} to 1, 2, 3, 4 and 5
broadcast "&a...adding to it..."
add 6 to network variable {zulfbungee::test::*}
broadcast "&a...and printing it! Expected values should be 1 through 6."
broadcast "%network variable {zulfbungee::test::*}%"
broadcast "&aDeleting that variable... :("
delete network variable {zulfbungee::test::*}
broadcast "&c&lCongrats! The test is done! Please send results back!"
Expected behavior
The variable appears as and `Congrats! The test is done! ‘Please send results back!’ appears and the server stops.
Screenshots
No screenshot but error in the message
# - Key Setup -
# This chooses what communication method ZulfBungee uses.
# pluginmessage requires no setup, but requires you to enter a connection name (see below).
# socket requires more setup but allows for more flexible setups.
# Generally, if you don't know what this means, leave it as pluginmessage.
transport-type: "pluginmessage"
# This will toggle the display of detailed messages about what is going to the console.
# When filing a bug report / checking for issues, this is extremely useful to know what exactly went wrong!
debug: false
# Enables or disables global scripts.
global-scripts: true
# - Socket Setup -
# This is the port that this server will bind to, which will it listen for incoming connections on.
port: 8000
# The IP that this server will bind to. Similar to the "client-host" in the Spigot config.
# This should usually be left as 0.0.0.0, or 127.0.0.1, but feel free to change this if you need to -
# (i.e. you are on shared hosting / Pterodactyl)
host: "0.0.0.0"
# - Storage -
# What kind of database should be used to store network variables.
# Currently, supported databases: MySQL, H2
# If you have no clue what this does, just leave this as the default.
storage-type: "MySQL"
# Skript by default is case-insensitive for variable names.
# If you want this functionality, enable it here.
case-insensitive-variables: false
# Each option should be self-explanatory if you know what you are doing.
# If you are using H2, this will not apply - these two settings only apply to remote databases like MySQL.
storage-host: "localhost"
storage-port: 3306
# !! Change these from the default to improve security !!
storage-username: "***"
storage-password: "***"
storage-database: "***"
# - MySQL Setup -
mysql-use-ssl: false
mysql-verify-certificate: true
Error Log
This log appears when you turn off the server.
[04:31:34] [Server thread/ERROR]: Nag author(s): '[zulfen]' of 'ZulfBungee v0.9.9-pre4' about the following: This plugin is not properly shutting down its async tasks when it is being shut down. This task may throw errors during the final shutdown logs and might not complete before process dies.
[04:31:34] [Server thread/ERROR]: Craft Scheduler Thread - 34 - ZulfBungee Stacktrace
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/jdk.internal.misc.Unsafe.park(Native Method)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.LinkedTransferQueue$Node.block(LinkedTransferQueue.java:470)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.awaitMatch(LinkedTransferQueue.java:669)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.xfer(LinkedTransferQueue.java:616)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.LinkedTransferQueue.transfer(LinkedTransferQueue.java:1256)
[04:31:34] [Server thread/ERROR]: ZulfBungee.jar//com.zulfen.zulfbungee.universal.util.BlockingPacketQueue.offer(BlockingPacketQueue.java:16)
[04:31:34] [Server thread/ERROR]: ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection.sendDirect(ClientConnection.java:113)
[04:31:34] [Server thread/ERROR]: ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection.handshakeTask(ClientConnection.java:63)
[04:31:34] [Server thread/ERROR]: ZulfBungee.jar//com.zulfen.zulfbungee.spigot.socket.ClientConnection$$Lambda$12211/0x00000008031906a8.run(Unknown Source)
[04:31:34] [Server thread/ERROR]: org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftTask.run(CraftTask.java:101)
[04:31:34] [Server thread/ERROR]: org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57)
[04:31:34] [Server thread/ERROR]: com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[04:31:34] [Server thread/ERROR]: java.base@17.0.1/java.lang.Thread.run(Thread.java:833)
more
As a result, both h2 and mysql show the same symptoms and work well in Release v0.9.8 version.
Zulfen
commented
1 year ago
Describe the bug When you run the command, the server stops, but does not crash.
To reproduce
Expected behavior The variable appears as and `Congrats! The test is done! ‘Please send results back!’ appears and the server stops.
Screenshots No screenshot but error in the message
Spigot server information (in this order)
Proxy information (in this order)
Additional context
Error Log This log appears when you turn off the server.
more As a result, both h2 and mysql show the same symptoms and work well in Release v0.9.8 version.