Fluid Language Limitations

[PepperCode1]

Currently, the FluidBuilder does not allow assigning translation keys or names in some situations and is inconsistent in others.

• If a block does not exist and .lang with a translation key and name was called, the datagenned name will use the provided translation key but the fluid attributes will use the default generated translation key. I suggest that the provided translation key be used in the fluid attributes as well.
• If a block does exist, the .lang methods on the builder become useless because the fluid's translation key will be set to the block's translation key. I suggest that in this case the .lang calls should proxy to the underlying BlockBuilder's methods or allow setting a different translation key and name than the block.
• There is no way to make the still fluid and the flowing fluid have different translation keys or names.