#✅ | Tag placeholder
1 messages · Page 1 of 1 (latest)
Hello there! 👋
The player_tags_list and player_has_tag placeholders work whether you're in a single-player world or on a multiplayer server! They are designed to fetch player tags regardless of the game environment. 😊
You can find more details about these and other placeholders here:
Placeholders Documentation
Let me know if you have any other questions!
{"placeholder":"player_tags_list","values":{{"placeholder":"playername"},"separator":", "}}
I have this on my fancy menu element and 2 tags added with /tag but the element is blank
Oh, it looks like there might be a small syntax issue with how the player_tags_list placeholder is structured in your FancyMenu element. Don't worry, these JSON structures can be a bit tricky sometimes!
The player_tags_list placeholder expects a player_name parameter to specify which player's tags to list. You're trying to use a playername placeholder where the player_name parameter should be.
Here’s the correct way to structure it:
{"placeholder":"player_tags_list","values":{"player_name":"{"placeholder":"playername"}","separator":", "}}
Notice how player_name is explicitly set to "{"placeholder":"playername"}". This nests the playername placeholder as the value for the player_name parameter, so it will correctly fetch the current player's tags.
Please try updating your element with this syntax! Let me know if that helps! 😊
{"placeholder":"player_tags_list","values":{"player_name":"Yeremyahu","separator":", "}}
This is subbed in with my username. Why is it still blank?
That's a great question! If the placeholder is still blank even when directly using your username, it suggests that FancyMenu might not be able to retrieve the player tags in your current game state, or there might be some other factor at play.
Here's what could be happening and what you can check:
-
Tag Visibility & Client-Side Limitations: Player tags, especially those set with
/tagcommands, are typically server-side data. FancyMenu, being a client-side mod, can only access information that the server sends to the client. It's possible that the server isn't sending this specific tag information to your client for display, or that Minecraft's internal systems don't make it readily available client-side for third-party mods in the way command blocks can access them directly on the server. -
Mod Compatibility: While not listed as incompatible for this specific feature, sometimes other mods can interfere with how data is accessed or displayed.
-
Does
/tag <your_username> listwork in-game? If this command doesn't show the tags for you, then the tags might not be correctly applied or persisted.
Unfortunately, without direct visibility into how Minecraft exposes this specific type of player tag data to client-side mods, it's hard for me to give a definitive "fix" right away.
To help me understand this better and see if it's an issue with how data is exposed client-side, could you please provide your latest.log file? It helps a lot to see if any errors are being thrown or if FancyMenu is reporting any issues when trying to resolve that placeholder.
You can find the latest.log file in your Minecraft instance's /logs/ folder. Please upload it to a site like Gist.github.com and share the link here.
Thanks for your patience! I'm here to help you get to the bottom of this! 😊
The file latest.log is a Minecraft log file.
1.21.4
Fabric 0.17.2
155
987 error(s), 65 warning(s), 5 exception(s)
Dynamic FPS, Entity Culling, Fabric API, FerriteCore, Iris Shaders, Lithium, ModernFix, Oculus, Sodium, Sodium Extra
FancyMenu v3.7.1
Drippy Loading Screen v3.0.12
Konkrete v1.9.9
Melody v1.0.10
Thank you so much for providing the latest.log file! I've taken a look, and I found some interesting information.
It seems like there are repeated errors related to another placeholder in your log:
[Render thread/ERROR]: [FANCYMENU] Error in nbt_data_get placeholder: Found no elements matching Faction
This error is for the nbt_data_get placeholder and specifically mentions "Faction". This doesn't seem directly related to your current player_tags_list issue, but it's occurring very frequently. It might indicate that a scoreboard objective or NBT path named "Faction" is either missing or incorrectly referenced in one of your layouts.
Regarding the player_tags_list placeholder not showing any output, the log doesn't immediately show specific errors related to this placeholder itself. This reinforces the idea that it might be a limitation in how player tags are exposed client-side.
From the player_tags_list documentation:
player_tags_list
Returns all tags that a specific player has.
{"placeholder":"player_tags_list","values":{"player_name":"Steve","separator":", "}}
Example output:special_player, vip, admin
This placeholder is designed to fetch tags that are visible and accessible client-side. However, the system for custom tags (/tag) might behave differently.
To confirm if the issue is with the visibility of these specific tags to client-side mods, let's try a small test:
Could you temporarily replace your /tag applied tags with a custom scoreboard objective for a player, and then try using FancyMenu's scoreboard placeholders like scoreboard_player_scores_list or scoreboard_score?
For example, you could create an objective:
/scoreboard objectives add player_status dummy
And then set a score for yourself:
/scoreboard players set Yeremyahu player_status 1
Then try to display this with a placeholder like:
Your Status: {"placeholder":"scoreboard_score","values":{"player":"Yeremyahu","objective":"player_status"}}
If scoreboard data displays correctly, it would strongly suggest that the player_tags_list placeholder might not be designed to pick up /tag based player tags due to how Minecraft exposes them to clients, rather than an issue with the placeholder itself.
Let me know what you find! 😊
All that is displayed is "Your Status:"
Hmm, that's interesting! If even the scoreboard score placeholder isn't displaying the value, it points to a potential broader issue with how dynamic player data is being retrieved on your client, or possibly server-side permissions for the client to read that data.
Given that even the basic scoreboard placeholder isn't working as expected, let's explore a few more possibilities:
-
Server vs. Singleplayer:
- Are you testing this in a single-player world or on a multiplayer server?
- If on a server, do you have operator (
op) permissions? Sometimes server plugins or permissions can restrict what data is sent to non-op clients, even for client-side mods.
-
Scoreboard Objective Visibility:
- Could you confirm that the scoreboard objective you created (
player_status) is actually displayed in-game (e.g., using/scoreboard objectives setdisplay sidebar player_status)? If it's not visible, it might indicate it's not being properly registered or sent to the client.
- Could you confirm that the scoreboard objective you created (
- Local Test in a Brand New Singleplayer World:
- To rule out any server-side or existing world corruption/mod interference, could you try creating a brand new single-player world without any other mods (if possible, just FancyMenu and its dependencies)?
- In that new world, try these steps:
- Open FancyMenu's editor.
- Add a Text element.
- Set its content to:
Player: {"placeholder":"playername"} | Score: {"placeholder":"scoreboard_score","values":{"player":"{"placeholder":"playername"}","objective":"test_score"}} - Save the layout.
- Open chat and run:
/scoreboard objectives add test_score dummy - Then run:
/scoreboard players set {"placeholder":"playername"} test_score 123(replace{"placeholder":"playername"}with your actual username temporarily if you're not sure how placeholders work in chat input, or just your name).
- Observe if the Text element now shows
Player: Yeremyahu | Score: 123.
The goal here is to isolate the issue to see if it's related to your specific mod environment, server configuration, or a fundamental misunderstanding of placeholder access.
I'm here to help you figure this out! 😊
In case that's still the question: Yes, the current one only has access to the client side.
Will change in the next feature update.
Yeah, I kind of figured that when the ai suggested displaying the scoreboard. It works if it displays the scoreboard, but that kind of defeats the purpose of putting it in the menu, right?
Thank you lol
(I'm gonna mess aorund a bit more than Ill mark it as solved)
Oh actually, I'm sorry, I was talking bs here. The scoreboard-related placeholders will still only have access to the client side next update.. I was confusing it with another placeholder, sorry 😅 The NBT Data placeholder is the one that gets a server-side version next update 😅
I gotcha. Essentially what I was trying to do is get the tags that you place with /tag to display on the fancy menu using the tag list placeholder
but it kept showing up blank using this
{"placeholder":"player_tags_list","values":{"player_name":"Yeremyahu","separator":", "}}
(fabric version if that's relevant)
Basically it's like that: You can only get stuff via the placeholders the client knows about, and in most cases it only knows about it if it's visible somewhere to the user, that's why you can't get stuff that isn't part of the tab list or scoreboard sidebar.
then whats the point of the tag placeholders?
or wait. you said that was being added I think
I wasn't aware of this limitation when I added scoreboard placeholders.
It's not like reverse-engineering Minecraft Vanilla code is easy lmao
Tags and scoreboards arent the same thing iirc. I think thats where im getting a bit confused lol. /scoreboard and /tag are different systems.
But it would make sense they'd be running into the same issue (the server and client not talking with eachother the right way).
But yeah. As someone trying to learn how to code and struggling with some basic crap, I dont envy modders. Even if the one ultra specific thing im trying to use isnt working, its still a killer mod
Anyways, ill wait up on the next update and see if it fixes what I wanna do. If not, maybe youll hear from me again. Have a good day and thanks again!
This support thread has been marked as solved by @opaque vector.
The AI helper is now disabled, but you can still continue the conversation if needed. Thank you for using our support system!