This tutorial is set by the author to use the CC by-NC protocol.

The first time the newcomer tries to write a tutorial, there may be incomplete places. Please contain a lot ~

(Puppets, bamboo light, silver paper, and white sheath are still registered items, which can be used directly, so it will not be explained)

The NBT format of the item of the sword is different from the previous. The original reference cannot be completely corresponding, so this tutorial is compiled.

Let's talk about the method first: As always, NBT editing must be performed on task items. The specific operation is as follows

After selecting items, cut the content contained in the Bladestate item, just retain the TranSlationKey, Specialeffects, Modelname, SpeciaLattackType, TextureName, and then set the NBT to True. True, soCan be distinguished normally.

The following is a detailed analysis of why you change this way

Here is an example of the "dead stone knife" as an example to explain the data structure, because the mechanism of the knife is more comprehensive:

(Because the original NBT data is displayed with a long screenshot)

Figure 1 is the body that is directly taken out. Figure 2 is the item after use, which can be viewed.Note that there are two labels: Bladestate and enchanting data Enchantments, which need to be edited in Bladestate.Blue is the recommended part that is recommended, and red is the part that must be deleted.

Since the example is directly selected by the original item, only the red part can be deleted.However, considering that a variety of custom knives and accessories will also add other content, it is still recommended to retain the blue part.

The specific analysis is as follows:

It is recommended to keep it, this part allows the knife to present a normal item style in the task

TranslationKey item translation data

Specialeffects passive special effects, such as the "withered" of the sample knife

Modelname

Object model

SpeciaLattackType special attack, that is, SA

TextureName item sticker

Must be deleted, every knife is different in this part

LastACTINTIME

The time when this knife was used last time, it was 0 if it was not used before

Currentcombo

This knife currently uses the movement of the continuous section

(But because the NBT update is sometimes changed in time, it is not timely.

Will record it as the last use of the last time)

Bladeuniqueid

The unique ID of this knife is different in each knife

(In the example, because they are the same because they are created)

ProudSoul, Killcount's soul number, killing number, will grow naturally with the sword

maxDamage, RepairCounter

The upper limit and the number of reinforcements will be strengthened naturally with the sword

Targetentity, FALLDECREASERATE use automatically generated data

Although the rest of the content (such as the phantom sword style SummonDswordColor, the model location correction Adjustxyz, etc.), although it does not affect the matching, it is not helpful in the task display.

Supplement: a little detail correction in actual use

Sometimes, even if the NBT data is changed according to the above steps, it is still not possible to identify items well. After the test, it is found that this is likely to be caused by enchanting data.

As we all know, there are many enchantment available to swords, integrating armor, swords, and bows. A knife can still reach ten without adding other enchanting modules. This may cause the FTB task to run normally when matching the matching matchingAs a result, the task was delayed.

It is not difficult to solve this problem technically. Delete the enchanting data of the task items, but this will cause the items icons in the task to be a bit "boring":

So replace the icon of its own icon with a custom task item icon:

In this way, you can get a more perfect match.