That last line is for all things that use a freeform. All fences and anything in the building menu
From Jay: Good for you (Fern) on remembering the name "Long Life Fence". Previously you mentioned "Unbreakable Fence", which is why I couldn't find it.
As for other comments... We should never intentionally use a currently unused ID. Even if an ID is unused now, it may not be in the future. It is also safer to have a valid ID instead of intentionally picking an invalid ID number. We have seen cases for other things where an invalid number confused ZT, making it have problems.
Yes, 7-zip can look inside ".dll" files. But that also depends on what program 7-zip is set to use for "View". There are 2 programs I use to look inside ".dll" files. One is called Resource Hacker. It is free, but not open source. Most people in the ZT community use that because it was available even before ZT was created. Its web site is:
http://www.angusj.com/resourcehacker
The other is RisohEditor. It is free and open source. Its web site is:
https://katahiromz.web.fc2.com/re/en/
As fern mentioned, you should not create a ".dll" only for your things. ZT has a limit of how many ".dll" files there can be. In the early days of people making things for ZT, each person made their own ".dll" and we quickly hit ZT's limit. So ever since then, we use ".dll" files "for sites". LANG--ZTCDD.dll and LANG--ZKL.dll are actually for multiple sites. If messages are likely to be used for more things in the future, LANG--ZTCDD.dll is the best place for them, since that ".dll" is meant to be for the entire ZT Community.
Technically cNameID and cHelpID do not have to match. But it gets confusing when they do not, because ZT does not use the cHelpID setting directly. It first tries to add 30000 to it and tries to find that ID.
Exhibit fences and decorative fences can use the same cNameID settings and cHelpID settings, as long as both messages make sense for both fences. For my cliff walls, the exhibit fences and decorative fences use the same IDs.
Yes, it is preferred to use separate unlock files instead of combined unlock files. That is because separate ones allow reusing the same unlock file for things made in the future that use the same ID.