#Minecraft Texture pack config file json help

1 messages · Page 1 of 1 (latest)

jade slate
#

I am trying to make a texture pack that enables nametags of invisible players just like how the normal nametags would be, but I ran into a roadblock. I have a json code but when i put it in models>entity>player.json it does nkt work. I have tried everything. Please take 5 minutes and help me.

dense spearBOT
#

<@&987246652869971988> please have a look, thanks.

dense spearBOT
#

While you are waiting for getting help, here are some tips to improve your experience:

Code is much easier to read if posted with syntax highlighting and proper formatting.

If nobody is calling back, that usually means that your question was not well asked and hence nobody feels confident enough answering. Try to use your time to elaborate, provide details, context, more code, examples and maybe some screenshots. With enough info, someone knows the answer for sure.

Don't forget to close your thread using the command </help-thread close:1027500463647621170> when your question has been answered, thanks.

jade slate
#
{
    "parent": "minecraft:entity",
    "components": {
      "minecraft:display_name": {
        "text": "Player",
        "color": "white"
      },
      "minecraft:nametag_visibility": "always"
    }
  }
dense spearBOT
jade slate
#

please someone respond...

static flame
#

It seems that the JSON code you provided is for modifying the name tag of a player entity, rather than modifying the texture pack to show name tags of invisible players. If you want to modify the texture pack to show name tags of invisible players, you will need to modify the rendering of the player entity itself.

To do this, you will need to create a new JSON file in the models/entity directory of your texture pack, which specifies the model for the player entity. You can call this file invisible_player.json, for example.

In this new JSON file, you can define the model for the invisible player entity, and also specify that the name tag should always be visible, even when the player is invisible. Here is an example of what your invisible_player.json file might look like:

#

{
"parent": "entity/player",
"textures": {
"layer0": "entity/player"
},
"overrides": [
{
"predicate": {
"invisible": 1
},
"model": "entity/player",
"custom": {
"minecraft:display_name": {
"text": "Player",
"color": "white"
},
"minecraft:nametag_visibility": "always"
}
}
]
}

#

In this example, we are using the parent model entity/player, which is the default model for the player entity. We then define an overrides array, which specifies how the model should be modified in certain situations. In this case, we are specifying that if the player entity is invisible ("invisible": 1), the model should be replaced with the default player model, but with a modified display name and always-visible name tag.

#

Once you have created this new JSON file, you will need to make sure it is referenced correctly in the models/entity/player.json file. You can do this by adding the following line to the overrides array:

#

{
"predicate": {
"invisible": 1
},
"model": "your_texture_pack:entity/invisible_player"
}

#

This tells Minecraft to use your new invisible_player.json model when rendering invisible player entities.

jade slate
#

yeah i already looked at chatgpt thanks

#

please give me an actual response

peak zodiac
jade slate
#

please can you help me

#

btw the pack would need to work in 1.8

peak zodiac
jade slate
#

i just tried what the guy said

#

it still didnt work

thorny lichen
#

AFAIK you can’t even change what you want in a java resource pack. So you’ll have to wait if someone else knows

#

Like I don’t think you can change the player model like that in a resource pack

jade slate
#

you can

#

ive seen someone do it

#

but they are a

#

they are annoying and wont gifve me it

thorny lichen
#

Are you sure it’s not with a mod

jade slate
#

nope

#

cant find anything on it onlne

#

it shoiuld be possible its just nametags

dense spearBOT
#

Closed the thread due to inactivity.

If your question was not resolved yet, feel free to just post a message to reopen it, or create a new thread. But try to improve the quality of your question to make it easier to help you 👍

jade slate
#

a