You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**LWC Version (/lwc admin version):2.2.7-ad0f824
**Server version (/version):1.16.5
Short five word summary of issue:
Some special mod item ID names are not supported
Detailed description of problem:
When adding mod container protection, some mod IDs are special, such as fashion workshops, whose IDs are as follows:
armourers_ workshop_ colour-mixer
armourers_ workshop_ dye-table
Such containers cannot be added to LWC protection.
2.When the ID name of mod is too long, it seems that the automatic locking will not take effect (it will prompt that the container has been automatically locked, but the container cannot be protected. I need to manually enter the / lock command to make the protection take effect)
The reason for this conclusion is that there is a container ID in variedcomponents mod that is particularly long. Only this one has a problem
ID of automatic locking without protection effect:
variedcommodities_ weapon_ rack_ dark_ oak
Automatic locking normal ID:
variedcommodities_ pedestal_ stone
I found that if there are four "_" (five words) may trigger the bug described above
If there was an error in console, put it here:
<paste it here between the little tick marks>
The text was updated successfully, but these errors were encountered:
luoxiawuchen
changed the title
[BUG] Some special mod item ID names are not supported
[BUG] Some special mod ID names are not supported
Aug 7, 2022
**LWC Version (/lwc admin version):2.2.7-ad0f824
**Server version (/version):1.16.5
Short five word summary of issue:
Some special mod item ID names are not supported
Detailed description of problem:
armourers_ workshop_ colour-mixer
armourers_ workshop_ dye-table
Such containers cannot be added to LWC protection.
2.When the ID name of mod is too long, it seems that the automatic locking will not take effect (it will prompt that the container has been automatically locked, but the container cannot be protected. I need to manually enter the / lock command to make the protection take effect)
The reason for this conclusion is that there is a container ID in variedcomponents mod that is particularly long. Only this one has a problem
ID of automatic locking without protection effect:
variedcommodities_ weapon_ rack_ dark_ oak
Automatic locking normal ID:
variedcommodities_ pedestal_ stone
I found that if there are four "_" (five words) may trigger the bug described above
If there was an error in console, put it here:
The text was updated successfully, but these errors were encountered: