We are releasing two new full updates and one patch update. These updates will fix some bugs that were present, including the sound bug for 1.7.10 branch of MCreators. One of the reasons for these updates is also the upcoming big website update. More in the article!
MCreator 1.7.5 patch update
The first important update is the so-called 20. 8. 2017 patch update of MCreator 1.7.5. MCreator 1.7.5 had some problematic bugs that had to be fixed. The recommended version of Minecraft Forge has also changed, so we have decided to release patch update of MCreator 1.7.5. As this update was not big enough to be worth to force all users to update, we have decided to make it a patch update, so all the users that want to have these bugs fixed, they need to redownload and reinstall MCreator 1.7.5.
This patch update fixed the armor textures bug, some events not working properly, it also tries to fix rendering glitches on some Nvidia graphic cards and includes some other minor fixes.
MCreator 1.7.4 for Minecraft 1.10.2
With MCreator 1.7.4 update, we have upgraded Minecraft Forge to the recommended version 2185 for Minecraft 1.10.2 so all your mods will be 100% compatible with the right Forge version. This update also includes the render bug fix. Users have to update their old MCreator for Minecraft 1.10.2 as this update includes some mandatory fixes and improvements that will make sure that MCreator will also work with our new website when it will be released.
MCreator 1.7.3 for Minecraft 1.7.10
The most important fix in this update is the sound system. Finally it works as it should in both test environment and in exported mods. The update also includes rendering bug fix. This version is also a must for updating if you make mods for Minecraft 1.7.10, as this update makes sure that MCreator will still work when we release our new website.
Upcoming website update
Last but not least, I will speak some words about the rumored website update, also known as "Big website update". We are working on this update in the few past months. The update will add some important changes, that will make the experiance of the use of the MCreator's website as good as never before. Many really good changes will be made, so stay tuned as we will disclose some of the changes that are planned in the upcoming articles.
Changes in MCreator 20. 8. 2017 patch of 1.7.5:
- Updated supported Minecraft Forge MDK to recommended version 2386 for Minecraft 1.11.2
- [Bugfix] Armor textures for inventory not working
- [Bugfix] "When right clicked on block" event in item creation not working
- [Bugfix] Disabled hardware acceleration of 2D UI components to increase performance and to fix some render glitches on Nvidia graphic cards
All changes in MCreator 1.7.4 update:
- Updated supported Minecraft Forge MDK to recommended version 2185 for Minecraft 1.10.2
- [Bugfix] Disabled hardware acceleration of 2D UI components to increase performance and to fix some render glitches on Nvidia graphic cards
All changes in MCreator 1.7.3 update:
- [Bugfix] Fixed bug with custom sounds not working - now custom OGG sounds work in both test environment and in exported mods
- [Bugfix] Disabled hardware acceleration of 2D UI components to increase performance and to fix some render glitches on Nvidia graphic cards
Don't forget to leave your feedback on these updates in the comments, and stay tuned for more information on the MCreator for Minecraft 1.12.1 update and on the big website update - we will leak some info in the near future ;)
Comments
@#18.3 Just put in the block class. (To be more exact, the inner class in code of the block element, that extends Block, or some of its child). The @Override annotation is quite recommended to use but is not necessary. In case that everything is all right, the Java compiler should be able to override a method without it , however, if you use it, it will tell if you made some misspell in the methods name (simply: If there is no method with the name and parameters to override, it will result in compile error, and that can really save some time)
The reason of this behavior is quite simple. The code, that actually checks if the player (or to be more exact players colliding box) is in blocks, that are marked as "full blocks" (most of blocks, like stone, dirt, etc..), and moves the player to a safe position. And because if the block is "full block" is determined by boolean with name isFullCube, and the default value of this boolean is true and MCreator doesn't override it, it simply acts like it was any full blocks.
Simply this will work:
public boolean isFullCube(IBlockState state) {
return false;
}