Tag Doesn't Work in 1.20.1 And Later Versions.

[KnightMithridatis]

For some reason, I cannot assign tags to blocks in version 1.20.1. So I tried all kinds of commands. For example, I set a tag to put 10 coals in the furnace. Unfortunately it didn't spawn.

[KnightMithridatis]

The problem is definitely related to the Lost Cities mod. Maybe the Lost Cities tag code may be incompatible with version +1.20.

[KnightMithridatis]

Because in version 1.18.2, I can assign tags to blocks without any problems.

[McJty]

You cannot assign tags to blocks within an array like you're trying to do. i.e. if you have a palette entry with multiple possible blocks then those blocks cannot have tags. That's simply not supported

[KnightMithridatis]

You cannot assign tags to blocks within an array like you're trying to do. i.e. if you have a palette entry with multiple possible blocks then those blocks cannot have tags. That's simply not supported

So, is there another way to add tags in 1.20.1 Lost Cities mod? Because it worked in 1.18.2. I can't even put coal in furnace anymore in 1.20.1. It's a bit absurd.

[McJty]

No, this didn't work in 1.18.2 either. This hasn't changed. Lost Cities has never been able to assign tags to blocks that are part of a single character block array. You can assign tags to blocks that are independent of course. Both in 1.18 and 1.20. But not to blocks in a randomizer

[KnightMithridatis]

No, this didn't work in 1.18.2 either. This hasn't changed. Lost Cities has never been able to assign tags to blocks that are part of a single character block array. You can assign tags to blocks that are independent of course. Both in 1.18 and 1.20. But not to blocks in a randomizer

It works on Lost Cities version 1.18.2. I'm making highways with TrafficCraft. I need to adjust the color of the blocks with tags. As evidence I can offer this:

[McJty]

You don't understand. That's different. There you are using the tag on a block that has no variations. That character is always assigned to that block. And then tags work. You cannot use tags on blocks that have variations. i..e multiple possible blocks for the same palette entry

[KnightMithridatis]

You don't understand. That's different. There you are using the tag on a block that has no variations. That character is always assigned to that block. And then tags work. You cannot use tags on blocks that have variations. i..e multiple possible blocks for the same palette entry

So I understand you won't help.

[McJty]

What? I'm trying to help. I'm explaining what's going on. Tags work on standalone blocks. They don't work on randomized blocks. That was also like that in 1.18. That code literally hasn't changed

[McJty]

We have just confirmed that tags on a standalone block still work. Like the ";" that is defined in default.json from Lost Cities itself

[KnightMithridatis]

We have just confirmed that tags on a standalone block still work. Like the ";" that is defined in default.json from Lost Cities itself

So can you give me a code example?

[KnightMithridatis]

We have just confirmed that tags on a standalone block still work. Like the ";" that is defined in default.json from Lost Cities itself

We have just confirmed that tags on a standalone block still work. Like the ";" that is defined in default.json from Lost Cities itself

{
"char": ";",
"block": "minecraft:furnace",
"damaged": "minecraft:iron_bars",
"tag": {
"Items": [
{
"Slot": 0,
"id": "minecraft:coal",
"Count": 10
}
]
}
},

I assigned this to the code in default.json, but it still didn't work.

[McJty]

That entry is by defaulit already present in default.json (from Lost Cities). Not sure why it isn't working for you though

[KnightMithridatis]

That entry is by defaulit already present in default.json (from Lost Cities). Not sure why it isn't working for you though

I did it via kubejs. But kubejs works.

[McJty]

Can you show me your datapack where you are trying to do this?

[KnightMithridatis]

Can you show me your datapack where you are trying to do this?

I'm trying another way. If it doesn't work, I'll write.

[KnightMithridatis]

Can you show me your datapack where you are trying to do this?

I placed a separate generic block in default.json. It worked. Now I will try it for trafficcraft blocks.

[KnightMithridatis]

Can you show me your datapack where you are trying to do this?

Unfortunately, whatever you did to the code in Lost Cities version 1.20-7.3.5. I can't tag the trafficcraft asphalt pattern block. However, I can assign tags in Lost Cities version 1.20-7.1.8. I share the pictures below, one by one.

[KnightMithridatis]

In short, the problem isn't related to TrafficCraft. There is a problem with Lost Cities version 7.3.5.

[McJty]

Well I can't reproduce the problem with the latest version. I would still like to see your datapack

[KnightMithridatis]

Well I can't reproduce the problem with the latest version. I would still like to see your datapack

So how can I get the datapack? What exactly do you want? I think you want the kubejs\data\lostcities folder.

[McJty]

Well it's your datapack. So I assume you know how to get it? It's me that need to get it from you :-)

[KnightMithridatis]

Well it's your datapack. So I assume you know how to get it? It's me that need to get it from you :-)

I'll send you the .jar files of the mods I used. I will also send the kubejs\data\lostcities folder. Because I've never had anything to do with datapack. You can test it yourself by creating a world. You can find trafficcraft blocks in buildings. Test it first with 7.1.8 and then with 7.3.5.

Mods for 1.20.1 forge.zip
kubejs.zip