Well the time has come to get a few more crashes out of the way. We had a major server crash that some how managed to slip through testing on our end, along with a client side crash with tukMC is also installed and you looked at one of our quarter, elbow or mini logs due to tukMC trying to render an a block with invalid metadata.
We also started updating some of the block “names” that minecraft/forge stores in maps in preparation for upgrading to 1.7. This will cause MC to complain that blocks have changed but is just MC/forge letting you know that we updated stuff on our end so that once the fully get rid of external id’s you won’t have to type something like “extrabiomes.block.BlockCustomFlower:extrabiomes.block.BlockCustomFlower” and instead be able to do something more along the lines of “extrabiomesxl:flower1”, much easier on the keyboard ehh?
Oh and we back-ported the new localization and smart tool tip code so that flowers and such can now have their tool tips localized. If anyone has any suggestions for flavor text for any of the flowers that don’t have descriptions feel free to chime on in, although Annysia would probably prefer that you do it over on the official forums thread where you gets notifications about such any posts.
Change Log
Bug fixes:
- Fixed crash with tukMC and any other mod that creates fake items for render resulting in invalid metadata in the item form for Mini, Quarter and Elbow logs.
- Fix server crash from missed placed SideOnly in BlockCustomFlower.
Changes:
- Tool tips for flowers are now localized, and will automatically wrap text so that it does not need to manually be formatted as such in the localization.
- Flower names localization has changed for easier translation in the future. No more extrabiomes.flower.0, as the localization string now says the flower name. This breaks most existing translation, but will be better in the long run.
- Some blocks had their internal “keys” changed in preparation for updating to 1.7, this will result in MC saying that some blocks have changed but it is not an issue as it will not break anything in 1.6.
??1.7.2 version??
Yeah we have our 1.7.2 version in development and hope to have it working well enough to get in the hands of testers in the next week or two.