#(nybiksigma) after server list ping
49 messages · Page 1 of 1 (latest)
(nybiksigma) after server list ping
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.
Problem on screenshot
!paste
Help us help you by pasting your script to https://paste.denizenscript.com/New/Script and linking it back here.
Content of Denizen Script Paste #123558: Motd_handler... pasted 2024/06/08 06:26:38 UTC-07:00, Paste length: 157 characters across 5 lines, Content: motd_handler: type: world
nothing
!l script event after vs on
Modern ScriptEvents let you choose between "on" and "after".
An "on" event looks like "on player breaks block:" while an "after" event looks like "after player breaks block:".
An "on" event fires *before* the event actually happens in the world. This means some relevant data won't be updated
(for example, "<context.location.material>" would still show the block type that is going to be broken)
and the result of the event can be changed (eg the event can be cancelled to stop it from actually going through).
An "after" event, as the name implies, fires *after* the event actually happens. This means data will be already updated to the new state
(so "<context.location.material>" would now show air) but could potentially contain an arbitrary new state from unrelated changes
(for example "<con...
Script Events
might be just it ?
what's surprising is the partial result
i.e. actually getting VERSION: :star: on the server list
I replace after with on, but now:
Server
server list ping
when the server is pinged for a client's server list.
<context.motd> returns the MOTD that will show.
<context.max_players> returns the number of max players that will show.
<context.num_players> returns the number of online players that will show.
<context.address> returns the IP address requesting the list.
<context.hostname> returns an ElementTag of the server address that is being pinged. Available only on MC 1.19+.
<context.protocol_version> returns the protocol ID of the server's version (only on Paper).
<context.version_name> returns the name of the server's version (only on Paper).
<context.client_protocol_version> returns the client's protocol version ID (only on Paper).
"MAX_PLAYERS:<ElementTag(Number)>" to change the max player amount that will show.
"ICON:<ElementTag>" of a file path to an icon image, to change the icon that will display.
"PROTOCOL_VERSION:<ElementTag(Number)>" to change the protocol ID number of the server's version (only on Paper).
"VERSION_NAME:<ElementTag>" to change the server's version name (only on Paper).
"EXCLUDE_PLAYERS:<ListTag(PlayerTag)>" to exclude a set of players from showing in the player count or preview of online players (only on Paper).
"ALTERNATE_PLAYER_TEXT:<ListTag>" to set custom text for the player list section of the server status (only on Paper). (Requires "Allow restricted actions" in Denizen/config.yml). Usage of this to present lines that look like player names (but aren't) is forbidden.
"MOTD:<ElementTag>" to change the MOTD that will show.
"VERSION_NAME:<ElementTag>" to change the server's version name (only on Paper).
Other work?
oh
i have purpur
Purpur is a fork of Paper, it's not officially supported and we'd usually recommend Paper, but it should work fine
but it not
Did you try with the proper name?
You had VERSION, it's VERSION_NAME ^
Its work! But now...
Please paste your new/updated script
Content of Denizen Script Paste #123560: Motd_handler_new... pasted 2024/06/08 06:50:06 UTC-07:00, Paste length: 162 characters across 5 lines, Content: motd_handler: type: world
oh
i forgot
replace after
Content of Denizen Script Paste #123561: Edit of paste 123560: Motd_handler_new... pasted 2024/06/08 06:50:48 UTC-07:00, Paste length: 159 characters across 5 lines, Content: motd_handler: type: world
here
same problem
but VERSION_NAME works!
If you need help with a script issue, one of the most powerful tools Denizen has to offer is full debug output. This is displaying in your console whenever scripts are running until you turn debug off. To share a debug log quickly and easily with helpers, simply run the command /denizen debug -r in-game to begin recording, then run through the part of the script you need help with, then run the command /denizen submit. This will give you a link to a paste of the debug log, which you can then copy/paste back to us!
try refreshing your server list while recording a debug
maybe there's another issue
1 sec
Content of Plain Text Paste #123565: Edit of paste 123564: Debug... pasted 2024/06/08 06:58:46 UTC-07:00, Paste length: 2204 characters across 20 lines, Content: 16:56:34 Running script event ServerListPing, event=on server list ping for script MOTD_HANDLER 16:5...
that's not a debug
that's a log snippet
/denizen debug -r then /denizen submit to get a debug
@green harness ban @velvet ermine 2y alting to go around dns ref: #1245077725903851654 message
@grave crow has temporarily banned @velvet ermine. Expires: <t:1780932139:R>.