#(thatkev) <player.glowing> incorrect?
1 messages · Page 1 of 1 (latest)
(thatkev) <player.glowing> incorrect?
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.
!debug
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!
just a sec
Content of Server Log Paste #126458: Denizen Debug Logs From PLANET SMP ᴅɪꜱᴄᴏʀᴅ.ɢɢ/ᴘʟᴀɴᴇᴛꜱᴍᴘ... pasted 2024/09/12 04:13:48 UTC-07:00, Paste length: 4383 characters across 49 lines, Content: Java Version: 21.0.3Up-time: 4h 24m
Content of Server Log Paste #126458: Denizen Debug Logs From PLANET SMP ᴅɪꜱᴄᴏʀᴅ.ɢɢ/ᴘʟᴀɴᴇᴛꜱᴍᴘ... pasted 2024/09/12 04:13:48 UTC-07:00, Paste length: 4383 characters across 49 lines, Content: Java Version: 21.0.3Up-time: 4h 24m
Paper version 1.21.1-76-e945cfe (MC: 1.21.1)
Citizens: 2.0.35-SNAPSHOT (build 3492) -- (:warning:Outdated build, behind by 66)
Denizen: 1.3.1-SNAPSHOT (build 7059-DEV) -- (:warning:Outdated build, behind by 8)
Depenizen: 2.1.1 (build 864) -- (Current build :white_check_mark:)
@lofty fable
0 (:triangular_flag_on_post: Hacked or Invalid ID)
21.0.3 :white_check_mark:
WorldGuard: 7.0.11-beta1+a801a9d, ProtocolLib: 5.3.0-SNAPSHOT-726, Quests: 5.1.3-b503
PlugManX: 2.3.7 - :warning: Plugin Managers are dangerous and will cause unpredictable issues. Remove it.
Geyser-Spigot: 2.4.2-SNAPSHOT - Bedrock clients are unsupportable. Please do all testing with a Java Edition client.
floodgate: 2.2.3-SNAPSHOT (b109-49bd564)
TAB: 4.1.6 - This plugin adds Below_Name scoreboards to NPCs.
Multiverse-Core: 4.3.12 - Multi-world configuration plugins may affect NPCs in unexpected ways.
GSit: 1.10.0 - 'Sit on other players' or 'sit on mobs' plugins sometimes allow players to sit on NPCs.
!t player.glowing
Returns whether this entity is glowing.
attributes
ElementTag(Boolean)
EntityTag.glowing
!c glow
entity
glow (<entity>|...) ({true}/false/toggle/reset) (for:<player>|...)
Sets whether an NPC or entity is glowing.
Sets whether the specified entities glow, defaults to the linked player/NPC if none were specified.
Optionally specify 'for:' with a list of players to fake the entities' glow state for these players.
When using 'toggle' with the 'for:' argument, the glow state will be toggled for each player separately.
If unspecified, will be set globally.
'for:' players remain tracked even when offline/reconnecting, but are forgotten after server restart.
When not using 'for:', the glow is global / on the r...
Is there any reason you are making yourself glowing only for yourself?
But you are aware that only they see them glow, not others?
What do you mean, sorry?
By using the for: arguments, only these players specified will see the entity glow.
Oh, so I don't specify the for:?
If you dont specify that, they will glow globally for anyone.
Ok
that fixed it
Now I'm trying to figure out the colours and I can't seem to get it working
The for: argument makes the entity glow only for specific players. That's why glowing returns false for the server. It makes use of network packets.
!m glow_color
Did you mean to search for command glow?
!m entity.glow_color
(Property) A display entity's glow color override, if any.
For the mechanism: provide no input to remove the override.
Properties
EntityTag
ColorTag
<EntityTag.glow_color> (Property) A display entity's glow color override, if any. For the mechanis...
Ah hold it's players isnt it
yeah
I got this
glow_command:
type: command
name: glow
debug: true
description: Makes you glow!
usage: /glow <<>world<>>
tab completions:
1: aqua|black|blue|dark_aqua|dark_blue|dark_gray|dark_green|dark_purple|dark_red|gold|gray|green|light_purple|red|white|yellow
script:
- define colour:<context.args.get[1].to_lowercase>
- if <list[aqua|black|blue|dark_aqua|dark_blue|dark_gray|dark_green|dark_purple|dark_red|gold|gray|green|light_purple|red|white|yellow].contains[<[colour]>]>:
- if <player.glowing>:
- glow <player> false
- narrate "<&7>You are no longer glowing!"
- else:
- team name:glow-<[colour]> add:<player> color:<[colour].to_uppercase>
- glow <player> true
- narrate "<&7>You are now glowing!"
- else:
- narrate "<&4>That colour is invalid. Try again."
I can't seem to get the team working
You need to add the player to the team
Adding a player to the team will also create it, if it does not exist yet
Do I have to do it separately
Yee
Holding
works fine for me
hmm, my client is keeping it white
Nope
try a server restart then
rightio
'for:' players remain tracked even when offline/reconnecting, but are forgotten after server restart.
Got it
Restarting rn
Still doesn't seem to work
glow_command:
type: command
name: glow
debug: true
description: Makes you glow!
usage: /glow <<>world<>>
tab completions:
1: aqua|black|blue|dark_aqua|dark_blue|dark_gray|dark_green|dark_purple|dark_red|gold|gray|green|light_purple|red|white|yellow
script:
- define colour:<context.args.get[1].to_lowercase>
- if <list[aqua|black|blue|dark_aqua|dark_blue|dark_gray|dark_green|dark_purple|dark_red|gold|gray|green|light_purple|red|white|yellow].contains[<[colour]>]>:
- narrate "<&a>Chose <&l><[colour]>"
- else:
- narrate "<&4>That colour is invalid. Try again."
- if <player.glowing>:
- glow false
- narrate "<&7>You are no longer glowing!"
- else:
- glow true
- team name:glow.<[colour]> add:<player> color:<[colour].to_uppercase>
- narrate "<&7>You are now glowing!"
ok
Content of Server Log Paste #126460: Denizen Debug Logs From A Minecraft Server... pasted 2024/09/12 04:44:51 UTC-07:00, Paste length: 5926 characters across 59 lines, Content: Java Version: 21.0.4Up-time: 19s
oh
Hm?
wrong denizen build
should i update/change?
you can also update yeah
where would the dev build be
!update
Latest Denizen stable release builds are at https://ci.citizensnpcs.co/job/Denizen/. Most users should download the stable release build.
Latest Denizen dev builds are at https://ci.citizensnpcs.co/job/Denizen_Developmental/. Dev builds are for usually for test servers only.
Spigot resource page for Denizen is at https://www.spigotmc.org/resources/denizen.21039/ (do NOT download builds from Spigot).
Paper is a higher-performance alternative to Spigot that is 100% compatible with the equivalent Spigot version. It's much easier to update than Spigot itself, and carries a lot of performance and quality-of-life benefits.
Latest Paper builds are at https://papermc.io/downloads/paper.
(If you would prefer to use a Spigot build, refer to !update spigot).
If that's also not working try it again on a freshly made test server
Content of Server Log Paste #126461: Denizen Debug Logs From A Minecraft Server... pasted 2024/09/12 04:49:37 UTC-07:00, Paste length: 5865 characters across 59 lines, Content: Java Version: 21.0.4Up-time: 30s
Works perfectly on latest paper + denizen on my end
The client won't affect anything wouldn't it
it can yes
I'm on Lunar so I might just try vanilla launcher
Lemme see how updating works
Nope, gonna try the blank server
Works on a blank server
Now I am gonna have to go through the headache of finding which plugin is breaking stuff
😮💨
guess i could try from a dry run
this is just... 😞
oh
^ fixed
Actually looks like when I rejoin it causes the crashes
weird
Only fixes when I delete the teams
How do you create them
Using that command there
yeah
@outer vault did you fix this? or do you still need help
can’t do it because of scoreboard plug-in, thanks